Commit b0e43c7
doc: add gpg key export directions to releases doc
Adds an extra step with instructions for exporting a gpg key to be
uploaded to the key server.
PR-URL: #35298
Reviewed-By: Richard Lau <riclau@uk.ibm.com>
Reviewed-By: Beth Griggs <Bethany.Griggs@uk.ibm.com>
Reviewed-By: Rich Trott <rtrott@gmail.com>1 parent cc11464 commit b0e43c7
1 file changed
Lines changed: 8 additions & 2 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
@@ -92,8 +92,14 @@ signed by someone who has been authorized to create a release. | |||
| 92 | 92 | ||
| 93 | 93 | The GPG keys should be fetchable from a known third-party keyserver. The SKS | |
| 94 | 94 | Keyservers at <https://sks-keyservers.net> are recommended. Use the | |
| 95 | - [submission](https://pgp.mit.edu/) form to submit a new GPG key. Keys should be | ||
| 96 | - fetchable via: | ||
| 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: | ||
| 97 | + | ||
| 98 | + ```console | ||
| 99 | + $ gpg --armor --export email@server.com > ~/nodekey.asc | ||
| 100 | + ``` | ||
| 101 | + | ||
| 102 | + Keys should be fetchable via: | ||
| 97 | 103 | ||
| 98 | 104 | ```console | |
| 99 | 105 | $ gpg --keyserver pool.sks-keyservers.net --recv-keys <FINGERPRINT> | |
0 commit comments