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.
-
-
Replying to @marcan42
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.
2 replies 10 retweets 10 likes -
Replying to @marcan42
This SHA1 attack does NOT allow you to collide an innocent-looking file with a malicious file. You need TWO blatantly malicious files.
2 replies 13 retweets 10 likes -
Replying to @marcan42
With anything Turing-complete you can probably pull off "subtly malicious". Branch on a bit in the colliding block.
2 replies 0 retweets 0 likes -
Replying to @dfranke
Yes of course, that's why executable binaries (or things like PDF) are the easy way to use this attack.
1 reply 0 retweets 0 likes -
But it's not really practical with source code because hopefully the evil branch would raise eyebrows.
1 reply 0 retweets 0 likes -
Replying to @marcan42
That would be an interesting theme for the Underhanded C Code Contest. Make the branch and the garbage block look innocuous.
2 replies 0 retweets 0 likes
Part of the problem is the garbage is binary. But yes, that's what I just said on IRC actually )
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.