On Mon, Oct 24, 2016 at 10:44:41PM +0200, Richard Weinberger wrote: > That's a very good idea! > Do we also have designated git tree for fscrypto? > As soon UBIFS file encryption is mainline I'll have to monitor changes > to fscrypto very closely because changes in fscrypto could introduce > changes in the on-flash format of UBIFS. > i.e. a subtle change in filename encryption... :-) There isn't yet a dedicated fscrypto tree. Ted has been taking in most of my fscrypto patches through the ext4 tree. This was discussed briefly before, but as designed filesystems do not need to be aware of the format of the xattr (fscrypt_context) or the format of the encrypted data per se. Thus, new modes/formats can be introduced without requiring changes to filesystem-specific code. The point that was brought up is whether some filesystems would additionally like to track in their superblock which encryption modes and flags are used and either deny mounts or warn at mount-time if some are unrecognized. So it should be decided soon if UBIFS is going to do that or not. Eric -- To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
