From: "Swâmi Petaramesh" <swami@petaramesh.org>
To: radames42@freenet.de
Cc: linux-btrfs@vger.kernel.org
Subject: Re: cow versus data erasure
Date: Sun, 15 May 2011 12:00:08 +0200 [thread overview]
Message-ID: <1305453608.5117.6.camel@tethys> (raw)
In-Reply-To: <72d360c3a60a791182b5901cca382570@email.freenet.de>
Le dimanche 15 mai 2011 =C3=A0 11:43 +0200, radames42@freenet.de a =C3=A9=
crit :
> since btrfs uses cow I wonder how I can erase confidential data.
> Replacing the file does not work, since the new content is written to=
new
> blocks while the old confidential content remains in its old block (w=
hich
> may be unused now - depending on snapshots).
Yep. COW filesystems typically do not allow secure deletion, there's no
way to work around this AFAIK.
> Alternatives are:
> - using encfs to save confidential data
> - using luks to encrypt the whole disk/partition
> other suggestions?
I'm currently writing this message from a machine using a BTRFS inside
an LVM built upon LUKS. That works fine.
I also use some ecryptfs on other machines, that comes standard with
Ubuntu and is allright.
It may be worth noting that encryption is not equivalent to secure
deletion : If it's secure-deleted, it's truly gone. If it's "unsecurely=
"
deleted from an encrypted container, somebody getting the decryption
key, possibly by force, might be able to recover the data.
OTOH, even though COW filesystems don't allow secure deletion, they're
typically known to generally not have any reliable "undelete" tools, an=
d
COW filesystems have a greater chance to overwrite relased blocks soone=
r
than non-COW FSes would do, so the average lifespan of "parts of erased
files data on disk" is probably typically much shorter with a COW FS
than with a non-COW one.
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" =
in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2011-05-15 10:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-15 9:43 cow versus data erasure radames42
2011-05-15 10:00 ` Swâmi Petaramesh [this message]
2011-05-15 10:20 ` Radames
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=1305453608.5117.6.camel@tethys \
--to=swami@petaramesh.org \
--cc=linux-btrfs@vger.kernel.org \
--cc=radames42@freenet.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.