Skip to content

Commit

Permalink
doc: add gpg key export directions to releases doc
Browse files Browse the repository at this point in the history
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>
  • Loading branch information
danielleadams authored and Trott committed Sep 26, 2020

Unverified

This commit is not signed, but one or more authors requires that any commit attributed to them is signed.
1 parent d7dfa66 commit b15ed65
Showing 1 changed file with 8 additions and 2 deletions.
10 changes: 8 additions & 2 deletions doc/guides/releases.md
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.

The GPG keys should be fetchable from a known third-party keyserver. The SKS
Keyservers at <https://sks-keyservers.net> are recommended. Use the
[submission](https://pgp.mit.edu/) form to submit a new GPG key. Keys should be
fetchable via:
[submission](https://pgp.mit.edu/) form to submit a new GPG key. You'll need to
do an ASCII-armored export of your key first:

```console
$ gpg --armor --export email@server.com > ~/nodekey.asc
```

Keys should be fetchable via:

```console
$ gpg --keyserver pool.sks-keyservers.net --recv-keys <FINGERPRINT>

0 comments on commit b15ed65

Please sign in to comment.