diff options
author | Jon Moss <me@jonathanmoss.me> | 2017-08-30 15:12:31 -0400 |
---|---|---|
committer | Refael Ackermann <refack@gmail.com> | 2017-08-30 16:15:11 -0400 |
commit | 676522fc025b9ecdfb02bc72cddd8cf7a81f9ac1 (patch) | |
tree | 372cf9718f095c11e04c060a68fe9ea1f352eaa7 /README.md | |
parent | 0b0c2ec29ac9ea6d8f2bc10016c6625dfc1c5ba7 (diff) | |
download | android-node-v8-676522fc025b9ecdfb02bc72cddd8cf7a81f9ac1.tar.gz android-node-v8-676522fc025b9ecdfb02bc72cddd8cf7a81f9ac1.tar.bz2 android-node-v8-676522fc025b9ecdfb02bc72cddd8cf7a81f9ac1.zip |
doc: /s/SHASUM256/SHASUMS256
As an example, `curl https://nodejs.org/dist/v8.4.0/SHASUM256.txt` will
return a 404 right now.
PR-URL: https://github.com/nodejs/node/pull/15101
Reviewed-By: Benjamin Gruenbaum <benjamingr@gmail.com>
Reviewed-By: James M Snell <jasnell@gmail.com>
Reviewed-By: Ruben Bridgewater <ruben@bridgewater.de>
Reviewed-By: Luigi Pinca <luigipinca@gmail.com>
Reviewed-By: Refael Ackermann <refack@gmail.com>
Diffstat (limited to 'README.md')
-rw-r--r-- | README.md | 8 |
1 files changed, 4 insertions, 4 deletions
@@ -114,11 +114,11 @@ documentation of the latest stable version. ### Verifying Binaries -Current, LTS and Nightly download directories all contain a _SHASUM256.txt_ +Current, LTS and Nightly download directories all contain a _SHASUMS256.txt_ file that lists the SHA checksums for each file available for download. -The _SHASUM256.txt_ can be downloaded using curl. +The _SHASUMS256.txt_ can be downloaded using curl. ```console $ curl -O https://nodejs.org/dist/vx.y.z/SHASUMS256.txt @@ -135,10 +135,10 @@ _(Where "node-vx.y.z.tar.gz" is the name of the file you have downloaded)_ Additionally, Current and LTS releases (not Nightlies) have GPG signed -copies of SHASUM256.txt files available as SHASUM256.txt.asc. You can use +copies of SHASUMS256.txt files available as SHASUMS256.txt.asc. You can use `gpg` to verify that the file has not been tampered with. -To verify a SHASUM256.txt.asc, you will first need to import all of +To verify a SHASUMS256.txt.asc, you will first need to import all of the GPG keys of individuals authorized to create releases. They are listed at the bottom of this README under [Release Team](#release-team). Use a command such as this to import the keys: |