News for hackers. Stuff that matters.
Re:When AES(☢) = ☠ – a crypto-binary trick by jimktrains2 on Tuesday May 20, 2014 @07:49AM (#7772052)
I guess I'm not following your logic. If there is a salted, hashed password in a db, allowing arbitrary length passwords shouldn't matter? HMACs and KDFs work very differently from symetric-crypto primatives.
Re:When AES(☢) = ☠ – a crypto-binary trick by michaelmior on Tuesday May 20, 2014 @08:13AM (#7772111)
The point is that it makes it easier for an attacker to find a hash collision. It's much easier to construct data which hashes to a given value if it can be of arbitrary length. I don't immediately see the connection with this article however.
Re:When AES(☢) = ☠ – a crypto-binary trick by asdfaoeu on Tuesday May 20, 2014 @08:34AM (#7772197)
I don't follow. Breaking a password hash your not trying to find a hash collision you need to break the preimage attack. Sure are some stage in the future there might be a preimage attack that requires a large amount of data to use. But really if your worried about theoretical preimage attack you aren't using md5.
Re:When AES(☢) = ☠ – a crypto-binary trick by tptacek on Tuesday May 20, 2014 @08:30AM (#7772185)
The attacker doesn't need a hash collision in the case you're describing; they need a preimage.