<?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 for Adventures of an Eternal Optimist</title>
	<atom:link href="http://eternallyoptimistic.com/comments/feed/" rel="self" type="application/rss+xml" />
	<link>http://eternallyoptimistic.com</link>
	<description></description>
	<lastBuildDate>Fri, 29 Jan 2010 22:51:53 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>Comment on Oracle Waveset by &#187; Soracle Waveset CQ2 &#124; Ed Murphy</title>
		<link>http://eternallyoptimistic.com/2010/01/29/oracle-waveset/comment-page-1/#comment-554</link>
		<dc:creator>&#187; Soracle Waveset CQ2 &#124; Ed Murphy</dc:creator>
		<pubDate>Fri, 29 Jan 2010 22:51:53 +0000</pubDate>
		<guid isPermaLink="false">http://eternallyoptimistic.com/?p=1492#comment-554</guid>
		<description>[...] Dingle from Ping Identity has an insightful post on the identity implications of the newly-approved Oracle acquisition of [...]</description>
		<content:encoded><![CDATA[<p>[...] Dingle from Ping Identity has an insightful post on the identity implications of the newly-approved Oracle acquisition of [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on New Gig! by Dave Kearns</title>
		<link>http://eternallyoptimistic.com/2009/11/24/new-gig/comment-page-1/#comment-550</link>
		<dc:creator>Dave Kearns</dc:creator>
		<pubDate>Wed, 25 Nov 2009 05:32:15 +0000</pubDate>
		<guid isPermaLink="false">http://eternallyoptimistic.com/?p=1418#comment-550</guid>
		<description>Does this mean leaving Calgary?</description>
		<content:encoded><![CDATA[<p>Does this mean leaving Calgary?</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on New Gig! by TerryG</title>
		<link>http://eternallyoptimistic.com/2009/11/24/new-gig/comment-page-1/#comment-549</link>
		<dc:creator>TerryG</dc:creator>
		<pubDate>Wed, 25 Nov 2009 04:45:19 +0000</pubDate>
		<guid isPermaLink="false">http://eternallyoptimistic.com/?p=1418#comment-549</guid>
		<description>Congratulations, Pam, sounds like a great opportunity.  Once you get settled we should talk, as both OpenID and now OAuth are likely in the (hopefully near) future.  

Does the new position imply a change of locale to Vancouver, Denver or Boston, or all three?  Or none of the above?  Keep in touch, and best regards...TCG</description>
		<content:encoded><![CDATA[<p>Congratulations, Pam, sounds like a great opportunity.  Once you get settled we should talk, as both OpenID and now OAuth are likely in the (hopefully near) future.  </p>
<p>Does the new position imply a change of locale to Vancouver, Denver or Boston, or all three?  Or none of the above?  Keep in touch, and best regards&#8230;TCG</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on New Gig! by stevenbender</title>
		<link>http://eternallyoptimistic.com/2009/11/24/new-gig/comment-page-1/#comment-547</link>
		<dc:creator>stevenbender</dc:creator>
		<pubDate>Tue, 24 Nov 2009 21:56:33 +0000</pubDate>
		<guid isPermaLink="false">http://eternallyoptimistic.com/?p=1418#comment-547</guid>
		<description>Congratulations Pam! 

I am so happy for you. These Pingers are smart and I am sure you will contribute greatly. 

Please send me your new contact details, and PHONE me so we can catch up.:)

As always wishing you the best, and grateful you are my friend.

Steven</description>
		<content:encoded><![CDATA[<p>Congratulations Pam! </p>
<p>I am so happy for you. These Pingers are smart and I am sure you will contribute greatly. </p>
<p>Please send me your new contact details, and PHONE me so we can catch up.:)</p>
<p>As always wishing you the best, and grateful you are my friend.</p>
<p>Steven</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Sears == Slimy by johndiii</title>
		<link>http://eternallyoptimistic.com/2009/09/24/sears-slimy/comment-page-1/#comment-544</link>
		<dc:creator>johndiii</dc:creator>
		<pubDate>Fri, 25 Sep 2009 23:43:50 +0000</pubDate>
		<guid isPermaLink="false">http://eternallyoptimistic.com/?p=1383#comment-544</guid>
		<description>Wow.  That&#039;s unbelievable.  I&#039;d be seriously angry at Sears.  Of course, it&#039;s not helpful that the FTC took over eighteen months to come to some kind of solution - the story apparently came out in early January 2008.  

There ought to be a place to go to find out which companies use questionable practices like these.  A net search is kind of hit or miss, depending on what one is looking for.  Try googling &quot;privacy practices&quot;.</description>
		<content:encoded><![CDATA[<p>Wow.  That&#8217;s unbelievable.  I&#8217;d be seriously angry at Sears.  Of course, it&#8217;s not helpful that the FTC took over eighteen months to come to some kind of solution &#8211; the story apparently came out in early January 2008.  </p>
<p>There ought to be a place to go to find out which companies use questionable practices like these.  A net search is kind of hit or miss, depending on what one is looking for.  Try googling &#8220;privacy practices&#8221;.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on DIY Security for the Utterly Paranoid by futureidentity</title>
		<link>http://eternallyoptimistic.com/2009/08/26/diy-security-for-the-utterly-paranoid/comment-page-1/#comment-543</link>
		<dc:creator>futureidentity</dc:creator>
		<pubDate>Fri, 25 Sep 2009 16:49:00 +0000</pubDate>
		<guid isPermaLink="false">http://eternallyoptimistic.com/?p=1348#comment-543</guid>
		<description>Absolutely agree. I have found it to be instructive (but scary) to ask IT security folks who manage authentication servers how the protection they give to password recovery questions stacks up against the protection they think appropriate to the passwords themselves.</description>
		<content:encoded><![CDATA[<p>Absolutely agree. I have found it to be instructive (but scary) to ask IT security folks who manage authentication servers how the protection they give to password recovery questions stacks up against the protection they think appropriate to the passwords themselves.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on So funny I forgot to laugh by Pamela</title>
		<link>http://eternallyoptimistic.com/2009/08/24/so-funny-i-forgot-to-laugh/comment-page-1/#comment-542</link>
		<dc:creator>Pamela</dc:creator>
		<pubDate>Sat, 19 Sep 2009 05:25:46 +0000</pubDate>
		<guid isPermaLink="false">http://eternallyoptimistic.com/?p=1317#comment-542</guid>
		<description>Great points - I suppose I think of a one-way hash as more of a bare minimum than &quot;the&quot; answer, but then considering that I called one-way hashes an industry best practice, perhaps I was setting the bar too low for banking best practices?</description>
		<content:encoded><![CDATA[<p>Great points &#8211; I suppose I think of a one-way hash as more of a bare minimum than &#8220;the&#8221; answer, but then considering that I called one-way hashes an industry best practice, perhaps I was setting the bar too low for banking best practices?</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on So funny I forgot to laugh by Raleigh</title>
		<link>http://eternallyoptimistic.com/2009/08/24/so-funny-i-forgot-to-laugh/comment-page-1/#comment-541</link>
		<dc:creator>Raleigh</dc:creator>
		<pubDate>Thu, 17 Sep 2009 06:05:14 +0000</pubDate>
		<guid isPermaLink="false">http://eternallyoptimistic.com/?p=1317#comment-541</guid>
		<description>You have raised some good points. Here are a few things to consider. Using one way hash is not a good way to store passwords for e-commerce applications because anyone having access to hashed passwords can easily do a dictionary attack. Hashing algorithms are fast by design and you can hash around a million words on decent CPU. Try openssl speed to see what I mean here. Even a salt would not protect against this attack because the salt has to be stored some where and attacker can get that.

A better way to protect passwords is to use FIPS 140-2 Level 3 or above devices which provide industrial strength encryption. The key never leaves the hardware crypto card and all crypto operations are performed inside the device. That&#039;s what most banks use.

Asking for random characters from your password does protect against key loggers. Seems like a good idea to me.</description>
		<content:encoded><![CDATA[<p>You have raised some good points. Here are a few things to consider. Using one way hash is not a good way to store passwords for e-commerce applications because anyone having access to hashed passwords can easily do a dictionary attack. Hashing algorithms are fast by design and you can hash around a million words on decent CPU. Try openssl speed to see what I mean here. Even a salt would not protect against this attack because the salt has to be stored some where and attacker can get that.</p>
<p>A better way to protect passwords is to use FIPS 140-2 Level 3 or above devices which provide industrial strength encryption. The key never leaves the hardware crypto card and all crypto operations are performed inside the device. That&#8217;s what most banks use.</p>
<p>Asking for random characters from your password does protect against key loggers. Seems like a good idea to me.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on So funny I forgot to laugh by Daily Digs &#8211; 09.15.2009 &#171; Security Stallions Blog</title>
		<link>http://eternallyoptimistic.com/2009/08/24/so-funny-i-forgot-to-laugh/comment-page-1/#comment-540</link>
		<dc:creator>Daily Digs &#8211; 09.15.2009 &#171; Security Stallions Blog</dc:creator>
		<pubDate>Wed, 16 Sep 2009 03:32:17 +0000</pubDate>
		<guid isPermaLink="false">http://eternallyoptimistic.com/?p=1317#comment-540</guid>
		<description>[...] This was one of the best / most disturbing banking related articles I&#8217;ve read in a while.  It&#8217;s also why you shouldn&#8217;t do most any online business with HSBC.  I hope HSBC just had a PCI audit done by a large firm so that particular QSA can head to the chopping block.  This one&#8217;s just downright &#8220;special&#8221; (and not really from today, but I ran across it in my feeds). [So Funny I Forgot To Laugh] [...]</description>
		<content:encoded><![CDATA[<p>[...] This was one of the best / most disturbing banking related articles I&#8217;ve read in a while.  It&#8217;s also why you shouldn&#8217;t do most any online business with HSBC.  I hope HSBC just had a PCI audit done by a large firm so that particular QSA can head to the chopping block.  This one&#8217;s just downright &#8220;special&#8221; (and not really from today, but I ran across it in my feeds). [So Funny I Forgot To Laugh] [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Second Class (Non) Citizens by ignisvulpis</title>
		<link>http://eternallyoptimistic.com/2009/09/06/second-class-non-citizens/comment-page-1/#comment-538</link>
		<dc:creator>ignisvulpis</dc:creator>
		<pubDate>Mon, 07 Sep 2009 13:52:00 +0000</pubDate>
		<guid isPermaLink="false">http://eternallyoptimistic.com/?p=1363#comment-538</guid>
		<description>Some time ago I made a fool out of myself by trying to share a video on a German video portal called Clipfish.de. I uploaded the video that I had created and notified friends where they could view it. Some potential viewers are from Canada and the US. But then messsages dropped in with complaints that they are not allowed to view my video because copyright reasons restrict the access to viewers in Germany. I felt so stupid :-/</description>
		<content:encoded><![CDATA[<p>Some time ago I made a fool out of myself by trying to share a video on a German video portal called Clipfish.de. I uploaded the video that I had created and notified friends where they could view it. Some potential viewers are from Canada and the US. But then messsages dropped in with complaints that they are not allowed to view my video because copyright reasons restrict the access to viewers in Germany. I felt so stupid :-/</p>
]]></content:encoded>
	</item>
</channel>
</rss>
