-
Notifications
You must be signed in to change notification settings - Fork 500
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.
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
Conversation
need to verify fingerprints are authentic by comparing them in multiple places
Makes sense to me, the instructions for verifying signatures are somewhat vague as-is. |
intended or not, this enshrines the for-profit social construct NAK |
ACK |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Concept ACK, but I would:
- add the extra trustworthiness verification instructions at the end of the paragraph, instead of at the beginning
- rationale: these instructions are mostly aimed at people unfamiliar with the process, and the process can already be intimidating (or appear too much hassle) as is. Imo it's a big win already if people start out with just getting keys from
builder-keys
. Then, when that all worked, they can (but if they don't, they're still much better off than not verifying at all) increase their trust in the keys by looking at other platforms etc). I can imagine that when some people read these extended instructions, they would just not verify at all because they don't know (or don't want to spend the time to investigate) what trustworthy websites are and therefore assume the whole thing is pointless.
- rationale: these instructions are mostly aimed at people unfamiliar with the process, and the process can already be intimidating (or appear too much hassle) as is. Imo it's a big win already if people start out with just getting keys from
- in addition to looking at trustworthy websites, suggest comparing fingerprints with people they trust
@@ -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 |
There was a problem hiding this comment.
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
Are you still working on this? |
Another friendly ping, especially for updating the URL pointing to the builder keys as it's confusing users. |
Incorporated into new PR: #964 |
need to verify fingerprints are authentic by comparing them in multiple places