From: Ric Wheeler <ricwheeler@gmail.com>
To: Marco Stornelli <marco.stornelli@gmail.com>
Cc: Linux FS Devel <linux-fsdevel@vger.kernel.org>,
Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: Secure file deletion option question
Date: Wed, 13 Apr 2011 14:31:08 -0400 [thread overview]
Message-ID: <4DA5EBEC.10807@gmail.com> (raw)
In-Reply-To: <4DA5E20E.4070904@gmail.com>
On 04/13/2011 01:49 PM, Marco Stornelli wrote:
> Hi all,
>
> I don't see any fs implements that feature. The flag FS_SECRM_FL seems never
> used with the exception of some define in some fs. Is there a motivation for
> this? It seems a good option to me.
>
> Marco
I think that most secure deletion code is done from user space, which can deal
with odd storage types and so on. Just deleting and overwriting the blocks with
zero data is not sufficient for some needs.
Having user space tools deal with the myriad of ways that it could be done keeps
the policy out of the kernel...
Ric
prev parent reply other threads:[~2011-04-13 18:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-13 17:49 Secure file deletion option question Marco Stornelli
2011-04-13 18:31 ` Ric Wheeler [this message]
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=4DA5EBEC.10807@gmail.com \
--to=ricwheeler@gmail.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marco.stornelli@gmail.com \
/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