Repository navigation
Verify the fast start's build by builder signature, not by sha256 alone - #3
Merged
Merged
Conversation
The 29.4.2 + PR #444 build behind the fast start now has a Guix attestation signed with a pinned 29.4.2 release-builder key (chrisguida), published on https://github.com/chrisguida/guix.sigs/tree/assumeutxo976000, and the release carries SHA256SUMS and SHA256SUMS.asc next to the archive, which is where sig_fetch looks. So the fast row moves from pin to builders: the installer now requires a valid pinned-builder signature on SHA256SUMS that lists the archive, and still checks the pinned sha256. The archive, its sha256 and the snapshot are unchanged, so installed nodes are unaffected. The mode's label, trust notice and README say what is signed and by whom; further builder signatures are appended to the release's SHA256SUMS.asc.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The 29.4.2 + PR #444 build behind the
faststart now has a Guix attestation signed with a pinned 29.4.2 release-builder key (mine,658E64021E5793C6C4E15E45C2E581F5B998F30E). The attestation is on https://github.com/chrisguida/guix.sigs/tree/assumeutxo976000 (the build was reproduced on a second machine with the same three hashes), and the release now carriesSHA256SUMSandSHA256SUMS.ascnext to the archive, which is wheresig_fetchlooks:https://github.com/chrisguida/bitcoin/releases/download/v29.4.2.knots20260508-assumeutxo976000/SHA256SUMS
https://github.com/chrisguida/bitcoin/releases/download/v29.4.2.knots20260508-assumeutxo976000/SHA256SUMS.asc
This moves the
fastrow frompintobuilders: the installer requires a valid pinned-builder signature on aSHA256SUMSthat lists the archive, and still checks the pinned sha256. The archive, its sha256 and the snapshot are unchanged, so installed nodes are unaffected andalphapool-node upgradehas nothing to move. The label, the trust notice (English and Chinese) and the README fast-start paragraph say what is signed and by whom; the changelog has the entry under "unreleased".Further builder signatures are appended to the release's
SHA256SUMS.ascas they come in; nothing changes here when they do. Independent of #1 and #2, which I will rebase separately.Checked:
bash -n, the row parses to its 11 fields withbuildersand 976000 among the known heights, and the two files verify with gpg after a download from the URLs above. Not run end to end on a server.