From: Anand Jain <anand.jain@oracle.com>
To: Hugo Mills <hugo@carfax.org.uk>,
Filip Bystricky <filipbystricky@google.com>,
linux-btrfs@vger.kernel.org
Subject: Re: btrfs native encryption
Date: Sun, 11 Jun 2017 02:22:22 +0900 [thread overview]
Message-ID: <593C2ACE.2070705@oracle.com> (raw)
In-Reply-To: <20170609160337.GA30723@carfax.org.uk>
For phase-1 the idea was to make btrfs encryption inline with
fs/crytpo which wasn't available when it started, so certainly there are
things which could straight away filter out after its known what went
into fs/crypto from ext4, especially the cryptography part.
Now, 4.10 kernel based, btrfs encryption using fs/crypto is here [1].
It has under gone limited testing by me and yet to arrive at a
conclusion on the file-name encryption, though its discussions are here
[2], and patches aren't sent out to the BTRFS ML yet.
[1] Phase-1.
Progs: https://github.com/asj/btrfs-progs-fscryptv1
Kernel: https://github.com/asj/linux-btrfs-fscryptv1
[2] File name encryption discussions are here:
(I don't see some of the emails I have in the google search, so
instead I have listed the subject for your search).
On the ext4 ML:
Sub: fs/crypto: file-name encryption, optional ?
Sub: fs/crypto: root read-access without key
Thanks, Anand
next prev parent reply other threads:[~2017-06-10 18:17 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-09 15:50 btrfs native encryption Filip Bystricky
2017-06-09 16:03 ` Hugo Mills
2017-06-10 17:22 ` Anand Jain [this message]
2017-06-09 18:09 ` Chris Murphy
2017-06-10 17:31 ` Anand Jain
2017-06-12 12:40 ` David Sterba
2017-06-12 12:46 ` David Sterba
-- strict thread matches above, loose matches on Subject: below --
2020-04-26 13:54 Btrfs " Neal Gompa
2020-04-26 14:14 ` Nikolay Borisov
2020-04-26 14:25 ` Mark Harmstone
2020-04-27 4:49 ` Chris Murphy
2020-04-27 8:00 ` Mark Harmstone
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=593C2ACE.2070705@oracle.com \
--to=anand.jain@oracle.com \
--cc=filipbystricky@google.com \
--cc=hugo@carfax.org.uk \
--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