keybase / keybase/client

Feature Request: Ledger Nano S

Open
#5,816 5 comments 12 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

The Ledger Nano S is a hardware security device that does secure key management for a variety of crypto apps. For example, I am using it both as a bitcoin signer and as a U2F login device. I'd love to keep a keybase key in there instead of on my computer or on paper. https://www.ledgerwallet.com/products/ledger-nano-s

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 the Ledger Nano S product information and the Keybase client’s existing key-management behavior. The issue names no source files, tests, or entry points; done would mean defining and implementing Ledger-backed storage for a Keybase key, with the expected signing and retrieval behavior documented and tested.

Written by the indexing model from the issue text.

Assessment

Tech stack
go
Domain
cryptography, 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.