Re:Announcing the first SHA-1 collision
by ddlatham on Thursday February 23, 2017 @01:18PM
(#13716252)
You're missing something in your definition of a second-preimage attack, which is that Y != X.
[ Parent
| on HN ]
Re:Announcing the first SHA-1 collision
by Gankro on Thursday February 23, 2017 @01:25PM
(#13716324)
Ah good point. It could be that the first-preimage attack gets you exactly X, in which case it fails to handle second-preimage. I would expect this to be incredibly unlikely (especially since they seem to generally involve generating some random garbage). I would also expect most first-preimage attacks have a way to "continue" to a third value, eventually.
Re:Announcing the first SHA-1 collision
by shawabawa3 on Thursday February 23, 2017 @01:33PM
(#13716403)
That's kind of implicit.
If X = Y, it's not an attack, it's the primary purpose of hashing