On Mon, Mar 29, 2021 at 01:43:04PM +0000, Johannes Schindelin via GitGitGadget wrote: > Whenever we fix critical vulnerabilities, we follow some sort of > protocol (e.g. setting a coordinated release date, keeping the fix under > embargo until that time, coordinating with packagers and/or hosting > sites, etc). > > Similar in spirit to `Documentation/howto/maintain-git.txt`, let's > formalize the details in a document. ... > +Notifying the Linux distributions > +--------------------------------- As one of the Gentoo maintainer for Git, I was wondering if the embargoed-releases process could be tweaked slightly. Specifically, in the embargo email, could you please publishing the exact size & digests of the to-be-released tarballs, esp. the htmldocs & manpages tarballs. Gentoo, as a source-based distribution, intends users to download the upstream tarballs (we mirror them as well), and verify the digests of the tarballs vs a signed copy of what the digests should be. This has meant some delay at the end of embargoed releases because we have to wait for the official files to be available, then update the build instructions (specifically "Manifest" which contains the matching digests), and get that out to users. Fields in of the Gentoo side of the digests: name, size, digests w/ prefix. Example: DIST git-2.31.1.tar.xz 6413368 BLAKE2B ... SHA512 ... DIST git-htmldocs-2.31.1.tar.xz 1357592 BLAKE2B ... SHA512 ... DIST git-manpages-2.31.1.tar.xz 487784 BLAKE2B ... SHA512 ... The minimum set of hash algorithms for this Gentoo code right now is BLAKE2B, which should be easy to script into the announcement mail via: openssl dgst -blake2b512 "$FILENAME" -- Robin Hugh Johnson Gentoo Linux: Dev, Infra Lead, Foundation Treasurer E-Mail : robbat2@xxxxxxxxxx GnuPG FP : 11ACBA4F 4778E3F6 E4EDF38E B27B944E 34884E85 GnuPG FP : 7D0B3CEB E9B85B1F 825BCECF EE05E6F6 A48F6136
Attachment:
signature.asc
Description: PGP signature
