Skip to content

Commit 5b76313

Browse files
Trotttargos
authored andcommitted
doc: improve instructions for verifying binaries
Simplify and clarify the text in README.md for verifying binaries. PR-URL: #23248 Reviewed-By: Anna Henningsen <[email protected]> Reviewed-By: Sakthipriyan Vairamani <[email protected]> Reviewed-By: Ruben Bridgewater <[email protected]> Reviewed-By: James M Snell <[email protected]>
1 parent 6943fa9 commit 5b76313

File tree

1 file changed

+10
-18
lines changed

1 file changed

+10
-18
lines changed

README.md

+10-18
Original file line numberDiff line numberDiff line change
@@ -116,11 +116,10 @@ directory under _docs_ or at <https://nodejs.org/download/docs/>.
116116

117117
### Verifying Binaries
118118

119-
Current, LTS, and Nightly download directories all contain a SHASUMS256.txt
120-
file that lists the SHA checksums for each file available for
121-
download.
119+
Download directories contain a SHASUMS256.txt file with SHA checksums for the
120+
files.
122121

123-
The SHASUMS256.txt can be downloaded using `curl`.
122+
To download SHASUMS256.txt using `curl`:
124123

125124
```console
126125
$ curl -O https://nodejs.org/dist/vx.y.z/SHASUMS256.txt
@@ -133,14 +132,11 @@ it through `sha256sum` with a command such as:
133132
$ grep node-vx.y.z.tar.gz SHASUMS256.txt | sha256sum -c -
134133
```
135134

136-
Current and LTS releases (but not Nightlies) also have the GPG detached
137-
signature of SHASUMS256.txt available as SHASUMS256.txt.sig. You can use `gpg`
138-
to verify that SHASUMS256.txt has not been tampered with.
139-
140-
To verify SHASUMS256.txt has not been altered, you will first need to import
141-
all of the GPG keys of individuals authorized to create releases. They are
142-
listed at the bottom of this README under [Release Team](#release-team).
143-
Use a command such as this to import the keys:
135+
For Current and LTS, the GPG detached signature of SHASUMS256.txt is in
136+
SHASUMS256.txt.sig. You can use it with `gpg` to verify the integrity of
137+
SHASUM256.txt. You will first need to import all the GPG keys of individuals
138+
authorized to create releases. They are at the bottom of this README under
139+
[Release Team](#release-team). To import the keys:
144140

145141
```console
146142
$ gpg --keyserver pool.sks-keyservers.net --recv-keys DD8F2338BAE7501E3DD5AC78C273792F7D83545D
@@ -154,12 +150,8 @@ Next, download the SHASUMS256.txt.sig for the release:
154150
$ curl -O https://nodejs.org/dist/vx.y.z/SHASUMS256.txt.sig
155151
```
156152

157-
After downloading the appropriate SHASUMS256.txt and SHASUMS256.txt.sig files,
158-
you can then use `gpg --verify SHASUMS256.txt.sig SHASUMS256.txt` to verify
159-
that the file has been signed by an authorized member of the Node.js team.
160-
161-
Once verified, use the SHASUMS256.txt file to get the checksum for
162-
the binary verification command above.
153+
Then use `gpg --verify SHASUMS256.txt.sig SHASUMS256.txt` to verify
154+
the file's signature.
163155

164156
## Building Node.js
165157

0 commit comments

Comments
 (0)