From: R.E.Wolff@BitWizard.nl (Rogier Wolff)
To: Roy Sigurd Karlsbakk <roy@karlsbakk.net>
Cc: Jens Schmidt <j.schmidt@paradise.net.nz>, linux-kernel@vger.kernel.org
Subject: Re: secure erasure of files?
Date: Tue, 19 Feb 2002 18:32:17 +0100 (MET) [thread overview]
Message-ID: <200202191732.SAA08008@cave.bitwizard.nl> (raw)
In-Reply-To: <20020219.HQ8.97132600@karlsbakk.net> from Roy Sigurd Karlsbakk at "Feb 19, 2002 02:48:45 pm"
Roy Sigurd Karlsbakk wrote:
> What is sure: Ibas does not know any documented methods, scientific
> environments or commercial services that do or demonstrate reading
> of overwritten data.
Ah. Our data-recovery competitor IBAS. Short addition: "Same here".
Wietze Venema, (I'm sure you know what he's famous for) once had a
slide in his show that showed an image of magnetic track that had been
overwritten with new data. You could visually see that the head had
been mis-positioned by about 0.1 track-width, such that the old data
was still visible from below. This would lead you to believe that
possibly your old data could be retrieved.
This is easier said than done. In this case they had been able to
image the patter at over 100 times more resolution than the magnetic
head of the drive. Imaging a whole 10G platter this way would yield
you a few terabytes of data, from which you can try to find the old
data back. Good luck.
Some success is rumored to be able to be achieved by sampling the
normal signal, and then subtracting the "expected signal assuming the
current sequence of bits that was read". That way you might be able to
recover the information that peeks out from below. On the other hand,
the electronics is ALREADY partly doing this to recover the normal
data that is read from the platter...
In practise all this doesn't work: The head will not be mispositioned
0.1 track to the same side during the whole revolution. Thus you will
have parts of the previous data generation peeking out on the left
side for part of the track and data from the generation before on the
other side. Which you will see is not predetermined.
Now, if there are military secrets on the drive, the opponent may want
to acutally go and image the platter, and reconstruct the data on a
bit by bit basis. If you then happen to stumble on just a couple of
"launch codes" or something like that, then "all hell breaks loose".
Thus the chance that this might possibly happen is to be prevented.
Roger.
--
** R.E.Wolff@BitWizard.nl ** http://www.BitWizard.nl/ ** +31-15-2137555 **
*-- BitWizard writes Linux device drivers for any device you may have! --*
* There are old pilots, and there are bold pilots.
* There are also old, bald pilots.
next prev parent reply other threads:[~2002-02-19 17:32 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-19 14:48 secure erasure of files? Roy Sigurd Karlsbakk
2002-02-19 17:32 ` Rogier Wolff [this message]
2002-02-19 17:59 ` Martin J. Bligh
2002-02-19 18:48 ` Rogier Wolff
2002-02-19 20:01 ` Andreas Dilger
2002-02-19 23:13 ` Roy Sigurd Karlsbakk
-- strict thread matches above, loose matches on Subject: below --
2002-02-19 16:19 Jesse Pollard
2002-02-12 21:14 Torrey Hoffman
[not found] <200202121326.g1CDQct12086@Port.imtp.ilyichevsk.odessa.ua>
2002-02-12 13:33 ` Roy Sigurd Karlsbakk
2002-02-17 21:19 ` Jan-Frode Myklebust
2002-02-19 12:54 ` Jens Schmidt
2002-02-19 14:24 ` Richard B. Johnson
2002-02-21 2:56 ` Petro
2002-02-21 3:20 ` M. Edward Borasky
2002-02-21 17:01 ` Holger Lubitz
2002-02-26 3:39 ` Petro
2002-02-12 13:12 Roy Sigurd Karlsbakk
2002-02-12 13:41 ` Davidovac Zoran
2002-02-12 14:03 ` Padraig Brady
2002-02-12 15:55 ` Andreas Ferber
2002-02-12 19:47 ` Jan Hudec
2002-02-12 20:25 ` Andrew Morton
2002-02-13 0:03 ` Jeff Garzik
2002-02-13 9:33 ` Helge Hafting
2002-02-13 18:27 ` Mike Fedyk
2002-02-13 0:36 ` Tom Vier
2002-02-13 0:45 ` Jeff Garzik
2002-02-20 15:34 ` Bill Davidsen
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=200202191732.SAA08008@cave.bitwizard.nl \
--to=r.e.wolff@bitwizard.nl \
--cc=j.schmidt@paradise.net.nz \
--cc=linux-kernel@vger.kernel.org \
--cc=roy@karlsbakk.net \
/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