Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

FR: hardware wallet support for storing the master key #11683

Open
EDmitry opened this issue Dec 18, 2019 · 1 comment
Open

FR: hardware wallet support for storing the master key #11683

EDmitry opened this issue Dec 18, 2019 · 1 comment
Labels
A-E2EE O-Uncommon Most users are unlikely to come across this or unexpected workflow T-Enhancement

Comments

@EDmitry
Copy link

EDmitry commented Dec 18, 2019

Is your suggestion related to a problem? Please describe.
With MSC1756 the master key becomes incredibly valuable. It would be nice to store it entirely separate from the computer where Riot is running.

Describe the solution you'd like
A few of existing hardware bitcoin wallets (most notably Trezor, since it's open hardware/software) support deriving Ed25519 keys from the mnemonic seed for GPG signing/encryption. It would be great if these hardware devices could be used to sign self-signing/user-signing keys. Or perhaps all three keys could be generated (derived) by the device.

Describe alternatives you've considered
Storing the key on Yubikey/Flashdrive. If flash drive is used, the key will have to be copied on the computer for signing operations to be performed. Yubikey can sign/encrypt on the device itself, but if Yubikey is lost, the key is lost as well. Trezor and other mnemonic-based wallets provide an ability to recover keys if the original mnemonic was backed up.

Additional context
https://github.com/romanz/trezor-agent — reference project. Handles communication with hardware wallets and interaction with keys, stored on the device, exposes GPG functionality.

https://www.google.com/amp/s/amp.reddit.com/r/TREZOR/comments/7du53z/pythontrezor_ed25519_signing/ — a bit of random information to give a basic understanding of how the signing API works.

@peterclemenko
Copy link

I'd like to see this as well

@SimonBrandner SimonBrandner added A-E2EE O-Uncommon Most users are unlikely to come across this or unexpected workflow labels Mar 27, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-E2EE O-Uncommon Most users are unlikely to come across this or unexpected workflow T-Enhancement
Projects
None yet
Development

No branches or pull requests

4 participants
@EDmitry @peterclemenko @SimonBrandner and others