-
Notifications
You must be signed in to change notification settings - Fork 38
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
unable to sign public key #247
Comments
Thanks, I'll try to take a look tonight. Can you send me the signature you tried to upload too? Many thanks. It's 100% public, feel free to post it into this issue. |
|
Gracias. I'm in the middle of something now, I'll take a look when I hit a good stopping point. |
So I see what's going on, though I'm not quite sure what to do. Your key lacks any key flags, so our software can't figure out how to verify the given signature. I guess we can take the attitude that the primary key should always be used for verification purposes... |
Cool. This could date from the fact that the current only ID on the keychain was a secondary (actually, tertiary one) and the original was revoked. It may even be that key flags automatically get applied properly now, but I would have done this circa 2001. I can add the flags? |
Hmm, been digging around and my key does appear to have flags on it. When editing:
The |
Oh interesting. There might be a sensible default that gpg is applying or
|
Another theory is that with DSA and ElGamal, it's obvious which key to use for what. I think I have a fix I can roll out for you in an hour or two. |
Ok, fix is live, let me know if you still have problems. Thanks for your feedback! |
Booyah, works! 👍 |
Booyah indeed. Thanks Justin! |
I've tried several times, but I can't get it to work. I get:
My key, if it's useful:
http://pgp.mit.edu/pks/lookup?op=get&search=0xF7877A2BC9C40C31
It has two revoked identities on it (old email addresses), if that helps.
The text was updated successfully, but these errors were encountered: