public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: devrandom <c1.sf-bitcoin@niftybox.net>
To: Bitcoin-development <bitcoin-development@lists.sourceforge.net>
Subject: [Bitcoin-development] Securing hardware wallets
Date: Sun, 30 Mar 2014 13:12:01 -0700	[thread overview]
Message-ID: <1396210321.27001.39.camel@mimiz> (raw)

I would like to solicit feedback on a whitepaper I wrote about securing
hardware wallets even if the hardware or software is compromised.  Let's
consider turning this into a BIP.

Abstract: With wide adoption hardware wallets present a very tempting
target. Once enough wealth is controlled by a specific hardware wallet
model, attacking the supply chain of the wallet becomes attractive.
Malware could be inserted in hardware or software. The random seed could
be generated in a way that is predictable to the attacker or the seed
could be leaked.

The paper describes a way for a "Warden" computer to manage a hardware
wallet in a way that protects the resulting private keys from
compromise.

https://github.com/devrandom/btc-papers/blob/master/hardware-wallet-security.md

-- 
Miron / devrandom






                 reply	other threads:[~2014-03-30 20:12 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1396210321.27001.39.camel@mimiz \
    --to=c1.sf-bitcoin@niftybox.net \
    --cc=bitcoin-development@lists.sourceforge.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox