Login Issues
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 9.2k
- Forks
- 1.3k
- Avg merge
- 12h 58m
- Merged PRs (30d)
- 56
Description
Hi there,
I can’t seem to find any way to reach out for support, so I’m blindly trying here.
I have been a keybase.io member for a looong time and way back when I chose to keep my private key in the system so I could use the browser interface. At some point I installed keybase on my phone, but never really used it there. Since that install I’ve upgraded phones and apparently the device key associated with it was lost.
Now, I’d like to install and use the apps on my phone and on my Mac, but, apparently it appears I’m required to authenticate with that now obsolete phone install before I can login with the apps or even on the command line. I can login to the website without issue, so I’m frustrated that I can not authenticate my devices, and I’m really not interested (nor do I think it is required) in resetting my keys.
Your help would be greatly appreciated.
Thank you,
Levi
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
The report identifies no source files, tests, or entry points to inspect. Begin by determining which authentication and device-key flow handles existing web users whose old phone device key is unavailable; done would require a decided, tested way to authenticate the Mac, phone, or command-line clients without unnecessarily resetting keys.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- authentication, cli, desktop, mobile
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 15/100