This is how the SHA1 collision PDF format trick works (it's really an embedded JPEG format trick)pic.twitter.com/ogPuPegKL6
-
it's 16 bytes of pure randomness for easy distribution during the computation.
Interesting. Didn't know that part was relevant to the collision computation.
-
-
one last thing not visible in the poc: scan sizes optimization.
-
Yeah, I figured it takes a bit of finesse to get the JPEG data scans to optimally line up with comment lengths.
- Show replies
New conversation -
-
-
it's one of these crypto-binary negociations: give me X byte of free space... ok, then you set this bit to 0... ;)
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
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.