diff options
author | Eric Biggers <ebiggers@google.com> | 2019-05-20 09:52:07 -0700 |
---|---|---|
committer | Herbert Xu <herbert@gondor.apana.org.au> | 2019-05-30 15:28:40 +0800 |
commit | 87804144cb7ad09126f1d16e205a7d6b4bc35404 (patch) | |
tree | 36bc52a9d008a1a19b0e38d4082b09bce1b047aa | |
parent | c8a3315a5f691cc4be16421aeb0608495c9a33ba (diff) | |
download | linux-87804144cb7ad09126f1d16e205a7d6b4bc35404.tar.bz2 |
crypto: echainiv - change to 'default n'
echainiv is the only algorithm or template in the crypto API that is
enabled by default. But there doesn't seem to be a good reason for it.
And it pulls in a lot of stuff as dependencies, like AEAD support and a
"NIST SP800-90A DRBG" including HMAC-SHA256.
The commit which made it default 'm', commit 3491244c6298 ("crypto:
echainiv - Set Kconfig default to m"), mentioned that it's needed for
IPsec. However, later commit 32b6170ca59c ("ipv4+ipv6: Make INET*_ESP
select CRYPTO_ECHAINIV") made the IPsec kconfig options select it.
So, remove the 'default m'.
Signed-off-by: Eric Biggers <ebiggers@google.com>
Signed-off-by: Herbert Xu <herbert@gondor.apana.org.au>
-rw-r--r-- | crypto/Kconfig | 1 |
1 files changed, 0 insertions, 1 deletions
diff --git a/crypto/Kconfig b/crypto/Kconfig index af8c6b4e6a83..1062e1031f73 100644 --- a/crypto/Kconfig +++ b/crypto/Kconfig @@ -428,7 +428,6 @@ config CRYPTO_ECHAINIV select CRYPTO_NULL select CRYPTO_RNG_DEFAULT select CRYPTO_MANAGER - default m help This IV generator generates an IV based on the encryption of a sequence number xored with a salt. This is the default |