keybase / keybase/client

Support adding security key as new kind of "device"

Open
#17,047 7 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Go
Stars
9.2k
Forks
1.3k
Avg merge
12h 58m
Merged PRs (30d)
56

Description

I would like to be able to add a Security Key (e.g. Yubikey or similar U2F key) as a "device" in keybase.
The key could be enrolled via the desktop app or the mobile app or perhaps even the Keybase website (possibly using the Webauthn standard).

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reviewing how Keybase currently enrolls devices in the desktop and mobile apps, and whether the website has a device-enrollment path. Read the WebAuthn standard to define the security-key flow and its platform requirements. Done means a security key can be enrolled as a device through an agreed client path and used consistently afterward.

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
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.