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.

Sign up for GitHub

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

Jump to bottom

doc: additional note in README(.md) informing users that it is advise… #32655

Closed
wants to merge 4 commits into from
Closed

doc: additional note in README(.md) informing users that it is advise… #32655

Changes from 1 commit
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
9bd6618
doc: additional note in README(.md) informing users that it is advise…
haqer1 Apr 4, 2020
2e103ed
doc: apply suggestion from code review
haqer1 Apr 9, 2020
945cce5
doc: additional note in README(.md) informing users that it is advise…
haqer1 Oct 28, 2020
69d81a9
doc: additional note in README(.md) informing users that it is advise…
haqer1 Oct 28, 2020
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
4 changes: 3 additions & 1 deletion README.md
View file
Open in desktop
Expand Up @@ -565,7 +565,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:
To avoid nuances involved in verification of a sub-key possibly used to sign a
release, it is advised to import the full set of trusted release keys (rather
than an individual key used to sign a release):
haqer1 marked this conversation as resolved.
Show resolved Hide resolved

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