From: "brian m. carlson" <sandals@crustytoothpaste.net>
To: Junio C Hamano <gitster@pobox.com>
Cc: "Eric W. Biederman" <ebiederm@xmission.com>,
"Jeff King" <peff@peff.net>,
"Ævar Arnfjörð Bjarmason" <avarab@gmail.com>,
"Stephen Smith" <ischis2@cox.net>, git <git@vger.kernel.org>
Subject: Re: Plan for SHA-256 repos to support SHA-1?
Date: Sun, 26 Jun 2022 15:19:10 +0000 [thread overview]
Message-ID: <Yrh47mun9U9t0HpO@tapette.crustytoothpaste.net> (raw)
In-Reply-To: <CAPc5daVtRZ-Str_yCqRXZKT5+KKcXdnptFaer27XneUwj76KjQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 782 bytes --]
On 2022-06-26 at 00:27:57, Junio C Hamano wrote:
> 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
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 263 bytes --]
next prev parent reply other threads:[~2022-06-26 15:19 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-20 22:51 SHA-256 transition Stephen Smith
2022-06-20 23:13 ` rsbecker
2022-06-21 10:25 ` Ævar Arnfjörð Bjarmason
2022-06-21 13:18 ` rsbecker
2022-06-21 18:14 ` Ævar Arnfjörð Bjarmason
2022-06-22 0:29 ` brian m. carlson
2022-06-23 0:45 ` Stephen Smith
2022-06-23 1:44 ` brian m. carlson
2022-06-23 15:32 ` Junio C Hamano
2022-06-23 22:21 ` Ævar Arnfjörð Bjarmason
2022-06-24 0:29 ` Kyle Meyer
2022-06-24 1:03 ` Stephen Smith
2022-06-24 1:19 ` Ævar Arnfjörð Bjarmason
2022-06-24 14:42 ` Jonathan Corbet
2022-06-24 10:52 ` Jeff King
2022-06-24 15:49 ` Ævar Arnfjörð Bjarmason
2022-06-25 8:53 ` brian m. carlson
2022-06-26 0:09 ` Plan for SHA-256 repos to support SHA-1? Eric W. Biederman
2022-06-26 0:27 ` Junio C Hamano
2022-06-26 15:19 ` brian m. carlson [this message]
2022-07-01 18:00 ` SHA-256 transition Jeff King
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Yrh47mun9U9t0HpO@tapette.crustytoothpaste.net \
--to=sandals@crustytoothpaste.net \
--cc=avarab@gmail.com \
--cc=ebiederm@xmission.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=ischis2@cox.net \
--cc=peff@peff.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).