diff options
| author | MarcoFalke <falke.marco@gmail.com> | 2019-12-03 13:41:50 -0500 |
|---|---|---|
| committer | MarcoFalke <falke.marco@gmail.com> | 2019-12-03 13:41:56 -0500 |
| commit | e354db787790b84b0b3f34cc55b65446c71e4fa2 (patch) | |
| tree | b26b50a138893ce3991d6ba054d6ae44ddb558a5 | |
| parent | 54b12e425b502e7777e6910117b4527ab4ead0ff (diff) | |
| parent | bd6a24307564a56d54d98331d5e1680d27ddc09e (diff) | |
| download | bitcoin-e354db787790b84b0b3f34cc55b65446c71e4fa2.tar.xz | |
Merge #17637: script: Add Keyserver to verify-commits README
bd6a24307564a56d54d98331d5e1680d27ddc09e script: Add Keyserver to verify-commits README (Emil Engler)
Pull request description:
When I use the option with the default keyserver on `gpg (GnuPG) 2.2.12` from the Debian repositories only the keys from meshcollider and fanquake are actually found. Using the ubuntu keyserver works without any problems and all keys are getting found.
As this keyserver is also suggested on [https://bitcoincore.org/en/download/](), it would be good to have a common keyserver.
ACKs for top commit:
laanwj:
ACK bd6a24307564a56d54d98331d5e1680d27ddc09e, better to be explicit here
Tree-SHA512: d4127c42490390bed4e0074ebb1f8a6cc983f96bbea0ec1da011a93bed325a7f465ed9936e4bc2ef7c4b2e4501a2868d00b67ceb7bf85f2a902db9c6173a6c61
| -rw-r--r-- | contrib/verify-commits/README.md | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/contrib/verify-commits/README.md b/contrib/verify-commits/README.md index 1215962a16..e95a57586f 100644 --- a/contrib/verify-commits/README.md +++ b/contrib/verify-commits/README.md @@ -40,7 +40,7 @@ Import trusted keys In order to check the commit signatures, you must add the trusted PGP keys to your machine. [GnuPG](https://gnupg.org/) may be used to import the trusted keys by running the following command: ```sh -gpg --recv-keys $(<contrib/verify-commits/trusted-keys) +gpg --keyserver hkp://keyserver.ubuntu.com --recv-keys $(<contrib/verify-commits/trusted-keys) ``` Key expiry/revocation |