keybase / keybase/keybase-issues
Paper key generation is confusing
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 899
- Forks
- 40
- PR merge metrics
- No merged PRs in 30d
Description
Using the Linux GUI, in the paper key generation process, it's not clear:
- Why this is happening
- What the paper key will be used for in the future
- How sensitive the paper key is
Is it equivalent to my keybase account passphrase? Is it equivalent to my GPG passphrase? Is it equivalent to any of my GPG key material? All of this is very unclear. All that's stated is that it's important and I need to write it down.
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 Linux GUI paper key generation flow and its current user-facing explanation. Clarify why the paper key is generated, its future use, its sensitivity, and whether it corresponds to the Keybase passphrase, GPG passphrase, or GPG key material; done means users can distinguish these concepts and know how to handle the paper key.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation, security
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100