From: Josef Bacik <josef@redhat.com>
To: Carl Cook <CACook@quantum-sci.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: Encryption
Date: Thu, 20 Jan 2011 11:10:44 -0500 [thread overview]
Message-ID: <20110120161044.GC6609@dhcp231-156.rdu.redhat.com> (raw)
In-Reply-To: <201101200705.52547.CACook@quantum-sci.com>
On Thu, Jan 20, 2011 at 07:05:52AM -0800, Carl Cook wrote:
>
> Does BTRFS have subvolume encryption built in? If not, why?
>
No, and because nobody has done it yet. Thanks,
Josef
next prev parent reply other threads:[~2011-01-20 16:10 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-20 15:05 Encryption Carl Cook
2011-01-20 15:14 ` Encryption Hugo Mills
2011-01-20 16:10 ` Josef Bacik [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-12-07 16:16 merc1984
2012-12-12 17:12 ` Encryption merc1984
2012-12-12 18:31 ` Encryption Mitch Harder
2012-12-12 18:38 ` Encryption merc1984
2012-12-12 18:48 ` Encryption cwillu
2012-12-12 20:06 ` Encryption merc1984
2012-12-12 20:22 ` Encryption cwillu
2012-12-13 9:17 ` Encryption Sander
2012-12-13 17:23 ` Encryption merc1984
2012-12-13 22:39 ` Encryption Hugo Mills
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=20110120161044.GC6609@dhcp231-156.rdu.redhat.com \
--to=josef@redhat.com \
--cc=CACook@quantum-sci.com \
--cc=linux-btrfs@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).