<?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: So funny I forgot to laugh</title>
	<atom:link href="http://eternallyoptimistic.com/2009/08/24/so-funny-i-forgot-to-laugh/feed/" rel="self" type="application/rss+xml" />
	<link>http://eternallyoptimistic.com/2009/08/24/so-funny-i-forgot-to-laugh/</link>
	<description></description>
	<lastBuildDate>Wed, 21 Apr 2010 14:34:25 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>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>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>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>By: rbobel</title>
		<link>http://eternallyoptimistic.com/2009/08/24/so-funny-i-forgot-to-laugh/comment-page-1/#comment-537</link>
		<dc:creator>rbobel</dc:creator>
		<pubDate>Fri, 04 Sep 2009 19:58:38 +0000</pubDate>
		<guid isPermaLink="false">http://eternallyoptimistic.com/?p=1317#comment-537</guid>
		<description>I hate this kind of stupid stuff. Another peve of mine is week-ass password policies... I found a clasic in my own company http://www.bobbobel.com/the-number-one-reason-to-use-sso-password-policies/</description>
		<content:encoded><![CDATA[<p>I hate this kind of stupid stuff. Another peve of mine is week-ass password policies&#8230; I found a clasic in my own company <a href="http://www.bobbobel.com/the-number-one-reason-to-use-sso-password-policies/" rel="nofollow">http://www.bobbobel.com/the-number-one-reason-to-use-sso-password-policies/</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: johndiii</title>
		<link>http://eternallyoptimistic.com/2009/08/24/so-funny-i-forgot-to-laugh/comment-page-1/#comment-534</link>
		<dc:creator>johndiii</dc:creator>
		<pubDate>Mon, 24 Aug 2009 17:05:06 +0000</pubDate>
		<guid isPermaLink="false">http://eternallyoptimistic.com/?p=1317#comment-534</guid>
		<description>Wow.  How do you suppose something like this even gets deployed?  I know that HSBC is a fairly large bank, so do they have some guy in the back room doing their web site?  Highly unprofessional, and it speaks volumes about the organization itself.  I&#039;d be thinking about jumping ship, too.  What are the odds that your password is transmitted to some client-side script in clear to check those characters?  

I&#039;ve noticed that lists of security questions seem to be more common these days.  I&#039;m not sure why, because they actually lessen security, particularly if the questions are badly chosen (like the ones in this example).  My policy has been to give fake answers for things like mother&#039;s maiden name, elementary school attended, and so on.  With genealogy sites and classmates.com, this information is not that hard to find on the net.  Of course, that means that I have to write the answers down somewhere - but it seems a better idea than trusting the web sites.  

I&#039;d be very tempted to enter &quot;hacking bank web sites&quot; for my favorite hobby in this case. :-)</description>
		<content:encoded><![CDATA[<p>Wow.  How do you suppose something like this even gets deployed?  I know that HSBC is a fairly large bank, so do they have some guy in the back room doing their web site?  Highly unprofessional, and it speaks volumes about the organization itself.  I&#8217;d be thinking about jumping ship, too.  What are the odds that your password is transmitted to some client-side script in clear to check those characters?  </p>
<p>I&#8217;ve noticed that lists of security questions seem to be more common these days.  I&#8217;m not sure why, because they actually lessen security, particularly if the questions are badly chosen (like the ones in this example).  My policy has been to give fake answers for things like mother&#8217;s maiden name, elementary school attended, and so on.  With genealogy sites and classmates.com, this information is not that hard to find on the net.  Of course, that means that I have to write the answers down somewhere &#8211; but it seems a better idea than trusting the web sites.  </p>
<p>I&#8217;d be very tempted to enter &#8220;hacking bank web sites&#8221; for my favorite hobby in this case. :-)</p>
]]></content:encoded>
	</item>
</channel>
</rss>
