Re:6.5 Million LinkedIn Password Hashes Leaked
by jlgreco on Wednesday June 06, 2012 @09:13AM
(#4073578)
To be clear, MD5 (or SHA1 as these apparently are) is a problem. Passwords should be stored using a cryptographic hash function that is designed to hash passwords (read: be slow), not a generic cryptographic hash function (which are designed to be fast). This is exactly the problem that bcrypt was created to solve (among others).
[ Parent
| on HN ]
Re:6.5 Million LinkedIn Password Hashes Leaked
by jere on Wednesday June 06, 2012 @09:23AM
(#4073629)
I think people are missing the point that SHA2 is light years ahead of MD5. MD5 has had known security flaws for years.
>Do not use the MD5 algorithm Software developers, Certification Authorities, website owners, and users should avoid using the MD5 algorithm in any capacity.
http://www.kb.cert.org/vuls/id/836068
This is from over 3 years ago.
Re:6.5 Million LinkedIn Password Hashes Leaked
by tptacek on Wednesday June 06, 2012 @11:21AM
(#4074322)
The security differences between SHA2 and MD5 are irrelevant to the matter at hand. If they were MD5 hashes they'd be broken approximately as quickly and in exactly the same way.
Re:6.5 Million LinkedIn Password Hashes Leaked
by jlgreco on Wednesday June 06, 2012 @09:25AM
(#4073652)
The primary problem with using either as a password hash is their speed.
Re:6.5 Million LinkedIn Password Hashes Leaked
by jere on Wednesday June 06, 2012 @11:30AM
(#4074378)
I agree, but my point is that the "use bcrypt" drum has only been beating for a couple years to my knowledge: http://codahale.com/how-to-safely-store-a-password/
Wind the clock back 3-5 years and it's still stupid to use MD5. I could kind of understand some old code laying around that was less secure.
Re:6.5 Million LinkedIn Password Hashes Leaked
by veemjeem on Wednesday June 06, 2012 @09:51AM
(#4073793)
Still, it doesn't matter. As long as one can generate a rainbow table for the hash function, then password lookups will be a O(1) operation. The rainbow table for md5 is moderately small, sha1 is bigger, and I'm sure sha2 is even bigger than the sha1 table.