Finally a SHA-1 collision. TL;DR: same-prefix collision, don't panic *yet*, but Git better start thinking of SHA-256 and don't trust PDFs.
-
If you update the CRC you break the SHA1 collision. Doing both at the same time is hard.
I think given the mathematical properties of CRC it's actually impossible. If it were a true hash it'd be practical.
-
-
If it were a 32-bit hash you could construct a collision chain, but AFAIK, CRC(X) != CRC(Y) implies CRC(X+Z) != CRC(Y+Z)
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.