On Thu, 2020-04-09 at 08:50 +0000, Johannes Thumshirn wrote:
> Maybe having someone in the community being interested in this work
> can
> accelerate it's upstream acceptance.
I think it would be great having something like this in btrfs.
If this was to be merged, it would perhaps make sense to have it
audited by a number of crypto experts.
And also, to clearly specify what it can to and what not:
- like how it behaves with other features of btrfs (compression, raid,
repair, etc.)
- limitations (e.g. fs-verity was just read-only, wasn't it?!)
- what exactly does it protect?
- "just" the content of files (i.e. a file with invalid HMAC will be
detected)
- file metadata (dates, names, permissions, owners, xattrs, etc)
- the file hirarchy (location of the files in the tree)
- would files removed/added (by an attacker) be detected
Cheers,
Chris.
