News for hackers. Stuff that matters.
Re:How To Safely Store A Password by Xk on Wednesday December 15, 2010 @12:53AM (#2007213)
Wrong. Collisions can be found in MD5 in 2^21 time due to an attack by Xie and Feng. 2^64 is a very respectable number and is not practical for people to do on their home machines. 2^21 is.
Re:How To Safely Store A Password by gxti on Wednesday December 15, 2010 @09:43AM (#2008225)
You are right, of course. I wrote that as 'ideal digest' instead of MD5 then rewrote it. Specific digests always lose a few bits in real life, or in MD5's case, most of the bits...
Re:How To Safely Store A Password by StavrosK on Wednesday December 15, 2010 @05:55AM (#2007689)
Plus you only need a collision to break into a system that uses hashed passwords, not a preimage.
Re:How To Safely Store A Password by gxti on Wednesday December 15, 2010 @09:48AM (#2008245)
Clarify? Collision attacks by definition do not feature an existing digest as input so they are not useful for breaking into a system secured with a digest.
Re:How To Safely Store A Password by StavrosK on Wednesday December 15, 2010 @11:27AM (#2008640)
Ah, I misunderstood. By "collision attack" you meant "find two plaintexts that hash to the same digest", I interpreted it as "find one plaintext that hashes to a specific digest", and "preimage attack" as "find the plaintext that was hashed to this digest".

Please disregard my comment above.

Re:How To Safely Store A Password by Xk on Wednesday December 15, 2010 @09:56AM (#2008272)
I guess he could mean that you could find a plaintext that had the same hash value through use of a collision ... but that's just finding a preimage.