On Mon, Jun 12, 2017 at 02:40:38PM +0200, David Sterba wrote:
> 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
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.
The file-based encryption is covered by the
dealing with inheritance of
encryption when making snapshots, and dealing with reflinks.
Right. To address this, there is a proposal to bring encryption down
to the extent level, it solves these limitations.
Thanks, Anand
--
To unsubscribe from this list: send the line "unsubscribe
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,
On Fri, Jun 9, 2017 at 9:50 AM, 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
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
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.