Update btcdrak key with new expiry dates #8547
Closed
Conversation
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
Member
|
I think my key in the repo expired as well... We might ask people to just refresh the keys from a keyserver. |
Member
|
On the other hand, the key servers are a sewer, people should be careful not to request keys by 32-bit key-id anymore at least. So if we're going to ask people to refresh from there, we should provide the right commands. |
Member
gpg --import bitcoin/contrib/gitian-keys/*.pgp
gpg --refresh-keysIt should not request by 32-bit id, when you import from the repo. |
Member
|
I didn't even know about --refresh-keys. Let's add that to |
Member
|
Closing in favor of #8603 |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
3 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.
No description provided.