From: Andi Kleen <freitag@alancoxonachip.com>
To: linux-kernel@vger.kernel.org
Cc: ehaase@inf.fu-berlin.de
Subject: Re: ext2 not NULLing deleted files?
Date: 17 Aug 2001 10:03:46 +0200 [thread overview]
Message-ID: <oupitfnw1st.fsf@pigdrop.muc.suse.de> (raw)
In-Reply-To: <01081709381000.08800@haneman.suse.lists.linux.kernel>
In-Reply-To: Enver Haase's message of "17 Aug 2001 09:42:44 +0200"
Enver Haase <ehaase@inf.fu-berlin.de> writes:
> Hi there,
>
> I just recognized there's an "undelete" now for ext2 file systems [a KDE
> app]\b.
There have been ext2 undeletes for many years now (and howtos how to do
it manually even longer), nothing new.
>
> "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?
Old ext2 (before 2.0) supported this with a special attribute bit; but it was
removed for good reasons.
Just NULLing alone is quite useless anyways; just 0ed data can be easily
recovered in a special laboratory by using old traces of magnetism on the
surfaces.
If you care about real data deletion you should probably use an utility
like wipe which does about 20-30 passes with random data. That is far too
complex to do in kernel space of course, but you can run it in user space
as needed. 0ing would just give you a false sense of security.
-Andi
next parent reply other threads:[~2001-08-17 8:43 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <01081709381000.08800@haneman.suse.lists.linux.kernel>
2001-08-17 8:03 ` Andi Kleen [this message]
2001-08-17 14:20 ` ext2 not NULLing deleted files? Kent Borg
2001-08-17 22:05 Jesse Pollard
-- 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=oupitfnw1st.fsf@pigdrop.muc.suse.de \
--to=freitag@alancoxonachip.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