Viewing a response to: @heiditravels/why-an-update-can-t-fix-trezor-and-keepkey-vulnerability-and-what-you-can-do-about-it
There's also Bitfi, which doesn't store your keys, but instead generates them every time from your passphrase. The problem with Bitfi is that it has a screen that can be hacked, so you don't know if what the device is telling you is the correct address actually is generated from the device or maliciously swapped with a hackers substituted address. If Trezor or Ledger could follow Bitfi's seed generating practices, but keep their separate screen, that would be the best of both worlds.
author | zoidsoft |
---|---|
permlink | pv249h |
category | trezor |
json_metadata | {"tags":["trezor"],"app":"steemit/0.1"} |
created | 2019-07-22 18:48:54 |
last_update | 2019-07-22 18:48:54 |
depth | 1 |
children | 0 |
last_payout | 2019-07-29 18:48:54 |
cashout_time | 1969-12-31 23:59:59 |
total_payout_value | 0.000 HBD |
curator_payout_value | 0.000 HBD |
pending_payout_value | 0.000 HBD |
promoted | 0.000 HBD |
body_length | 490 |
author_reputation | 17,657,439,386,076 |
root_title | "Why an Update Can't Fix Trezor and KeepKey Vulnerability (And What You Can Do About It)" |
beneficiaries | [] |
max_accepted_payout | 1,000,000.000 HBD |
percent_hbd | 10,000 |
post_id | 88,617,311 |
net_rshares | 0 |