Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

doc: make README(.md) more informative by indicating that a GPG key u… #32591

Closed
Closed
Changes from 2 commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
7 changes: 5 additions & 2 deletions README.md
Expand Up @@ -542,7 +542,8 @@ maintaining the Node.js project.

### Release Keys

GPG keys used to sign Node.js releases:
GPG keys used to sign Node.js releases (you may encounter a release signed
by a sub-key of a key listed below (which itself isn't listed below)):
haqer1 marked this conversation as resolved.
Show resolved Hide resolved

* **Beth Griggs** <bethany.griggs@uk.ibm.com>
`4ED778F539E3634C779C87C6D7062848A1AB005C`
Expand All @@ -565,7 +566,9 @@ GPG keys used to sign Node.js releases:
* **Shelley Vohr** <shelley.vohr@gmail.com>
`B9E2F5981AA6E0CD28160D9FF13993A75599653C`

To import the full set of trusted release keys:
If you encounter a release signed by a key not listed above, please import it
and check whether it is a sub-key of a primary key listed above. You can also
import the full set of trusted release keys:
haqer1 marked this conversation as resolved.
Show resolved Hide resolved

```shell
gpg --keyserver pool.sks-keyservers.net --recv-keys 4ED778F539E3634C779C87C6D7062848A1AB005C
Expand Down