mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jesse Pollard <pollard@tomcat.admin.navo.hpc.mil>
To: adilger@turbolabs.com, "Mark H. Wood" <mwood@IUPUI.Edu>
Cc: linux-kernel@vger.kernel.org
Subject: Re: ext2 not NULLing deleted files?
Date: Fri, 17 Aug 2001 17:05:54 -0500 (CDT)	[thread overview]
Message-ID: <200108172205.RAA28109@tomcat.admin.navo.hpc.mil> (raw)

--
> 
> On Aug 17, 2001  12:55 -0500, Mark H. Wood wrote:
> > Regarding the need to do more than just zero unwanted data, I note that
> > there is a U.S. DOD MIL-SPEC (no, I do not know the number) which defines
> > a sequence of patterns to be used for erasing magnetic media.
> 
> In the Usenix paper quoted earlier in this thread (I believe) it was
> stated that the MIL-SPEC document was actually bogus.  REAL secure
> deletion requirements were much more strict (something like 15 passes of
> various random and non-random patterns vs. 7 passes of alternating all 0
> and all 1 data), but the US government made it think that the MIL-SPEC
> requirements were enough, so that naive users would follow it, still
> leaving enough trace data on the disk for the government to retrieve it.

Actually, it does exist as part of the rainbow series under object reuse.
I have a copy of the current renewed memo draft + addendum (this year) for
purging.

No change.

> Still, even a single pass of zero writes is enough to prevent 99.9%
> of attackers from getting the data back.

Absolutely - the only people that can still retrieve data are the data
recovery companies out there (even fire doesn't fully erase the data unless
above 2-3,000 degrees). Tunneling magnetic microscopes are amazing at
data retrieval. Polishing off the top layer even allows reading some data
recorded many times earlier, though the newer thin film surfaces make this
harder.

-------------------------------------------------------------------------
Jesse I Pollard, II
Email: pollard@navo.hpc.mil

Any opinions expressed are solely my own.

             reply	other threads:[~2001-08-17 22:06 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-08-17 22:05 Jesse Pollard [this message]
     [not found] <01081709381000.08800@haneman.suse.lists.linux.kernel>
2001-08-17  8:03 ` Andi Kleen
2001-08-17 14:20   ` Kent Borg
  -- strict thread matches above, loose matches on Subject: below --
2001-08-17  7:38 Enver Haase
2001-08-17  7:47 ` Robert Love
2001-08-17 17:40   ` Mark H. Wood
2001-08-17  7:56 ` Thomas Pornin
2001-08-17  8:02 ` Andreas Dilger
2001-08-17 17:55   ` Mark H. Wood
2001-08-17 20:09     ` Andreas Dilger
2001-08-21 14:19   ` Andreas Bombe
2001-08-17 16:32 ` Marc SCHAEFER
2001-08-17 17:25   ` Andreas Dilger

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=200108172205.RAA28109@tomcat.admin.navo.hpc.mil \
    --to=pollard@tomcat.admin.navo.hpc.mil \
    --cc=adilger@turbolabs.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mwood@IUPUI.Edu \
    /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®