summaryrefslogtreecommitdiffstats
path: root/fs/crypto
diff options
context:
space:
mode:
authorEric Biggers <ebiggers@google.com>2016-11-26 21:06:43 +0100
committerTheodore Ts'o <tytso@mit.edu>2016-12-11 22:26:07 +0100
commit8048123576d1011e186b1f62478bcd06ac7cabc8 (patch)
tree2758589773f03d0cdcbe09193cd5f30f05849115 /fs/crypto
parentMAINTAINERS: fscrypto: recommend linux-fsdevel for fscrypto patches (diff)
downloadlinux-8048123576d1011e186b1f62478bcd06ac7cabc8.tar.xz
linux-8048123576d1011e186b1f62478bcd06ac7cabc8.zip
fscrypto: remove unneeded Kconfig dependencies
SHA256 and ENCRYPTED_KEYS are not needed. CTR shouldn't be needed either, but I left it for now because it was intentionally added by commit 71dea01ea2ed ("ext4 crypto: require CONFIG_CRYPTO_CTR if ext4 encryption is enabled"). So it sounds like there may be a dependency problem elsewhere, which I have not been able to identify specifically, that must be solved before CTR can be removed. Signed-off-by: Eric Biggers <ebiggers@google.com> Signed-off-by: Theodore Ts'o <tytso@mit.edu>
Diffstat (limited to 'fs/crypto')
-rw-r--r--fs/crypto/Kconfig2
1 files changed, 0 insertions, 2 deletions
diff --git a/fs/crypto/Kconfig b/fs/crypto/Kconfig
index 92348faf9865..f514978f6688 100644
--- a/fs/crypto/Kconfig
+++ b/fs/crypto/Kconfig
@@ -8,9 +8,7 @@ config FS_ENCRYPTION
select CRYPTO_XTS
select CRYPTO_CTS
select CRYPTO_CTR
- select CRYPTO_SHA256
select KEYS
- select ENCRYPTED_KEYS
help
Enable encryption of files and directories. This
feature is similar to ecryptfs, but it is more memory