From: Kent Borg <kentborg@borg.org>
To: linux-kernel@vger.kernel.org
Subject: Where is ext2/3 secure delete ("s") attribute?
Date: Thu, 21 Nov 2002 12:52:40 -0500 [thread overview]
Message-ID: <20021121125240.K16336@borg.org> (raw)
I happened upon the chattr command and was pleased to see that "s"
means to write zeros (or is it random data?) to the blocks of deleted
files. Cool, except I can't see that it works.
First, deleting a large file with the "s" attribute happens far too
quickly.
Second, I can't see where any of this is implemented in the source
code (as of Red Hat's 2.4.18-17.7.x and straight 2.4.19). The file
fs/ext2/CHANGES talks about how the zero writing was changed to
writing random data--but nothing seems to implement this.
What happened to this feature? Was it too slow or buggy? Did the
Federales force its removal?
(Would this be best implemented as a background scrub and I am missing
a daemon?)
Thanks,
-kb, the Kent who would like to have his notebook not be full of
easily undeletable files.
next reply other threads:[~2002-11-21 17:45 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-21 17:52 Kent Borg [this message]
2002-11-21 18:24 ` Where is ext2/3 secure delete ("s") attribute? 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 20:28 ` Alan Cox
2002-11-21 19:14 ` Jeff Garzik
-- strict thread matches above, loose matches on Subject: below --
2002-11-21 18:20 Marc-Christian Petersen
2002-11-21 22:43 ` Harald Arnesen
2002-11-22 1:22 Albert D. Cahalan
2002-11-22 1:30 ` Jeff Garzik
2002-11-22 2:41 ` Albert D. Cahalan
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
2002-11-24 6:40 Albert D. Cahalan
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=20021121125240.K16336@borg.org \
--to=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