keybase login fails with: no auth system available; consider upgrading your client if it's old (error 100)
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 9.2k
- Forks
- 1.3k
- Avg merge
- 12h 58m
- Merged PRs (30d)
- 56
Description
I upgraded from 1.0.15 to 1.0.16. It couldn't start because it couldn't find my config.json or secretkeys.$USER.mpack (they were in my home directory for some reason). After restoring those files in .config/keybase/ , I tried to log in and got "no auth system available".
my log id: 19df5bf4f756c26c04fc2b1c
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 reviewing the 1.0.15-to-1.0.16 upgrade behavior and the reported log id 19df5bf4f756c26c04fc2b1c. Check how config.json and secretkeys.$USER.mpack are located under .config/keybase/, then investigate the resulting “no auth system available” login failure. Done means the client can start and log in after the upgrade without restoring those files manually.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- authentication
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100