Linux Btrfs filesystem development
 help / color / mirror / Atom feed
From: Martin Steigerwald <Martin@lichtvoll.de>
To: linux-btrfs@vger.kernel.org
Cc: Marek Otahal <markotahal@gmail.com>, Kyle <lists@lolwut.org>
Subject: Re: Impossible or Possible to Securely Erase File on Btrfs?
Date: Wed, 20 Mar 2013 20:20:34 +0100	[thread overview]
Message-ID: <201303202020.34699.Martin@lichtvoll.de> (raw)
In-Reply-To: <1510992.7BWEEWRdZp@beruska>

Am Dienstag, 19. März 2013 schrieb Marek Otahal:
> Hi,
> 
> just reading chattr manpage..
> 
> On Monday 18 March 2013 14:15:17 you wrote:
> > Hi,
> > 
> > After reading through the btrfs documentation I'm curious to know if
> > it's possible to ever securely erase a file from a btrfs filesystem (or
> > ZFS for that matter). On non-COW filesystems atop regular HDDs one can
> > simply overwrite the file with zeros or random data using dd or some
> > other tool and rest assured that the blocks which contained the
> > sensitive information have been wiped. However on btrfs it would seem
> > any such attempt would write the zeros/random data to a new location,
> > leaving the old blocks with the sensitive data intact. Further, since
> > specifying NOCOW is only possible for newly created files, there seems
> > to be no way to overwrite the appropriate blocks short of deleting the
> > associated file and then filling the entire free filesystem space with
> > zeros/random data such that the old blocks are eventually overwritten.
> > What's the verdict on this?
> 
> what would chattr +s do?
> 
> "
> When a file with the `s' attribute set is deleted, its blocks are zeroed
> and written back to the disk.  Note: please make sure to read the bugs
> and limitations section at the end of this document. "
> 
> Nice spring to all of you! :)

Did you read on as suggested?

BUGS AND LIMITATIONS
       The `c', 's',  and `u' attributes are not honored by the ext2 and 
ext3 filesystems as implemented in the current mainline Linux kernels.


But well question still stands: Does BTRFS honor it?

My bet is: It doesn´t.

Thanks,
-- 
Martin 'Helios' Steigerwald - http://www.Lichtvoll.de
GPG: 03B0 0D6C 0040 0710 4AFA  B82F 991B EAAC A599 84C7

      reply	other threads:[~2013-03-20 19:20 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-18 18:15 Impossible or Possible to Securely Erase File on Btrfs? Kyle
2013-03-18 18:57 ` Hugo Mills
2013-03-18 19:09   ` Chris Murphy
2013-03-18 23:00     ` Kyle
2013-03-19  4:41       ` Chris Murphy
2013-03-18 19:18 ` Chris Mason
2013-03-18 22:48   ` Gareth Pye
2013-03-19  9:19     ` David Sterba
2013-03-19  3:18   ` Chris Murphy
2013-03-19  9:06     ` David Sterba
2013-03-20  0:52       ` Chris Murphy
2013-03-19 22:46 ` Marek Otahal
2013-03-20 19:20   ` Martin Steigerwald [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=201303202020.34699.Martin@lichtvoll.de \
    --to=martin@lichtvoll.de \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=lists@lolwut.org \
    --cc=markotahal@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