keybase / keybase/keybase-issues
Changed public keys don't seem to be replaced by the command line client.
- Dominant language
- No language data
- Stars
- 899
- Forks
- 40
- PR merge metrics
- No merged PRs in 30d
Description
Earlier I had accidentally uploaded a public key with an expired subkey to keybase, which my friend had downloaded. Even after I uploaded the fixed version of the public key, my friend could not encrypt messages for me with 'keybase encrypt' without first running gpg --delete-keys on it.
I'm pretty sure he also tried running keybase id and keybase track.
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by reproducing the reported behavior with the keybase command line client: upload a corrected public key, then try keybase encrypt, keybase id, and keybase track using a client that already has the old key. Compare this with the result after running gpg --delete-keys. Done means the client recognizes the replacement without requiring manual deletion.
Written by the indexing model from the issue text.
Assessment
- Domain
- cli, security
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100