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.
-
-
Of course the real answer is to engineer hash forward-migration such that *future* migrations are easy.
-
Yeah this is key. But I doubt it will happen.
End of conversation
New conversation -
-
-
is it save to assume that SHA-256 is good enough for now?
-
We don't have any good reason to believe SHA-256 is insecure.
- Show replies
New conversation -
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.