<?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: Encrypting Only the Login Page</title>
	<atom:link href="http://monduke.com/2006/12/19/encrypting-only-the-login-page/feed/" rel="self" type="application/rss+xml" />
	<link>http://monduke.com/2006/12/19/encrypting-only-the-login-page/</link>
	<description>Covering J2EE Security and WebLogic Topics</description>
	<lastBuildDate>Tue, 13 Apr 2010 01:53:49 -0600</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Mike Fleming</title>
		<link>http://monduke.com/2006/12/19/encrypting-only-the-login-page/comment-page-1/#comment-13971</link>
		<dc:creator>Mike Fleming</dc:creator>
		<pubDate>Wed, 14 Jan 2009 02:34:38 +0000</pubDate>
		<guid isPermaLink="false">http://monduke.com/?p=38#comment-13971</guid>
		<description>Nicolas,

Thanks for the comment.

With regard to GMail, if you navigate to https://www.gmail.com it will stay in https. Perhaps the other two you mentioned will, too, although I have seen sites that won&#039;t.

I think the high bandwidth sites have more to &quot;lose&quot; given their high data volumes. You&#039;re right, there&#039;s no reason to encrypt Flickr pics but I assume Google wants to save the processing overhead due to resource utilization. They just happen to allow the privacy nuts like us to use SSL if we explicitly ask for it. Then again, maybe a privacy nut shouldn&#039;t be using a Google property in the first place! ;-)</description>
		<content:encoded><![CDATA[<p>Nicolas,</p>
<p>Thanks for the comment.</p>
<p>With regard to GMail, if you navigate to <a href="https://www.gmail.com" rel="nofollow">https://www.gmail.com</a> it will stay in https. Perhaps the other two you mentioned will, too, although I have seen sites that won&#8217;t.</p>
<p>I think the high bandwidth sites have more to &#8220;lose&#8221; given their high data volumes. You&#8217;re right, there&#8217;s no reason to encrypt Flickr pics but I assume Google wants to save the processing overhead due to resource utilization. They just happen to allow the privacy nuts like us to use SSL if we explicitly ask for it. Then again, maybe a privacy nut shouldn&#8217;t be using a Google property in the first place! <img src='http://monduke.com/wp-includes/images/smilies/icon_wink.gif' alt=';-)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Nicolas</title>
		<link>http://monduke.com/2006/12/19/encrypting-only-the-login-page/comment-page-1/#comment-13970</link>
		<dc:creator>Nicolas</dc:creator>
		<pubDate>Tue, 13 Jan 2009 14:23:55 +0000</pubDate>
		<guid isPermaLink="false">http://monduke.com/?p=38#comment-13970</guid>
		<description>Hi Mike,
great article here (again !)
Direct impact of what you show : 
as gmail / flickr / facebook fall into those categories of websites who encrypt only the username/pass, i&#039;d never use them from a hotspot...Simple?

Second thought, if all those sites use this crippled strategy, there must be a very good reason in terms of performance...
For flickr, it&#039;s pretty clear, if you start encrypting pics, you&#039;re dead, but gmail???

Cheers</description>
		<content:encoded><![CDATA[<p>Hi Mike,<br />
great article here (again !)<br />
Direct impact of what you show :<br />
as gmail / flickr / facebook fall into those categories of websites who encrypt only the username/pass, i&#8217;d never use them from a hotspot&#8230;Simple?</p>
<p>Second thought, if all those sites use this crippled strategy, there must be a very good reason in terms of performance&#8230;<br />
For flickr, it&#8217;s pretty clear, if you start encrypting pics, you&#8217;re dead, but gmail???</p>
<p>Cheers</p>
]]></content:encoded>
	</item>
</channel>
</rss>
