From: "Luke-Jr" <luke@dashjr.org>
To: Douglas Huff <dhuff@jrbobdobbs.org>
Date: Tue, 13 Sep 2011 12:53:40 -0400
User-Agent: KMail/1.13.7 (Linux/2.6.39-gentoo; KDE/4.6.5; x86_64; ; )
References: <CABsx9T1SeEFkZkTfB_3Cy=iSms_2burxAo4bRdO-YJwHY7B8Ow@mail.gmail.com>
	<201109131240.26029.luke@dashjr.org>
	<CAPiTikUNHwVGi2bc8HrPi42E=9MpA4QvJv5dDFJGKFrAJWwW=w@mail.gmail.com>
In-Reply-To: <CAPiTikUNHwVGi2bc8HrPi42E=9MpA4QvJv5dDFJGKFrAJWwW=w@mail.gmail.com>
MIME-Version: 1.0
Content-Type: Text/Plain;
  charset="iso-8859-15"
Content-Transfer-Encoding: 7bit
Message-Id: <201109131253.43617.luke@dashjr.org>
Cc: bitcoin-development@lists.sourceforge.net
Subject: Re: [Bitcoin-development] Project status
Precedence: list

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.