keybase / keybase/keybase-issues
Can't log in via CLI
- Dominant language
- No language data
- Stars
- 899
- Forks
- 40
- PR merge metrics
- No merged PRs in 30d
Description
I'm in a bit of an odd situation:
1. Migrated from Windows to Linux, thought I copied the correct GPG keys over but may not have. In any case, I copied from Windows a 4096-bit RSA key that I can unlock with my passphrase, but there are so many Windows Gnupg installers that maybe I copied from the wrong folder under ~/AppData/Roaming/Can/We/Possibly/Make/This/More/Convoluted/GnuPG. :)
2. In either case, I want to replace my 4096-bit RSA key which I verified on Keybase with a 2048-bit RSA key that will work with my Yubikey Neo. I only used the key to sign Sandstorm packages anyway so it isn't a huge deal to me how the replacement occurs.
I'm on Fedora, and have installed your latest 64-bit CLI as of this morning. I've tried every Keybase login method except paper-based, which may not work for me since I'm blind.
## Existing device
This method hangs for a few seconds, then always times out when I run `keybase device add`. This is on Fedora 23.
## Passphrase
If I use my passphrase, I get:
```
▶ ERROR No synced secret PGP key stored on keybase.io for ndarilek; please try logging in via GPG, an existing device, or a paper key (error 901
```
Given that I no longer seem to have the key I thought I used on Keybase, I'm not sure how else to recover my account if I can't use the passphrase I _do_ have.
What should I try next? There's an issue with this error message that has something like 50 comments, but that's a lot to pour through just to log in.
Thanks.
Contributor guide
No contributing guide indexed for this repository
Research direction
Start with the `keybase device add` command and the passphrase login path that produces error 901; the issue names no source file or test. Reproduce the timeout and missing-key response on Fedora, then define done as a clear recovery path for users without an existing device or synced PGP key.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cli, linux
- Domain
- authentication, cli
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100