-
Notifications
You must be signed in to change notification settings - Fork 38.7k
doc: Suggest keys.openpgp.org as keyserver in SECURITY.md
#23466
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
This is in line with 4c43b7d from PR bitcoin#22688.
|
A related issue is that I couldn't find an unexpired version of @sipa's key, neither on |
|
review ACK 90f1f84 |
|
Wouldn't it make sense to update https://bitcoincore.org/en/contact/ as well, assuming that |
|
|
I think they don't accept any key updates, do they? |
|
Review ACK 90f1f84
I agree. Ideally we would not have to suggest any keyserver. It's frustrating enough to have to play keyserver ping-pong every time when yet another part of PGP infrastructure goes down, but it seems BTW instead of adding it in the command line every time you could also add in |
hebasto
left a comment
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.
ACK 90f1f84, agree with arguments above.
Zero-1729
left a comment
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.
ACK 90f1f84
Makes sense to keep the keyservers consistent.
This is in line with bitcoin/bitcoin#23466 .
This is in line with bitcoin/bitcoin#23466 .
…rver in SECURITY.md 90f1f84 doc: Suggest `keys.openpgp.org` as keyserver in SECURITY.md (Tim Ruffing) Pull request description: `--recv-keys` without a `--keyserver` arg simply failed for me on a fresh Arch Linux installation, so I think it's a good idea to suggest a keyserver. OpenPGP ecosystem is broken in a number of ways, so the right way to approach this issue has some potential for bikeshedding. But the only thing that this PR does is to keep `SECURITY.md` in line with the instructions for builder keys, where there was agreement on switching to `keys.openpgp.org` (#22688). ACKs for top commit: MarcoFalke: review ACK 90f1f84 laanwj: Review ACK 90f1f84 hebasto: ACK 90f1f84, agree with arguments above. Zero-1729: ACK 90f1f84 Tree-SHA512: 1ab20c837cd952aa32b57473772cbfd33411a08db6e88b951bce38f76a3c509c0e91d6944ec0ca5eac8d5eb4d98a5489276d55691328f2e2556b2640f8e7c108
|
This has been merged. |
3b157c4 doc: Suggest keys.openpgp.org as keyserver in SECURITY.md (Tim Ruffing) 73a7472 doc: Replace apoelstra's GPG key by jonasnick's GPG key (Tim Ruffing) Pull request description: I have verified the new key via other secure channels. This closes #1003 . We can skip the second commit but I expect bitcoin/bitcoin#23466 to be merged. If it won't be merged, we could still revert. ACKs for top commit: sipa: ACK 3b157c4. I've also verified the key out of band. jonasnick: ACK 3b157c4 Tree-SHA512: 496f98121f14031bc693aa83bf208b253f79b700b4bca0b629deadc8852f76ef6d69ad90109baa771d7b9f6e4b983e4ed8dca404cf5aceffe9d520d3362b533a
…SECURITY.md 90f1f84 doc: Suggest `keys.openpgp.org` as keyserver in SECURITY.md (Tim Ruffing) Pull request description: `--recv-keys` without a `--keyserver` arg simply failed for me on a fresh Arch Linux installation, so I think it's a good idea to suggest a keyserver. OpenPGP ecosystem is broken in a number of ways, so the right way to approach this issue has some potential for bikeshedding. But the only thing that this PR does is to keep `SECURITY.md` in line with the instructions for builder keys, where there was agreement on switching to `keys.openpgp.org` (bitcoin#22688). ACKs for top commit: MarcoFalke: review ACK 90f1f84 laanwj: Review ACK 90f1f84 hebasto: ACK 90f1f84, agree with arguments above. Zero-1729: ACK 90f1f84 Tree-SHA512: 1ab20c837cd952aa32b57473772cbfd33411a08db6e88b951bce38f76a3c509c0e91d6944ec0ca5eac8d5eb4d98a5489276d55691328f2e2556b2640f8e7c108
d1492b6 Suggest `keys.openpgp.org` as keyserver (Tim Ruffing) Pull request description: See bitcoin/bitcoin#23466 ACKs for top commit: Zero-1729: ACK d1492b6 Tree-SHA512: c40201aad0bd49ada9dc2dbded6f8f75944f6951e5ea71068cf4e3a175ce1778869b8acd99c39c69312f023878979366cdf7653d22babc0f5c7c3d7d0c265672
…SECURITY.md 90f1f84 doc: Suggest `keys.openpgp.org` as keyserver in SECURITY.md (Tim Ruffing) Pull request description: `--recv-keys` without a `--keyserver` arg simply failed for me on a fresh Arch Linux installation, so I think it's a good idea to suggest a keyserver. OpenPGP ecosystem is broken in a number of ways, so the right way to approach this issue has some potential for bikeshedding. But the only thing that this PR does is to keep `SECURITY.md` in line with the instructions for builder keys, where there was agreement on switching to `keys.openpgp.org` (bitcoin#22688). ACKs for top commit: MarcoFalke: review ACK 90f1f84 laanwj: Review ACK 90f1f84 hebasto: ACK 90f1f84, agree with arguments above. Zero-1729: ACK 90f1f84 Tree-SHA512: 1ab20c837cd952aa32b57473772cbfd33411a08db6e88b951bce38f76a3c509c0e91d6944ec0ca5eac8d5eb4d98a5489276d55691328f2e2556b2640f8e7c108
--recv-keyswithout a--keyserverarg simply failed for me on a fresh Arch Linux installation, so I think it's a good idea to suggest a keyserver. OpenPGP ecosystem is broken in a number of ways, so the right way to approach this issue has some potential for bikeshedding. But the only thing that this PR does is to keepSECURITY.mdin line with the instructions for builder keys, where there was agreement on switching tokeys.openpgp.org(#22688).