From b0e43c718c89fd69d3822cb02060e59c546975e7 Mon Sep 17 00:00:00 2001 From: Danielle Adams Date: Tue, 22 Sep 2020 12:39:26 -0400 Subject: [PATCH] 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: https://github.com/nodejs/node/pull/35298 Reviewed-By: Richard Lau Reviewed-By: Beth Griggs Reviewed-By: Rich Trott --- doc/guides/releases.md | 10 ++++++++-- 1 file changed, 8 insertions(+), 2 deletions(-) diff --git a/doc/guides/releases.md b/doc/guides/releases.md index 74884d45ebbe42..c07fcbf5a82b8b 100644 --- a/doc/guides/releases.md +++ b/doc/guides/releases.md @@ -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 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