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.
-
Keccak/SHA-3 has actually been well-studied, see, e.g., http://eprint.iacr.org/2017/128 and refs therein
-
-
Basically I'm just saying the choice right now depends on factors other than security.
-
Of course the *real* lesson is to engineer in hash choice so you can switch if necessary.
End of conversation
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.