<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Redirect HTTP to SSL with IIS</title>
	<atom:link href="http://www.bohack.com/2008/12/redirect-http-to-ssl-with-iis/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.bohack.com/2008/12/redirect-http-to-ssl-with-iis/</link>
	<description>Check In and Tune Out!</description>
	<lastBuildDate>Fri, 28 May 2010 05:16:49 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=abc</generator>
	<item>
		<title>By: Bohack</title>
		<link>http://www.bohack.com/2008/12/redirect-http-to-ssl-with-iis/comment-page-1/#comment-80</link>
		<dc:creator>Bohack</dc:creator>
		<pubDate>Tue, 30 Dec 2008 15:06:06 +0000</pubDate>
		<guid isPermaLink="false">http://www.bohack.com/?p=141#comment-80</guid>
		<description>My personal recommendation is to check 128 bit encryption most all browsers today support 128 bit encryption. I think that with Internet Explorer 4.0 it became a standard feature and in Windows NT 4.0 Service Pack 4 it was in the standard service pack for the OS to support it. I can&#039;t remember it was too long ago either way it was almost 10 years ago, todays browsers can support 128 bit, the only motivation for not checking it is CPU power on the server.

 As for the strength of the key that has nothing to do with the strength of the encryption. The certificate has been signed with a 1024 bit signature for authentication purposes, that is only the first stage of SSL. During the IKE or Internet Key Exchange the browser and the server will use the key and the Diffe Helman algorithm to create a mutual SSL key and strength that is where that check box is relevant.</description>
		<content:encoded><![CDATA[<p>My personal recommendation is to check 128 bit encryption most all browsers today support 128 bit encryption. I think that with Internet Explorer 4.0 it became a standard feature and in Windows NT 4.0 Service Pack 4 it was in the standard service pack for the OS to support it. I can&#8217;t remember it was too long ago either way it was almost 10 years ago, todays browsers can support 128 bit, the only motivation for not checking it is CPU power on the server.</p>
<p> As for the strength of the key that has nothing to do with the strength of the encryption. The certificate has been signed with a 1024 bit signature for authentication purposes, that is only the first stage of SSL. During the IKE or Internet Key Exchange the browser and the server will use the key and the Diffe Helman algorithm to create a mutual SSL key and strength that is where that check box is relevant.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Andre Alexanian</title>
		<link>http://www.bohack.com/2008/12/redirect-http-to-ssl-with-iis/comment-page-1/#comment-79</link>
		<dc:creator>Andre Alexanian</dc:creator>
		<pubDate>Tue, 30 Dec 2008 08:23:20 +0000</pubDate>
		<guid isPermaLink="false">http://www.bohack.com/?p=141#comment-79</guid>
		<description>Thanks for your help.... this works great. One question, if my cert is 1024 bit, should I check the box to require 128 bit encryption?

Thanks

Andre Alexanian</description>
		<content:encoded><![CDATA[<p>Thanks for your help&#8230;. this works great. One question, if my cert is 1024 bit, should I check the box to require 128 bit encryption?</p>
<p>Thanks</p>
<p>Andre Alexanian</p>
]]></content:encoded>
	</item>
</channel>
</rss>
