-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
Add PGP key ids to AUTHORS.rst? #23
Comments
Mostly a good idea, but shouldn't the entire file be signed (possibly as a consequence of a release)? Obviously, if the value isn't authenticated somehow, it's pretty trivial for an attacker to make N fake GPG keys :) |
I don’t think we can solve this chicken-egg problem of trust. We could add finger prints for all I care, people using GPG will have to check the trust graphs anyway (but probably won’t). |
Right: it's strictly better, but only if anyone actually ever checks a signature. (Or, if you trust github and only ever use github over HTTPS, git over ssh/https). |
Please comment on the idea. I'm not particular happy with the redundancy of key id / fingerprint. AUTHORS
Acquire GPG keysYou can download all keys with a single command::
|
Putting there both seems redundant. It’s either key id XOR fingerprint. |
Having a file with a list of fingerprints in with no guidance on how the project intends you to use them for verifying things just doesn't seem very helpful on it's own. I guess the secure bug reporting issue may be the only case this is particularly useful right now, but then there should probably be some instruction in README.md on how to report security issues too? |
We started including these (or at least I did :P), so this is done. |
How do you feel about PGP key ids in the AUTHORs.rst file? As security concerned citizens we should encourage people to use PGP/GPG, especially if somebody wants to report a bug securely.
The text was updated successfully, but these errors were encountered: