Since that lets you generate keys on the hardware wallet, back up the high entropy recovery seed as a phrase, verify you backed it up correctly and then if you need to recover on a new device you can enter it directly onto a new hardware wallet without exposing it to a computer.
-
-
Replying to @DanielMicay @nitrokey and
The traditional approach is good if you have existing SSH and GPG keys that need to be moved onto an HSM. I'll definitely prefer the deterministic wallet approach for new keys though. It's not that bad to migrate to new SSH keys but GPG tends to make rotating keys very painful.
1 reply 0 retweets 0 likes -
Replying to @DanielMicay @nitrokey and
Signing keys for firmware usually can't be rotated at all since they're burned into fuses so that's another case where a more traditional HSM is the best option since existing keys need to be migrated. Android app signing keys were similar, but they've finally added key rotation.
1 reply 0 retweets 0 likes -
I really like the
@nitrokey - code has been audited by@cure53berlin so that is a huge plus in my book, and there's tons of eyes on the code as@linuxfoundation maintainers use them as well. Nothing against@Trezor - they are an incredible company and I use their devices for btc2 replies 0 retweets 0 likes -
Replying to @RobertSpigler @DanielMicay and
Entering a password on device (like you mention) is a big plus for Trezor though, as is their open CPU. (What smart card does nitrokey use?)
1 reply 0 retweets 0 likes -
Replying to @RobertSpigler @nitrokey and
I find the recovery model to be the biggest advantage of the approach based on deterministic wallet design. The hardware wallet generates a high entropy seed, displays it as a recovery phrase and you can write it down, store it and recover without exposing it to the computer.
2 replies 1 retweet 1 like -
Replying to @DanielMicay @RobertSpigler and
for the record, i actually wrote an implementation of OpenPGP smartcard emulation (á la Gnuk) for the Trezor One a few years back. the code is still in a branch on my GitHub, but never got around to refactoring and doing security review.
1 reply 0 retweets 1 like -
Replying to @saleemrash1d @spudowiar and
It's the approach to the security model including recovery, passphrases and on-device input / confirmations that I like rather than the hardware though. I don't want to import keys generated on my computer or expose them to it from cold storage if I need to do recovery, etc.
3 replies 0 retweets 1 like -
Replying to @DanielMicay @RobertSpigler and
it was an addition to the existing firmware and used keys generated from the recovery seed (with PIN and passphrase support)
2 replies 0 retweets 2 likes -
Replying to @saleemrash1d @spudowiar and
Ah, I misunderstood what you meant. I'm successfully using their current SSH support already and I plan on using their GPG support to replace my existing aging key which has been exposed to multiple generations of laptops and workstations. GPG makes key rotation horrible though.
1 reply 1 retweet 0 likes
the aim was to eventually implement full smartcard support, so anything that supported PKCS#11 could magically benefit from the recovery seed approach :)
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.