WARNING No key matching fingerprint found in the GPG keyring.
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 9.2k
- Forks
- 1.3k
- Avg merge
- 12h 58m
- Merged PRs (30d)
- 56
Description
Hi,
I am not able to keybase pgp update my key after adding a new uid, similar to -
https://github.com/keybase/keybase-issues/issues/2797. Any help would be appreciated.
Current key: https://gist.github.com/coop/34b8df3c73ad855691a6b475077d8bee
Keybase: https://keybase.io/timcooper
$ keybase pgp update
▶ WARNING No key matching fingerprint 4f0f5ea06fc8f50fa2fce6afc21a7faebb331c5b found in the GPG keyring.
Tim
my log id: ceeac2394f9b89416791fc1c
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
Start by reproducing keybase pgp update with the fingerprint and key details in the issue, then compare the behavior with issue 2797. Use the supplied log ID and GPG key information to trace why the fingerprint is not found; done means the command handles this updated-UID case without the warning.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- cli, cryptography
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100