News for hackers. Stuff that matters.
Re:Single-block collision for MD5 by Confusion on Sunday January 29, 2012 @03:36PM (#3526171)

  However, you will have to try real hard to do so.
This is coming back up again, because it's not so hard anymore.
Re:Single-block collision for MD5 by z92 on Sunday January 29, 2012 @09:17PM (#3527186)
The question I care is: Is the probability of naturally occurring a collision in MD5 hashing significantly more than any other 128 bit hashing algorithm?

The answer is: No.

Re:Single-block collision for MD5 by JoachimSchipper on Monday January 30, 2012 @03:42AM (#3527962)
Sure, but if you're willing to accept lots collisions on "bad" input there are faster hashes (Bernstein and Jenkins have nice fast non-cryptographic hashes, for instance.)

Non-cryptographic hash functions may be a bad idea: e.g. don't store URI parameters (?foo=bar&baz=bar) in such a hash table, or you'll be vulnerable to rather simple DoS (this was all over the internet a week or two ago.)

Re:Single-block collision for MD5 by jbapple on Wednesday February 01, 2012 @09:34AM (#3538055)
> Non-cryptographic hash functions may be a bad idea: e.g. don't store URI parameters (?foo=bar&baz=bar) in such a hash table, or you'll be vulnerable to rather simple DoS (this was all over the internet a week or two ago.)

I think universal hashing is the usual protection against that kind of attack, and I think universal hashing is not considered cryptographic:

http://www.cs.rice.edu/~scrosby/hash/CrosbyWallach_UsenixSec...

Re:Single-block collision for MD5 by maratd on Monday January 30, 2012 @08:11AM (#3528605)
> there are faster hashes

Yes, but none as widespread. MD5 is available in every system, on every language.