Remember, this SHA1 attack is *not* the attack that broke MD5 TLS certs and gave us Flame. *This* attack on MD5 you can run on a smartphone.
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.
-
-
-
This SHA1 attack does NOT allow you to collide an innocent-looking file with a malicious file. You need TWO blatantly malicious files.
- Show replies
New conversation -
-
-
shouldn't git move to sha-3 instead of sha-2?
-
Only if you believe SHA-3 is more secure than SHA-2. That is... not certain :-)
- Show replies
New conversation -
-
-
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.
- Show replies
New conversation -
-
-
We're talking about having two valid PNG files with the same SHA-1 hash and a different image (or similar).
-
Today's collision attack requires that both files be A+X0+B and A+X1+B and you don't control X0 or X1.
- Show replies
New conversation -
-
-
They already thought about it in 2006: http://marc.info/?l=git&m=115678778717621&w=2 …
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
if I remember right, there is a gist where linus explains why sha1 collisions are "skippable" on git
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.