-
Notifications
You must be signed in to change notification settings - Fork 3
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
doc: Display current pgp key used for signing RNP #44
Conversation
Ping @ni4 @antonsviridenko for thoughts. |
@ronaldtse approach looks good to me. We should also link from releases to this page (or the key file directly). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, thanks!
Thanks @ribose-jeffreylau @ni4 ! |
Has anyone actually tried to verify these signatures using provided key? :) |
|
And who controls secret part of this signing key and where is it stored? |
@ribose-jeffreylau Looks like you used other subkey for signing, with fingerprint |
I think we need more checks in place... maybe something like a cron job (on GHA) to check the validity of release signatures every day or so. @antonsviridenko Yes, I tried and they Worked On My Machine (tm), just didn't realize I used a similar-looking but different key :p The secret key is controlled by Ribose, which includes Ron and me. @ni4 Thanks! That looks like it! I've replaced all signatures now... |
@ribose-jeffreylau Thanks, now things work as expected! |
Fixes #43
Related to rnpgp/rnp#1586