From: Jesse Pollard <pollard@tomcat.admin.navo.hpc.mil>
To: roy@karlsbakk.net, "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 10:19:23 -0600 (CST) [thread overview]
Message-ID: <200202191619.KAA72194@tomcat.admin.navo.hpc.mil> (raw)
--------- Received message begins Here ---------
>
> >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.
[snip]
In the non-destructive read case - true.
HOWEVER: forensic specialists can:
http://www.cs.auckland.ac.nz/~pgut001/secure_del.html
or (same paper)
http://www.usenix.org/publications/library/proceedings/sec96/full_papers/gutmann/
>
> 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.
See the paper referenced above. There may be more recent documents, but
this one is quite clear on the limitations of erasure using the standard
drive electronics.
-------------------------------------------------------------------------
Jesse I Pollard, II
Email: pollard@navo.hpc.mil
Any opinions expressed are solely my own.
next reply other threads:[~2002-02-19 16:20 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-19 16:19 Jesse Pollard [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-02-19 14:48 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
2002-02-19 20:01 ` Andreas Dilger
2002-02-19 23:13 ` Roy Sigurd Karlsbakk
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=200202191619.KAA72194@tomcat.admin.navo.hpc.mil \
--to=pollard@tomcat.admin.navo.hpc.mil \
--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
all inboxes | Powered by JetHome®