Skip to content

adding more specific verification instructions #878

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
wants to merge 1 commit into from
Closed

adding more specific verification instructions #878

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 1 addition & 2 deletions _posts/en/pages/2017-01-01-download.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -95,8 +95,7 @@ obtain_release_key: >
key using this command:</p>

choosing_builders: >
It is recommended that you choose a few individuals from this list who you find
trustworthy and import their keys as above, or import all the keys per the
It is recommended that you choose a few individuals from this list whose fingerprints you have confirmed to be authentic by comparing them on multiple trustworthy websites and import their keys as above, or import all the keys per the
instructions in the <a href="$(BUILDER_KEYS_URL)"><code>contrib/builder-key</code>
README</a>. You will later use their keys to check the signature attesting to the
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This file no longer exits. It might be better to directly link to the guix attestations repo and explain that each release is signed by a different set of builders. For example the 23.1 one is signed by https://github.com/bitcoin-core/guix.sigs/tree/main/23.1

validity of the checksums you use to check the binaries.
Expand Down