1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
|
Received: from sog-mx-2.v43.ch3.sourceforge.com ([172.29.43.192]
helo=mx.sourceforge.net)
by sfs-ml-2.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <mith@jrbobdobbs.org>) id 1R3XER-0001jq-FL
for bitcoin-development@lists.sourceforge.net;
Tue, 13 Sep 2011 17:57:15 +0000
X-ACL-Warn:
Received: from mail-ey0-f175.google.com ([209.85.215.175])
by sog-mx-2.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1R3XEP-0007Dm-6X
for bitcoin-development@lists.sourceforge.net;
Tue, 13 Sep 2011 17:57:15 +0000
Received: by eya25 with SMTP id 25so447294eya.34
for <bitcoin-development@lists.sourceforge.net>;
Tue, 13 Sep 2011 10:57:06 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.14.3.196 with SMTP id 44mr456421eeh.155.1315932538559; Tue, 13
Sep 2011 09:48:58 -0700 (PDT)
Sender: mith@jrbobdobbs.org
Received: by 10.14.186.136 with HTTP; Tue, 13 Sep 2011 09:48:58 -0700 (PDT)
Received: by 10.14.186.136 with HTTP; Tue, 13 Sep 2011 09:48:58 -0700 (PDT)
In-Reply-To: <201109131240.26029.luke@dashjr.org>
References: <CABsx9T1SeEFkZkTfB_3Cy=iSms_2burxAo4bRdO-YJwHY7B8Ow@mail.gmail.com>
<201109131240.26029.luke@dashjr.org>
Date: Tue, 13 Sep 2011 11:48:58 -0500
X-Google-Sender-Auth: Cgg3iT1C4RfPC3OIAkJSsQ291rI
Message-ID: <CAPiTikUNHwVGi2bc8HrPi42E=9MpA4QvJv5dDFJGKFrAJWwW=w@mail.gmail.com>
From: Douglas Huff <dhuff@jrbobdobbs.org>
To: Luke-Jr <luke@dashjr.org>
Content-Type: multipart/alternative; boundary=0016364c723f825b8204acd56bf5
X-Spam-Score: 1.0 (+)
X-Spam-Report: Spam Filtering performed by mx.sourceforge.net.
See http://spamassassin.org/tag/ for more details.
1.0 HTML_MESSAGE BODY: HTML included in message
X-Headers-End: 1R3XEP-0007Dm-6X
Cc: bitcoin-development@lists.sourceforge.net
Subject: Re: [Bitcoin-development] Project status
X-BeenThere: bitcoin-development@lists.sourceforge.net
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <bitcoin-development.lists.sourceforge.net>
List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
<mailto:bitcoin-development-request@lists.sourceforge.net?subject=unsubscribe>
List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum_name=bitcoin-development>
List-Post: <mailto:bitcoin-development@lists.sourceforge.net>
List-Help: <mailto:bitcoin-development-request@lists.sourceforge.net?subject=help>
List-Subscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
<mailto:bitcoin-development-request@lists.sourceforge.net?subject=subscribe>
X-List-Received-Date: Tue, 13 Sep 2011 17:57:15 -0000
--0016364c723f825b8204acd56bf5
Content-Type: text/plain; charset=ISO-8859-1
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.
It is close to impossible to reliably delete such data, moreso on usb keys
than ssd, short of absolute physical destruction and noone should be
recommending this. Ever.
--0016364c723f825b8204acd56bf5
Content-Type: text/html; charset=ISO-8859-1
<p>On Sep 13, 2011 11:40 AM, "Luke-Jr" <<a href="mailto:luke@dashjr.org">luke@dashjr.org</a>> wrote:<br>
> Once created, they must submit the<br>
> transaction to a staff member with the proper authority to bring it to the<br>
> offline transaction-signing wallet (on a USB key), where it is signed, and<br>
> returned to this third wallet.</p>
<p>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.</p>
<p>It is close to impossible to reliably delete such data, moreso on usb keys than ssd, short of absolute physical destruction and noone should be recommending this. Ever.</p>
--0016364c723f825b8204acd56bf5--
|
