3 ms·
That isn’t really the case. Sha1 still isn’t broken in a particularly useful way. Md5 is still basically safe from pre-image attacks.
by kortilla 5y ago
That isn’t really the case. Sha1 still isn’t broken in a particularly useful way. Md5 is still basically safe from pre-image attacks.
- martinralbrecht 5y agohttps://shattered.io/ https://shattered.io/
- woodruffw 5y agoSHAttered is a collision attack on SHA-1, not a pre-image attack. There is no known pre-image attack for SHA-1.
- wizzwizz4 5y agoYet. We get closer every time a new vulnerability is discovered.
- woodruffw 5y ago> Yet. We get closer every time a new vulnerability is discovered. Skipjack is the famous counterexample to this: it's been broken up to 31 rounds, but specified usage mandates 32 rounds. Skipjack was given immense scrutiny due to the NSA's role in its design, and we're no closer to a full-round break of it than we were in 1999.
- saati 5y agoEven that is only theoretical, it's not a practical attack.
- anfilt 5y agoMD5 even still has pre-image resistance. A practical preimage attack would indicate something even more serious was overlooked with a design of a hash function. A practical attack would mean you could reverse the value of what produced the hash, by just using the hash. Only seriously lousy cryptographic hash functions would have bad preimage resistance. Heck even the pigeon hole principal makes this aspect of design easier for a hash function. If a wildy used hash function some how had a practical pre image attack i would be more concerned about our process of standardizing algorithms.
- sonograph 5y agoCollision attacks can still be useful in an attack tree
- maqp 5y agoThis is quite disingenuous, as with hash functions there's infinite preimages that map to each digest.
- kortilla 5y agoIt’s not at all. Understanding the differences between the types of hash image resistance is critical to know whether it matters for your application.