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 fscrypt API, that's implemented in ext4/f2fs, so implementing that in btrfs could allow you to start evaluating btrfs. As other pointed, the usecases with snapshots and reflinks need to be reviewed. > 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? Wiki is a snapshot of status, knowledge and best practices from mixed times, so not everything is up to date or accurate. That no one is working on encryption is partially true, as we've seen some proposed patches that received objections and from my perspective are not close to being considered for merging. The fscrypt functionality has been designed and the API defined, so it's a matter of implementation on the btrfs side. Anything else is in the phase of design and prototyping. -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
