Changing PGP key keeps the old verification (with old PGP key) still valid
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'm not sure if it's a bug or not, but I've recently changed my PGP key (and also added a second one I use at work) and I've noticed that if I click on my website and GitHub/Gist proofs they still show the old validation, for example:
I hereby claim:
* I am an admin of https://www.andreagrandi.it
* I am andreagrandi (https://keybase.io/andreagrandi) on keybase.
* I have a public key with fingerprint 7238 74F6 886D 5994 323F 1781 8CFB 47AD C384 F0CC
but that's the PGP id of my old key, not the ID of the current one. Keybase client doesn't refresh these information and show these proofs as still valid.
I can manually revoke and re-add these proofs, it's not a big deal for me, but other users may be tricked to think I have a certain number of proofs while instead they are related to the old PGP key.
Cheers
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 the issue after changing or adding a PGP key, then inspect the proof verification flow in the Keybase client. Confirm whether existing website and GitHub/Gist proofs continue to validate against the old fingerprint. Done means proofs no longer retain misleading validation after the associated key changes, with existing proof behavior preserved.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- cryptography, security
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100