To avoid any confusion: I did *not* break SHA1 nor played any role in the cryptographic part of the new SHA1 collision...
-
-
Replying to @angealbertini
I crafted the collision prefix to guarantee that no matter what the collision blocks would be, we could obtain 2 valid (PDF) files...
5 replies 10 retweets 45 likes -
Replying to @angealbertini
1/ define prefix 2/ compute collision, based on the prefix (it's an identical prefix collision) 3/ append data to make them both validpic.twitter.com/z6U1c0PK47
3 replies 37 retweets 58 likes -
Replying to @angealbertini @marcan42
aha. not that they found a collision, it's that the compression function is so broken it's easy to find your own.
1 reply 0 retweets 0 likes
Replying to @OhMeadhbh @angealbertini
For $100k values of easy, yes. Not *completely* trivial but easy enough to be very broken :)
8:28 AM - 24 Feb 2017
0 replies
0 retweets
0 likes
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.