keybase login chooses disabled key
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 9.2k
- Forks
- 1.3k
- Avg merge
- 12h 58m
- Merged PRs (30d)
- 56
Description
on arch linux, when I try to login for the first time, keybase will not let me choose which key and for some reason the key it tries to use is an old, disabled one for which I no longer have the passphrase. Is there anything I can do about this? Since I no longer have the passphrase, I cannot easily delete the key.
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
Reproduce the first-login flow on Arch Linux and inspect how the Keybase client selects an existing key, focusing on why a disabled key is chosen before the user can choose one. Done means a user without the old key's passphrase can complete login by selecting an available valid key or otherwise avoiding the disabled key.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- arch-linux, go
- Domain
- authentication, operating-systems, security
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100