git/list[1] front-page[2] threads[3] people[4] search[5] about
 

[PATCH 0/2] doc hash-function-transition: minor & major clarifications

From
Ævar Arnfjörð Bjarmason <avarab@gmail.com>
Date
Mar 26, 2018, 18:27 UTC
Message-ID
<20180326182708.26551-1-avarab@gmail.com>

Having read through the hash-function-transition.txt again, a couple of things jumped out at me:

Ævar Arnfjörð Bjarmason (2):
  doc hash-function-transition: clarify how older gits die on NewHash

We weren't accurately describing how "git status" would die on NewHash repos on new versions.

  doc hash-function-transition: clarify what SHAttered means

I don't think we had a good summary of how SHA-1 vulnerabilities overlap with concerns Git has, now that we've moved to the hardened SHA-1.

I may very well have gotten this new summary subtly wrong though. So please review.

 .../technical/hash-function-transition.txt    | 40 +++++++++++++++----
 1 file changed, 32 insertions(+), 8 deletions(-)
-- 
2.16.2.804.g6dcf76e118
Next: Ævar Arnfjörð Bjarmason
Message 1 of 5 in “doc hash-function-transition: minor & major clarifications”
  1. 0/2 doc hash-function-transition: minor & major clarificationsÆvar Arnfjörð Bjarmason, Mar 26, 2018
  2. 1/2 doc hash-function-transition: clarify how older gits die on NewHashÆvar Arnfjörð Bjarmason, Mar 26, 2018
  3. 2/2 doc hash-function-transition: clarify what SHAttered meansÆvar Arnfjörð Bjarmason, Mar 26, 2018
  4. Eric SunshineMar 26, 2018
  5. Stefan BellerMar 26, 2018

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.