lib/crypto: add prompts back to crypto libraries
Subsystems (4)
PATCH v2 1/1 lib/crypto: add prompts back to crypto libraries
Commit 6048fdcc5f269 ("lib/crypto: blake2s: include as built-in") took away a number of prompt texts from other crypto libraries. This makes values flip from built-in to module when oldconfig runs, and causes problems when these crypto libs need to be built in for thingslike BIG_KEYS.
--- lib/crypto/Kconfig | 12 ++++++++---- 1 file changed, 8 insertions(+), 4 deletions(-)
lib/crypto/Kconfig +8 -4
@@ -1,5 +1,7 @@ # SPDX-License-Identifier: GPL-2.0 +menu "Crypto library routines" + config CRYPTO_LIB_AES tristate
@@ -40,7 +42,7 @@ config CRYPTO_LIB_CHACHA_GENERIC of CRYPTO_LIB_CHACHA. config CRYPTO_LIB_CHACHA - tristate + tristate "ChaCha library interface" depends on CRYPTO_ARCH_HAVE_LIB_CHACHA || !CRYPTO_ARCH_HAVE_LIB_CHACHA select CRYPTO_LIB_CHACHA_GENERIC if CRYPTO_ARCH_HAVE_LIB_CHACHA=n help
@@ -65,7 +67,7 @@ config CRYPTO_LIB_CURVE25519_GENERIC of CRYPTO_LIB_CURVE25519. config CRYPTO_LIB_CURVE25519 - tristate + tristate "Curve25519 scalar multiplication library" depends on CRYPTO_ARCH_HAVE_LIB_CURVE25519 || !CRYPTO_ARCH_HAVE_LIB_CURVE25519 select CRYPTO_LIB_CURVE25519_GENERIC if CRYPTO_ARCH_HAVE_LIB_CURVE25519=n help
@@ -100,7 +102,7 @@ config CRYPTO_LIB_POLY1305_GENERIC of CRYPTO_LIB_POLY1305. config CRYPTO_LIB_POLY1305 - tristate + tristate "Poly1305 library interface" depends on CRYPTO_ARCH_HAVE_LIB_POLY1305 || !CRYPTO_ARCH_HAVE_LIB_POLY1305 select CRYPTO_LIB_POLY1305_GENERIC if CRYPTO_ARCH_HAVE_LIB_POLY1305=n help
@@ -109,7 +111,7 @@ config CRYPTO_LIB_POLY1305 is available and enabled. config CRYPTO_LIB_CHACHA20POLY1305 - tristate + tristate "ChaCha20-Poly1305 AEAD support (8-byte nonce library version)" depends on CRYPTO_ARCH_HAVE_LIB_CHACHA || !CRYPTO_ARCH_HAVE_LIB_CHACHA depends on CRYPTO_ARCH_HAVE_LIB_POLY1305 || !CRYPTO_ARCH_HAVE_LIB_POLY1305 select CRYPTO_LIB_CHACHA
@@ -120,3 +122,5 @@ config CRYPTO_LIB_SHA256 config CRYPTO_LIB_SM4 tristate + +endmenu
Signature · 1 line
2.34.1
Jason A. Donenfeld
maintainerThis commit also needs this snippet:
crypto/Kconfig +0 -2
@@ -1928,5 +1928,3 @@ source "crypto/asymmetric_keys/Kconfig" source "certs/Kconfig" endif # if CRYPTO - -source "lib/crypto/Kconfig"
lib/Kconfig +2 -0
@@ -122,6 +122,8 @@ config INDIRECT_IOMEM_FALLBACK mmio accesses when the IO memory address is not a registered emulated region. +source "lib/crypto/Kconfig" + config CRC_CCITT tristate "CRC-CCITT functions" help
Ard Biesheuvel
maintainerQuoted 3 lines · Jason A. Donenfeld
This commit also needs this snippet:
Why?
Quoted 23 lines
crypto/Kconfig +0
-2@@ -1928,5 +1928,3 @@ source "crypto/asymmetric_keys/Kconfig" source "certs/Kconfig" endif # if CRYPTO - -source "lib/crypto/Kconfig"lib/Kconfig +2
-0@@ -122,6 +122,8 @@ config INDIRECT_IOMEM_FALLBACK mmio accesses when the IO memory address is not a registered emulated region. +source "lib/crypto/Kconfig" + config CRC_CCITT tristate "CRC-CCITT functions" help
Jason A. Donenfeld
maintainerQuoted 7 lines · Ard Biesheuvel
Quoted 3 lines · Jason A. Donenfeld
This commit also needs this snippet:
Why?
So that the menu of crypto library options is inside of the library menu. Otherwise this will appear inside of the _root_ menu, which isn't what we want.
Ard Biesheuvel
maintainerQuoted 5 lines · Jason A. Donenfeld
Quoted 3 lines · Ard Biesheuvel
Quoted 1 line · Jason A. Donenfeld
Quoted 8 lines
Quoted 4 lines
Quoted 2 lines
This commit also needs this snippet:
Why?
So that the menu of crypto library options is inside of the library menu. Otherwise this will appear inside of the _root_ menu, which isn't what we want.
Why not? I think that's fine.
Jason A. Donenfeld
maintainerQuoted 10 lines · Ard Biesheuvel
Quoted 8 lines · Jason A. Donenfeld
Quoted 6 lines · Ard Biesheuvel
Quoted 3 lines · Jason A. Donenfeld
This commit also needs this snippet:
Quoted 7 lines
Quoted 5 lines
Quoted 1 line
Why?
So that the menu of crypto library options is inside of the library menu. Otherwise this will appear inside of the _root_ menu, which isn't what we want.
Why not? I think that's fine.
It's really not appropriate there. Look:
- Justin vanilla: https://i.imgur.com/14UBpML.png
- Justin + Jason: https://i.imgur.com/lDfZnma.png
We really don't want another top level menu. We're not that important. Rather, crypto libraries are but one ordinary subset of ordinary libraries, just like how the build system does it too.
Ard Biesheuvel
maintainerQuoted 20 lines · Jason A. Donenfeld
Quoted 10 lines · Ard Biesheuvel
Quoted 8 lines · Jason A. Donenfeld
Quoted 6 lines · Ard Biesheuvel
Quoted 3 lines · Jason A. Donenfeld
This commit also needs this snippet:
Quoted 7 lines
Quoted 5 lines
Quoted 1 line
Why?
So that the menu of crypto library options is inside of the library menu. Otherwise this will appear inside of the _root_ menu, which isn't what we want.
Why not? I think that's fine.
Quoted 8 lines
It's really not appropriate there. Look:
- Justin vanilla: https://i.imgur.com/14UBpML.png
- Justin + Jason: https://i.imgur.com/lDfZnma.pngWe really don't want another top level menu. We're not that important. Rather, crypto libraries are but one ordinary subset of ordinary libraries, just like how the build system does it too.
I disagree. The root menu is a jumble of things already, and having this one at the root is really not a problem.
Jason A. Donenfeld
maintainerQuoted 27 lines · Ard Biesheuvel
Quoted 25 lines · Jason A. Donenfeld
Quoted 10 lines · Ard Biesheuvel
Quoted 8 lines · Jason A. Donenfeld
Quoted 6 lines · Ard Biesheuvel
Quoted 3 lines · Jason A. Donenfeld
This commit also needs this snippet:
Quoted 7 lines
Quoted 5 lines
Quoted 1 line
Why?
So that the menu of crypto library options is inside of the library menu. Otherwise this will appear inside of the _root_ menu, which isn't what we want.
Why not? I think that's fine.
It's really not appropriate there. Look:
- Justin vanilla: https://i.imgur.com/14UBpML.png
- Justin + Jason: https://i.imgur.com/lDfZnma.png
Quoted 6 lines
Quoted 3 lines
We really don't want another top level menu. We're not that important. Rather, crypto libraries are but one ordinary subset of ordinary libraries, just like how the build system does it too.
I disagree. The root menu is a jumble of things already, and having this one at the root is really not a problem.
Should CRC routines also go into a submenu and be put at the root? What about other library functions? Library functions belong in the library submenu. We don't need our own top level submenu for this. The whole point of lib/crypto/ is that they're just boring library functions. Libraries! So, part of the libraries menu.
Quoted 33 lines · Jason A. Donenfeld
Quoted 31 lines · Ard Biesheuvel
Quoted 28 lines · Jason A. Donenfeld
Quoted 10 lines · Ard Biesheuvel
Quoted 8 lines · Jason A. Donenfeld
Quoted 6 lines · Ard Biesheuvel
Quoted 3 lines · Jason A. Donenfeld
This commit also needs this snippet:
Quoted 7 lines
Quoted 5 lines
Quoted 1 line
Why?
So that the menu of crypto library options is inside of the library menu. Otherwise this will appear inside of the _root_ menu, which isn't what we want.
Why not? I think that's fine.
It's really not appropriate there. Look:
- Justin vanilla: https://i.imgur.com/14UBpML.png
- Justin + Jason: https://i.imgur.com/lDfZnma.pngWe really don't want another top level menu. We're not that important. Rather, crypto libraries are but one ordinary subset of ordinary libraries, just like how the build system does it too.
Quoted 8 lines
Quoted 2 lines
I disagree. The root menu is a jumble of things already, and having this one at the root is really not a problem.
Should CRC routines also go into a submenu and be put at the root? What about other library functions? Library functions belong in the library submenu. We don't need our own top level submenu for this. The whole point of
lib/crypto/is that they're just boring library functions. Libraries! So, part of the libraries menu.
Specifically in this menu, users were expecting to see it in the Cryptographic API menu. I think having it in the main menu just below this entry is much more appropriate than being buried under another menu. Particularly if the goal is to get rid of the menu again all together once we can audit the full set of deps on crypto libraries.
Justin
Jason A. Donenfeld
maintainerQuoted 44 lines · Justin Forbes
Quoted 33 lines · Jason A. Donenfeld
Quoted 31 lines · Ard Biesheuvel
Quoted 28 lines · Jason A. Donenfeld
Quoted 10 lines · Ard Biesheuvel
Quoted 8 lines · Jason A. Donenfeld
Quoted 6 lines · Ard Biesheuvel
Quoted 3 lines · Jason A. Donenfeld
This commit also needs this snippet:
Quoted 7 lines
Quoted 5 lines
Quoted 1 line
Why?
So that the menu of crypto library options is inside of the library menu. Otherwise this will appear inside of the _root_ menu, which isn't what we want.
Why not? I think that's fine.
It's really not appropriate there. Look:
- Justin vanilla: https://i.imgur.com/14UBpML.png
- Justin + Jason: https://i.imgur.com/lDfZnma.pngWe really don't want another top level menu. We're not that important. Rather, crypto libraries are but one ordinary subset of ordinary libraries, just like how the build system does it too.
Quoted 8 lines
Quoted 2 lines
I disagree. The root menu is a jumble of things already, and having this one at the root is really not a problem.
Should CRC routines also go into a submenu and be put at the root? What about other library functions? Library functions belong in the library submenu. We don't need our own top level submenu for this. The whole point of
lib/crypto/is that they're just boring library functions. Libraries! So, part of the libraries menu.
Quoted 5 lines
Specifically in this menu, users were expecting to see it in the Cryptographic API menu. I think having it in the main menu just below this entry is much more appropriate than being buried under another menu. Particularly if the goal is to get rid of the menu again all together once we can audit the full set of deps on crypto libraries.
The thing is, even once we get rid of the labels, part of detangling everything is going to involve moving the sourcing of those symbols into lib/Kconfig anyway. No use delaying the inevitable.
Ard Biesheuvel
maintainerQuoted 33 lines · Jason A. Donenfeld
Quoted 31 lines · Ard Biesheuvel
Quoted 28 lines · Jason A. Donenfeld
Quoted 10 lines · Ard Biesheuvel
Quoted 8 lines · Jason A. Donenfeld
Quoted 6 lines · Ard Biesheuvel
Quoted 3 lines · Jason A. Donenfeld
This commit also needs this snippet:
Quoted 7 lines
Quoted 5 lines
Quoted 1 line
Why?
So that the menu of crypto library options is inside of the library menu. Otherwise this will appear inside of the _root_ menu, which isn't what we want.
Why not? I think that's fine.
It's really not appropriate there. Look:
- Justin vanilla: https://i.imgur.com/14UBpML.png
- Justin + Jason: https://i.imgur.com/lDfZnma.pngWe really don't want another top level menu. We're not that important. Rather, crypto libraries are but one ordinary subset of ordinary libraries, just like how the build system does it too.
Quoted 8 lines
Quoted 2 lines
I disagree. The root menu is a jumble of things already, and having this one at the root is really not a problem.
Should CRC routines also go into a submenu and be put at the root? What about other library functions? Library functions belong in the library submenu. We don't need our own top level submenu for this. The whole point of
lib/crypto/is that they're just boring library functions. Libraries! So, part of the libraries menu.
Shouting it doesn't make it true.
Nobody cares about what the root menu looks like, and given that this patch is presumably going to be sent as an early fix on top of your rng branch, it is better not to touch anything under crypto/ unless you are 100% certain it is not going to conflict with Herbert's tree.
Jason A. Donenfeld
maintainerQuoted 38 lines · Ard Biesheuvel
Quoted 36 lines · Jason A. Donenfeld
Quoted 33 lines · Ard Biesheuvel
Quoted 20 lines · Jason A. Donenfeld
Quoted 10 lines · Ard Biesheuvel
Quoted 8 lines · Jason A. Donenfeld
Quoted 6 lines · Ard Biesheuvel
Quoted 3 lines · Jason A. Donenfeld
This commit also needs this snippet:
Quoted 7 lines
Quoted 5 lines
Quoted 1 line
Why?
So that the menu of crypto library options is inside of the library menu. Otherwise this will appear inside of the _root_ menu, which isn't what we want.
Why not? I think that's fine.
Quoted 8 lines
It's really not appropriate there. Look:
- Justin vanilla: https://i.imgur.com/14UBpML.png
- Justin + Jason: https://i.imgur.com/lDfZnma.pngWe really don't want another top level menu. We're not that important. Rather, crypto libraries are but one ordinary subset of ordinary libraries, just like how the build system does it too.
I disagree. The root menu is a jumble of things already, and having this one at the root is really not a problem.
Quoted 7 lines
Quoted 5 lines
Should CRC routines also go into a submenu and be put at the root? What about other library functions? Library functions belong in the library submenu. We don't need our own top level submenu for this. The whole point of
lib/crypto/is that they're just boring library functions. Libraries! So, part of the libraries menu.Shouting it doesn't make it true.
I'm not shouting. I respectfully disagree with your perspective. I think the comparison to CRC routines is an apt one, still unaddressed.
Quoted 1 line
Nobody cares about what the root menu looks like
I certainly do.
Quoted 4 lines
and given that this
patch is presumably going to be sent as an early fix on top of your rng branch, it is better not to touch anything undercrypto/unless you are 100% certain it is not going to conflict with Herbert's tree.
Oh, I was thinking Herbert would take this since he hasn't sent a pull yet? Otherwise, sure, I can do it.
Jason
Ard Biesheuvel
maintainerQuoted 46 lines · Jason A. Donenfeld
Quoted 44 lines · Ard Biesheuvel
Quoted 41 lines · Jason A. Donenfeld
Quoted 27 lines · Ard Biesheuvel
Quoted 25 lines · Jason A. Donenfeld
Quoted 10 lines · Ard Biesheuvel
Quoted 8 lines · Jason A. Donenfeld
Quoted 6 lines · Ard Biesheuvel
Quoted 3 lines · Jason A. Donenfeld
This commit also needs this snippet:
Quoted 7 lines
Quoted 5 lines
Quoted 1 line
Why?
So that the menu of crypto library options is inside of the library menu. Otherwise this will appear inside of the _root_ menu, which isn't what we want.
Why not? I think that's fine.
It's really not appropriate there. Look:
- Justin vanilla: https://i.imgur.com/14UBpML.png
- Justin + Jason: https://i.imgur.com/lDfZnma.pngQuoted 6 lines
Quoted 3 lines
We really don't want another top level menu. We're not that important. Rather, crypto libraries are but one ordinary subset of ordinary libraries, just like how the build system does it too.
I disagree. The root menu is a jumble of things already, and having this one at the root is really not a problem.
Should CRC routines also go into a submenu and be put at the root? What about other library functions? Library functions belong in the library submenu. We don't need our own top level submenu for this. The whole point of
lib/crypto/is that they're just boring library functions. Libraries! So, part of the libraries menu.
Quoted 5 lines
Quoted 1 line
Shouting it doesn't make it true.
I'm not shouting. I respectfully disagree with your perspective. I think the comparison to CRC routines is an apt one, still unaddressed.
Sure, but none of this is relevant for the short term fix that we need to get in asap. There are lots of future changes we can philosophize about, but those discussions should take place on the linux-crypto list after the merge window closes.
Quoted 4 lines
Quoted 1 line
Nobody cares about what the root menu looks like
I certainly do.
Fair enough. But on many architectures, it looks absolutely horrid, and I rarely see fixes sent for it.
Quoted 8 lines
Quoted 4 lines
and given that this
patch is presumably going to be sent as an early fix on top of your rng branch, it is better not to touch anything undercrypto/unless you are 100% certain it is not going to conflict with Herbert's tree.Oh, I was thinking Herbert would take this since he hasn't sent a pull yet? Otherwise, sure, I can do it.
How could he? This patch does not apply to his cryptodev tree, which won't receive backmerges from mainline until the next cycle.
Jason A. Donenfeld
maintainerQuoted 5 lines · Ard Biesheuvel
Sure, but none of this is relevant for the short term fix that we need to get in asap. There are lots of future changes we can philosophize about, but those discussions should take place on the linux-crypto list after the merge window closes.
I think of adding things to the root menu as a regression. I'd like to avoid an additional regression in fixing this.
Quoted 11 lines
Quoted 8 lines
Quoted 4 lines
and given that this
patch is presumably going to be sent as an early fix on top of your rng branch, it is better not to touch anything undercrypto/unless you are 100% certain it is not going to conflict with Herbert's tree.Oh, I was thinking Herbert would take this since he hasn't sent a pull yet? Otherwise, sure, I can do it.
How could he? This patch does not apply to his cryptodev tree, which won't receive backmerges from mainline until the next cycle.
Oh, okay then. I'll take it. In which case, I really don't want to be the one responsible for mucking up the root menu with something nobody cares about (crypto library submenu). I'll fix up the menu location thing locally then and send a v3 here.
Jason
Jason A. Donenfeld
maintainerPATCH v3 1/1 lib/crypto: add prompts back to crypto libraries
From: "Justin M. Forbes" <[email protected]>
Commit 6048fdcc5f269 ("lib/crypto: blake2s: include as built-in") took away a number of prompt texts from other crypto libraries. This makes values flip from built-in to module when oldconfig runs, and causes problems when these crypto libs need to be built in for thingslike BIG_KEYS.
--- crypto/Kconfig | 2 -- lib/Kconfig | 2 ++ lib/crypto/Kconfig | 12 ++++++++---- 3 files changed, 10 insertions(+), 6 deletions(-)
crypto/Kconfig +0 -2
@@ -1924,5 +1924,3 @@ source "crypto/asymmetric_keys/Kconfig" source "certs/Kconfig" endif # if CRYPTO - -source "lib/crypto/Kconfig"
lib/Kconfig +2 -0
@@ -122,6 +122,8 @@ config INDIRECT_IOMEM_FALLBACK mmio accesses when the IO memory address is not a registered emulated region. +source "lib/crypto/Kconfig" + config CRC_CCITT tristate "CRC-CCITT functions" help
lib/crypto/Kconfig +8 -4
@@ -1,5 +1,7 @@ # SPDX-License-Identifier: GPL-2.0 +menu "Crypto library routines" + config CRYPTO_LIB_AES tristate
@@ -40,7 +42,7 @@ config CRYPTO_LIB_CHACHA_GENERIC of CRYPTO_LIB_CHACHA. config CRYPTO_LIB_CHACHA - tristate + tristate "ChaCha library interface" depends on CRYPTO_ARCH_HAVE_LIB_CHACHA || !CRYPTO_ARCH_HAVE_LIB_CHACHA select CRYPTO_LIB_CHACHA_GENERIC if CRYPTO_ARCH_HAVE_LIB_CHACHA=n help
@@ -65,7 +67,7 @@ config CRYPTO_LIB_CURVE25519_GENERIC of CRYPTO_LIB_CURVE25519. config CRYPTO_LIB_CURVE25519 - tristate + tristate "Curve25519 scalar multiplication library" depends on CRYPTO_ARCH_HAVE_LIB_CURVE25519 || !CRYPTO_ARCH_HAVE_LIB_CURVE25519 select CRYPTO_LIB_CURVE25519_GENERIC if CRYPTO_ARCH_HAVE_LIB_CURVE25519=n help
@@ -100,7 +102,7 @@ config CRYPTO_LIB_POLY1305_GENERIC of CRYPTO_LIB_POLY1305. config CRYPTO_LIB_POLY1305 - tristate + tristate "Poly1305 library interface" depends on CRYPTO_ARCH_HAVE_LIB_POLY1305 || !CRYPTO_ARCH_HAVE_LIB_POLY1305 select CRYPTO_LIB_POLY1305_GENERIC if CRYPTO_ARCH_HAVE_LIB_POLY1305=n help
@@ -109,7 +111,7 @@ config CRYPTO_LIB_POLY1305 is available and enabled. config CRYPTO_LIB_CHACHA20POLY1305 - tristate + tristate "ChaCha20-Poly1305 AEAD support (8-byte nonce library version)" depends on CRYPTO_ARCH_HAVE_LIB_CHACHA || !CRYPTO_ARCH_HAVE_LIB_CHACHA depends on CRYPTO_ARCH_HAVE_LIB_POLY1305 || !CRYPTO_ARCH_HAVE_LIB_POLY1305 select CRYPTO_LIB_CHACHA
@@ -120,3 +122,5 @@ config CRYPTO_LIB_SHA256 config CRYPTO_LIB_SM4 tristate + +endmenu
Signature · 1 line
2.34.1
Jason A. Donenfeld
maintainerPATCH v4 1/1 lib/crypto: add prompts back to crypto libraries
From: "Justin M. Forbes" <[email protected]>
Commit 6048fdcc5f269 ("lib/crypto: blake2s: include as built-in") took away a number of prompt texts from other crypto libraries. This makes values flip from built-in to module when oldconfig runs, and causes problems when these crypto libs need to be built in for thingslike BIG_KEYS.
[Jason: - moved menu into submenu of lib/ instead of root menu
- fixed chacha sub-dependencies for CONFIG_CRYPTO]
--- crypto/Kconfig | 2 -- lib/Kconfig | 2 ++ lib/crypto/Kconfig | 17 ++++++++++++----- 3 files changed, 14 insertions(+), 7 deletions(-)
crypto/Kconfig +0 -2
@@ -1924,5 +1924,3 @@ source "crypto/asymmetric_keys/Kconfig" source "certs/Kconfig" endif # if CRYPTO - -source "lib/crypto/Kconfig"
lib/Kconfig +2 -0
@@ -122,6 +122,8 @@ config INDIRECT_IOMEM_FALLBACK mmio accesses when the IO memory address is not a registered emulated region. +source "lib/crypto/Kconfig" + config CRC_CCITT tristate "CRC-CCITT functions" help
lib/crypto/Kconfig +12 -5
@@ -1,5 +1,7 @@ # SPDX-License-Identifier: GPL-2.0 +menu "Crypto library routines" + config CRYPTO_LIB_AES tristate
@@ -31,7 +33,7 @@ config CRYPTO_ARCH_HAVE_LIB_CHACHA config CRYPTO_LIB_CHACHA_GENERIC tristate - select CRYPTO_ALGAPI + select XOR_BLOCKS help This symbol can be depended upon by arch implementations of the ChaCha library interface that require the generic code as a
@@ -40,7 +42,8 @@ config CRYPTO_LIB_CHACHA_GENERIC of CRYPTO_LIB_CHACHA. config CRYPTO_LIB_CHACHA - tristate + tristate "ChaCha library interface" + depends on CRYPTO depends on CRYPTO_ARCH_HAVE_LIB_CHACHA || !CRYPTO_ARCH_HAVE_LIB_CHACHA select CRYPTO_LIB_CHACHA_GENERIC if CRYPTO_ARCH_HAVE_LIB_CHACHA=n help
@@ -65,7 +68,7 @@ config CRYPTO_LIB_CURVE25519_GENERIC of CRYPTO_LIB_CURVE25519. config CRYPTO_LIB_CURVE25519 - tristate + tristate "Curve25519 scalar multiplication library" depends on CRYPTO_ARCH_HAVE_LIB_CURVE25519 || !CRYPTO_ARCH_HAVE_LIB_CURVE25519 select CRYPTO_LIB_CURVE25519_GENERIC if CRYPTO_ARCH_HAVE_LIB_CURVE25519=n help
@@ -100,7 +103,7 @@ config CRYPTO_LIB_POLY1305_GENERIC of CRYPTO_LIB_POLY1305. config CRYPTO_LIB_POLY1305 - tristate + tristate "Poly1305 library interface" depends on CRYPTO_ARCH_HAVE_LIB_POLY1305 || !CRYPTO_ARCH_HAVE_LIB_POLY1305 select CRYPTO_LIB_POLY1305_GENERIC if CRYPTO_ARCH_HAVE_LIB_POLY1305=n help
@@ -109,14 +112,18 @@ config CRYPTO_LIB_POLY1305 is available and enabled. config CRYPTO_LIB_CHACHA20POLY1305 - tristate + tristate "ChaCha20-Poly1305 AEAD support (8-byte nonce library version)" depends on CRYPTO_ARCH_HAVE_LIB_CHACHA || !CRYPTO_ARCH_HAVE_LIB_CHACHA depends on CRYPTO_ARCH_HAVE_LIB_POLY1305 || !CRYPTO_ARCH_HAVE_LIB_POLY1305 + depends on CRYPTO select CRYPTO_LIB_CHACHA select CRYPTO_LIB_POLY1305 + select CRYPTO_ALGAPI config CRYPTO_LIB_SHA256 tristate config CRYPTO_LIB_SM4 tristate + +endmenu
Signature · 1 line
2.34.1