Account no longer linked?
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 9.2k
- Forks
- 1.3k
- Avg merge
- 12h 58m
- Merged PRs (30d)
- 56
Description
When I first created my Keybase account, I did so with a PGP key -- in the attempt to move things using that key to a new(er) key [to avoid swapping yubikeys as often] I dropped that key, and resubmitted proofs with the new one. That part worked fine.
However, when I look at https://keybase.io/dive/graph, it appears that dive@keybase is no longer connected to any valid keys - only a deleted PGP key.
It's worth noting that keybase encrypt, decrypt, sign, and kbfs functionality seem to be working fine, I can login and logout, etc.
Is this a situation I can recover from or do I need to start over from scratch?
Let me know what other information you need and I'll drop it on KBFS.
my log id: 4b27df897afdfa3203a2371c
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 file, test, or entry point is identified in the report. Start by reviewing the key-linking and proof state associated with log ID 4b27df897afdfa3203a2371c, comparing the deleted PGP key with the submitted replacement. Done means determining whether the account can be recovered or documenting that a restart is required.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- authentication, cryptography, security
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100