Twitter | Search | |
Ąż杏👼 Feb 23
Replying to @jhripley @arw
Reply Retweet Like
Adam Couper Feb 23
Replying to @arw
Reply Retweet Like
cuneyt ozdas Feb 23
Replying to @arw
SHA-1 is dead!!!!! ;)
Reply Retweet Like
Morgan Jones Feb 25
Replying to @arw
Reply Retweet Like
FennecTECH Mar 7
Replying to @arw @shuffle2
two html documents with identical sha1sums?
Reply Retweet Like
Ąż杏👼 May 17
Replying to @_numinit @arw
dead link?
Reply Retweet Like
Morgan Jones May 18
Replying to @angealbertini @arw
should work now
Reply Retweet Like
MiKa Jul 28
Replying to @arw
Nice idea, testing for the first byte of the SHAttered collision block, no clean HTML though. Works only because browsers ignore garbage.
Reply Retweet Like
MiKa Jul 28
Replying to @arw
Neat, monkeys are unicode. Was searching for JFIFF header... Sneaky!
Reply Retweet Like
MiKa Jul 28
Replying to @_numinit @arw
You could have returned two colliding PDFs, if aligned on 512 bit boundaries SHA1 for HTML and PDFs would be the same. SHA1 inception :D
Reply Retweet Like
MiKa Jul 28
Replying to @_numinit @arw
Meant of course: SHA1 for the two HTMLs are same, and SHA1 for the two PDFs are same. HTMLs and PDFs will have different SHA1 of course.
Reply Retweet Like