From: R.E.Wolff@BitWizard.nl (Rogier Wolff)
To: "Martin J. Bligh" <Martin.Bligh@us.ibm.com>
Cc: Rogier Wolff <R.E.Wolff@BitWizard.nl>,
Roy Sigurd Karlsbakk <roy@karlsbakk.net>,
Jens Schmidt <j.schmidt@paradise.net.nz>,
linux-kernel@vger.kernel.org
Subject: Re: secure erasure of files?
Date: Tue, 19 Feb 2002 19:48:58 +0100 (MET) [thread overview]
Message-ID: <200202191848.TAA08419@cave.bitwizard.nl> (raw)
In-Reply-To: <31030000.1014141568@flay> from "Martin J. Bligh" at "Feb 19, 2002 09:59:28 am"
Martin J. Bligh wrote:
> > 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.
>
> It's more than rumour - I've seen this done. Dr Solomon's (whatever
> they called their data recovery branch), early 1990's, England.
> Maybe it was easier on older hardware like the MFM / RLL disks,
> and certainly easier to piece together fragmented data with earlier
> file formats.
Maybe the difference is in "what's the goal". For datarecovery we
don't really care about just a couple of bits here and there: We want
to piece together the whole thing.
If you don't want a piece of your data getting into wrong hands
however, you'd better be safe than sorry.
So I (and the Ibas guy) are talking about practical recovery of a
useful amount of data, while even a couple of bits is in theory
dangerous if you really want it "gone".
> I believe the point of overwriting 3 times (or whatever) is to reduce
> the "subtracted difference" to noise levels where it's no longer useful.
Right.
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 18:49 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
2002-02-19 17:59 ` Martin J. Bligh
2002-02-19 18:48 ` Rogier Wolff [this message]
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=200202191848.TAA08419@cave.bitwizard.nl \
--to=r.e.wolff@bitwizard.nl \
--cc=Martin.Bligh@us.ibm.com \
--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