public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Marc Joliet <marcec@gmx.de>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Securely deletion of an HDD
Date: Mon, 13 Jul 2015 13:04:18 +0200	[thread overview]
Message-ID: <20150713130418.659d03e0@thetick> (raw)
In-Reply-To: <55A296A7.5070301@googlemail.com>

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

Am Sun, 12 Jul 2015 18:32:39 +0200
schrieb Volker Armin Hemmann <volkerarmin@googlemail.com>:

> Am 12.07.2015 um 14:35 schrieb Marc Joliet:
> > Hi,
> >
> > I have to failed drives that I want to give away for recycling purposes, but
> > want to be sure to properly clear them first.  They used be part of a btrfs
> > RAID10 array, but needed to be replaced (with "btrfs replace").  (In the
> > meantime I converted the array to RAID1 with only two drives.)
> >
> > My question is how precisely the disks should be cleared.  From various sources
> > I know that overwriting them with random data a few times is enough to render
> > old versions of data unreadable.  I'm guessing 3 times ought to be enough, but
> > maybe even that small amount is overly paranoid these days?
> >
> > As to the actual command, I would suspect something like "dd if=/dev/urandom
> > of=/dev/sdx bs=4096" should suffice, and according to
> > https://wiki.archlinux.org/index.php/Random_number_generation#.2Fdev.2Furandom,
> > /dev/urandom ought to be random enough for this task.  Or are cat/cp that much
> > faster?
> >
> > Any thoughts?
> >
> > Greetings
> 
> actually 1 time is enough. With zeros. Or ones. Does not matter at all.

If you look at my initial response to Rich, I already concluded that "one time
is enough", although I'm going to stick with whatever random data shred(1)
produces.

-- 
Marc Joliet
--
"People who think they know everything really annoy those of us who know we
don't" - Bjarne Stroustrup

[-- Attachment #2: Digitale Signatur von OpenPGP --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

  parent reply	other threads:[~2015-07-13 11:04 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-12 12:35 [gentoo-user] Securely deletion of an HDD Marc Joliet
2015-07-12 12:48 ` Rich Freeman
2015-07-12 14:39   ` Marc Joliet
2015-07-12 19:21     ` Rich Freeman
2015-07-12 19:42       ` Neil Bothwick
2015-07-13 15:03     ` [gentoo-user] " Grant Edwards
2015-07-13 17:20       ` Marc Joliet
2015-07-12 13:00 ` [gentoo-user] " Mick
2015-07-12 13:22   ` Francisco Ares
2015-07-12 16:32 ` Volker Armin Hemmann
2015-07-12 19:14   ` Rich Freeman
2015-07-12 20:43     ` Volker Armin Hemmann
2015-07-12 21:10       ` Rich Freeman
2015-07-12 21:20         ` Volker Armin Hemmann
2015-07-12 21:30           ` Rich Freeman
2015-07-13  8:05             ` Volker Armin Hemmann
2015-07-13 11:03               ` Rich Freeman
2015-07-12 22:22         ` R0b0t1
2015-07-13  0:18           ` Rich Freeman
2015-07-13  1:50             ` Thomas Mueller
2015-07-13  8:09               ` Volker Armin Hemmann
2015-07-13 10:58               ` Marc Joliet
2015-07-14 22:21             ` R0b0t1
2015-07-15 12:29               ` Rich Freeman
2015-07-13 10:54       ` Marc Joliet
2015-07-13 11:04   ` Marc Joliet [this message]
2015-07-13  9:53 ` Joerg Schilling

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=20150713130418.659d03e0@thetick \
    --to=marcec@gmx.de \
    --cc=gentoo-user@lists.gentoo.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