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 | 3d32c5c2abd09065c7d8c5e35ad5a3d2ed0ad7d9 (patch) | |
| tree | bce856aa8285a97a66886e42797815f8b40dcf4a | |
| parent | 74705592f5fcb07ad90c0794a4c6b2cd9cd2a7fa (diff) | |
| download | linux-crypto-3d32c5c2abd09065c7d8c5e35ad5a3d2ed0ad7d9.tar.gz linux-crypto-3d32c5c2abd09065c7d8c5e35ad5a3d2ed0ad7d9.zip | |
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 e3cf1c151f07 ("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 af8c6b4e..1062e103 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 |