UI request: Warn people that they should create a paper key when starting out.
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 9.2k
- Forks
- 1.3k
- Avg merge
- 12h 58m
- Merged PRs (30d)
- 56
Description
I'm helping a friend get up to speed with the Windows port of Keybase, and we ran into a workflow misfeature that resulted in an account reset.
Installing Keybase, generating the initial key, and following each other went fine. Then the hard drive crashed. One new drive, OS reinstall, and Keybase reinstallation later and he was unable to reprovision his laptop using Keybase even though he was able to log into the website (hence, the account reset).
When Keybase is first installed, it might be a good idea to tell the user to generate and safely store a paperkey to avoid this particular class of failure mode.
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 locating the Windows installation and initial-key onboarding flow in the Keybase client. Confirm where a first-time user can be warned to generate and safely store a paper key; done means the warning appears during initial setup and addresses recovery after device loss.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- authentication, operating-systems
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100