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

checksums #171

Closed
dheles opened this issue Sep 18, 2015 · 4 comments
Closed

checksums #171

dheles opened this issue Sep 18, 2015 · 4 comments

Comments

@dheles
Copy link

dheles commented Sep 18, 2015

Checksums listed on the v4.1.0 announcement page ( https://nodejs.org/en/blog/release/v4.1.0/ ) are listed as "Hash: SHA512" but are actually SHA256 ( as per https://nodejs.org/dist/v4.1.0/SHASUMS256.txt). Checking them as 512 yields a different result and thus, confusion.

@rvagg
Copy link
Member

rvagg commented Sep 18, 2015

512 is the GPG signing hash, not the file hash

@rvagg rvagg closed this as completed Sep 18, 2015
@fhemberger
Copy link
Contributor

@rvagg As this is not the first time this question comes up, is there a way to express this better in the release post?

e.g:
Shasums (GPG signing hash: SHA512, file hash: SHA256):
(block of shasums)

@fhemberger fhemberger reopened this Sep 18, 2015
@fhemberger
Copy link
Contributor

Hijacking this issue: @phillipj, I'd like to make a little change to the release posts and script:

Before

After

bildschirmfoto 2015-09-18 um 07 00 27

@phillipj
Copy link
Member

@fhemberger 👍

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants