You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

Daniel Rosenberg e16d8494ec fscrypt: don't allow v1 policies with casefolding ... Casefolded encrypted directories will use a new dirhash method that requires a secret key. If the directory uses a v2 encryption policy, it's easy to derive this key from the master key using HKDF. However, v1 encryption policies don't provide a way to derive additional keys. Therefore, don't allow casefolding on directories that use a v1 policy. Specifically, make it so that trying to enable casefolding on a directory that has a v1 policy fails, trying to set a v1 policy on a casefolded directory fails, and trying to open a casefolded directory that has a v1 policy (if one somehow exists on-disk) fails. Signed-off-by: Daniel Rosenberg <drosen@google.com> [EB: improved commit message, updated fscrypt.rst, and other cleanups] Link: https://lore.kernel.org/r/20200120223201.241390-2-ebiggers@kernel.org Signed-off-by: Eric Biggers <ebiggers@google.com>		5 years ago
..
Kconfig	…
Makefile	…
bio.c	…
crypto.c	…
fname.c	fscrypt: add "fscrypt_" prefix to fname_encrypt()	5 years ago
fscrypt_private.h	fscrypt: add "fscrypt_" prefix to fname_encrypt()	5 years ago
hkdf.c	…
hooks.c	fscrypt: don't allow v1 policies with casefolding	5 years ago
keyring.c	…
keysetup.c	…
keysetup_v1.c	…
policy.c	fscrypt: don't allow v1 policies with casefolding	5 years ago