From: Arno Wagner <arno@wagner.name>
To: dm-crypt@saout.de
Subject: Re: [dm-crypt] (OT) Secure data wipe
Date: Sun, 9 Dec 2012 17:38:29 +0100 [thread overview]
Message-ID: <20121209163828.GA17651@tansi.org> (raw)
In-Reply-To: <50C4A4A1.4090003@babioch.de>
On Sun, Dec 09, 2012 at 03:48:01PM +0100, Karol Babioch wrote:
> Hi,
>
> Am 09.12.2012 13:26, schrieb Javier Juan Martínez Cabezón:
> > overwritting unallocated space several times
>
> this basically is a myth. Overwriting the whole drive just one time will
> make any recovery practically impossible, see [1].
>
> The "multiple times" aspect to my best knowledge originates from the
> good old days, where the density of tracks on floppies wasn't as high as
> it is with todays hard drives and it was possible to "miss" the track by
> some amount.
Actually, the background is as follows (track density, bit-density,
etc, are secondary): A magnetic medium has a s/n (signal-to-noise)
ratio and a ratio an overwrite weakens an older singnal by.
As a simplified example, you may get 10mV of noise and a maximum
signal of 100mV. Then you have signal-to-noise of 10:1. An overwrite
always weakens the original signal, bit it is still there. Say, it
gets weakened by a factor of 3. Then you have the n-th (overwriting)
signal at 100mV singal strengt, and the n-1 (older) signal at
30mV. You can hence read signal n, reconstruct (in analog) how it
was written, subtract it from an analog media read and get the
n-1 signal.
For floppies, I did some measurements 20 years back, and I
could clearly see the n-1 signal and maybe the n-2 signal
would also have been possible to read. The s/n ratio was
was very high.
For modern disks, the s/n ratio is low enough that the n-1
signal vanishes in the noise after a single overwrite. The
background is that modern electronics can read the signal
almost perfectly in analog and modern signal processors can
do all the math needed to get the maximum possible decoding
quality in real-time. If the HDD manufacturers could cram
in more bits, they would, but the surfaces can simply not
hold them reliably. They certainly cannot hold twice as
much data, as in a signal and the overwritten signal from
before. Ordinary 1.44MB floppy disks coukld be made to
hold > 20MB with special equipment back in the day.
Rumour has it that after one overwrite you may get lucky and
pull off single bits, like occasionally recognizing a keyword,
using very expensive equipment and a lot of time. For encrypted
data that is pretty worthless.
Arno
--
Arno Wagner, Dr. sc. techn., Dipl. Inform., Email: arno@wagner.name
GnuPG: ID: CB5D9718 FP: 12D6 C03B 1B30 33BB 13CF B774 E35C 5FA1 CB5D 9718
----
One of the painful things about our time is that those who feel certainty
are stupid, and those with any imagination and understanding are filled
with doubt and indecision. -- Bertrand Russell
next prev parent reply other threads:[~2012-12-09 16:37 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-09 11:20 [dm-crypt] (OT) Secure data wipe jugree
2012-12-09 12:26 ` Javier Juan Martínez Cabezón
2012-12-09 14:48 ` Karol Babioch
2012-12-09 15:49 ` Javier Juan Martínez Cabezón
2012-12-09 16:38 ` Arno Wagner [this message]
2012-12-09 14:55 ` Karol Babioch
2012-12-09 16:18 ` Arno Wagner
2012-12-11 8:39 ` Roscoe
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=20121209163828.GA17651@tansi.org \
--to=arno@wagner.name \
--cc=dm-crypt@saout.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.