keybase / keybase/keybase-issues
error: signature verification failed
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 899
- Forks
- 40
- PR merge metrics
- No merged PRs in 30d
Description
Getting this error whenever I try to prove or id anything.
warn: gpg: Signature made Tue Sep 23 17:18:59 2014 SGT using RSA key ID 8466A8D6
warn: gpg: Can't check signature: No public key
I am not sure where I messed up. I believed when I first created my keybase account, I had to add a subkey to my old pgp key. I had verified myself then on github, etc.
When I moved machines I couldn't find this new updated key (with the subkey). So I used the original key and added new subkeys to it. I updated the public keys on my keybase account keybase push --update. But now whenever I try to id something, I get this error. Is that old lost subkey still being used somewhere?
Contributor guide
No contributing guide indexed for this repository
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
No source files or tests are named. Start by reproducing the failure with the prove and id commands, then inspect the key state after keybase push --update, including whether the missing public key is the old lost subkey. Done means identifying the key being requested and restoring successful signature verification.
Written by the indexing model from the issue text.
Assessment
- Domain
- cryptography, security
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100