public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: R0b0t1 <r030t1@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Securely deletion of an HDD
Date: Sun, 12 Jul 2015 17:22:47 -0500	[thread overview]
Message-ID: <CAAD4mYiZqw17XyBw6EZ1u8QEJ-HWOYS=zdaVSrKcHyKUa_2Msw@mail.gmail.com> (raw)
In-Reply-To: <CAGfcS_k8d2b3FPJVS80j5KJY6mqTX1sObCJSZdM0QbsdKNfPWg@mail.gmail.com>

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

@topic: I would strongly suggest using a hardware key that also utilizes a
passphrase. To delete, remove the key and/or don't tell anyone the
passphrase. If you need to destroy a platter drive take it apart and sand
the platters (probably the easiest). If it's solid state heat the drive
over 150C-250C for an extended period of time or mechanically destroy the
chips.


>It contains no theoretical arguments against the possibility of data
recovery.

The superparmagnetic limit sets the upper bound for storage density. It is
impossible to store information inside the grain of a metal because it acts
as if the magnetic moment is the sum of all of the atoms in the grain. At
this size, the polarity of the magnet can randomly flip directions
depending on the temperature. For ~2005 drives that was about 1Tbit/in^2
with ~850Gbit/in^2 used. Newer drives continue to have higher numbers but
unless the efficiency drops there is not enough room to shadow all the data
(you will need to calculate or find these numbers for each drive you are
interested in). At best you could hope to recover some portion of it with
magnetic force microscopy, which you can/should assume will read back at
the maximum density available on the medium.

But, simpler: if you combine a random stream of data with what is on the
drive, the result looks just like random data. You need only overwrite the
drive once.

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

  parent reply	other threads:[~2015-07-12 22:22 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 [this message]
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
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='CAAD4mYiZqw17XyBw6EZ1u8QEJ-HWOYS=zdaVSrKcHyKUa_2Msw@mail.gmail.com' \
    --to=r030t1@gmail.com \
    --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