From: Billy Crook <billycrook@gmail.com>
To: Sandra Schlichting <littlesandra88@gmail.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: Encryption implementation like ZFS?
Date: Fri, 30 Dec 2011 13:27:43 -0600 [thread overview]
Message-ID: <CANZ96zUydMMYSGoX9QM8p5KSE_17faDCM9ruEeT9peO4_q181A@mail.gmail.com> (raw)
In-Reply-To: <CAELiMBN7vPQ=42eNwT3oGztWS-666RrpzDzv7nDF_LX+0gjxhQ@mail.gmail.com>
On Fri, Dec 30, 2011 at 12:32, Sandra Schlichting
<littlesandra88@gmail.com> wrote:
> According to [0] ZFS does encryption:
>
> One exception to this is the encryption support being added to the ZFS
> filesystem. Filesystem metadata such as filenames, ownership, ACLs,
> extended attributes are all stored encrypted on disk. The ZFS metadata
> about the storage pool is still stored in the clear so it is possible
> to determine how many filesystems (datasets) are available in the pool
> and even which ones are encrypted but not what the content of the
> stored files or directories are.
How is this advantageous over dmcrypt-LUKS?
LUKS has always been supported between the block device and a btrfs
filesystem, and would not even let an attacker discern what type of
file-system was in use.
next prev parent reply other threads:[~2011-12-30 19:27 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-30 18:32 Encryption implementation like ZFS? Sandra Schlichting
2011-12-30 19:27 ` Billy Crook [this message]
2011-12-30 20:12 ` Sandra Schlichting
2011-12-30 20:49 ` Billy Crook
2011-12-30 21:12 ` Sandra Schlichting
2011-12-31 9:53 ` Felix Blanke
2011-12-31 14:12 ` Sandra Schlichting
2011-12-31 9:53 ` Fajar A. Nugraha
2011-12-31 14:00 ` Sandra Schlichting
2011-12-31 17:12 ` Niels de Carpentier
2011-12-31 23:04 ` Fajar A. Nugraha
2012-01-01 15:22 ` Niels de Carpentier
2011-12-31 16:01 ` Edward Ned Harvey
2011-12-30 22:10 ` Tomasz Torcz
2011-12-31 3:36 ` Niels de Carpentier
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=CANZ96zUydMMYSGoX9QM8p5KSE_17faDCM9ruEeT9peO4_q181A@mail.gmail.com \
--to=billycrook@gmail.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=littlesandra88@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;
as well as URLs for NNTP newsgroup(s).