OSSForks/node
1
0
Fork 0
mirror of https://github.com/zebrajr/node.git synced 2026-01-15 12:15:26 +00:00
Code Issues Actions 8 Packages Projects Releases Wiki Activity

doc: add gpg key export directions to releases doc

Browse Source 
Adds an extra step with instructions for exporting a gpg key to be
uploaded to the key server.

PR-URL: https://github.com/nodejs/node/pull/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>
This commit is contained in:
Danielle Adams
2020-09-22 12:39:26 -04:00
committed by Rich Trott
parent d7dfa66baa
commit b15ed65153
1 changed files with 8 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

10
doc/guides/releases.md
View File

@@ -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>