public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: "Luke-Jr" <luke@dashjr•org>
To: Douglas Huff <dhuff@jrbobdobbs•org>
Cc: bitcoin-development@lists•sourceforge.net
Subject: Re: [Bitcoin-development] Project status
Date: Tue, 13 Sep 2011 12:53:40 -0400	[thread overview]
Message-ID: <201109131253.43617.luke@dashjr.org> (raw)
In-Reply-To: <CAPiTikUNHwVGi2bc8HrPi42E=9MpA4QvJv5dDFJGKFrAJWwW=w@mail.gmail.com>

On Tuesday, September 13, 2011 12:48:58 PM Douglas Huff wrote:
> On Sep 13, 2011 11:40 AM, "Luke-Jr" <luke@dashjr•org> wrote:
> > Once created, they must submit the
> > transaction to a staff member with the proper authority to bring it to
> > the offline transaction-signing wallet (on a USB key), where it is
> > signed, and returned to this third wallet.
> 
> I agreed up to this point. Private keys should not be stored on nand.
> Please look in to the data recovery clusterfuck nand creates when
> concerning sensitive data.

I didn't recommend storing private keys on NAND. The USB stick would contain 
only the transaction that it being approved, and the offline-signing-wallet 
would sign it. The USB stick then contains only the signed transaction to be 
returned to an online node. At no time does it contain keys.



  reply	other threads:[~2011-09-13 16:53 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-13 14:43 Gavin Andresen
2011-09-13 16:40 ` Luke-Jr
2011-09-13 16:48   ` Douglas Huff
2011-09-13 16:53     ` Luke-Jr [this message]
  -- strict thread matches above, loose matches on Subject: below --
2011-08-29 20:10 Gavin Andresen
2011-08-29 20:15 ` Luke-Jr
2011-08-30  1:09 ` Matt Corallo

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=201109131253.43617.luke@dashjr.org \
    --to=luke@dashjr$(echo .)org \
    --cc=bitcoin-development@lists$(echo .)sourceforge.net \
    --cc=dhuff@jrbobdobbs$(echo .)org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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