1 # SPDX-License-Identifier: GPL-2.0
3 # Generic algorithms support
9 # async_tx api: hardware offloaded memory transfer/transform support
11 source "crypto/async_tx/Kconfig"
14 # Cryptographic API Configuration
17 tristate "Cryptographic API"
19 This option provides the core Cryptographic API.
23 comment "Crypto core or helper"
26 bool "FIPS 200 compliance"
27 depends on (CRYPTO_ANSI_CPRNG || CRYPTO_DRBG) && !CRYPTO_MANAGER_DISABLE_TESTS
28 depends on (MODULE_SIG || !MODULES)
30 This option enables the fips boot option which is
31 required if you want the system to operate in a FIPS 200
32 certification. You should say no unless you know what
39 This option provides the API for cryptographic algorithms.
55 config CRYPTO_SKCIPHER
57 select CRYPTO_SKCIPHER2
60 config CRYPTO_SKCIPHER2
83 config CRYPTO_RNG_DEFAULT
85 select CRYPTO_DRBG_MENU
87 config CRYPTO_AKCIPHER2
91 config CRYPTO_AKCIPHER
93 select CRYPTO_AKCIPHER2
107 select CRYPTO_ALGAPI2
115 config CRYPTO_MANAGER
116 tristate "Cryptographic algorithm manager"
117 select CRYPTO_MANAGER2
119 Create default cryptographic template instantiations such as
122 config CRYPTO_MANAGER2
123 def_tristate CRYPTO_MANAGER || (CRYPTO_MANAGER!=n && CRYPTO_ALGAPI=y)
126 select CRYPTO_SKCIPHER2
127 select CRYPTO_AKCIPHER2
132 tristate "Userspace cryptographic algorithm configuration"
134 select CRYPTO_MANAGER
136 Userspace configuration for cryptographic instantiations such as
139 config CRYPTO_MANAGER_DISABLE_TESTS
140 bool "Disable run-time self tests"
143 Disable run-time self tests that normally take place at
144 algorithm registration.
146 config CRYPTO_MANAGER_EXTRA_TESTS
147 bool "Enable extra run-time crypto self tests"
148 depends on DEBUG_KERNEL && !CRYPTO_MANAGER_DISABLE_TESTS
150 Enable extra run-time self tests of registered crypto algorithms,
151 including randomized fuzz tests.
153 This is intended for developer use only, as these tests take much
154 longer to run than the normal self tests.
156 config CRYPTO_GF128MUL
160 tristate "Null algorithms"
163 These are 'Null' algorithms, used by IPsec, which do nothing.
167 select CRYPTO_ALGAPI2
168 select CRYPTO_SKCIPHER2
172 tristate "Parallel crypto engine"
175 select CRYPTO_MANAGER
178 This converts an arbitrary crypto algorithm into a parallel
179 algorithm that executes in kernel threads.
182 tristate "Software async crypto daemon"
183 select CRYPTO_SKCIPHER
185 select CRYPTO_MANAGER
187 This is a generic software asynchronous crypto daemon that
188 converts an arbitrary synchronous software crypto algorithm
189 into an asynchronous algorithm that executes in a kernel thread.
191 config CRYPTO_AUTHENC
192 tristate "Authenc support"
194 select CRYPTO_SKCIPHER
195 select CRYPTO_MANAGER
199 Authenc: Combined mode wrapper for IPsec.
200 This is required for IPSec.
203 tristate "Testing module"
205 select CRYPTO_MANAGER
207 Quick & dirty crypto test module.
213 config CRYPTO_GLUE_HELPER_X86
216 select CRYPTO_SKCIPHER
221 comment "Public-key cryptography"
224 tristate "RSA algorithm"
225 select CRYPTO_AKCIPHER
226 select CRYPTO_MANAGER
230 Generic implementation of the RSA public key algorithm.
233 tristate "Diffie-Hellman algorithm"
237 Generic implementation of the Diffie-Hellman algorithm.
243 tristate "ECDH algorithm"
246 select CRYPTO_RNG_DEFAULT
248 Generic implementation of the ECDH algorithm
251 tristate "EC-RDSA (GOST 34.10) algorithm"
253 select CRYPTO_AKCIPHER
254 select CRYPTO_STREEBOG
258 Elliptic Curve Russian Digital Signature Algorithm (GOST R 34.10-2012,
259 RFC 7091, ISO/IEC 14888-3:2018) is one of the Russian cryptographic
260 standard algorithms (called GOST algorithms). Only signature verification
263 config CRYPTO_CURVE25519
264 tristate "Curve25519 algorithm"
266 select CRYPTO_LIB_CURVE25519_GENERIC
268 config CRYPTO_CURVE25519_X86
269 tristate "x86_64 accelerated Curve25519 scalar multiplication library"
270 depends on X86 && 64BIT
271 select CRYPTO_LIB_CURVE25519_GENERIC
272 select CRYPTO_ARCH_HAVE_LIB_CURVE25519
274 comment "Authenticated Encryption with Associated Data"
277 tristate "CCM support"
281 select CRYPTO_MANAGER
283 Support for Counter with CBC MAC. Required for IPsec.
286 tristate "GCM/GMAC support"
291 select CRYPTO_MANAGER
293 Support for Galois/Counter Mode (GCM) and Galois Message
294 Authentication Code (GMAC). Required for IPSec.
296 config CRYPTO_CHACHA20POLY1305
297 tristate "ChaCha20-Poly1305 AEAD support"
298 select CRYPTO_CHACHA20
299 select CRYPTO_POLY1305
301 select CRYPTO_MANAGER
303 ChaCha20-Poly1305 AEAD support, RFC7539.
305 Support for the AEAD wrapper using the ChaCha20 stream cipher combined
306 with the Poly1305 authenticator. It is defined in RFC7539 for use in
309 config CRYPTO_AEGIS128
310 tristate "AEGIS-128 AEAD algorithm"
312 select CRYPTO_AES # for AES S-box tables
314 Support for the AEGIS-128 dedicated AEAD algorithm.
316 config CRYPTO_AEGIS128_SIMD
317 bool "Support SIMD acceleration for AEGIS-128"
318 depends on CRYPTO_AEGIS128 && ((ARM || ARM64) && KERNEL_MODE_NEON)
319 depends on !ARM || CC_IS_CLANG || GCC_VERSION >= 40800
322 config CRYPTO_AEGIS128_AESNI_SSE2
323 tristate "AEGIS-128 AEAD algorithm (x86_64 AESNI+SSE2 implementation)"
324 depends on X86 && 64BIT
328 AESNI+SSE2 implementation of the AEGIS-128 dedicated AEAD algorithm.
331 tristate "Sequence Number IV Generator"
333 select CRYPTO_SKCIPHER
335 select CRYPTO_RNG_DEFAULT
336 select CRYPTO_MANAGER
338 This IV generator generates an IV based on a sequence number by
339 xoring it with a salt. This algorithm is mainly useful for CTR
341 config CRYPTO_ECHAINIV
342 tristate "Encrypted Chain IV Generator"
345 select CRYPTO_RNG_DEFAULT
346 select CRYPTO_MANAGER
348 This IV generator generates an IV based on the encryption of
349 a sequence number xored with a salt. This is the default
352 comment "Block modes"
355 tristate "CBC support"
356 select CRYPTO_SKCIPHER
357 select CRYPTO_MANAGER
359 CBC: Cipher Block Chaining mode
360 This block cipher algorithm is required for IPSec.
363 tristate "CFB support"
364 select CRYPTO_SKCIPHER
365 select CRYPTO_MANAGER
367 CFB: Cipher FeedBack mode
368 This block cipher algorithm is required for TPM2 Cryptography.
371 tristate "CTR support"
372 select CRYPTO_SKCIPHER
374 select CRYPTO_MANAGER
377 This block cipher algorithm is required for IPSec.
380 tristate "CTS support"
381 select CRYPTO_SKCIPHER
382 select CRYPTO_MANAGER
384 CTS: Cipher Text Stealing
385 This is the Cipher Text Stealing mode as described by
386 Section 8 of rfc2040 and referenced by rfc3962
387 (rfc3962 includes errata information in its Appendix A) or
388 CBC-CS3 as defined by NIST in Sp800-38A addendum from Oct 2010.
389 This mode is required for Kerberos gss mechanism support
392 See: https://csrc.nist.gov/publications/detail/sp/800-38a/addendum/final
395 tristate "ECB support"
396 select CRYPTO_SKCIPHER
397 select CRYPTO_MANAGER
399 ECB: Electronic CodeBook mode
400 This is the simplest block cipher algorithm. It simply encrypts
401 the input block by block.
404 tristate "LRW support"
405 select CRYPTO_SKCIPHER
406 select CRYPTO_MANAGER
407 select CRYPTO_GF128MUL
409 LRW: Liskov Rivest Wagner, a tweakable, non malleable, non movable
410 narrow block cipher mode for dm-crypt. Use it with cipher
411 specification string aes-lrw-benbi, the key must be 256, 320 or 384.
412 The first 128, 192 or 256 bits in the key are used for AES and the
413 rest is used to tie each cipher block to its logical position.
416 tristate "OFB support"
417 select CRYPTO_SKCIPHER
418 select CRYPTO_MANAGER
420 OFB: the Output Feedback mode makes a block cipher into a synchronous
421 stream cipher. It generates keystream blocks, which are then XORed
422 with the plaintext blocks to get the ciphertext. Flipping a bit in the
423 ciphertext produces a flipped bit in the plaintext at the same
424 location. This property allows many error correcting codes to function
425 normally even when applied before encryption.
428 tristate "PCBC support"
429 select CRYPTO_SKCIPHER
430 select CRYPTO_MANAGER
432 PCBC: Propagating Cipher Block Chaining mode
433 This block cipher algorithm is required for RxRPC.
436 tristate "XTS support"
437 select CRYPTO_SKCIPHER
438 select CRYPTO_MANAGER
441 XTS: IEEE1619/D16 narrow block cipher use with aes-xts-plain,
442 key size 256, 384 or 512 bits. This implementation currently
443 can't handle a sectorsize which is not a multiple of 16 bytes.
445 config CRYPTO_KEYWRAP
446 tristate "Key wrapping support"
447 select CRYPTO_SKCIPHER
448 select CRYPTO_MANAGER
450 Support for key wrapping (NIST SP800-38F / RFC3394) without
453 config CRYPTO_NHPOLY1305
456 select CRYPTO_LIB_POLY1305_GENERIC
458 config CRYPTO_NHPOLY1305_SSE2
459 tristate "NHPoly1305 hash function (x86_64 SSE2 implementation)"
460 depends on X86 && 64BIT
461 select CRYPTO_NHPOLY1305
463 SSE2 optimized implementation of the hash function used by the
464 Adiantum encryption mode.
466 config CRYPTO_NHPOLY1305_AVX2
467 tristate "NHPoly1305 hash function (x86_64 AVX2 implementation)"
468 depends on X86 && 64BIT
469 select CRYPTO_NHPOLY1305
471 AVX2 optimized implementation of the hash function used by the
472 Adiantum encryption mode.
474 config CRYPTO_ADIANTUM
475 tristate "Adiantum support"
476 select CRYPTO_CHACHA20
477 select CRYPTO_LIB_POLY1305_GENERIC
478 select CRYPTO_NHPOLY1305
479 select CRYPTO_MANAGER
481 Adiantum is a tweakable, length-preserving encryption mode
482 designed for fast and secure disk encryption, especially on
483 CPUs without dedicated crypto instructions. It encrypts
484 each sector using the XChaCha12 stream cipher, two passes of
485 an ε-almost-∆-universal hash function, and an invocation of
486 the AES-256 block cipher on a single 16-byte block. On CPUs
487 without AES instructions, Adiantum is much faster than
490 Adiantum's security is provably reducible to that of its
491 underlying stream and block ciphers, subject to a security
492 bound. Unlike XTS, Adiantum is a true wide-block encryption
493 mode, so it actually provides an even stronger notion of
494 security than XTS, subject to the security bound.
499 tristate "ESSIV support for block encryption"
500 select CRYPTO_AUTHENC
502 Encrypted salt-sector initialization vector (ESSIV) is an IV
503 generation method that is used in some cases by fscrypt and/or
504 dm-crypt. It uses the hash of the block encryption key as the
505 symmetric key for a block encryption pass applied to the input
506 IV, making low entropy IV sources more suitable for block
509 This driver implements a crypto API template that can be
510 instantiated either as an skcipher or as an AEAD (depending on the
511 type of the first template argument), and which defers encryption
512 and decryption requests to the encapsulated cipher after applying
513 ESSIV to the input IV. Note that in the AEAD case, it is assumed
514 that the keys are presented in the same format used by the authenc
515 template, and that the IV appears at the end of the authenticated
516 associated data (AAD) region (which is how dm-crypt uses it.)
518 Note that the use of ESSIV is not recommended for new deployments,
519 and so this only needs to be enabled when interoperability with
520 existing encrypted volumes of filesystems is required, or when
521 building for a particular system that requires it (e.g., when
522 the SoC in question has accelerated CBC but not XTS, making CBC
523 combined with ESSIV the only feasible mode for h/w accelerated
529 tristate "CMAC support"
531 select CRYPTO_MANAGER
533 Cipher-based Message Authentication Code (CMAC) specified by
534 The National Institute of Standards and Technology (NIST).
536 https://tools.ietf.org/html/rfc4493
537 http://csrc.nist.gov/publications/nistpubs/800-38B/SP_800-38B.pdf
540 tristate "HMAC support"
542 select CRYPTO_MANAGER
544 HMAC: Keyed-Hashing for Message Authentication (RFC2104).
545 This is required for IPSec.
548 tristate "XCBC support"
550 select CRYPTO_MANAGER
552 XCBC: Keyed-Hashing with encryption algorithm
553 http://www.ietf.org/rfc/rfc3566.txt
554 http://csrc.nist.gov/encryption/modes/proposedmodes/
555 xcbc-mac/xcbc-mac-spec.pdf
558 tristate "VMAC support"
560 select CRYPTO_MANAGER
562 VMAC is a message authentication algorithm designed for
563 very high speed on 64-bit architectures.
566 <http://fastcrypto.org/vmac>
571 tristate "CRC32c CRC algorithm"
575 Castagnoli, et al Cyclic Redundancy-Check Algorithm. Used
576 by iSCSI for header and data digests and by others.
577 See Castagnoli93. Module will be crc32c.
579 config CRYPTO_CRC32C_INTEL
580 tristate "CRC32c INTEL hardware acceleration"
584 In Intel processor with SSE4.2 supported, the processor will
585 support CRC32C implementation using hardware accelerated CRC32
586 instruction. This option will create 'crc32c-intel' module,
587 which will enable any routine to use the CRC32 instruction to
588 gain performance compared with software implementation.
589 Module will be crc32c-intel.
591 config CRYPTO_CRC32C_VPMSUM
592 tristate "CRC32c CRC algorithm (powerpc64)"
593 depends on PPC64 && ALTIVEC
597 CRC32c algorithm implemented using vector polynomial multiply-sum
598 (vpmsum) instructions, introduced in POWER8. Enable on POWER8
599 and newer processors for improved performance.
602 config CRYPTO_CRC32C_SPARC64
603 tristate "CRC32c CRC algorithm (SPARC64)"
608 CRC32c CRC algorithm implemented using sparc64 crypto instructions,
612 tristate "CRC32 CRC algorithm"
616 CRC-32-IEEE 802.3 cyclic redundancy-check algorithm.
617 Shash crypto api wrappers to crc32_le function.
619 config CRYPTO_CRC32_PCLMUL
620 tristate "CRC32 PCLMULQDQ hardware acceleration"
625 From Intel Westmere and AMD Bulldozer processor with SSE4.2
626 and PCLMULQDQ supported, the processor will support
627 CRC32 PCLMULQDQ implementation using hardware accelerated PCLMULQDQ
628 instruction. This option will create 'crc32-pclmul' module,
629 which will enable any routine to use the CRC-32-IEEE 802.3 checksum
630 and gain better performance as compared with the table implementation.
632 config CRYPTO_CRC32_MIPS
633 tristate "CRC32c and CRC32 CRC algorithm (MIPS)"
634 depends on MIPS_CRC_SUPPORT
637 CRC32c and CRC32 CRC algorithms implemented using mips crypto
638 instructions, when available.
642 tristate "xxHash hash algorithm"
646 xxHash non-cryptographic hash algorithm. Extremely fast, working at
647 speeds close to RAM limits.
649 config CRYPTO_BLAKE2B
650 tristate "BLAKE2b digest algorithm"
653 Implementation of cryptographic hash function BLAKE2b (or just BLAKE2),
654 optimized for 64bit platforms and can produce digests of any size
655 between 1 to 64. The keyed hash is also implemented.
657 This module provides the following algorithms:
664 See https://blake2.net for further information.
666 config CRYPTO_BLAKE2S
667 tristate "BLAKE2s digest algorithm"
668 select CRYPTO_LIB_BLAKE2S_GENERIC
671 Implementation of cryptographic hash function BLAKE2s
672 optimized for 8-32bit platforms and can produce digests of any size
673 between 1 to 32. The keyed hash is also implemented.
675 This module provides the following algorithms:
682 See https://blake2.net for further information.
684 config CRYPTO_BLAKE2S_X86
685 tristate "BLAKE2s digest algorithm (x86 accelerated version)"
686 depends on X86 && 64BIT
687 select CRYPTO_LIB_BLAKE2S_GENERIC
688 select CRYPTO_ARCH_HAVE_LIB_BLAKE2S
690 config CRYPTO_CRCT10DIF
691 tristate "CRCT10DIF algorithm"
694 CRC T10 Data Integrity Field computation is being cast as
695 a crypto transform. This allows for faster crc t10 diff
696 transforms to be used if they are available.
698 config CRYPTO_CRCT10DIF_PCLMUL
699 tristate "CRCT10DIF PCLMULQDQ hardware acceleration"
700 depends on X86 && 64BIT && CRC_T10DIF
703 For x86_64 processors with SSE4.2 and PCLMULQDQ supported,
704 CRC T10 DIF PCLMULQDQ computation can be hardware
705 accelerated PCLMULQDQ instruction. This option will create
706 'crct10dif-pclmul' module, which is faster when computing the
707 crct10dif checksum as compared with the generic table implementation.
709 config CRYPTO_CRCT10DIF_VPMSUM
710 tristate "CRC32T10DIF powerpc64 hardware acceleration"
711 depends on PPC64 && ALTIVEC && CRC_T10DIF
714 CRC10T10DIF algorithm implemented using vector polynomial
715 multiply-sum (vpmsum) instructions, introduced in POWER8. Enable on
716 POWER8 and newer processors for improved performance.
718 config CRYPTO_VPMSUM_TESTER
719 tristate "Powerpc64 vpmsum hardware acceleration tester"
720 depends on CRYPTO_CRCT10DIF_VPMSUM && CRYPTO_CRC32C_VPMSUM
722 Stress test for CRC32c and CRC-T10DIF algorithms implemented with
723 POWER8 vpmsum instructions.
724 Unless you are testing these algorithms, you don't need this.
727 tristate "GHASH hash function"
728 select CRYPTO_GF128MUL
731 GHASH is the hash function used in GCM (Galois/Counter Mode).
732 It is not a general-purpose cryptographic hash function.
734 config CRYPTO_POLY1305
735 tristate "Poly1305 authenticator algorithm"
737 select CRYPTO_LIB_POLY1305_GENERIC
739 Poly1305 authenticator algorithm, RFC7539.
741 Poly1305 is an authenticator algorithm designed by Daniel J. Bernstein.
742 It is used for the ChaCha20-Poly1305 AEAD, specified in RFC7539 for use
743 in IETF protocols. This is the portable C implementation of Poly1305.
745 config CRYPTO_POLY1305_X86_64
746 tristate "Poly1305 authenticator algorithm (x86_64/SSE2/AVX2)"
747 depends on X86 && 64BIT
748 select CRYPTO_LIB_POLY1305_GENERIC
749 select CRYPTO_ARCH_HAVE_LIB_POLY1305
751 Poly1305 authenticator algorithm, RFC7539.
753 Poly1305 is an authenticator algorithm designed by Daniel J. Bernstein.
754 It is used for the ChaCha20-Poly1305 AEAD, specified in RFC7539 for use
755 in IETF protocols. This is the x86_64 assembler implementation using SIMD
758 config CRYPTO_POLY1305_MIPS
759 tristate "Poly1305 authenticator algorithm (MIPS optimized)"
760 depends on CPU_MIPS32 || (CPU_MIPS64 && 64BIT)
761 select CRYPTO_ARCH_HAVE_LIB_POLY1305
764 tristate "MD4 digest algorithm"
767 MD4 message digest algorithm (RFC1320).
770 tristate "MD5 digest algorithm"
773 MD5 message digest algorithm (RFC1321).
775 config CRYPTO_MD5_OCTEON
776 tristate "MD5 digest algorithm (OCTEON)"
777 depends on CPU_CAVIUM_OCTEON
781 MD5 message digest algorithm (RFC1321) implemented
782 using OCTEON crypto instructions, when available.
784 config CRYPTO_MD5_PPC
785 tristate "MD5 digest algorithm (PPC)"
789 MD5 message digest algorithm (RFC1321) implemented
792 config CRYPTO_MD5_SPARC64
793 tristate "MD5 digest algorithm (SPARC64)"
798 MD5 message digest algorithm (RFC1321) implemented
799 using sparc64 crypto instructions, when available.
801 config CRYPTO_MICHAEL_MIC
802 tristate "Michael MIC keyed digest algorithm"
805 Michael MIC is used for message integrity protection in TKIP
806 (IEEE 802.11i). This algorithm is required for TKIP, but it
807 should not be used for other purposes because of the weakness
811 tristate "RIPEMD-128 digest algorithm"
814 RIPEMD-128 (ISO/IEC 10118-3:2004).
816 RIPEMD-128 is a 128-bit cryptographic hash function. It should only
817 be used as a secure replacement for RIPEMD. For other use cases,
818 RIPEMD-160 should be used.
820 Developed by Hans Dobbertin, Antoon Bosselaers and Bart Preneel.
821 See <http://homes.esat.kuleuven.be/~bosselae/ripemd160.html>
824 tristate "RIPEMD-160 digest algorithm"
827 RIPEMD-160 (ISO/IEC 10118-3:2004).
829 RIPEMD-160 is a 160-bit cryptographic hash function. It is intended
830 to be used as a secure replacement for the 128-bit hash functions
831 MD4, MD5 and it's predecessor RIPEMD
832 (not to be confused with RIPEMD-128).
834 It's speed is comparable to SHA1 and there are no known attacks
837 Developed by Hans Dobbertin, Antoon Bosselaers and Bart Preneel.
838 See <http://homes.esat.kuleuven.be/~bosselae/ripemd160.html>
841 tristate "RIPEMD-256 digest algorithm"
844 RIPEMD-256 is an optional extension of RIPEMD-128 with a
845 256 bit hash. It is intended for applications that require
846 longer hash-results, without needing a larger security level
849 Developed by Hans Dobbertin, Antoon Bosselaers and Bart Preneel.
850 See <http://homes.esat.kuleuven.be/~bosselae/ripemd160.html>
853 tristate "RIPEMD-320 digest algorithm"
856 RIPEMD-320 is an optional extension of RIPEMD-160 with a
857 320 bit hash. It is intended for applications that require
858 longer hash-results, without needing a larger security level
861 Developed by Hans Dobbertin, Antoon Bosselaers and Bart Preneel.
862 See <http://homes.esat.kuleuven.be/~bosselae/ripemd160.html>
865 tristate "SHA1 digest algorithm"
868 SHA-1 secure hash standard (FIPS 180-1/DFIPS 180-2).
870 config CRYPTO_SHA1_SSSE3
871 tristate "SHA1 digest algorithm (SSSE3/AVX/AVX2/SHA-NI)"
872 depends on X86 && 64BIT
876 SHA-1 secure hash standard (FIPS 180-1/DFIPS 180-2) implemented
877 using Supplemental SSE3 (SSSE3) instructions or Advanced Vector
878 Extensions (AVX/AVX2) or SHA-NI(SHA Extensions New Instructions),
881 config CRYPTO_SHA256_SSSE3
882 tristate "SHA256 digest algorithm (SSSE3/AVX/AVX2/SHA-NI)"
883 depends on X86 && 64BIT
887 SHA-256 secure hash standard (DFIPS 180-2) implemented
888 using Supplemental SSE3 (SSSE3) instructions, or Advanced Vector
889 Extensions version 1 (AVX1), or Advanced Vector Extensions
890 version 2 (AVX2) instructions, or SHA-NI (SHA Extensions New
891 Instructions) when available.
893 config CRYPTO_SHA512_SSSE3
894 tristate "SHA512 digest algorithm (SSSE3/AVX/AVX2)"
895 depends on X86 && 64BIT
899 SHA-512 secure hash standard (DFIPS 180-2) implemented
900 using Supplemental SSE3 (SSSE3) instructions, or Advanced Vector
901 Extensions version 1 (AVX1), or Advanced Vector Extensions
902 version 2 (AVX2) instructions, when available.
904 config CRYPTO_SHA1_OCTEON
905 tristate "SHA1 digest algorithm (OCTEON)"
906 depends on CPU_CAVIUM_OCTEON
910 SHA-1 secure hash standard (FIPS 180-1/DFIPS 180-2) implemented
911 using OCTEON crypto instructions, when available.
913 config CRYPTO_SHA1_SPARC64
914 tristate "SHA1 digest algorithm (SPARC64)"
919 SHA-1 secure hash standard (FIPS 180-1/DFIPS 180-2) implemented
920 using sparc64 crypto instructions, when available.
922 config CRYPTO_SHA1_PPC
923 tristate "SHA1 digest algorithm (powerpc)"
926 This is the powerpc hardware accelerated implementation of the
927 SHA-1 secure hash standard (FIPS 180-1/DFIPS 180-2).
929 config CRYPTO_SHA1_PPC_SPE
930 tristate "SHA1 digest algorithm (PPC SPE)"
931 depends on PPC && SPE
933 SHA-1 secure hash standard (DFIPS 180-4) implemented
934 using powerpc SPE SIMD instruction set.
937 tristate "SHA224 and SHA256 digest algorithm"
939 select CRYPTO_LIB_SHA256
941 SHA256 secure hash standard (DFIPS 180-2).
943 This version of SHA implements a 256 bit hash with 128 bits of
944 security against collision attacks.
946 This code also includes SHA-224, a 224 bit hash with 112 bits
947 of security against collision attacks.
949 config CRYPTO_SHA256_PPC_SPE
950 tristate "SHA224 and SHA256 digest algorithm (PPC SPE)"
951 depends on PPC && SPE
955 SHA224 and SHA256 secure hash standard (DFIPS 180-2)
956 implemented using powerpc SPE SIMD instruction set.
958 config CRYPTO_SHA256_OCTEON
959 tristate "SHA224 and SHA256 digest algorithm (OCTEON)"
960 depends on CPU_CAVIUM_OCTEON
964 SHA-256 secure hash standard (DFIPS 180-2) implemented
965 using OCTEON crypto instructions, when available.
967 config CRYPTO_SHA256_SPARC64
968 tristate "SHA224 and SHA256 digest algorithm (SPARC64)"
973 SHA-256 secure hash standard (DFIPS 180-2) implemented
974 using sparc64 crypto instructions, when available.
977 tristate "SHA384 and SHA512 digest algorithms"
980 SHA512 secure hash standard (DFIPS 180-2).
982 This version of SHA implements a 512 bit hash with 256 bits of
983 security against collision attacks.
985 This code also includes SHA-384, a 384 bit hash with 192 bits
986 of security against collision attacks.
988 config CRYPTO_SHA512_OCTEON
989 tristate "SHA384 and SHA512 digest algorithms (OCTEON)"
990 depends on CPU_CAVIUM_OCTEON
994 SHA-512 secure hash standard (DFIPS 180-2) implemented
995 using OCTEON crypto instructions, when available.
997 config CRYPTO_SHA512_SPARC64
998 tristate "SHA384 and SHA512 digest algorithm (SPARC64)"
1000 select CRYPTO_SHA512
1003 SHA-512 secure hash standard (DFIPS 180-2) implemented
1004 using sparc64 crypto instructions, when available.
1007 tristate "SHA3 digest algorithm"
1010 SHA-3 secure hash standard (DFIPS 202). It's based on
1011 cryptographic sponge function family called Keccak.
1014 http://keccak.noekeon.org/
1017 tristate "SM3 digest algorithm"
1020 SM3 secure hash function as defined by OSCCA GM/T 0004-2012 SM3).
1021 It is part of the Chinese Commercial Cryptography suite.
1024 http://www.oscca.gov.cn/UpFile/20101222141857786.pdf
1025 https://datatracker.ietf.org/doc/html/draft-shen-sm3-hash
1027 config CRYPTO_STREEBOG
1028 tristate "Streebog Hash Function"
1031 Streebog Hash Function (GOST R 34.11-2012, RFC 6986) is one of the Russian
1032 cryptographic standard algorithms (called GOST algorithms).
1033 This setting enables two hash algorithms with 256 and 512 bits output.
1036 https://tc26.ru/upload/iblock/fed/feddbb4d26b685903faa2ba11aea43f6.pdf
1037 https://tools.ietf.org/html/rfc6986
1039 config CRYPTO_TGR192
1040 tristate "Tiger digest algorithms"
1043 Tiger hash algorithm 192, 160 and 128-bit hashes
1045 Tiger is a hash function optimized for 64-bit processors while
1046 still having decent performance on 32-bit processors.
1047 Tiger was developed by Ross Anderson and Eli Biham.
1050 <http://www.cs.technion.ac.il/~biham/Reports/Tiger/>.
1053 tristate "Whirlpool digest algorithms"
1056 Whirlpool hash algorithm 512, 384 and 256-bit hashes
1058 Whirlpool-512 is part of the NESSIE cryptographic primitives.
1059 Whirlpool will be part of the ISO/IEC 10118-3:2003(E) standard
1062 <http://www.larc.usp.br/~pbarreto/WhirlpoolPage.html>
1064 config CRYPTO_GHASH_CLMUL_NI_INTEL
1065 tristate "GHASH hash function (CLMUL-NI accelerated)"
1066 depends on X86 && 64BIT
1067 select CRYPTO_CRYPTD
1069 This is the x86_64 CLMUL-NI accelerated implementation of
1070 GHASH, the hash function used in GCM (Galois/Counter mode).
1075 tristate "AES cipher algorithms"
1076 select CRYPTO_ALGAPI
1077 select CRYPTO_LIB_AES
1079 AES cipher algorithms (FIPS-197). AES uses the Rijndael
1082 Rijndael appears to be consistently a very good performer in
1083 both hardware and software across a wide range of computing
1084 environments regardless of its use in feedback or non-feedback
1085 modes. Its key setup time is excellent, and its key agility is
1086 good. Rijndael's very low memory requirements make it very well
1087 suited for restricted-space environments, in which it also
1088 demonstrates excellent performance. Rijndael's operations are
1089 among the easiest to defend against power and timing attacks.
1091 The AES specifies three key sizes: 128, 192 and 256 bits
1093 See <http://csrc.nist.gov/CryptoToolkit/aes/> for more information.
1095 config CRYPTO_AES_TI
1096 tristate "Fixed time AES cipher"
1097 select CRYPTO_ALGAPI
1098 select CRYPTO_LIB_AES
1100 This is a generic implementation of AES that attempts to eliminate
1101 data dependent latencies as much as possible without affecting
1102 performance too much. It is intended for use by the generic CCM
1103 and GCM drivers, and other CTR or CMAC/XCBC based modes that rely
1104 solely on encryption (although decryption is supported as well, but
1105 with a more dramatic performance hit)
1107 Instead of using 16 lookup tables of 1 KB each, (8 for encryption and
1108 8 for decryption), this implementation only uses just two S-boxes of
1109 256 bytes each, and attempts to eliminate data dependent latencies by
1110 prefetching the entire table into the cache at the start of each
1111 block. Interrupts are also disabled to avoid races where cachelines
1112 are evicted when the CPU is interrupted to do something else.
1114 config CRYPTO_AES_NI_INTEL
1115 tristate "AES cipher algorithms (AES-NI)"
1118 select CRYPTO_LIB_AES
1119 select CRYPTO_ALGAPI
1120 select CRYPTO_SKCIPHER
1121 select CRYPTO_GLUE_HELPER_X86 if 64BIT
1124 Use Intel AES-NI instructions for AES algorithm.
1126 AES cipher algorithms (FIPS-197). AES uses the Rijndael
1129 Rijndael appears to be consistently a very good performer in
1130 both hardware and software across a wide range of computing
1131 environments regardless of its use in feedback or non-feedback
1132 modes. Its key setup time is excellent, and its key agility is
1133 good. Rijndael's very low memory requirements make it very well
1134 suited for restricted-space environments, in which it also
1135 demonstrates excellent performance. Rijndael's operations are
1136 among the easiest to defend against power and timing attacks.
1138 The AES specifies three key sizes: 128, 192 and 256 bits
1140 See <http://csrc.nist.gov/encryption/aes/> for more information.
1142 In addition to AES cipher algorithm support, the acceleration
1143 for some popular block cipher mode is supported too, including
1144 ECB, CBC, LRW, XTS. The 64 bit version has additional
1145 acceleration for CTR.
1147 config CRYPTO_AES_SPARC64
1148 tristate "AES cipher algorithms (SPARC64)"
1150 select CRYPTO_SKCIPHER
1152 Use SPARC64 crypto opcodes for AES algorithm.
1154 AES cipher algorithms (FIPS-197). AES uses the Rijndael
1157 Rijndael appears to be consistently a very good performer in
1158 both hardware and software across a wide range of computing
1159 environments regardless of its use in feedback or non-feedback
1160 modes. Its key setup time is excellent, and its key agility is
1161 good. Rijndael's very low memory requirements make it very well
1162 suited for restricted-space environments, in which it also
1163 demonstrates excellent performance. Rijndael's operations are
1164 among the easiest to defend against power and timing attacks.
1166 The AES specifies three key sizes: 128, 192 and 256 bits
1168 See <http://csrc.nist.gov/encryption/aes/> for more information.
1170 In addition to AES cipher algorithm support, the acceleration
1171 for some popular block cipher mode is supported too, including
1174 config CRYPTO_AES_PPC_SPE
1175 tristate "AES cipher algorithms (PPC SPE)"
1176 depends on PPC && SPE
1177 select CRYPTO_SKCIPHER
1179 AES cipher algorithms (FIPS-197). Additionally the acceleration
1180 for popular block cipher modes ECB, CBC, CTR and XTS is supported.
1181 This module should only be used for low power (router) devices
1182 without hardware AES acceleration (e.g. caam crypto). It reduces the
1183 size of the AES tables from 16KB to 8KB + 256 bytes and mitigates
1184 timining attacks. Nevertheless it might be not as secure as other
1185 architecture specific assembler implementations that work on 1KB
1186 tables or 256 bytes S-boxes.
1188 config CRYPTO_ANUBIS
1189 tristate "Anubis cipher algorithm"
1190 select CRYPTO_ALGAPI
1192 Anubis cipher algorithm.
1194 Anubis is a variable key length cipher which can use keys from
1195 128 bits to 320 bits in length. It was evaluated as a entrant
1196 in the NESSIE competition.
1199 <https://www.cosic.esat.kuleuven.be/nessie/reports/>
1200 <http://www.larc.usp.br/~pbarreto/AnubisPage.html>
1203 tristate "ARC4 cipher algorithm"
1204 select CRYPTO_SKCIPHER
1205 select CRYPTO_LIB_ARC4
1207 ARC4 cipher algorithm.
1209 ARC4 is a stream cipher using keys ranging from 8 bits to 2048
1210 bits in length. This algorithm is required for driver-based
1211 WEP, but it should not be for other purposes because of the
1212 weakness of the algorithm.
1214 config CRYPTO_BLOWFISH
1215 tristate "Blowfish cipher algorithm"
1216 select CRYPTO_ALGAPI
1217 select CRYPTO_BLOWFISH_COMMON
1219 Blowfish cipher algorithm, by Bruce Schneier.
1221 This is a variable key length cipher which can use keys from 32
1222 bits to 448 bits in length. It's fast, simple and specifically
1223 designed for use on "large microprocessors".
1226 <http://www.schneier.com/blowfish.html>
1228 config CRYPTO_BLOWFISH_COMMON
1231 Common parts of the Blowfish cipher algorithm shared by the
1232 generic c and the assembler implementations.
1235 <http://www.schneier.com/blowfish.html>
1237 config CRYPTO_BLOWFISH_X86_64
1238 tristate "Blowfish cipher algorithm (x86_64)"
1239 depends on X86 && 64BIT
1240 select CRYPTO_SKCIPHER
1241 select CRYPTO_BLOWFISH_COMMON
1243 Blowfish cipher algorithm (x86_64), by Bruce Schneier.
1245 This is a variable key length cipher which can use keys from 32
1246 bits to 448 bits in length. It's fast, simple and specifically
1247 designed for use on "large microprocessors".
1250 <http://www.schneier.com/blowfish.html>
1252 config CRYPTO_CAMELLIA
1253 tristate "Camellia cipher algorithms"
1255 select CRYPTO_ALGAPI
1257 Camellia cipher algorithms module.
1259 Camellia is a symmetric key block cipher developed jointly
1260 at NTT and Mitsubishi Electric Corporation.
1262 The Camellia specifies three key sizes: 128, 192 and 256 bits.
1265 <https://info.isl.ntt.co.jp/crypt/eng/camellia/index_s.html>
1267 config CRYPTO_CAMELLIA_X86_64
1268 tristate "Camellia cipher algorithm (x86_64)"
1269 depends on X86 && 64BIT
1271 select CRYPTO_SKCIPHER
1272 select CRYPTO_GLUE_HELPER_X86
1274 Camellia cipher algorithm module (x86_64).
1276 Camellia is a symmetric key block cipher developed jointly
1277 at NTT and Mitsubishi Electric Corporation.
1279 The Camellia specifies three key sizes: 128, 192 and 256 bits.
1282 <https://info.isl.ntt.co.jp/crypt/eng/camellia/index_s.html>
1284 config CRYPTO_CAMELLIA_AESNI_AVX_X86_64
1285 tristate "Camellia cipher algorithm (x86_64/AES-NI/AVX)"
1286 depends on X86 && 64BIT
1288 select CRYPTO_SKCIPHER
1289 select CRYPTO_CAMELLIA_X86_64
1290 select CRYPTO_GLUE_HELPER_X86
1294 Camellia cipher algorithm module (x86_64/AES-NI/AVX).
1296 Camellia is a symmetric key block cipher developed jointly
1297 at NTT and Mitsubishi Electric Corporation.
1299 The Camellia specifies three key sizes: 128, 192 and 256 bits.
1302 <https://info.isl.ntt.co.jp/crypt/eng/camellia/index_s.html>
1304 config CRYPTO_CAMELLIA_AESNI_AVX2_X86_64
1305 tristate "Camellia cipher algorithm (x86_64/AES-NI/AVX2)"
1306 depends on X86 && 64BIT
1308 select CRYPTO_CAMELLIA_AESNI_AVX_X86_64
1310 Camellia cipher algorithm module (x86_64/AES-NI/AVX2).
1312 Camellia is a symmetric key block cipher developed jointly
1313 at NTT and Mitsubishi Electric Corporation.
1315 The Camellia specifies three key sizes: 128, 192 and 256 bits.
1318 <https://info.isl.ntt.co.jp/crypt/eng/camellia/index_s.html>
1320 config CRYPTO_CAMELLIA_SPARC64
1321 tristate "Camellia cipher algorithm (SPARC64)"
1324 select CRYPTO_ALGAPI
1325 select CRYPTO_SKCIPHER
1327 Camellia cipher algorithm module (SPARC64).
1329 Camellia is a symmetric key block cipher developed jointly
1330 at NTT and Mitsubishi Electric Corporation.
1332 The Camellia specifies three key sizes: 128, 192 and 256 bits.
1335 <https://info.isl.ntt.co.jp/crypt/eng/camellia/index_s.html>
1337 config CRYPTO_CAST_COMMON
1340 Common parts of the CAST cipher algorithms shared by the
1341 generic c and the assembler implementations.
1344 tristate "CAST5 (CAST-128) cipher algorithm"
1345 select CRYPTO_ALGAPI
1346 select CRYPTO_CAST_COMMON
1348 The CAST5 encryption algorithm (synonymous with CAST-128) is
1349 described in RFC2144.
1351 config CRYPTO_CAST5_AVX_X86_64
1352 tristate "CAST5 (CAST-128) cipher algorithm (x86_64/AVX)"
1353 depends on X86 && 64BIT
1354 select CRYPTO_SKCIPHER
1356 select CRYPTO_CAST_COMMON
1359 The CAST5 encryption algorithm (synonymous with CAST-128) is
1360 described in RFC2144.
1362 This module provides the Cast5 cipher algorithm that processes
1363 sixteen blocks parallel using the AVX instruction set.
1366 tristate "CAST6 (CAST-256) cipher algorithm"
1367 select CRYPTO_ALGAPI
1368 select CRYPTO_CAST_COMMON
1370 The CAST6 encryption algorithm (synonymous with CAST-256) is
1371 described in RFC2612.
1373 config CRYPTO_CAST6_AVX_X86_64
1374 tristate "CAST6 (CAST-256) cipher algorithm (x86_64/AVX)"
1375 depends on X86 && 64BIT
1376 select CRYPTO_SKCIPHER
1378 select CRYPTO_CAST_COMMON
1379 select CRYPTO_GLUE_HELPER_X86
1383 The CAST6 encryption algorithm (synonymous with CAST-256) is
1384 described in RFC2612.
1386 This module provides the Cast6 cipher algorithm that processes
1387 eight blocks parallel using the AVX instruction set.
1390 tristate "DES and Triple DES EDE cipher algorithms"
1391 select CRYPTO_ALGAPI
1392 select CRYPTO_LIB_DES
1394 DES cipher algorithm (FIPS 46-2), and Triple DES EDE (FIPS 46-3).
1396 config CRYPTO_DES_SPARC64
1397 tristate "DES and Triple DES EDE cipher algorithms (SPARC64)"
1399 select CRYPTO_ALGAPI
1400 select CRYPTO_LIB_DES
1401 select CRYPTO_SKCIPHER
1403 DES cipher algorithm (FIPS 46-2), and Triple DES EDE (FIPS 46-3),
1404 optimized using SPARC64 crypto opcodes.
1406 config CRYPTO_DES3_EDE_X86_64
1407 tristate "Triple DES EDE cipher algorithm (x86-64)"
1408 depends on X86 && 64BIT
1409 select CRYPTO_SKCIPHER
1410 select CRYPTO_LIB_DES
1412 Triple DES EDE (FIPS 46-3) algorithm.
1414 This module provides implementation of the Triple DES EDE cipher
1415 algorithm that is optimized for x86-64 processors. Two versions of
1416 algorithm are provided; regular processing one input block and
1417 one that processes three blocks parallel.
1419 config CRYPTO_FCRYPT
1420 tristate "FCrypt cipher algorithm"
1421 select CRYPTO_ALGAPI
1422 select CRYPTO_SKCIPHER
1424 FCrypt algorithm used by RxRPC.
1426 config CRYPTO_KHAZAD
1427 tristate "Khazad cipher algorithm"
1428 select CRYPTO_ALGAPI
1430 Khazad cipher algorithm.
1432 Khazad was a finalist in the initial NESSIE competition. It is
1433 an algorithm optimized for 64-bit processors with good performance
1434 on 32-bit processors. Khazad uses an 128 bit key size.
1437 <http://www.larc.usp.br/~pbarreto/KhazadPage.html>
1439 config CRYPTO_SALSA20
1440 tristate "Salsa20 stream cipher algorithm"
1441 select CRYPTO_SKCIPHER
1443 Salsa20 stream cipher algorithm.
1445 Salsa20 is a stream cipher submitted to eSTREAM, the ECRYPT
1446 Stream Cipher Project. See <http://www.ecrypt.eu.org/stream/>
1448 The Salsa20 stream cipher algorithm is designed by Daniel J.
1449 Bernstein <djb@cr.yp.to>. See <http://cr.yp.to/snuffle.html>
1451 config CRYPTO_CHACHA20
1452 tristate "ChaCha stream cipher algorithms"
1453 select CRYPTO_LIB_CHACHA_GENERIC
1454 select CRYPTO_SKCIPHER
1456 The ChaCha20, XChaCha20, and XChaCha12 stream cipher algorithms.
1458 ChaCha20 is a 256-bit high-speed stream cipher designed by Daniel J.
1459 Bernstein and further specified in RFC7539 for use in IETF protocols.
1460 This is the portable C implementation of ChaCha20. See also:
1461 <http://cr.yp.to/chacha/chacha-20080128.pdf>
1463 XChaCha20 is the application of the XSalsa20 construction to ChaCha20
1464 rather than to Salsa20. XChaCha20 extends ChaCha20's nonce length
1465 from 64 bits (or 96 bits using the RFC7539 convention) to 192 bits,
1466 while provably retaining ChaCha20's security. See also:
1467 <https://cr.yp.to/snuffle/xsalsa-20081128.pdf>
1469 XChaCha12 is XChaCha20 reduced to 12 rounds, with correspondingly
1470 reduced security margin but increased performance. It can be needed
1471 in some performance-sensitive scenarios.
1473 config CRYPTO_CHACHA20_X86_64
1474 tristate "ChaCha stream cipher algorithms (x86_64/SSSE3/AVX2/AVX-512VL)"
1475 depends on X86 && 64BIT
1476 select CRYPTO_SKCIPHER
1477 select CRYPTO_LIB_CHACHA_GENERIC
1478 select CRYPTO_ARCH_HAVE_LIB_CHACHA
1480 SSSE3, AVX2, and AVX-512VL optimized implementations of the ChaCha20,
1481 XChaCha20, and XChaCha12 stream ciphers.
1483 config CRYPTO_CHACHA_MIPS
1484 tristate "ChaCha stream cipher algorithms (MIPS 32r2 optimized)"
1485 depends on CPU_MIPS32_R2
1486 select CRYPTO_SKCIPHER
1487 select CRYPTO_ARCH_HAVE_LIB_CHACHA
1490 tristate "SEED cipher algorithm"
1491 select CRYPTO_ALGAPI
1493 SEED cipher algorithm (RFC4269).
1495 SEED is a 128-bit symmetric key block cipher that has been
1496 developed by KISA (Korea Information Security Agency) as a
1497 national standard encryption algorithm of the Republic of Korea.
1498 It is a 16 round block cipher with the key size of 128 bit.
1501 <http://www.kisa.or.kr/kisa/seed/jsp/seed_eng.jsp>
1503 config CRYPTO_SERPENT
1504 tristate "Serpent cipher algorithm"
1505 select CRYPTO_ALGAPI
1507 Serpent cipher algorithm, by Anderson, Biham & Knudsen.
1509 Keys are allowed to be from 0 to 256 bits in length, in steps
1510 of 8 bits. Also includes the 'Tnepres' algorithm, a reversed
1511 variant of Serpent for compatibility with old kerneli.org code.
1514 <http://www.cl.cam.ac.uk/~rja14/serpent.html>
1516 config CRYPTO_SERPENT_SSE2_X86_64
1517 tristate "Serpent cipher algorithm (x86_64/SSE2)"
1518 depends on X86 && 64BIT
1519 select CRYPTO_SKCIPHER
1520 select CRYPTO_GLUE_HELPER_X86
1521 select CRYPTO_SERPENT
1524 Serpent cipher algorithm, by Anderson, Biham & Knudsen.
1526 Keys are allowed to be from 0 to 256 bits in length, in steps
1529 This module provides Serpent cipher algorithm that processes eight
1530 blocks parallel using SSE2 instruction set.
1533 <http://www.cl.cam.ac.uk/~rja14/serpent.html>
1535 config CRYPTO_SERPENT_SSE2_586
1536 tristate "Serpent cipher algorithm (i586/SSE2)"
1537 depends on X86 && !64BIT
1538 select CRYPTO_SKCIPHER
1539 select CRYPTO_GLUE_HELPER_X86
1540 select CRYPTO_SERPENT
1543 Serpent cipher algorithm, by Anderson, Biham & Knudsen.
1545 Keys are allowed to be from 0 to 256 bits in length, in steps
1548 This module provides Serpent cipher algorithm that processes four
1549 blocks parallel using SSE2 instruction set.
1552 <http://www.cl.cam.ac.uk/~rja14/serpent.html>
1554 config CRYPTO_SERPENT_AVX_X86_64
1555 tristate "Serpent cipher algorithm (x86_64/AVX)"
1556 depends on X86 && 64BIT
1557 select CRYPTO_SKCIPHER
1558 select CRYPTO_GLUE_HELPER_X86
1559 select CRYPTO_SERPENT
1563 Serpent cipher algorithm, by Anderson, Biham & Knudsen.
1565 Keys are allowed to be from 0 to 256 bits in length, in steps
1568 This module provides the Serpent cipher algorithm that processes
1569 eight blocks parallel using the AVX instruction set.
1572 <http://www.cl.cam.ac.uk/~rja14/serpent.html>
1574 config CRYPTO_SERPENT_AVX2_X86_64
1575 tristate "Serpent cipher algorithm (x86_64/AVX2)"
1576 depends on X86 && 64BIT
1577 select CRYPTO_SERPENT_AVX_X86_64
1579 Serpent cipher algorithm, by Anderson, Biham & Knudsen.
1581 Keys are allowed to be from 0 to 256 bits in length, in steps
1584 This module provides Serpent cipher algorithm that processes 16
1585 blocks parallel using AVX2 instruction set.
1588 <http://www.cl.cam.ac.uk/~rja14/serpent.html>
1591 tristate "SM4 cipher algorithm"
1592 select CRYPTO_ALGAPI
1594 SM4 cipher algorithms (OSCCA GB/T 32907-2016).
1596 SM4 (GBT.32907-2016) is a cryptographic standard issued by the
1597 Organization of State Commercial Administration of China (OSCCA)
1598 as an authorized cryptographic algorithms for the use within China.
1600 SMS4 was originally created for use in protecting wireless
1601 networks, and is mandated in the Chinese National Standard for
1602 Wireless LAN WAPI (Wired Authentication and Privacy Infrastructure)
1605 The latest SM4 standard (GBT.32907-2016) was proposed by OSCCA and
1606 standardized through TC 260 of the Standardization Administration
1607 of the People's Republic of China (SAC).
1609 The input, output, and key of SMS4 are each 128 bits.
1611 See also: <https://eprint.iacr.org/2008/329.pdf>
1616 tristate "TEA, XTEA and XETA cipher algorithms"
1617 select CRYPTO_ALGAPI
1619 TEA cipher algorithm.
1621 Tiny Encryption Algorithm is a simple cipher that uses
1622 many rounds for security. It is very fast and uses
1625 Xtendend Tiny Encryption Algorithm is a modification to
1626 the TEA algorithm to address a potential key weakness
1627 in the TEA algorithm.
1629 Xtendend Encryption Tiny Algorithm is a mis-implementation
1630 of the XTEA algorithm for compatibility purposes.
1632 config CRYPTO_TWOFISH
1633 tristate "Twofish cipher algorithm"
1634 select CRYPTO_ALGAPI
1635 select CRYPTO_TWOFISH_COMMON
1637 Twofish cipher algorithm.
1639 Twofish was submitted as an AES (Advanced Encryption Standard)
1640 candidate cipher by researchers at CounterPane Systems. It is a
1641 16 round block cipher supporting key sizes of 128, 192, and 256
1645 <http://www.schneier.com/twofish.html>
1647 config CRYPTO_TWOFISH_COMMON
1650 Common parts of the Twofish cipher algorithm shared by the
1651 generic c and the assembler implementations.
1653 config CRYPTO_TWOFISH_586
1654 tristate "Twofish cipher algorithms (i586)"
1655 depends on (X86 || UML_X86) && !64BIT
1656 select CRYPTO_ALGAPI
1657 select CRYPTO_TWOFISH_COMMON
1659 Twofish cipher algorithm.
1661 Twofish was submitted as an AES (Advanced Encryption Standard)
1662 candidate cipher by researchers at CounterPane Systems. It is a
1663 16 round block cipher supporting key sizes of 128, 192, and 256
1667 <http://www.schneier.com/twofish.html>
1669 config CRYPTO_TWOFISH_X86_64
1670 tristate "Twofish cipher algorithm (x86_64)"
1671 depends on (X86 || UML_X86) && 64BIT
1672 select CRYPTO_ALGAPI
1673 select CRYPTO_TWOFISH_COMMON
1675 Twofish cipher algorithm (x86_64).
1677 Twofish was submitted as an AES (Advanced Encryption Standard)
1678 candidate cipher by researchers at CounterPane Systems. It is a
1679 16 round block cipher supporting key sizes of 128, 192, and 256
1683 <http://www.schneier.com/twofish.html>
1685 config CRYPTO_TWOFISH_X86_64_3WAY
1686 tristate "Twofish cipher algorithm (x86_64, 3-way parallel)"
1687 depends on X86 && 64BIT
1688 select CRYPTO_SKCIPHER
1689 select CRYPTO_TWOFISH_COMMON
1690 select CRYPTO_TWOFISH_X86_64
1691 select CRYPTO_GLUE_HELPER_X86
1693 Twofish cipher algorithm (x86_64, 3-way parallel).
1695 Twofish was submitted as an AES (Advanced Encryption Standard)
1696 candidate cipher by researchers at CounterPane Systems. It is a
1697 16 round block cipher supporting key sizes of 128, 192, and 256
1700 This module provides Twofish cipher algorithm that processes three
1701 blocks parallel, utilizing resources of out-of-order CPUs better.
1704 <http://www.schneier.com/twofish.html>
1706 config CRYPTO_TWOFISH_AVX_X86_64
1707 tristate "Twofish cipher algorithm (x86_64/AVX)"
1708 depends on X86 && 64BIT
1709 select CRYPTO_SKCIPHER
1710 select CRYPTO_GLUE_HELPER_X86
1712 select CRYPTO_TWOFISH_COMMON
1713 select CRYPTO_TWOFISH_X86_64
1714 select CRYPTO_TWOFISH_X86_64_3WAY
1716 Twofish cipher algorithm (x86_64/AVX).
1718 Twofish was submitted as an AES (Advanced Encryption Standard)
1719 candidate cipher by researchers at CounterPane Systems. It is a
1720 16 round block cipher supporting key sizes of 128, 192, and 256
1723 This module provides the Twofish cipher algorithm that processes
1724 eight blocks parallel using the AVX Instruction Set.
1727 <http://www.schneier.com/twofish.html>
1729 comment "Compression"
1731 config CRYPTO_DEFLATE
1732 tristate "Deflate compression algorithm"
1733 select CRYPTO_ALGAPI
1734 select CRYPTO_ACOMP2
1738 This is the Deflate algorithm (RFC1951), specified for use in
1739 IPSec with the IPCOMP protocol (RFC3173, RFC2394).
1741 You will most probably want this if using IPSec.
1744 tristate "LZO compression algorithm"
1745 select CRYPTO_ALGAPI
1746 select CRYPTO_ACOMP2
1748 select LZO_DECOMPRESS
1750 This is the LZO algorithm.
1753 tristate "842 compression algorithm"
1754 select CRYPTO_ALGAPI
1755 select CRYPTO_ACOMP2
1757 select 842_DECOMPRESS
1759 This is the 842 algorithm.
1762 tristate "LZ4 compression algorithm"
1763 select CRYPTO_ALGAPI
1764 select CRYPTO_ACOMP2
1766 select LZ4_DECOMPRESS
1768 This is the LZ4 algorithm.
1771 tristate "LZ4HC compression algorithm"
1772 select CRYPTO_ALGAPI
1773 select CRYPTO_ACOMP2
1774 select LZ4HC_COMPRESS
1775 select LZ4_DECOMPRESS
1777 This is the LZ4 high compression mode algorithm.
1780 tristate "Zstd compression algorithm"
1781 select CRYPTO_ALGAPI
1782 select CRYPTO_ACOMP2
1783 select ZSTD_COMPRESS
1784 select ZSTD_DECOMPRESS
1786 This is the zstd algorithm.
1788 comment "Random Number Generation"
1790 config CRYPTO_ANSI_CPRNG
1791 tristate "Pseudo Random Number Generation for Cryptographic modules"
1795 This option enables the generic pseudo random number generator
1796 for cryptographic modules. Uses the Algorithm specified in
1797 ANSI X9.31 A.2.4. Note that this option must be enabled if
1798 CRYPTO_FIPS is selected
1800 menuconfig CRYPTO_DRBG_MENU
1801 tristate "NIST SP800-90A DRBG"
1803 NIST SP800-90A compliant DRBG. In the following submenu, one or
1804 more of the DRBG types must be selected.
1808 config CRYPTO_DRBG_HMAC
1812 select CRYPTO_SHA256
1814 config CRYPTO_DRBG_HASH
1815 bool "Enable Hash DRBG"
1816 select CRYPTO_SHA256
1818 Enable the Hash DRBG variant as defined in NIST SP800-90A.
1820 config CRYPTO_DRBG_CTR
1821 bool "Enable CTR DRBG"
1823 depends on CRYPTO_CTR
1825 Enable the CTR DRBG variant as defined in NIST SP800-90A.
1829 default CRYPTO_DRBG_MENU
1831 select CRYPTO_JITTERENTROPY
1833 endif # if CRYPTO_DRBG_MENU
1835 config CRYPTO_JITTERENTROPY
1836 tristate "Jitterentropy Non-Deterministic Random Number Generator"
1839 The Jitterentropy RNG is a noise that is intended
1840 to provide seed to another RNG. The RNG does not
1841 perform any cryptographic whitening of the generated
1842 random numbers. This Jitterentropy RNG registers with
1843 the kernel crypto API and can be used by any caller.
1845 config CRYPTO_USER_API
1848 config CRYPTO_USER_API_HASH
1849 tristate "User-space interface for hash algorithms"
1852 select CRYPTO_USER_API
1854 This option enables the user-spaces interface for hash
1857 config CRYPTO_USER_API_SKCIPHER
1858 tristate "User-space interface for symmetric key cipher algorithms"
1860 select CRYPTO_SKCIPHER
1861 select CRYPTO_USER_API
1863 This option enables the user-spaces interface for symmetric
1864 key cipher algorithms.
1866 config CRYPTO_USER_API_RNG
1867 tristate "User-space interface for random number generator algorithms"
1870 select CRYPTO_USER_API
1872 This option enables the user-spaces interface for random
1873 number generator algorithms.
1875 config CRYPTO_USER_API_AEAD
1876 tristate "User-space interface for AEAD cipher algorithms"
1879 select CRYPTO_SKCIPHER
1881 select CRYPTO_USER_API
1883 This option enables the user-spaces interface for AEAD
1887 bool "Crypto usage statistics for User-space"
1888 depends on CRYPTO_USER
1890 This option enables the gathering of crypto stats.
1892 - encrypt/decrypt size and numbers of symmeric operations
1893 - compress/decompress size and numbers of compress operations
1894 - size and numbers of hash operations
1895 - encrypt/decrypt/sign/verify numbers for asymmetric operations
1896 - generate/seed numbers for rng operations
1898 config CRYPTO_HASH_INFO
1901 source "lib/crypto/Kconfig"
1902 source "drivers/crypto/Kconfig"
1903 source "crypto/asymmetric_keys/Kconfig"
1904 source "certs/Kconfig"