From: Thomas Pornin <Thomas.Pornin@ens.fr>
To: ehaase@inf.fu-berlin.de
Cc: linux-kernel@vger.kernel.org
Subject: Re: ext2 not NULLing deleted files?
Date: Fri, 17 Aug 2001 09:56:27 +0200 [thread overview]
Message-ID: <20010817095627.A15129@bolet.ens.fr> (raw)
In-Reply-To: <01081709381000.08800@haneman>
In article <01081709381000.08800@haneman> you write:
> "The Other OS" in its professional version does of course clear the
> deleted blocks with 0's for security reasons
That's not much more than a smoke screen, actually. Wiping out data
from a disk requires more than merely writing 0's, if the bad guy is
assumed to physically have hold of the disk. See, for instance, the
paper from Peter Gutmann, "Secure Deletion of Data from Magnetic and
Solid-State Memory" (published in Usenix'96). Such games are much
dependant on the actual writing technology, and harddisk cache (which
cannot be deacticated on some modern IDE disks) gets in the way.
Besides, performance is terrible (if you need to rewrite seven times a
file with different patterns for each deletion, imagine what happens
when you delete a 100 MBytes file...).
The only truly secure way to do is encryption: if all data that gets to
the disk is encrypted, physical details about the disk are unimportant,
so security cannot be compromised by some smarter physicist with more
expensive tools.
--Thomas Pornin
next prev parent reply other threads:[~2001-08-17 7:56 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
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 [this message]
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
[not found] <01081709381000.08800@haneman.suse.lists.linux.kernel>
2001-08-17 8:03 ` Andi Kleen
2001-08-17 14:20 ` Kent Borg
2001-08-17 22:05 Jesse Pollard
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=20010817095627.A15129@bolet.ens.fr \
--to=thomas.pornin@ens.fr \
--cc=ehaase@inf.fu-berlin.de \
--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®