From: "Roy Sigurd Karlsbakk" <roy@karlsbakk.net>
To: "Jens Schmidt" <j.schmidt@paradise.net.nz>,
linux-kernel@vger.kernel.org, j.schmidt@paradise.net.nz
Subject: Re: secure erasure of files?
Date: Tue, 19 Feb 2002 14:48:45 +0000 [thread overview]
Message-ID: <20020219.HQ8.97132600@karlsbakk.net> (raw)
>I would strongly encourage somebody with fluent Norsk/English skills
>to do a translation and post it to the list.
I'll do my very best ...
(translated by Roy Sigurd Karlsbakk - please don't spam me in case of bad
speling :)
With permission from the leader of Research and Deveopment department, I
quote his complete answer:
I'll try to answer your questions:
The short answer is: No. It is not possible to read data that are (really)
physically overwritten.
Still, the reason to this is is a little different than what you are describing.
To speak reasonably about this, we firstly need some basic understanding of how
data is stored on a harddisk. A harddisk does not manipulate individual bits, but
flux change. Simply explained is 'flux direction' however the magnetic field points
clockwise or counter-clockwise. Thus, a 'flux change' is where the flux changes from
CCW to CW or the other way around. The mapping between flux changes is not
one-to-one.
This means that we DO NOT use CW=0, CCW=1, but rather have each flux
change
giving the origin pf 2.5 to 3 bits in addition to the disks sequence detection.
This means that it does not attempt to detect each bit isolated, but rather decodes
a sequence at a time (typically 4096 bit = 1 sector).
This sequence detection is quite the same as a human reading a bad
fax. If we try to read the fax letter by letter, we may for instance
mistake an 'a' with an 'o'. If this letter is part of the word 'bank',
and we read it letter by letter, we'll end up with 'bonk. However, if we
look at the whole word (the sequence of letters), we can probably see
the most probable word is 'bank'.
After data is overwritten, we can measure how strong the (field of the)
old data is compared to the new ones. This means that all 'old' signals
never really disappear. Still, our investigation shows that there is no
officially documented way of how to change these (old) signals back to
the origial data-
It may seem this will demand trail-breaking discoveries in many different
fields: Non-linear analysis and modelling, low-noice electronics (cryo-
electronics), computer technology (super-fast number-chrunchers)
This was the long (complicated) answer :)
What is sure: Ibas does not know any documented methods, scientific
environments or commercial services that do or demonstrate reading
of overwritten data.
--
Thor Arne Johansen
Avdelingssjef FoU, Ibas AS
Addition:
Still, it should be said that this is being argued upon between the
'wise' ones. This is - there are people that mean it is possible
to read/recover overwritten data. But we have, as mentioned above,
not found any scientific documentation or decriptions of how this
can be done.
-----------------------------------------------------------------------------
--
--
Roy Sigurd Karlsbakk, MCSE, MCNE, CLS, LCA
Computers are like air conditioners.
They stop working when you open Windows.
next reply other threads:[~2002-02-19 14:49 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-19 14:48 Roy Sigurd Karlsbakk [this message]
2002-02-19 17:32 ` Rogier Wolff
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=20020219.HQ8.97132600@karlsbakk.net \
--to=roy@karlsbakk.net \
--cc=j.schmidt@paradise.net.nz \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®