Date: Wed, 2 Sep 2020 22:41:13 -0400 From: grarpamp <grarpamp@gmail.com> To: freebsd-security@freebsd.org Cc: freebsd-current@freebsd.org, freebsd-git@freebsd.org Subject: Re: Plans for git (was: Please check the current beta git conversions) Message-ID: <CAD2Ti28DONAGDNacFjReSyAiG4_eNWiS5nc5u12p9bznFQe_qQ@mail.gmail.com> In-Reply-To: <CAD2Ti28fn99=SSKXRHFkMrNvYJVTpbDVBi%2B6A3vwRrb=VgE_ew@mail.gmail.com> References: <CAPyFy2CTTecRJDnXNvF%2BM2%2BaLWJpA%2BEdG43ZeU3qwsCruecoFA@mail.gmail.com> <20200902045939.GA15897@eureka.lemis.com> <CAD2Ti28fn99=SSKXRHFkMrNvYJVTpbDVBi%2B6A3vwRrb=VgE_ew@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> The underlying initializing 'git init' commit hash must be > signed by security officer key having sufficient human PGP-WoT. > > Git also supports sha-256 soon now, adoption should > be researched from various online article series and > work product before committing plans... > https://lwn.net/Articles/823352/ > https://git-scm.com/docs/hash-function-transition For those interested, additional topical from same site... https://github.com/bk2204/git/tree/transition-stage-4 https://lwn.net/Articles/823352/ Updating the Git protocol for SHA-256 https://lwn.net/Articles/811068/ A new hash algorithm for Git https://lwn.net/Articles/715716/ Moving Git past SHA-1 https://lwn.net/Articles/813646/ Attestation for kernel patches https://lwn.net/Articles/821367/ Merkle trees and build systems https://lwn.net/Articles/663875/ Changes in the TLS certificate ecosystem, part 1 https://lwn.net/Articles/468911/ Sovereign Keys for certificate verification https://lwn.net/Articles/652580/ Decentralization for the web
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAD2Ti28DONAGDNacFjReSyAiG4_eNWiS5nc5u12p9bznFQe_qQ>