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

[SECURITY] Consider signing releases with PGP #5313

Open
ChristopherSchultz opened this issue Jul 26, 2022 · 0 comments
Open

[SECURITY] Consider signing releases with PGP #5313

ChristopherSchultz opened this issue Jul 26, 2022 · 0 comments
Labels
Internal-Issue-Created An issue has been created in NextGen's internal issue tracker RS-9151 Security triaged

Comments

@ChristopherSchultz
Copy link
Contributor

NextGen currently computes hashes for some release artifacts and hosts them side-by-side with the downloadable packages from their release-hosting site. The hashes can only provide proof that a particular binary matches the hash and has therefore not been tampered-with after downloading. They do not, however, provide any authentication of the signature at all.

PGP (or GPG) signatures provide both tamper-evident hashing and authenticated signing to prove that the binary was signed by a (presumably) trusted signer. This allows binaries to be mirrored, copied, shared, etc. and signatures cannot be forged. Theoretically, hashes can be "forged" simply by updating the hash after the binary has been modified.

@lmillergithub lmillergithub added triaged Internal-Issue-Created An issue has been created in NextGen's internal issue tracker RS-9151 labels Aug 17, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Internal-Issue-Created An issue has been created in NextGen's internal issue tracker RS-9151 Security triaged
Projects
None yet
Development

No branches or pull requests

2 participants