From: Chris Mason <chris.mason@fusionio.com>
To: Kyle <lists@lolwut.org>,
"linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>
Subject: Re: Impossible or Possible to Securely Erase File on Btrfs?
Date: Mon, 18 Mar 2013 15:18:15 -0400 [thread overview]
Message-ID: <20130318191815.15073.49770@localhost.localdomain> (raw)
In-Reply-To: <514759B5.5000507@lolwut.org>
Quoting Kyle (2013-03-18 14:15:17)
> 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?
We don't do this now for other reasons mentioned in the thread. The
best path to get here is to use trim, and to find a device that supports
a secure erase trim (I don't know if this even exists, sorry).
Outside of that, the only way to do this securely is to delete the
files, rotate in new drives, rotate out the old drives, and run a full
drive secure delete (not very practical).
-chris
next prev parent reply other threads:[~2013-03-18 19:18 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 [this message]
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
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=20130318191815.15073.49770@localhost.localdomain \
--to=chris.mason@fusionio.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=lists@lolwut.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