<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/MU" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel>
	<title>Comments on: Require 128-bit Encryption for HTTPS Traffic with ISA Server 2006</title>
	<link>http://blogs.isaserver.org/pouseele/2007/03/18/require-128-bit-encryption-for-https-traffic-with-isa-server-2006/</link>
	<description>Stefaan Pouseele, an ISA Server MVP, discusses issues brought up within various ISA articles and Microsoft publications. Updates to the ISA Firewall, protocol support, discussions on the different ISA clients, ISA features, how to clean up network traffic and links to new ISA server literature are all be included within the blog. Get help on troubleshooting the ISA network firewall and learn how to create good security policies. Coverage on ISA Server 2006 also appears.</description>
	<pubDate>Sat, 22 Nov 2008 05:49:33 +0000</pubDate>
	<generator>http://wordpress.org/?v=MU</generator>

	<item>
		<title>by: Stefaan Pouseele Blog &#187; Blog Archive &#187; Require 128-bit Encryption for HTTPS Traffic with ISA Server 2006 (Part2)</title>
		<link>http://blogs.isaserver.org/pouseele/2007/03/18/require-128-bit-encryption-for-https-traffic-with-isa-server-2006/#comment-7391</link>
		<pubDate>Sun, 25 Mar 2007 17:39:56 +0000</pubDate>
		<guid>http://blogs.isaserver.org/pouseele/2007/03/18/require-128-bit-encryption-for-https-traffic-with-isa-server-2006/#comment-7391</guid>
					<description>[...] In my blog Require 128-bit Encryption for HTTPS Traffic with ISA Server 2006&amp;#160;I posted a workaround for enabling Redirect all traffic from HTTP to HTTPS *and* Require 128-bit encryption for HTTPS traffic in a web publishing rule. However, what does that setting Require 128-bit encryption for HTTPS traffic really means and&amp;#160;how does it work? [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] In my blog Require 128-bit Encryption for HTTPS Traffic with ISA Server 2006&nbsp;I posted a workaround for enabling Redirect all traffic from HTTP to HTTPS *and* Require 128-bit encryption for HTTPS traffic in a web publishing rule. However, what does that setting Require 128-bit encryption for HTTPS traffic really means and&nbsp;how does it work? [&#8230;]
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Thomas Shinder Blog &#187; Blog Archive &#187; Mystery of the &#34;Notify HTTP Users to use HTTPS instead&#34; Checkbox Solved!</title>
		<link>http://blogs.isaserver.org/pouseele/2007/03/18/require-128-bit-encryption-for-https-traffic-with-isa-server-2006/#comment-7268</link>
		<pubDate>Tue, 20 Mar 2007 14:44:55 +0000</pubDate>
		<guid>http://blogs.isaserver.org/pouseele/2007/03/18/require-128-bit-encryption-for-https-traffic-with-isa-server-2006/#comment-7268</guid>
					<description>[...] Read about Stefaan&amp;#8217;s solution at http://blogs.isaserver.org/pouseele/2007/03/18/req...-2006/ [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] Read about Stefaan&#8217;s solution at <a href='http://blogs.isaserver.org/pouseele/2007/03/18/req&#8230;-2006/' rel='nofollow'>http://blogs.isaserver.org/pouseele/2007/03/18/req...-2006/</a> [&#8230;]
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Tom Shinder</title>
		<link>http://blogs.isaserver.org/pouseele/2007/03/18/require-128-bit-encryption-for-https-traffic-with-isa-server-2006/#comment-7267</link>
		<pubDate>Tue, 20 Mar 2007 14:39:35 +0000</pubDate>
		<guid>http://blogs.isaserver.org/pouseele/2007/03/18/require-128-bit-encryption-for-https-traffic-with-isa-server-2006/#comment-7267</guid>
					<description>Excellent finding, Stefaan! I've been wondering about this problem myself for quite a while. I agree that it's a bug in the UI.
Thanks!
Tom</description>
		<content:encoded><![CDATA[<p>Excellent finding, Stefaan! I&#8217;ve been wondering about this problem myself for quite a while. I agree that it&#8217;s a bug in the UI.<br />
Thanks!<br />
Tom
</p>
]]></content:encoded>
				</item>
</channel>
</rss>
