File tree Expand file tree Collapse file tree 1 file changed +6
-5
lines changed Expand file tree Collapse file tree 1 file changed +6
-5
lines changed Original file line number Diff line number Diff line change @@ -90,10 +90,11 @@ responsible for that release. In order to be able to verify downloaded binaries,
90
90
the public should be able to check that the ` SHASUMS256.txt ` file has been
91
91
signed by someone who has been authorized to create a release.
92
92
93
- The GPG keys should be fetchable from a known third-party keyserver. The SKS
94
- Keyservers at < https://sks-keyservers.net > are recommended. Use the
95
- [ submission] ( https://pgp.mit.edu/ ) form to submit a new GPG key. You'll need to
96
- do an ASCII-armored export of your key first:
93
+ The public keys should be fetchable from a known third-party keyserver.
94
+ The OpenPGP keyserver at < https://keys.openpgp.org/ > is recommended.
95
+ Use the [ submission] ( https://keys.openpgp.org/upload ) form to submit
96
+ a new public key, and make sure to verify the associated email.
97
+ You'll need to do an ASCII-armored export of your key first:
97
98
98
99
``` bash
99
100
gpg --armor --export email@server.com > ~ /nodekey.asc
@@ -102,7 +103,7 @@ gpg --armor --export email@server.com > ~/nodekey.asc
102
103
Keys should be fetchable via:
103
104
104
105
``` bash
105
- gpg --keyserver pool.sks-keyservers.net --recv-keys < FINGERPRINT>
106
+ gpg --keyserver hkps://keys.openpgp.org --recv-keys < FINGERPRINT>
106
107
```
107
108
108
109
The key you use may be a child/subkey of an existing key.
You can’t perform that action at this time.
0 commit comments