----- Ursprüngliche Mail ----- > Von: "Johannes Thumshirn" <Johannes.Thumshirn@xxxxxxx> > An: "richard" <richard@xxxxxx> > CC: "Eric Biggers" <ebiggers@xxxxxxxxxx>, "Johannes Thumshirn" <jth@xxxxxxxxxx>, "David Sterba" <dsterba@xxxxxxx>, > "linux-fsdevel" <linux-fsdevel@xxxxxxxxxxxxxxx>, "linux-btrfs" <linux-btrfs@xxxxxxxxxxxxxxx>, "david" > <david@xxxxxxxxxxxxx>, "Sascha Hauer" <s.hauer@xxxxxxxxxxxxxx> > Gesendet: Dienstag, 5. Mai 2020 09:46:42 > Betreff: Re: [PATCH v2 1/2] btrfs: add authentication support > On 04/05/2020 23:41, Richard Weinberger wrote: >> Well, UBIFS stores auth_hash_name on disk but does not trust it. >> It is always required to provide auth_hash_name as mount parameter. >> At mount time it is compared to the stored name (among with other parameters) >> to detect misconfigurations. > > OK, thanks for the information. > > Will do so as well in v3 With UBIFS this is now the second in-tree filesystem with authentication support. IMHO it is worth adding a new statx flag to denote this. Just like we do already for encrypted and verity protected files. STATX_ATTR_AUTHED? Especially for BTRFS user this is valubale information since BTRFS authentication is incompatible with nodatacow'ed files/dirs/subvolumes. And it might be not obvious which files are protected and which are not. Thanks, //richard
