public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Arthur Britto <ahbritto@gmail.com>
To: Luke-Jr <luke@dashjr.org>
Cc: bitcoin-development@lists.sourceforge.net
Subject: Re: [Bitcoin-development] Wallet encryption migration
Date: Sat, 16 Jul 2011 15:38:02 -0700	[thread overview]
Message-ID: <CAFjXj6NocN+iPh2hOsRvP63jOc3hgi82RzztByk74rL2hBO3Yw@mail.gmail.com> (raw)
In-Reply-To: <201107142250.44189.luke@dashjr.org>

[-- Attachment #1: Type: text/plain, Size: 370 bytes --]

On Thu, Jul 14, 2011 at 7:50 PM, Luke-Jr <luke@dashjr.org> 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

[-- Attachment #2: Type: text/html, Size: 1013 bytes --]

  reply	other threads:[~2011-07-16 22:38 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-15  2:50 [Bitcoin-development] Wallet encryption migration Luke-Jr
2011-07-16 22:38 ` Arthur Britto [this message]
2011-07-17  8:01 ` Gregory Maxwell

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=CAFjXj6NocN+iPh2hOsRvP63jOc3hgi82RzztByk74rL2hBO3Yw@mail.gmail.com \
    --to=ahbritto@gmail.com \
    --cc=bitcoin-development@lists.sourceforge.net \
    --cc=luke@dashjr.org \
    /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