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

Re: Plan for SHA-256 repos to support SHA-1?

From
brian m. carlson <sandals@crustytoothpaste.net>
Date
Jun 26, 2022, 15:19 UTC
Message-ID
<Yrh47mun9U9t0HpO@tapette.crustytoothpaste.net>
In-Reply-To
<CAPc5daVtRZ-Str_yCqRXZKT5+KKcXdnptFaer27XneUwj76KjQ@mail.gmail.com>
On 2022-06-26 at 00:27:57, Junio C Hamano wrote:
Show 9 quoted lines
> On Sat, Jun 25, 2022 at 5:10 PM Eric W. Biederman <ebiederm@xmission.com> wrote:
> > Is there at this point a solid plan for how SHA-256 repos will support
> > access SHA-1 only clients?
> >
> > I remember reading a discussion of having a table somewhere that would
> > translate SHA-256 to SHA-1 when needed.
> 
> Documentation/technical/hash-function-transition.txt has flushed out
> the necessary details?

Yup. The design there sounds very simple and it is, conceptually, but practically implementing it is quite complex.

You can pull the in-progress work from transition-interop on my GitHub remote to see where some of the complexity lies.

-- 
brian m. carlson (he/him or they/them)
Toronto, Ontario, CA
Previous: Junio C HamanoNext: Jeff King
Message 20 of 21 in “SHA-256 transition”
  1. Stephen SmithJun 20, 2022
  2. rsbecker@nexbridge.comJun 20, 2022
  3. Ævar Arnfjörð BjarmasonJun 21, 2022
  4. rsbecker@nexbridge.comJun 21, 2022
  5. Ævar Arnfjörð BjarmasonJun 21, 2022
  6. brian m. carlsonJun 22, 2022
  7. Stephen SmithJun 23, 2022
  8. brian m. carlsonJun 23, 2022
  9. Junio C HamanoJun 23, 2022
  10. Ævar Arnfjörð BjarmasonJun 23, 2022
  11. Kyle MeyerJun 24, 2022
  12. Stephen SmithJun 24, 2022
  13. Ævar Arnfjörð BjarmasonJun 24, 2022
  14. Jonathan CorbetJun 24, 2022
  15. Jeff KingJun 24, 2022
  16. Ævar Arnfjörð BjarmasonJun 24, 2022
  17. brian m. carlsonJun 25, 2022
  18. Plan for SHA-256 repos to support SHA-1?Eric W. Biederman, Jun 26, 2022
  19. Junio C HamanoJun 26, 2022
  20. brian m. carlsonJun 26, 2022
  21. Jeff KingJul 1, 2022

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.