Add new device should NOT rely only on existing device…
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 9.2k
- Forks
- 1.3k
- Avg merge
- 12h 58m
- Merged PRs (30d)
- 56
Description
Hello,
I wanted to add a new device to my keybase account, having already added the one at my office. A bit disappointing: in order to add my home laptop, I have to access my workstation at the office… Having my gpg private key at hand should be more than enough to prove myself, I think.
Hence, allowing to have a "local" way to prove "I'm me", like signing something as we do for all the other proofs might allow people to NOT have to transport all their devices in order to simply add them.
Thank you!
Cheers,
C.
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 issue names no files, tests, or entry points. Start by locating the device-add flow and the existing proof-signing or GPG identity logic; done would mean supporting a local identity proof without requiring access to an existing device, with security behavior and tests defined.
Written by the indexing model from the issue text.
Assessment
- Domain
- authentication, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100