At this point...

Posted Jun 26, 2022 18:34 UTC (Sun) by jd (guest, #26381)
Parent article: Whatever happened to SHA-256 support in Git?

...Switch to SHA-3. It won't, apparently, slow adoption at all and, at least, will still be secure by the time everyone uses it.

At this point...

Posted Jun 27, 2022 8:56 UTC (Mon) by kilobyte (subscriber, #108024) [Link] (1 responses)

BLAKE3 instead? Much faster, an earlier version of it was a SHA-3 finalist, there's no risk the NSA picked an algorithm they know how to break (there were some irregularities during the competition), can be arbitrarily parallelized.

At this point...

Posted Feb 14, 2024 7:57 UTC (Wed) by JeffBai (guest, #103577) [Link]

(Very late reply, but!) https://git-scm.com/docs/hash-function-transition/ mentions that blake2sp-256 was a contender. I have no interest in looking through the big mail thread to find out what happened to it. Could be something about OpenMP.

Plan is to make it easy to transition.

Posted Jun 30, 2022 13:53 UTC (Thu) by gmatht (subscriber, #58961) [Link]

As jthill already mentioned, we can already do `git init --object-format=sha256`. The difficulty is making it easy to transition to a new hash. Once it is easy to transition to a new hash, there is less need to pick a future-proof hash, and in the meanwhile sha256 has more widespread hardware acceleration. See: https://stackoverflow.com/questions/60087759/git-is-movin...