Received: from sog-mx-1.v43.ch3.sourceforge.com ([172.29.43.191] helo=mx.sourceforge.net) by sfs-ml-2.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1QiDUx-0000Tm-E7 for bitcoin-development@lists.sourceforge.net; Sat, 16 Jul 2011 22:38:11 +0000 Received-SPF: pass (sog-mx-1.v43.ch3.sourceforge.com: domain of gmail.com designates 209.85.161.47 as permitted sender) client-ip=209.85.161.47; envelope-from=ahbritto@gmail.com; helo=mail-fx0-f47.google.com; Received: from mail-fx0-f47.google.com ([209.85.161.47]) by sog-mx-1.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1QiDUw-00066Y-A9 for bitcoin-development@lists.sourceforge.net; Sat, 16 Jul 2011 22:38:11 +0000 Received: by fxg11 with SMTP id 11so5078798fxg.34 for ; Sat, 16 Jul 2011 15:38:04 -0700 (PDT) MIME-Version: 1.0 Received: by 10.223.159.8 with SMTP id h8mr7628867fax.3.1310855882375; Sat, 16 Jul 2011 15:38:02 -0700 (PDT) Received: by 10.223.114.197 with HTTP; Sat, 16 Jul 2011 15:38:02 -0700 (PDT) In-Reply-To: <201107142250.44189.luke@dashjr.org> References: <201107142250.44189.luke@dashjr.org> Date: Sat, 16 Jul 2011 15:38:02 -0700 Message-ID: From: Arthur Britto To: Luke-Jr Content-Type: multipart/alternative; boundary=002354186d403880a404a8376b05 X-Spam-Score: -0.6 (/) X-Spam-Report: Spam Filtering performed by mx.sourceforge.net. See http://spamassassin.org/tag/ for more details. -1.5 SPF_CHECK_PASS SPF reports sender host as permitted sender for sender-domain 0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider (ahbritto[at]gmail.com) -0.0 SPF_PASS SPF: sender matches SPF record 1.0 HTML_MESSAGE BODY: HTML included in message -0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from author's domain 0.1 DKIM_SIGNED Message has a DKIM or DK signature, not necessarily valid -0.1 DKIM_VALID Message has at least one valid DKIM or DK signature X-Headers-End: 1QiDUw-00066Y-A9 Cc: bitcoin-development@lists.sourceforge.net Subject: Re: [Bitcoin-development] Wallet encryption migration X-BeenThere: bitcoin-development@lists.sourceforge.net X-Mailman-Version: 2.1.9 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 16 Jul 2011 22:38:11 -0000 --002354186d403880a404a8376b05 Content-Type: text/plain; charset=ISO-8859-1 On Thu, Jul 14, 2011 at 7:50 PM, Luke-Jr wrote: > Just wanted to get these suggestions out here: > 1. Write over the old, unencrypted wallet.dat a couple of times with > pseudo- > random data in an attempt to secure-delete it. > Writing zeros just once should be sufficient: http://cmrr.ucsd.edu/people/Hughes/DataSanitizationTutorial.pdf -Arthur --002354186d403880a404a8376b05 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable On Thu, Jul 14, 2011 at 7:50 PM, Luke-Jr=A0<luke@dashjr.org>=A0wrote:
Just wanted to get these suggestions out here:
1. Write over the old, un= encrypted wallet.dat a couple of times with pseudo-
=A0 random data in a= n attempt to secure-delete it.
=A0
Writing zeros just once should be=A0sufficient:

-Arthur

 --002354186d403880a404a8376b05--