From: Hugo Mills <hugo@carfax.org.uk>
To: Filip Bystricky <filipbystricky@google.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: btrfs native encryption
Date: Fri, 9 Jun 2017 16:03:37 +0000 [thread overview]
Message-ID: <20170609160337.GA30723@carfax.org.uk> (raw)
In-Reply-To: <CADvCoti_3iDwXfqepMdva6E6OOis_rqqVQ4adCV1T67PVhRrOQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1227 bytes --]
On Fri, Jun 09, 2017 at 08:50:12AM -0700, Filip Bystricky wrote:
> Dear btrfs maintainers,
> Google is evaluating btrfs for its potential use in android, but
> currently the lack of native file-based encryption unfortunately makes
> it a nonstarter. According to the FAQ (specifically the answer to
> "Does btrfs support encryption"), nobody is currently working on this.
> How up-to-date is that answer, and are there any new plans to add
> native FBE in the future?
There were initial patches from Anand Jain back in September, but
they weren't well-received in terms of the (lack of) cryptography
design. IIRC, the patches provided file-level data encryption without
encrypting metadata. I haven't seen anything since then (although
Anand was planning on doing a session on btrfs encryption at LSF/MM in
March -- I don't know if that happened, or what the outcome was).
So, there's some interest in a fairly minimal implementation, but
progress doesn't seem to be particularly fast.
Hugo.
--
Hugo Mills | "Are you the man who rules the Universe?" "Well, I
hugo@... carfax.org.uk | try not to."
http://carfax.org.uk/ |
PGP: E2AB1DE4 | Life, the Universe and Everything.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2017-06-09 16:03 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 [this message]
2017-06-10 17:22 ` Anand Jain
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=20170609160337.GA30723@carfax.org.uk \
--to=hugo@carfax.org.uk \
--cc=filipbystricky@google.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 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.