From: "Albert D. Cahalan" <acahalan@cs.uml.edu>
To: jgarzik@pobox.com (Jeff Garzik)
Cc: acahalan@cs.uml.edu (Albert D. Cahalan),
linux-kernel@vger.kernel.org, kentborg@borg.org,
alan@lxorguk.ukuu.org.uk
Subject: Re: Where is ext2/3 secure delete ("s") attribute?
Date: Thu, 21 Nov 2002 21:41:14 -0500 (EST) [thread overview]
Message-ID: <200211220241.gAM2fEZ357378@saturn.cs.uml.edu> (raw)
In-Reply-To: <3DDD88BB.209@pobox.com> from "Jeff Garzik" at Nov 21, 2002 08:30:35 PM
Jeff Garzik writes:
> Albert D. Cahalan wrote:
>> Forget the shred program. It's less useful than having the
>> filesystem simply zero the blocks, because it's slow and you
>> can't be sure to hit the OS-visible blocks.
>
> Why not?
>
> Please name a filesystem that moves allocated blocks around on you. And
> point to code, too.
Reiserfs tails
fs/reiserfs
ext3 with data journalling
fs/ext3
the journalling flash filesystems
fs/jffs
fs/jffs2
NTFS with compression
fs/ntfs
Some of these are listed in the shred man page.
Multiple overwrites won't protect you from the disk manufacturer
or the NSA. Only one is needed to protect against root & kernel.
So it makes sense to have the filesystem zero the blocks when
they are freed from a file.
next prev parent reply other threads:[~2002-11-22 2:34 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-22 1:22 Albert D. Cahalan
2002-11-22 1:30 ` Jeff Garzik
2002-11-22 2:41 ` Albert D. Cahalan [this message]
2002-11-22 4:39 ` Jeff Garzik
2002-11-22 5:55 ` Albert D. Cahalan
2002-11-22 7:12 ` Ingo Oeser
2002-11-22 13:38 ` Alan Cox
2002-11-22 13:27 ` Nikita Danilov
2002-11-22 2:06 ` Mike Dresser
2002-11-22 14:13 ` Jesse Pollard
2002-11-22 21:31 ` Krzysztof Halasa
-- strict thread matches above, loose matches on Subject: below --
2002-11-24 6:40 Albert D. Cahalan
2002-11-21 18:20 Marc-Christian Petersen
2002-11-21 22:43 ` Harald Arnesen
2002-11-21 17:52 Kent Borg
2002-11-21 18:24 ` Jeff Garzik
2002-11-21 18:39 ` Kent Borg
2002-11-21 19:20 ` Alan Cox
2002-11-21 19:05 ` Kent Borg
2002-11-21 19:14 ` Jeff Garzik
2002-11-21 20:28 ` Alan Cox
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=200211220241.gAM2fEZ357378@saturn.cs.uml.edu \
--to=acahalan@cs.uml.edu \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=jgarzik@pobox.com \
--cc=kentborg@borg.org \
--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®