They don't depend on fscrypt but lag in development. Even some very basic features are missing. Actually fscrypt was originally based on e4crypt but now the former has come far ahead. At the moment the most stable implementation is AOSP's built-in filesystem encryption.
---------- Post added at 01:32 PM ---------- Previous post was at 01:28 PM ----------
dm-verity and dm-integrity are to prevent accidental or malicious data corruption. So is fs-verity. E.g. veritysetup is used to setup what Android's Verified Boot does to /system, /vendor etc. to prevent any modifications.
can dm-verity or dm-integrity be used with luks to prevent accidental or malicious data corruption? (i.e. luks header corruption)
---------- Post added at 04:03 AM ---------- Previous post was at 03:49 AM ----------
I've just put them in for completeness. Probably useless for end-users.
strace binaries are in the first post.
If 'fscrypt --verbose' doesn't provide any information about the keyring i can post a 'keyctl' binary for debugging. It will show if the key was properly assigned to your user/session if i reckon correctly.
Edit: Added 'keyctl' to the fscrypt archive here.
i dont understand how to use "keyctl". keyctl show shows 1key always, whether i lock/unlock that dir (/oem/1)
can u plz make f2fs-tools latest (1.13.0) ?