Re:Hash collisions and exploitations – Instant MD5 collision
by pxx on Wednesday September 21, 2022 @10:17AM
(#32925481)
This is not a feasible attack. There is a large difference between how academics use "broken" and what the practical consequences are.
As Schneier writes as an introduction in the very paragraph you are trying to quote, "in academic cryptography, the rules are relaxed considerably." This is not a snub on academia; colloquial terms sometimes just mean something different than the academic definition.
Re:Hash collisions and exploitations – Instant MD5 collision
by charcircuit on Tuesday September 20, 2022 @11:02PM
(#32920386)
That is "a" definition and that definition doesn't apply to the way the other commenter used broken.
Re:Hash collisions and exploitations – Instant MD5 collision
by dingosity on Wednesday September 21, 2022 @12:34AM
(#32920832)
That is the definition for hash functions. The other commenter was, not to put too fine a point on it, wrong. From Schneier's Self-Study Course in Block-Cipher Cryptanalysis:
"Breaking a cipher simply means finding a weakness in the cipher that can be exploited with a complexity less than brute-force."
But please go on about how you know more than Schneier.
Re:Hash collisions and exploitations – Instant MD5 collision
by prvit on Wednesday September 21, 2022 @07:55AM
(#32923742)
You're disregarding the context of those words.
Schneier is illustrating the gap between the academic and practical meanings of "broken".
https://link.springer.com/chapter/10.1007/978-3-642-01001-9_...