From: Andreas Dilger <adilger@turbolabs.com>
To: Enver Haase <ehaase@inf.fu-berlin.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: ext2 not NULLing deleted files?
Date: Fri, 17 Aug 2001 02:02:41 -0600 [thread overview]
Message-ID: <20010817020241.C32617@turbolinux.com> (raw)
In-Reply-To: <01081709381000.08800@haneman>
In-Reply-To: <01081709381000.08800@haneman>
On Aug 17, 2001 09:38 +0200, Enver Haase wrote:
> "The Other OS" in its professional version does of course clear the deleted
> blocks with 0's for security reasons; I would have bet a thousand bucks Linux
> would do so, too [seems I should have read the source code, good thing no-one
> wanted to take on the bet :) ].
>
> So how to go about this? With that feature wanted, which fs should one choose
> under Linux? Is there a patch for ext2 for that feature? Am I the only one
> liking the idea?
While there is an ext2 file attribute which sets "secure deletion" on a
per-file basis, it has never been implemented in the kernel. Several
reasons for this:
1) Deleting a file really securely takes more than just a single write
of zeros to the disk.
2) It would be a huge performance hit to overwrite a file the 15? or so
times (some random, some patterned data) to really securely delete a
file.
3) This is easily implemented in user-space, either by aliasing "rm" to
a new function, or actually putting in your own "rm" binary which
checks for the "S" attribute on ext2 files, and overwrites properly
it if it a file only has a single link. Then people can implement a
level of security they are comfortable with for their particular needs.
4) Anything that really needs to be secure should not be stored in an
insecure manner to begin with. It should only be written to disk
in encrypted form (see (a) and (b) above for why), and you also need
something like tmpfs + encrypted swap so that you don't get unencrypted
copies written to disk by mistake. Reasons for this are manyfold.
With enough money and technology it is nearly impossible to really
"delete" anything that was written to disk. If it gets written on
another part of the disk, you also have to scrub that (think /tmp or
swap for editing documents). If you make any backups of the disk,
you need to scrub the tapes for every deletion (while keeping copies
of all your other documents), very hard.
Cheers, Andreas
--
Andreas Dilger \ "If a man ate a pound of pasta and a pound of antipasto,
\ would they cancel out, leaving him still hungry?"
http://www-mddsp.enel.ucalgary.ca/People/adilger/ -- Dogbert
next prev parent reply other threads:[~2001-08-17 8:03 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-17 7:38 ext2 not NULLing deleted files? 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 [this message]
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
-- strict thread matches above, loose matches on Subject: below --
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=20010817020241.C32617@turbolinux.com \
--to=adilger@turbolabs.com \
--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