Let's document how to verify a Node.js downloads on the website
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 6.9k
- Forks
- 6.5k
- Avg merge
- 2d 8h
- Merged PRs (30d)
- 29
Description
As discussed in https://github.com/nodejs/node/issues/58904#issuecomment-3031456396, the way we document how to verify Node.js downloads is not ideal, and there seems to be consensus for switching our recommendation from the public OpenPGP.org server to our own nodejs/release-keys repository. On top of changes in the nodejs/node README, we should also host on the website what is the trusted way to verify a Node.js download.
What we need to provide on the website (presumably on the Downloads page) would be:
- a git commit hash to a revision of nodejs/release-keys that contain keys to all.
- a SHA-256 of the
gpg-only-active-keys/pubring.kbxon that revision.
Opening this now in case it involves design changes, but it shouldn't land until after the nodejs/node README is edited (currently it still points to keys.openpgp.org as the recommended source).
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the website's Downloads page and the related nodejs/node README change, noting the dependency on the updated recommendation. Document a trusted nodejs/release-keys revision and the SHA-256 of its gpg-only-active-keys/pubring.kbx; done means the verification guidance is published on the website.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git, nextjs, nodejs, typescript
- Domain
- documentation, security, web-dev
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100