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"
20 This option provides the core Cryptographic API.
24 comment "Crypto core or helper"
27 bool "FIPS 200 compliance"
28 depends on (CRYPTO_ANSI_CPRNG || CRYPTO_DRBG) && !CRYPTO_MANAGER_DISABLE_TESTS
29 depends on (MODULE_SIG || !MODULES)
31 This option enables the fips boot option which is
32 required if you want the system to operate in a FIPS 200
33 certification. You should say no unless you know what
40 This option provides the API for cryptographic algorithms.
56 config CRYPTO_SKCIPHER
58 select CRYPTO_SKCIPHER2
61 config CRYPTO_SKCIPHER2
84 config CRYPTO_RNG_DEFAULT
86 select CRYPTO_DRBG_MENU
88 config CRYPTO_AKCIPHER2
92 config CRYPTO_AKCIPHER
94 select CRYPTO_AKCIPHER2
108 select CRYPTO_ALGAPI2
116 config CRYPTO_MANAGER
117 tristate "Cryptographic algorithm manager"
118 select CRYPTO_MANAGER2
120 Create default cryptographic template instantiations such as
123 config CRYPTO_MANAGER2
124 def_tristate CRYPTO_MANAGER || (CRYPTO_MANAGER!=n && CRYPTO_ALGAPI=y)
127 select CRYPTO_SKCIPHER2
128 select CRYPTO_AKCIPHER2
133 tristate "Userspace cryptographic algorithm configuration"
135 select CRYPTO_MANAGER
137 Userspace configuration for cryptographic instantiations such as
140 config CRYPTO_MANAGER_DISABLE_TESTS
141 bool "Disable run-time self tests"
144 Disable run-time self tests that normally take place at
145 algorithm registration.
147 config CRYPTO_MANAGER_EXTRA_TESTS
148 bool "Enable extra run-time crypto self tests"
149 depends on DEBUG_KERNEL && !CRYPTO_MANAGER_DISABLE_TESTS && CRYPTO_MANAGER
151 Enable extra run-time self tests of registered crypto algorithms,
152 including randomized fuzz tests.
154 This is intended for developer use only, as these tests take much
155 longer to run than the normal self tests.
157 config CRYPTO_GF128MUL
161 tristate "Null algorithms"
164 These are 'Null' algorithms, used by IPsec, which do nothing.
168 select CRYPTO_ALGAPI2
169 select CRYPTO_SKCIPHER2
173 tristate "Parallel crypto engine"
176 select CRYPTO_MANAGER
179 This converts an arbitrary crypto algorithm into a parallel
180 algorithm that executes in kernel threads.
183 tristate "Software async crypto daemon"
184 select CRYPTO_SKCIPHER
186 select CRYPTO_MANAGER
188 This is a generic software asynchronous crypto daemon that
189 converts an arbitrary synchronous software crypto algorithm
190 into an asynchronous algorithm that executes in a kernel thread.
192 config CRYPTO_AUTHENC
193 tristate "Authenc support"
195 select CRYPTO_SKCIPHER
196 select CRYPTO_MANAGER
200 Authenc: Combined mode wrapper for IPsec.
201 This is required for IPSec.
204 tristate "Testing module"
205 depends on m || EXPERT
206 select CRYPTO_MANAGER
208 Quick & dirty crypto test module.
217 comment "Public-key cryptography"
220 tristate "RSA algorithm"
221 select CRYPTO_AKCIPHER
222 select CRYPTO_MANAGER
226 Generic implementation of the RSA public key algorithm.
229 tristate "Diffie-Hellman algorithm"
233 Generic implementation of the Diffie-Hellman algorithm.
235 config CRYPTO_DH_RFC7919_GROUPS
236 bool "Support for RFC 7919 FFDHE group parameters"
238 select CRYPTO_RNG_DEFAULT
240 Provide support for RFC 7919 FFDHE group parameters. If unsure, say N.
244 select CRYPTO_RNG_DEFAULT
247 tristate "ECDH algorithm"
251 Generic implementation of the ECDH algorithm
254 tristate "ECDSA (NIST P192, P256 etc.) algorithm"
256 select CRYPTO_AKCIPHER
259 Elliptic Curve Digital Signature Algorithm (NIST P192, P256 etc.)
260 is A NIST cryptographic standard algorithm. Only signature verification
264 tristate "EC-RDSA (GOST 34.10) algorithm"
266 select CRYPTO_AKCIPHER
267 select CRYPTO_STREEBOG
271 Elliptic Curve Russian Digital Signature Algorithm (GOST R 34.10-2012,
272 RFC 7091, ISO/IEC 14888-3:2018) is one of the Russian cryptographic
273 standard algorithms (called GOST algorithms). Only signature verification
277 tristate "SM2 algorithm"
279 select CRYPTO_AKCIPHER
280 select CRYPTO_MANAGER
284 Generic implementation of the SM2 public key algorithm. It was
285 published by State Encryption Management Bureau, China.
286 as specified by OSCCA GM/T 0003.1-2012 -- 0003.5-2012.
289 https://tools.ietf.org/html/draft-shen-sm2-ecdsa-02
290 http://www.oscca.gov.cn/sca/xxgk/2010-12/17/content_1002386.shtml
291 http://www.gmbz.org.cn/main/bzlb.html
293 config CRYPTO_CURVE25519
294 tristate "Curve25519 algorithm"
296 select CRYPTO_LIB_CURVE25519_GENERIC
298 config CRYPTO_CURVE25519_X86
299 tristate "x86_64 accelerated Curve25519 scalar multiplication library"
300 depends on X86 && 64BIT
301 select CRYPTO_LIB_CURVE25519_GENERIC
302 select CRYPTO_ARCH_HAVE_LIB_CURVE25519
304 comment "Authenticated Encryption with Associated Data"
307 tristate "CCM support"
311 select CRYPTO_MANAGER
313 Support for Counter with CBC MAC. Required for IPsec.
316 tristate "GCM/GMAC support"
321 select CRYPTO_MANAGER
323 Support for Galois/Counter Mode (GCM) and Galois Message
324 Authentication Code (GMAC). Required for IPSec.
326 config CRYPTO_CHACHA20POLY1305
327 tristate "ChaCha20-Poly1305 AEAD support"
328 select CRYPTO_CHACHA20
329 select CRYPTO_POLY1305
331 select CRYPTO_MANAGER
333 ChaCha20-Poly1305 AEAD support, RFC7539.
335 Support for the AEAD wrapper using the ChaCha20 stream cipher combined
336 with the Poly1305 authenticator. It is defined in RFC7539 for use in
339 config CRYPTO_AEGIS128
340 tristate "AEGIS-128 AEAD algorithm"
342 select CRYPTO_AES # for AES S-box tables
344 Support for the AEGIS-128 dedicated AEAD algorithm.
346 config CRYPTO_AEGIS128_SIMD
347 bool "Support SIMD acceleration for AEGIS-128"
348 depends on CRYPTO_AEGIS128 && ((ARM || ARM64) && KERNEL_MODE_NEON)
351 config CRYPTO_AEGIS128_AESNI_SSE2
352 tristate "AEGIS-128 AEAD algorithm (x86_64 AESNI+SSE2 implementation)"
353 depends on X86 && 64BIT
357 AESNI+SSE2 implementation of the AEGIS-128 dedicated AEAD algorithm.
360 tristate "Sequence Number IV Generator"
362 select CRYPTO_SKCIPHER
364 select CRYPTO_RNG_DEFAULT
365 select CRYPTO_MANAGER
367 This IV generator generates an IV based on a sequence number by
368 xoring it with a salt. This algorithm is mainly useful for CTR
370 config CRYPTO_ECHAINIV
371 tristate "Encrypted Chain IV Generator"
374 select CRYPTO_RNG_DEFAULT
375 select CRYPTO_MANAGER
377 This IV generator generates an IV based on the encryption of
378 a sequence number xored with a salt. This is the default
381 comment "Block modes"
384 tristate "CBC support"
385 select CRYPTO_SKCIPHER
386 select CRYPTO_MANAGER
388 CBC: Cipher Block Chaining mode
389 This block cipher algorithm is required for IPSec.
392 tristate "CFB support"
393 select CRYPTO_SKCIPHER
394 select CRYPTO_MANAGER
396 CFB: Cipher FeedBack mode
397 This block cipher algorithm is required for TPM2 Cryptography.
400 tristate "CTR support"
401 select CRYPTO_SKCIPHER
402 select CRYPTO_MANAGER
405 This block cipher algorithm is required for IPSec.
408 tristate "CTS support"
409 select CRYPTO_SKCIPHER
410 select CRYPTO_MANAGER
412 CTS: Cipher Text Stealing
413 This is the Cipher Text Stealing mode as described by
414 Section 8 of rfc2040 and referenced by rfc3962
415 (rfc3962 includes errata information in its Appendix A) or
416 CBC-CS3 as defined by NIST in Sp800-38A addendum from Oct 2010.
417 This mode is required for Kerberos gss mechanism support
420 See: https://csrc.nist.gov/publications/detail/sp/800-38a/addendum/final
423 tristate "ECB support"
424 select CRYPTO_SKCIPHER
425 select CRYPTO_MANAGER
427 ECB: Electronic CodeBook mode
428 This is the simplest block cipher algorithm. It simply encrypts
429 the input block by block.
432 tristate "LRW support"
433 select CRYPTO_SKCIPHER
434 select CRYPTO_MANAGER
435 select CRYPTO_GF128MUL
438 LRW: Liskov Rivest Wagner, a tweakable, non malleable, non movable
439 narrow block cipher mode for dm-crypt. Use it with cipher
440 specification string aes-lrw-benbi, the key must be 256, 320 or 384.
441 The first 128, 192 or 256 bits in the key are used for AES and the
442 rest is used to tie each cipher block to its logical position.
445 tristate "OFB support"
446 select CRYPTO_SKCIPHER
447 select CRYPTO_MANAGER
449 OFB: the Output Feedback mode makes a block cipher into a synchronous
450 stream cipher. It generates keystream blocks, which are then XORed
451 with the plaintext blocks to get the ciphertext. Flipping a bit in the
452 ciphertext produces a flipped bit in the plaintext at the same
453 location. This property allows many error correcting codes to function
454 normally even when applied before encryption.
457 tristate "PCBC support"
458 select CRYPTO_SKCIPHER
459 select CRYPTO_MANAGER
461 PCBC: Propagating Cipher Block Chaining mode
462 This block cipher algorithm is required for RxRPC.
465 tristate "XTS support"
466 select CRYPTO_SKCIPHER
467 select CRYPTO_MANAGER
470 XTS: IEEE1619/D16 narrow block cipher use with aes-xts-plain,
471 key size 256, 384 or 512 bits. This implementation currently
472 can't handle a sectorsize which is not a multiple of 16 bytes.
474 config CRYPTO_KEYWRAP
475 tristate "Key wrapping support"
476 select CRYPTO_SKCIPHER
477 select CRYPTO_MANAGER
479 Support for key wrapping (NIST SP800-38F / RFC3394) without
482 config CRYPTO_NHPOLY1305
485 select CRYPTO_LIB_POLY1305_GENERIC
487 config CRYPTO_NHPOLY1305_SSE2
488 tristate "NHPoly1305 hash function (x86_64 SSE2 implementation)"
489 depends on X86 && 64BIT
490 select CRYPTO_NHPOLY1305
492 SSE2 optimized implementation of the hash function used by the
493 Adiantum encryption mode.
495 config CRYPTO_NHPOLY1305_AVX2
496 tristate "NHPoly1305 hash function (x86_64 AVX2 implementation)"
497 depends on X86 && 64BIT
498 select CRYPTO_NHPOLY1305
500 AVX2 optimized implementation of the hash function used by the
501 Adiantum encryption mode.
503 config CRYPTO_ADIANTUM
504 tristate "Adiantum support"
505 select CRYPTO_CHACHA20
506 select CRYPTO_LIB_POLY1305_GENERIC
507 select CRYPTO_NHPOLY1305
508 select CRYPTO_MANAGER
510 Adiantum is a tweakable, length-preserving encryption mode
511 designed for fast and secure disk encryption, especially on
512 CPUs without dedicated crypto instructions. It encrypts
513 each sector using the XChaCha12 stream cipher, two passes of
514 an ε-almost-∆-universal hash function, and an invocation of
515 the AES-256 block cipher on a single 16-byte block. On CPUs
516 without AES instructions, Adiantum is much faster than
519 Adiantum's security is provably reducible to that of its
520 underlying stream and block ciphers, subject to a security
521 bound. Unlike XTS, Adiantum is a true wide-block encryption
522 mode, so it actually provides an even stronger notion of
523 security than XTS, subject to the security bound.
528 tristate "ESSIV support for block encryption"
529 select CRYPTO_AUTHENC
531 Encrypted salt-sector initialization vector (ESSIV) is an IV
532 generation method that is used in some cases by fscrypt and/or
533 dm-crypt. It uses the hash of the block encryption key as the
534 symmetric key for a block encryption pass applied to the input
535 IV, making low entropy IV sources more suitable for block
538 This driver implements a crypto API template that can be
539 instantiated either as an skcipher or as an AEAD (depending on the
540 type of the first template argument), and which defers encryption
541 and decryption requests to the encapsulated cipher after applying
542 ESSIV to the input IV. Note that in the AEAD case, it is assumed
543 that the keys are presented in the same format used by the authenc
544 template, and that the IV appears at the end of the authenticated
545 associated data (AAD) region (which is how dm-crypt uses it.)
547 Note that the use of ESSIV is not recommended for new deployments,
548 and so this only needs to be enabled when interoperability with
549 existing encrypted volumes of filesystems is required, or when
550 building for a particular system that requires it (e.g., when
551 the SoC in question has accelerated CBC but not XTS, making CBC
552 combined with ESSIV the only feasible mode for h/w accelerated
558 tristate "CMAC support"
560 select CRYPTO_MANAGER
562 Cipher-based Message Authentication Code (CMAC) specified by
563 The National Institute of Standards and Technology (NIST).
565 https://tools.ietf.org/html/rfc4493
566 http://csrc.nist.gov/publications/nistpubs/800-38B/SP_800-38B.pdf
569 tristate "HMAC support"
571 select CRYPTO_MANAGER
573 HMAC: Keyed-Hashing for Message Authentication (RFC2104).
574 This is required for IPSec.
577 tristate "XCBC support"
579 select CRYPTO_MANAGER
581 XCBC: Keyed-Hashing with encryption algorithm
582 https://www.ietf.org/rfc/rfc3566.txt
583 http://csrc.nist.gov/encryption/modes/proposedmodes/
584 xcbc-mac/xcbc-mac-spec.pdf
587 tristate "VMAC support"
589 select CRYPTO_MANAGER
591 VMAC is a message authentication algorithm designed for
592 very high speed on 64-bit architectures.
595 <https://fastcrypto.org/vmac>
600 tristate "CRC32c CRC algorithm"
604 Castagnoli, et al Cyclic Redundancy-Check Algorithm. Used
605 by iSCSI for header and data digests and by others.
606 See Castagnoli93. Module will be crc32c.
608 config CRYPTO_CRC32C_INTEL
609 tristate "CRC32c INTEL hardware acceleration"
613 In Intel processor with SSE4.2 supported, the processor will
614 support CRC32C implementation using hardware accelerated CRC32
615 instruction. This option will create 'crc32c-intel' module,
616 which will enable any routine to use the CRC32 instruction to
617 gain performance compared with software implementation.
618 Module will be crc32c-intel.
620 config CRYPTO_CRC32C_VPMSUM
621 tristate "CRC32c CRC algorithm (powerpc64)"
622 depends on PPC64 && ALTIVEC
626 CRC32c algorithm implemented using vector polynomial multiply-sum
627 (vpmsum) instructions, introduced in POWER8. Enable on POWER8
628 and newer processors for improved performance.
631 config CRYPTO_CRC32C_SPARC64
632 tristate "CRC32c CRC algorithm (SPARC64)"
637 CRC32c CRC algorithm implemented using sparc64 crypto instructions,
641 tristate "CRC32 CRC algorithm"
645 CRC-32-IEEE 802.3 cyclic redundancy-check algorithm.
646 Shash crypto api wrappers to crc32_le function.
648 config CRYPTO_CRC32_PCLMUL
649 tristate "CRC32 PCLMULQDQ hardware acceleration"
654 From Intel Westmere and AMD Bulldozer processor with SSE4.2
655 and PCLMULQDQ supported, the processor will support
656 CRC32 PCLMULQDQ implementation using hardware accelerated PCLMULQDQ
657 instruction. This option will create 'crc32-pclmul' module,
658 which will enable any routine to use the CRC-32-IEEE 802.3 checksum
659 and gain better performance as compared with the table implementation.
661 config CRYPTO_CRC32_MIPS
662 tristate "CRC32c and CRC32 CRC algorithm (MIPS)"
663 depends on MIPS_CRC_SUPPORT
666 CRC32c and CRC32 CRC algorithms implemented using mips crypto
667 instructions, when available.
669 config CRYPTO_CRC32_S390
670 tristate "CRC-32 algorithms"
675 Select this option if you want to use hardware accelerated
676 implementations of CRC algorithms. With this option, you
677 can optimize the computation of CRC-32 (IEEE 802.3 Ethernet)
678 and CRC-32C (Castagnoli).
680 It is available with IBM z13 or later.
683 tristate "xxHash hash algorithm"
687 xxHash non-cryptographic hash algorithm. Extremely fast, working at
688 speeds close to RAM limits.
690 config CRYPTO_BLAKE2B
691 tristate "BLAKE2b digest algorithm"
694 Implementation of cryptographic hash function BLAKE2b (or just BLAKE2),
695 optimized for 64bit platforms and can produce digests of any size
696 between 1 to 64. The keyed hash is also implemented.
698 This module provides the following algorithms:
705 See https://blake2.net for further information.
707 config CRYPTO_BLAKE2S
708 tristate "BLAKE2s digest algorithm"
709 select CRYPTO_LIB_BLAKE2S_GENERIC
712 Implementation of cryptographic hash function BLAKE2s
713 optimized for 8-32bit platforms and can produce digests of any size
714 between 1 to 32. The keyed hash is also implemented.
716 This module provides the following algorithms:
723 See https://blake2.net for further information.
725 config CRYPTO_BLAKE2S_X86
726 tristate "BLAKE2s digest algorithm (x86 accelerated version)"
727 depends on X86 && 64BIT
728 select CRYPTO_LIB_BLAKE2S_GENERIC
729 select CRYPTO_ARCH_HAVE_LIB_BLAKE2S
731 config CRYPTO_CRCT10DIF
732 tristate "CRCT10DIF algorithm"
735 CRC T10 Data Integrity Field computation is being cast as
736 a crypto transform. This allows for faster crc t10 diff
737 transforms to be used if they are available.
739 config CRYPTO_CRCT10DIF_PCLMUL
740 tristate "CRCT10DIF PCLMULQDQ hardware acceleration"
741 depends on X86 && 64BIT && CRC_T10DIF
744 For x86_64 processors with SSE4.2 and PCLMULQDQ supported,
745 CRC T10 DIF PCLMULQDQ computation can be hardware
746 accelerated PCLMULQDQ instruction. This option will create
747 'crct10dif-pclmul' module, which is faster when computing the
748 crct10dif checksum as compared with the generic table implementation.
750 config CRYPTO_CRCT10DIF_VPMSUM
751 tristate "CRC32T10DIF powerpc64 hardware acceleration"
752 depends on PPC64 && ALTIVEC && CRC_T10DIF
755 CRC10T10DIF algorithm implemented using vector polynomial
756 multiply-sum (vpmsum) instructions, introduced in POWER8. Enable on
757 POWER8 and newer processors for improved performance.
759 config CRYPTO_CRC64_ROCKSOFT
760 tristate "Rocksoft Model CRC64 algorithm"
764 config CRYPTO_VPMSUM_TESTER
765 tristate "Powerpc64 vpmsum hardware acceleration tester"
766 depends on CRYPTO_CRCT10DIF_VPMSUM && CRYPTO_CRC32C_VPMSUM
768 Stress test for CRC32c and CRC-T10DIF algorithms implemented with
769 POWER8 vpmsum instructions.
770 Unless you are testing these algorithms, you don't need this.
773 tristate "GHASH hash function"
774 select CRYPTO_GF128MUL
777 GHASH is the hash function used in GCM (Galois/Counter Mode).
778 It is not a general-purpose cryptographic hash function.
780 config CRYPTO_POLY1305
781 tristate "Poly1305 authenticator algorithm"
783 select CRYPTO_LIB_POLY1305_GENERIC
785 Poly1305 authenticator algorithm, RFC7539.
787 Poly1305 is an authenticator algorithm designed by Daniel J. Bernstein.
788 It is used for the ChaCha20-Poly1305 AEAD, specified in RFC7539 for use
789 in IETF protocols. This is the portable C implementation of Poly1305.
791 config CRYPTO_POLY1305_X86_64
792 tristate "Poly1305 authenticator algorithm (x86_64/SSE2/AVX2)"
793 depends on X86 && 64BIT
794 select CRYPTO_LIB_POLY1305_GENERIC
795 select CRYPTO_ARCH_HAVE_LIB_POLY1305
797 Poly1305 authenticator algorithm, RFC7539.
799 Poly1305 is an authenticator algorithm designed by Daniel J. Bernstein.
800 It is used for the ChaCha20-Poly1305 AEAD, specified in RFC7539 for use
801 in IETF protocols. This is the x86_64 assembler implementation using SIMD
804 config CRYPTO_POLY1305_MIPS
805 tristate "Poly1305 authenticator algorithm (MIPS optimized)"
807 select CRYPTO_ARCH_HAVE_LIB_POLY1305
810 tristate "MD4 digest algorithm"
813 MD4 message digest algorithm (RFC1320).
816 tristate "MD5 digest algorithm"
819 MD5 message digest algorithm (RFC1321).
821 config CRYPTO_MD5_OCTEON
822 tristate "MD5 digest algorithm (OCTEON)"
823 depends on CPU_CAVIUM_OCTEON
827 MD5 message digest algorithm (RFC1321) implemented
828 using OCTEON crypto instructions, when available.
830 config CRYPTO_MD5_PPC
831 tristate "MD5 digest algorithm (PPC)"
835 MD5 message digest algorithm (RFC1321) implemented
838 config CRYPTO_MD5_SPARC64
839 tristate "MD5 digest algorithm (SPARC64)"
844 MD5 message digest algorithm (RFC1321) implemented
845 using sparc64 crypto instructions, when available.
847 config CRYPTO_MICHAEL_MIC
848 tristate "Michael MIC keyed digest algorithm"
851 Michael MIC is used for message integrity protection in TKIP
852 (IEEE 802.11i). This algorithm is required for TKIP, but it
853 should not be used for other purposes because of the weakness
857 tristate "RIPEMD-160 digest algorithm"
860 RIPEMD-160 (ISO/IEC 10118-3:2004).
862 RIPEMD-160 is a 160-bit cryptographic hash function. It is intended
863 to be used as a secure replacement for the 128-bit hash functions
864 MD4, MD5 and it's predecessor RIPEMD
865 (not to be confused with RIPEMD-128).
867 It's speed is comparable to SHA1 and there are no known attacks
870 Developed by Hans Dobbertin, Antoon Bosselaers and Bart Preneel.
871 See <https://homes.esat.kuleuven.be/~bosselae/ripemd160.html>
874 tristate "SHA1 digest algorithm"
877 SHA-1 secure hash standard (FIPS 180-1/DFIPS 180-2).
879 config CRYPTO_SHA1_SSSE3
880 tristate "SHA1 digest algorithm (SSSE3/AVX/AVX2/SHA-NI)"
881 depends on X86 && 64BIT
885 SHA-1 secure hash standard (FIPS 180-1/DFIPS 180-2) implemented
886 using Supplemental SSE3 (SSSE3) instructions or Advanced Vector
887 Extensions (AVX/AVX2) or SHA-NI(SHA Extensions New Instructions),
890 config CRYPTO_SHA256_SSSE3
891 tristate "SHA256 digest algorithm (SSSE3/AVX/AVX2/SHA-NI)"
892 depends on X86 && 64BIT
896 SHA-256 secure hash standard (DFIPS 180-2) implemented
897 using Supplemental SSE3 (SSSE3) instructions, or Advanced Vector
898 Extensions version 1 (AVX1), or Advanced Vector Extensions
899 version 2 (AVX2) instructions, or SHA-NI (SHA Extensions New
900 Instructions) when available.
902 config CRYPTO_SHA512_SSSE3
903 tristate "SHA512 digest algorithm (SSSE3/AVX/AVX2)"
904 depends on X86 && 64BIT
908 SHA-512 secure hash standard (DFIPS 180-2) implemented
909 using Supplemental SSE3 (SSSE3) instructions, or Advanced Vector
910 Extensions version 1 (AVX1), or Advanced Vector Extensions
911 version 2 (AVX2) instructions, when available.
913 config CRYPTO_SHA512_S390
914 tristate "SHA384 and SHA512 digest algorithm"
918 This is the s390 hardware accelerated implementation of the
919 SHA512 secure hash standard.
921 It is available as of z10.
923 config CRYPTO_SHA1_OCTEON
924 tristate "SHA1 digest algorithm (OCTEON)"
925 depends on CPU_CAVIUM_OCTEON
929 SHA-1 secure hash standard (FIPS 180-1/DFIPS 180-2) implemented
930 using OCTEON crypto instructions, when available.
932 config CRYPTO_SHA1_SPARC64
933 tristate "SHA1 digest algorithm (SPARC64)"
938 SHA-1 secure hash standard (FIPS 180-1/DFIPS 180-2) implemented
939 using sparc64 crypto instructions, when available.
941 config CRYPTO_SHA1_PPC
942 tristate "SHA1 digest algorithm (powerpc)"
945 This is the powerpc hardware accelerated implementation of the
946 SHA-1 secure hash standard (FIPS 180-1/DFIPS 180-2).
948 config CRYPTO_SHA1_PPC_SPE
949 tristate "SHA1 digest algorithm (PPC SPE)"
950 depends on PPC && SPE
952 SHA-1 secure hash standard (DFIPS 180-4) implemented
953 using powerpc SPE SIMD instruction set.
955 config CRYPTO_SHA1_S390
956 tristate "SHA1 digest algorithm"
960 This is the s390 hardware accelerated implementation of the
961 SHA-1 secure hash standard (FIPS 180-1/DFIPS 180-2).
963 It is available as of z990.
966 tristate "SHA224 and SHA256 digest algorithm"
968 select CRYPTO_LIB_SHA256
970 SHA256 secure hash standard (DFIPS 180-2).
972 This version of SHA implements a 256 bit hash with 128 bits of
973 security against collision attacks.
975 This code also includes SHA-224, a 224 bit hash with 112 bits
976 of security against collision attacks.
978 config CRYPTO_SHA256_PPC_SPE
979 tristate "SHA224 and SHA256 digest algorithm (PPC SPE)"
980 depends on PPC && SPE
984 SHA224 and SHA256 secure hash standard (DFIPS 180-2)
985 implemented using powerpc SPE SIMD instruction set.
987 config CRYPTO_SHA256_OCTEON
988 tristate "SHA224 and SHA256 digest algorithm (OCTEON)"
989 depends on CPU_CAVIUM_OCTEON
993 SHA-256 secure hash standard (DFIPS 180-2) implemented
994 using OCTEON crypto instructions, when available.
996 config CRYPTO_SHA256_SPARC64
997 tristate "SHA224 and SHA256 digest algorithm (SPARC64)"
1002 SHA-256 secure hash standard (DFIPS 180-2) implemented
1003 using sparc64 crypto instructions, when available.
1005 config CRYPTO_SHA256_S390
1006 tristate "SHA256 digest algorithm"
1010 This is the s390 hardware accelerated implementation of the
1011 SHA256 secure hash standard (DFIPS 180-2).
1013 It is available as of z9.
1015 config CRYPTO_SHA512
1016 tristate "SHA384 and SHA512 digest algorithms"
1019 SHA512 secure hash standard (DFIPS 180-2).
1021 This version of SHA implements a 512 bit hash with 256 bits of
1022 security against collision attacks.
1024 This code also includes SHA-384, a 384 bit hash with 192 bits
1025 of security against collision attacks.
1027 config CRYPTO_SHA512_OCTEON
1028 tristate "SHA384 and SHA512 digest algorithms (OCTEON)"
1029 depends on CPU_CAVIUM_OCTEON
1030 select CRYPTO_SHA512
1033 SHA-512 secure hash standard (DFIPS 180-2) implemented
1034 using OCTEON crypto instructions, when available.
1036 config CRYPTO_SHA512_SPARC64
1037 tristate "SHA384 and SHA512 digest algorithm (SPARC64)"
1039 select CRYPTO_SHA512
1042 SHA-512 secure hash standard (DFIPS 180-2) implemented
1043 using sparc64 crypto instructions, when available.
1046 tristate "SHA3 digest algorithm"
1049 SHA-3 secure hash standard (DFIPS 202). It's based on
1050 cryptographic sponge function family called Keccak.
1053 http://keccak.noekeon.org/
1055 config CRYPTO_SHA3_256_S390
1056 tristate "SHA3_224 and SHA3_256 digest algorithm"
1060 This is the s390 hardware accelerated implementation of the
1061 SHA3_256 secure hash standard.
1063 It is available as of z14.
1065 config CRYPTO_SHA3_512_S390
1066 tristate "SHA3_384 and SHA3_512 digest algorithm"
1070 This is the s390 hardware accelerated implementation of the
1071 SHA3_512 secure hash standard.
1073 It is available as of z14.
1078 config CRYPTO_SM3_GENERIC
1079 tristate "SM3 digest algorithm"
1083 SM3 secure hash function as defined by OSCCA GM/T 0004-2012 SM3).
1084 It is part of the Chinese Commercial Cryptography suite.
1087 http://www.oscca.gov.cn/UpFile/20101222141857786.pdf
1088 https://datatracker.ietf.org/doc/html/draft-shen-sm3-hash
1090 config CRYPTO_SM3_AVX_X86_64
1091 tristate "SM3 digest algorithm (x86_64/AVX)"
1092 depends on X86 && 64BIT
1096 SM3 secure hash function as defined by OSCCA GM/T 0004-2012 SM3).
1097 It is part of the Chinese Commercial Cryptography suite. This is
1098 SM3 optimized implementation using Advanced Vector Extensions (AVX)
1103 config CRYPTO_STREEBOG
1104 tristate "Streebog Hash Function"
1107 Streebog Hash Function (GOST R 34.11-2012, RFC 6986) is one of the Russian
1108 cryptographic standard algorithms (called GOST algorithms).
1109 This setting enables two hash algorithms with 256 and 512 bits output.
1112 https://tc26.ru/upload/iblock/fed/feddbb4d26b685903faa2ba11aea43f6.pdf
1113 https://tools.ietf.org/html/rfc6986
1116 tristate "Whirlpool digest algorithms"
1119 Whirlpool hash algorithm 512, 384 and 256-bit hashes
1121 Whirlpool-512 is part of the NESSIE cryptographic primitives.
1122 Whirlpool will be part of the ISO/IEC 10118-3:2003(E) standard
1125 <http://www.larc.usp.br/~pbarreto/WhirlpoolPage.html>
1127 config CRYPTO_GHASH_CLMUL_NI_INTEL
1128 tristate "GHASH hash function (CLMUL-NI accelerated)"
1129 depends on X86 && 64BIT
1130 select CRYPTO_CRYPTD
1132 This is the x86_64 CLMUL-NI accelerated implementation of
1133 GHASH, the hash function used in GCM (Galois/Counter mode).
1135 config CRYPTO_GHASH_S390
1136 tristate "GHASH hash function"
1140 This is the s390 hardware accelerated implementation of GHASH,
1141 the hash function used in GCM (Galois/Counter mode).
1143 It is available as of z196.
1148 tristate "AES cipher algorithms"
1149 select CRYPTO_ALGAPI
1150 select CRYPTO_LIB_AES
1152 AES cipher algorithms (FIPS-197). AES uses the Rijndael
1155 Rijndael appears to be consistently a very good performer in
1156 both hardware and software across a wide range of computing
1157 environments regardless of its use in feedback or non-feedback
1158 modes. Its key setup time is excellent, and its key agility is
1159 good. Rijndael's very low memory requirements make it very well
1160 suited for restricted-space environments, in which it also
1161 demonstrates excellent performance. Rijndael's operations are
1162 among the easiest to defend against power and timing attacks.
1164 The AES specifies three key sizes: 128, 192 and 256 bits
1166 See <http://csrc.nist.gov/CryptoToolkit/aes/> for more information.
1168 config CRYPTO_AES_TI
1169 tristate "Fixed time AES cipher"
1170 select CRYPTO_ALGAPI
1171 select CRYPTO_LIB_AES
1173 This is a generic implementation of AES that attempts to eliminate
1174 data dependent latencies as much as possible without affecting
1175 performance too much. It is intended for use by the generic CCM
1176 and GCM drivers, and other CTR or CMAC/XCBC based modes that rely
1177 solely on encryption (although decryption is supported as well, but
1178 with a more dramatic performance hit)
1180 Instead of using 16 lookup tables of 1 KB each, (8 for encryption and
1181 8 for decryption), this implementation only uses just two S-boxes of
1182 256 bytes each, and attempts to eliminate data dependent latencies by
1183 prefetching the entire table into the cache at the start of each
1184 block. Interrupts are also disabled to avoid races where cachelines
1185 are evicted when the CPU is interrupted to do something else.
1187 config CRYPTO_AES_NI_INTEL
1188 tristate "AES cipher algorithms (AES-NI)"
1191 select CRYPTO_LIB_AES
1192 select CRYPTO_ALGAPI
1193 select CRYPTO_SKCIPHER
1196 Use Intel AES-NI instructions for AES algorithm.
1198 AES cipher algorithms (FIPS-197). AES uses the Rijndael
1201 Rijndael appears to be consistently a very good performer in
1202 both hardware and software across a wide range of computing
1203 environments regardless of its use in feedback or non-feedback
1204 modes. Its key setup time is excellent, and its key agility is
1205 good. Rijndael's very low memory requirements make it very well
1206 suited for restricted-space environments, in which it also
1207 demonstrates excellent performance. Rijndael's operations are
1208 among the easiest to defend against power and timing attacks.
1210 The AES specifies three key sizes: 128, 192 and 256 bits
1212 See <http://csrc.nist.gov/encryption/aes/> for more information.
1214 In addition to AES cipher algorithm support, the acceleration
1215 for some popular block cipher mode is supported too, including
1216 ECB, CBC, LRW, XTS. The 64 bit version has additional
1217 acceleration for CTR.
1219 config CRYPTO_AES_SPARC64
1220 tristate "AES cipher algorithms (SPARC64)"
1222 select CRYPTO_SKCIPHER
1224 Use SPARC64 crypto opcodes for AES algorithm.
1226 AES cipher algorithms (FIPS-197). AES uses the Rijndael
1229 Rijndael appears to be consistently a very good performer in
1230 both hardware and software across a wide range of computing
1231 environments regardless of its use in feedback or non-feedback
1232 modes. Its key setup time is excellent, and its key agility is
1233 good. Rijndael's very low memory requirements make it very well
1234 suited for restricted-space environments, in which it also
1235 demonstrates excellent performance. Rijndael's operations are
1236 among the easiest to defend against power and timing attacks.
1238 The AES specifies three key sizes: 128, 192 and 256 bits
1240 See <http://csrc.nist.gov/encryption/aes/> for more information.
1242 In addition to AES cipher algorithm support, the acceleration
1243 for some popular block cipher mode is supported too, including
1246 config CRYPTO_AES_PPC_SPE
1247 tristate "AES cipher algorithms (PPC SPE)"
1248 depends on PPC && SPE
1249 select CRYPTO_SKCIPHER
1251 AES cipher algorithms (FIPS-197). Additionally the acceleration
1252 for popular block cipher modes ECB, CBC, CTR and XTS is supported.
1253 This module should only be used for low power (router) devices
1254 without hardware AES acceleration (e.g. caam crypto). It reduces the
1255 size of the AES tables from 16KB to 8KB + 256 bytes and mitigates
1256 timining attacks. Nevertheless it might be not as secure as other
1257 architecture specific assembler implementations that work on 1KB
1258 tables or 256 bytes S-boxes.
1260 config CRYPTO_AES_S390
1261 tristate "AES cipher algorithms"
1263 select CRYPTO_ALGAPI
1264 select CRYPTO_SKCIPHER
1266 This is the s390 hardware accelerated implementation of the
1267 AES cipher algorithms (FIPS-197).
1269 As of z9 the ECB and CBC modes are hardware accelerated
1271 As of z10 the ECB and CBC modes are hardware accelerated
1272 for all AES key sizes.
1273 As of z196 the CTR mode is hardware accelerated for all AES
1274 key sizes and XTS mode is hardware accelerated for 256 and
1277 config CRYPTO_ANUBIS
1278 tristate "Anubis cipher algorithm"
1279 depends on CRYPTO_USER_API_ENABLE_OBSOLETE
1280 select CRYPTO_ALGAPI
1282 Anubis cipher algorithm.
1284 Anubis is a variable key length cipher which can use keys from
1285 128 bits to 320 bits in length. It was evaluated as a entrant
1286 in the NESSIE competition.
1289 <https://www.cosic.esat.kuleuven.be/nessie/reports/>
1290 <http://www.larc.usp.br/~pbarreto/AnubisPage.html>
1293 tristate "ARC4 cipher algorithm"
1294 depends on CRYPTO_USER_API_ENABLE_OBSOLETE
1295 select CRYPTO_SKCIPHER
1296 select CRYPTO_LIB_ARC4
1298 ARC4 cipher algorithm.
1300 ARC4 is a stream cipher using keys ranging from 8 bits to 2048
1301 bits in length. This algorithm is required for driver-based
1302 WEP, but it should not be for other purposes because of the
1303 weakness of the algorithm.
1305 config CRYPTO_BLOWFISH
1306 tristate "Blowfish cipher algorithm"
1307 select CRYPTO_ALGAPI
1308 select CRYPTO_BLOWFISH_COMMON
1310 Blowfish cipher algorithm, by Bruce Schneier.
1312 This is a variable key length cipher which can use keys from 32
1313 bits to 448 bits in length. It's fast, simple and specifically
1314 designed for use on "large microprocessors".
1317 <https://www.schneier.com/blowfish.html>
1319 config CRYPTO_BLOWFISH_COMMON
1322 Common parts of the Blowfish cipher algorithm shared by the
1323 generic c and the assembler implementations.
1326 <https://www.schneier.com/blowfish.html>
1328 config CRYPTO_BLOWFISH_X86_64
1329 tristate "Blowfish cipher algorithm (x86_64)"
1330 depends on X86 && 64BIT
1331 select CRYPTO_SKCIPHER
1332 select CRYPTO_BLOWFISH_COMMON
1335 Blowfish cipher algorithm (x86_64), by Bruce Schneier.
1337 This is a variable key length cipher which can use keys from 32
1338 bits to 448 bits in length. It's fast, simple and specifically
1339 designed for use on "large microprocessors".
1342 <https://www.schneier.com/blowfish.html>
1344 config CRYPTO_CAMELLIA
1345 tristate "Camellia cipher algorithms"
1346 select CRYPTO_ALGAPI
1348 Camellia cipher algorithms module.
1350 Camellia is a symmetric key block cipher developed jointly
1351 at NTT and Mitsubishi Electric Corporation.
1353 The Camellia specifies three key sizes: 128, 192 and 256 bits.
1356 <https://info.isl.ntt.co.jp/crypt/eng/camellia/index_s.html>
1358 config CRYPTO_CAMELLIA_X86_64
1359 tristate "Camellia cipher algorithm (x86_64)"
1360 depends on X86 && 64BIT
1361 select CRYPTO_SKCIPHER
1364 Camellia cipher algorithm module (x86_64).
1366 Camellia is a symmetric key block cipher developed jointly
1367 at NTT and Mitsubishi Electric Corporation.
1369 The Camellia specifies three key sizes: 128, 192 and 256 bits.
1372 <https://info.isl.ntt.co.jp/crypt/eng/camellia/index_s.html>
1374 config CRYPTO_CAMELLIA_AESNI_AVX_X86_64
1375 tristate "Camellia cipher algorithm (x86_64/AES-NI/AVX)"
1376 depends on X86 && 64BIT
1377 select CRYPTO_SKCIPHER
1378 select CRYPTO_CAMELLIA_X86_64
1382 Camellia cipher algorithm module (x86_64/AES-NI/AVX).
1384 Camellia is a symmetric key block cipher developed jointly
1385 at NTT and Mitsubishi Electric Corporation.
1387 The Camellia specifies three key sizes: 128, 192 and 256 bits.
1390 <https://info.isl.ntt.co.jp/crypt/eng/camellia/index_s.html>
1392 config CRYPTO_CAMELLIA_AESNI_AVX2_X86_64
1393 tristate "Camellia cipher algorithm (x86_64/AES-NI/AVX2)"
1394 depends on X86 && 64BIT
1395 select CRYPTO_CAMELLIA_AESNI_AVX_X86_64
1397 Camellia cipher algorithm module (x86_64/AES-NI/AVX2).
1399 Camellia is a symmetric key block cipher developed jointly
1400 at NTT and Mitsubishi Electric Corporation.
1402 The Camellia specifies three key sizes: 128, 192 and 256 bits.
1405 <https://info.isl.ntt.co.jp/crypt/eng/camellia/index_s.html>
1407 config CRYPTO_CAMELLIA_SPARC64
1408 tristate "Camellia cipher algorithm (SPARC64)"
1410 select CRYPTO_ALGAPI
1411 select CRYPTO_SKCIPHER
1413 Camellia cipher algorithm module (SPARC64).
1415 Camellia is a symmetric key block cipher developed jointly
1416 at NTT and Mitsubishi Electric Corporation.
1418 The Camellia specifies three key sizes: 128, 192 and 256 bits.
1421 <https://info.isl.ntt.co.jp/crypt/eng/camellia/index_s.html>
1423 config CRYPTO_CAST_COMMON
1426 Common parts of the CAST cipher algorithms shared by the
1427 generic c and the assembler implementations.
1430 tristate "CAST5 (CAST-128) cipher algorithm"
1431 select CRYPTO_ALGAPI
1432 select CRYPTO_CAST_COMMON
1434 The CAST5 encryption algorithm (synonymous with CAST-128) is
1435 described in RFC2144.
1437 config CRYPTO_CAST5_AVX_X86_64
1438 tristate "CAST5 (CAST-128) cipher algorithm (x86_64/AVX)"
1439 depends on X86 && 64BIT
1440 select CRYPTO_SKCIPHER
1442 select CRYPTO_CAST_COMMON
1446 The CAST5 encryption algorithm (synonymous with CAST-128) is
1447 described in RFC2144.
1449 This module provides the Cast5 cipher algorithm that processes
1450 sixteen blocks parallel using the AVX instruction set.
1453 tristate "CAST6 (CAST-256) cipher algorithm"
1454 select CRYPTO_ALGAPI
1455 select CRYPTO_CAST_COMMON
1457 The CAST6 encryption algorithm (synonymous with CAST-256) is
1458 described in RFC2612.
1460 config CRYPTO_CAST6_AVX_X86_64
1461 tristate "CAST6 (CAST-256) cipher algorithm (x86_64/AVX)"
1462 depends on X86 && 64BIT
1463 select CRYPTO_SKCIPHER
1465 select CRYPTO_CAST_COMMON
1470 The CAST6 encryption algorithm (synonymous with CAST-256) is
1471 described in RFC2612.
1473 This module provides the Cast6 cipher algorithm that processes
1474 eight blocks parallel using the AVX instruction set.
1477 tristate "DES and Triple DES EDE cipher algorithms"
1478 select CRYPTO_ALGAPI
1479 select CRYPTO_LIB_DES
1481 DES cipher algorithm (FIPS 46-2), and Triple DES EDE (FIPS 46-3).
1483 config CRYPTO_DES_SPARC64
1484 tristate "DES and Triple DES EDE cipher algorithms (SPARC64)"
1486 select CRYPTO_ALGAPI
1487 select CRYPTO_LIB_DES
1488 select CRYPTO_SKCIPHER
1490 DES cipher algorithm (FIPS 46-2), and Triple DES EDE (FIPS 46-3),
1491 optimized using SPARC64 crypto opcodes.
1493 config CRYPTO_DES3_EDE_X86_64
1494 tristate "Triple DES EDE cipher algorithm (x86-64)"
1495 depends on X86 && 64BIT
1496 select CRYPTO_SKCIPHER
1497 select CRYPTO_LIB_DES
1500 Triple DES EDE (FIPS 46-3) algorithm.
1502 This module provides implementation of the Triple DES EDE cipher
1503 algorithm that is optimized for x86-64 processors. Two versions of
1504 algorithm are provided; regular processing one input block and
1505 one that processes three blocks parallel.
1507 config CRYPTO_DES_S390
1508 tristate "DES and Triple DES cipher algorithms"
1510 select CRYPTO_ALGAPI
1511 select CRYPTO_SKCIPHER
1512 select CRYPTO_LIB_DES
1514 This is the s390 hardware accelerated implementation of the
1515 DES cipher algorithm (FIPS 46-2), and Triple DES EDE (FIPS 46-3).
1517 As of z990 the ECB and CBC mode are hardware accelerated.
1518 As of z196 the CTR mode is hardware accelerated.
1520 config CRYPTO_FCRYPT
1521 tristate "FCrypt cipher algorithm"
1522 select CRYPTO_ALGAPI
1523 select CRYPTO_SKCIPHER
1525 FCrypt algorithm used by RxRPC.
1527 config CRYPTO_KHAZAD
1528 tristate "Khazad cipher algorithm"
1529 depends on CRYPTO_USER_API_ENABLE_OBSOLETE
1530 select CRYPTO_ALGAPI
1532 Khazad cipher algorithm.
1534 Khazad was a finalist in the initial NESSIE competition. It is
1535 an algorithm optimized for 64-bit processors with good performance
1536 on 32-bit processors. Khazad uses an 128 bit key size.
1539 <http://www.larc.usp.br/~pbarreto/KhazadPage.html>
1541 config CRYPTO_CHACHA20
1542 tristate "ChaCha stream cipher algorithms"
1543 select CRYPTO_LIB_CHACHA_GENERIC
1544 select CRYPTO_SKCIPHER
1546 The ChaCha20, XChaCha20, and XChaCha12 stream cipher algorithms.
1548 ChaCha20 is a 256-bit high-speed stream cipher designed by Daniel J.
1549 Bernstein and further specified in RFC7539 for use in IETF protocols.
1550 This is the portable C implementation of ChaCha20. See also:
1551 <https://cr.yp.to/chacha/chacha-20080128.pdf>
1553 XChaCha20 is the application of the XSalsa20 construction to ChaCha20
1554 rather than to Salsa20. XChaCha20 extends ChaCha20's nonce length
1555 from 64 bits (or 96 bits using the RFC7539 convention) to 192 bits,
1556 while provably retaining ChaCha20's security. See also:
1557 <https://cr.yp.to/snuffle/xsalsa-20081128.pdf>
1559 XChaCha12 is XChaCha20 reduced to 12 rounds, with correspondingly
1560 reduced security margin but increased performance. It can be needed
1561 in some performance-sensitive scenarios.
1563 config CRYPTO_CHACHA20_X86_64
1564 tristate "ChaCha stream cipher algorithms (x86_64/SSSE3/AVX2/AVX-512VL)"
1565 depends on X86 && 64BIT
1566 select CRYPTO_SKCIPHER
1567 select CRYPTO_LIB_CHACHA_GENERIC
1568 select CRYPTO_ARCH_HAVE_LIB_CHACHA
1570 SSSE3, AVX2, and AVX-512VL optimized implementations of the ChaCha20,
1571 XChaCha20, and XChaCha12 stream ciphers.
1573 config CRYPTO_CHACHA_MIPS
1574 tristate "ChaCha stream cipher algorithms (MIPS 32r2 optimized)"
1575 depends on CPU_MIPS32_R2
1576 select CRYPTO_SKCIPHER
1577 select CRYPTO_ARCH_HAVE_LIB_CHACHA
1579 config CRYPTO_CHACHA_S390
1580 tristate "ChaCha20 stream cipher"
1582 select CRYPTO_SKCIPHER
1583 select CRYPTO_LIB_CHACHA_GENERIC
1584 select CRYPTO_ARCH_HAVE_LIB_CHACHA
1586 This is the s390 SIMD implementation of the ChaCha20 stream
1589 It is available as of z13.
1592 tristate "SEED cipher algorithm"
1593 depends on CRYPTO_USER_API_ENABLE_OBSOLETE
1594 select CRYPTO_ALGAPI
1596 SEED cipher algorithm (RFC4269).
1598 SEED is a 128-bit symmetric key block cipher that has been
1599 developed by KISA (Korea Information Security Agency) as a
1600 national standard encryption algorithm of the Republic of Korea.
1601 It is a 16 round block cipher with the key size of 128 bit.
1604 <http://www.kisa.or.kr/kisa/seed/jsp/seed_eng.jsp>
1606 config CRYPTO_SERPENT
1607 tristate "Serpent cipher algorithm"
1608 select CRYPTO_ALGAPI
1610 Serpent cipher algorithm, by Anderson, Biham & Knudsen.
1612 Keys are allowed to be from 0 to 256 bits in length, in steps
1616 <https://www.cl.cam.ac.uk/~rja14/serpent.html>
1618 config CRYPTO_SERPENT_SSE2_X86_64
1619 tristate "Serpent cipher algorithm (x86_64/SSE2)"
1620 depends on X86 && 64BIT
1621 select CRYPTO_SKCIPHER
1622 select CRYPTO_SERPENT
1626 Serpent cipher algorithm, by Anderson, Biham & Knudsen.
1628 Keys are allowed to be from 0 to 256 bits in length, in steps
1631 This module provides Serpent cipher algorithm that processes eight
1632 blocks parallel using SSE2 instruction set.
1635 <https://www.cl.cam.ac.uk/~rja14/serpent.html>
1637 config CRYPTO_SERPENT_SSE2_586
1638 tristate "Serpent cipher algorithm (i586/SSE2)"
1639 depends on X86 && !64BIT
1640 select CRYPTO_SKCIPHER
1641 select CRYPTO_SERPENT
1645 Serpent cipher algorithm, by Anderson, Biham & Knudsen.
1647 Keys are allowed to be from 0 to 256 bits in length, in steps
1650 This module provides Serpent cipher algorithm that processes four
1651 blocks parallel using SSE2 instruction set.
1654 <https://www.cl.cam.ac.uk/~rja14/serpent.html>
1656 config CRYPTO_SERPENT_AVX_X86_64
1657 tristate "Serpent cipher algorithm (x86_64/AVX)"
1658 depends on X86 && 64BIT
1659 select CRYPTO_SKCIPHER
1660 select CRYPTO_SERPENT
1665 Serpent cipher algorithm, by Anderson, Biham & Knudsen.
1667 Keys are allowed to be from 0 to 256 bits in length, in steps
1670 This module provides the Serpent cipher algorithm that processes
1671 eight blocks parallel using the AVX instruction set.
1674 <https://www.cl.cam.ac.uk/~rja14/serpent.html>
1676 config CRYPTO_SERPENT_AVX2_X86_64
1677 tristate "Serpent cipher algorithm (x86_64/AVX2)"
1678 depends on X86 && 64BIT
1679 select CRYPTO_SERPENT_AVX_X86_64
1681 Serpent cipher algorithm, by Anderson, Biham & Knudsen.
1683 Keys are allowed to be from 0 to 256 bits in length, in steps
1686 This module provides Serpent cipher algorithm that processes 16
1687 blocks parallel using AVX2 instruction set.
1690 <https://www.cl.cam.ac.uk/~rja14/serpent.html>
1695 config CRYPTO_SM4_GENERIC
1696 tristate "SM4 cipher algorithm"
1697 select CRYPTO_ALGAPI
1700 SM4 cipher algorithms (OSCCA GB/T 32907-2016).
1702 SM4 (GBT.32907-2016) is a cryptographic standard issued by the
1703 Organization of State Commercial Administration of China (OSCCA)
1704 as an authorized cryptographic algorithms for the use within China.
1706 SMS4 was originally created for use in protecting wireless
1707 networks, and is mandated in the Chinese National Standard for
1708 Wireless LAN WAPI (Wired Authentication and Privacy Infrastructure)
1711 The latest SM4 standard (GBT.32907-2016) was proposed by OSCCA and
1712 standardized through TC 260 of the Standardization Administration
1713 of the People's Republic of China (SAC).
1715 The input, output, and key of SMS4 are each 128 bits.
1717 See also: <https://eprint.iacr.org/2008/329.pdf>
1721 config CRYPTO_SM4_AESNI_AVX_X86_64
1722 tristate "SM4 cipher algorithm (x86_64/AES-NI/AVX)"
1723 depends on X86 && 64BIT
1724 select CRYPTO_SKCIPHER
1726 select CRYPTO_ALGAPI
1729 SM4 cipher algorithms (OSCCA GB/T 32907-2016) (x86_64/AES-NI/AVX).
1731 SM4 (GBT.32907-2016) is a cryptographic standard issued by the
1732 Organization of State Commercial Administration of China (OSCCA)
1733 as an authorized cryptographic algorithms for the use within China.
1735 This is SM4 optimized implementation using AES-NI/AVX/x86_64
1736 instruction set for block cipher. Through two affine transforms,
1737 we can use the AES S-Box to simulate the SM4 S-Box to achieve the
1738 effect of instruction acceleration.
1742 config CRYPTO_SM4_AESNI_AVX2_X86_64
1743 tristate "SM4 cipher algorithm (x86_64/AES-NI/AVX2)"
1744 depends on X86 && 64BIT
1745 select CRYPTO_SKCIPHER
1747 select CRYPTO_ALGAPI
1749 select CRYPTO_SM4_AESNI_AVX_X86_64
1751 SM4 cipher algorithms (OSCCA GB/T 32907-2016) (x86_64/AES-NI/AVX2).
1753 SM4 (GBT.32907-2016) is a cryptographic standard issued by the
1754 Organization of State Commercial Administration of China (OSCCA)
1755 as an authorized cryptographic algorithms for the use within China.
1757 This is SM4 optimized implementation using AES-NI/AVX2/x86_64
1758 instruction set for block cipher. Through two affine transforms,
1759 we can use the AES S-Box to simulate the SM4 S-Box to achieve the
1760 effect of instruction acceleration.
1765 tristate "TEA, XTEA and XETA cipher algorithms"
1766 depends on CRYPTO_USER_API_ENABLE_OBSOLETE
1767 select CRYPTO_ALGAPI
1769 TEA cipher algorithm.
1771 Tiny Encryption Algorithm is a simple cipher that uses
1772 many rounds for security. It is very fast and uses
1775 Xtendend Tiny Encryption Algorithm is a modification to
1776 the TEA algorithm to address a potential key weakness
1777 in the TEA algorithm.
1779 Xtendend Encryption Tiny Algorithm is a mis-implementation
1780 of the XTEA algorithm for compatibility purposes.
1782 config CRYPTO_TWOFISH
1783 tristate "Twofish cipher algorithm"
1784 select CRYPTO_ALGAPI
1785 select CRYPTO_TWOFISH_COMMON
1787 Twofish cipher algorithm.
1789 Twofish was submitted as an AES (Advanced Encryption Standard)
1790 candidate cipher by researchers at CounterPane Systems. It is a
1791 16 round block cipher supporting key sizes of 128, 192, and 256
1795 <https://www.schneier.com/twofish.html>
1797 config CRYPTO_TWOFISH_COMMON
1800 Common parts of the Twofish cipher algorithm shared by the
1801 generic c and the assembler implementations.
1803 config CRYPTO_TWOFISH_586
1804 tristate "Twofish cipher algorithms (i586)"
1805 depends on (X86 || UML_X86) && !64BIT
1806 select CRYPTO_ALGAPI
1807 select CRYPTO_TWOFISH_COMMON
1810 Twofish cipher algorithm.
1812 Twofish was submitted as an AES (Advanced Encryption Standard)
1813 candidate cipher by researchers at CounterPane Systems. It is a
1814 16 round block cipher supporting key sizes of 128, 192, and 256
1818 <https://www.schneier.com/twofish.html>
1820 config CRYPTO_TWOFISH_X86_64
1821 tristate "Twofish cipher algorithm (x86_64)"
1822 depends on (X86 || UML_X86) && 64BIT
1823 select CRYPTO_ALGAPI
1824 select CRYPTO_TWOFISH_COMMON
1827 Twofish cipher algorithm (x86_64).
1829 Twofish was submitted as an AES (Advanced Encryption Standard)
1830 candidate cipher by researchers at CounterPane Systems. It is a
1831 16 round block cipher supporting key sizes of 128, 192, and 256
1835 <https://www.schneier.com/twofish.html>
1837 config CRYPTO_TWOFISH_X86_64_3WAY
1838 tristate "Twofish cipher algorithm (x86_64, 3-way parallel)"
1839 depends on X86 && 64BIT
1840 select CRYPTO_SKCIPHER
1841 select CRYPTO_TWOFISH_COMMON
1842 select CRYPTO_TWOFISH_X86_64
1844 Twofish cipher algorithm (x86_64, 3-way parallel).
1846 Twofish was submitted as an AES (Advanced Encryption Standard)
1847 candidate cipher by researchers at CounterPane Systems. It is a
1848 16 round block cipher supporting key sizes of 128, 192, and 256
1851 This module provides Twofish cipher algorithm that processes three
1852 blocks parallel, utilizing resources of out-of-order CPUs better.
1855 <https://www.schneier.com/twofish.html>
1857 config CRYPTO_TWOFISH_AVX_X86_64
1858 tristate "Twofish cipher algorithm (x86_64/AVX)"
1859 depends on X86 && 64BIT
1860 select CRYPTO_SKCIPHER
1862 select CRYPTO_TWOFISH_COMMON
1863 select CRYPTO_TWOFISH_X86_64
1864 select CRYPTO_TWOFISH_X86_64_3WAY
1867 Twofish cipher algorithm (x86_64/AVX).
1869 Twofish was submitted as an AES (Advanced Encryption Standard)
1870 candidate cipher by researchers at CounterPane Systems. It is a
1871 16 round block cipher supporting key sizes of 128, 192, and 256
1874 This module provides the Twofish cipher algorithm that processes
1875 eight blocks parallel using the AVX Instruction Set.
1878 <https://www.schneier.com/twofish.html>
1880 comment "Compression"
1882 config CRYPTO_DEFLATE
1883 tristate "Deflate compression algorithm"
1884 select CRYPTO_ALGAPI
1885 select CRYPTO_ACOMP2
1889 This is the Deflate algorithm (RFC1951), specified for use in
1890 IPSec with the IPCOMP protocol (RFC3173, RFC2394).
1892 You will most probably want this if using IPSec.
1895 tristate "LZO compression algorithm"
1896 select CRYPTO_ALGAPI
1897 select CRYPTO_ACOMP2
1899 select LZO_DECOMPRESS
1901 This is the LZO algorithm.
1904 tristate "842 compression algorithm"
1905 select CRYPTO_ALGAPI
1906 select CRYPTO_ACOMP2
1908 select 842_DECOMPRESS
1910 This is the 842 algorithm.
1913 tristate "LZ4 compression algorithm"
1914 select CRYPTO_ALGAPI
1915 select CRYPTO_ACOMP2
1917 select LZ4_DECOMPRESS
1919 This is the LZ4 algorithm.
1922 tristate "LZ4HC compression algorithm"
1923 select CRYPTO_ALGAPI
1924 select CRYPTO_ACOMP2
1925 select LZ4HC_COMPRESS
1926 select LZ4_DECOMPRESS
1928 This is the LZ4 high compression mode algorithm.
1931 tristate "Zstd compression algorithm"
1932 select CRYPTO_ALGAPI
1933 select CRYPTO_ACOMP2
1934 select ZSTD_COMPRESS
1935 select ZSTD_DECOMPRESS
1937 This is the zstd algorithm.
1939 comment "Random Number Generation"
1941 config CRYPTO_ANSI_CPRNG
1942 tristate "Pseudo Random Number Generation for Cryptographic modules"
1946 This option enables the generic pseudo random number generator
1947 for cryptographic modules. Uses the Algorithm specified in
1948 ANSI X9.31 A.2.4. Note that this option must be enabled if
1949 CRYPTO_FIPS is selected
1951 menuconfig CRYPTO_DRBG_MENU
1952 tristate "NIST SP800-90A DRBG"
1954 NIST SP800-90A compliant DRBG. In the following submenu, one or
1955 more of the DRBG types must be selected.
1959 config CRYPTO_DRBG_HMAC
1963 select CRYPTO_SHA512
1965 config CRYPTO_DRBG_HASH
1966 bool "Enable Hash DRBG"
1967 select CRYPTO_SHA256
1969 Enable the Hash DRBG variant as defined in NIST SP800-90A.
1971 config CRYPTO_DRBG_CTR
1972 bool "Enable CTR DRBG"
1976 Enable the CTR DRBG variant as defined in NIST SP800-90A.
1980 default CRYPTO_DRBG_MENU
1982 select CRYPTO_JITTERENTROPY
1984 endif # if CRYPTO_DRBG_MENU
1986 config CRYPTO_JITTERENTROPY
1987 tristate "Jitterentropy Non-Deterministic Random Number Generator"
1990 The Jitterentropy RNG is a noise that is intended
1991 to provide seed to another RNG. The RNG does not
1992 perform any cryptographic whitening of the generated
1993 random numbers. This Jitterentropy RNG registers with
1994 the kernel crypto API and can be used by any caller.
1996 config CRYPTO_KDF800108_CTR
1999 select CRYPTO_SHA256
2001 config CRYPTO_USER_API
2004 config CRYPTO_USER_API_HASH
2005 tristate "User-space interface for hash algorithms"
2008 select CRYPTO_USER_API
2010 This option enables the user-spaces interface for hash
2013 config CRYPTO_USER_API_SKCIPHER
2014 tristate "User-space interface for symmetric key cipher algorithms"
2016 select CRYPTO_SKCIPHER
2017 select CRYPTO_USER_API
2019 This option enables the user-spaces interface for symmetric
2020 key cipher algorithms.
2022 config CRYPTO_USER_API_RNG
2023 tristate "User-space interface for random number generator algorithms"
2026 select CRYPTO_USER_API
2028 This option enables the user-spaces interface for random
2029 number generator algorithms.
2031 config CRYPTO_USER_API_RNG_CAVP
2032 bool "Enable CAVP testing of DRBG"
2033 depends on CRYPTO_USER_API_RNG && CRYPTO_DRBG
2035 This option enables extra API for CAVP testing via the user-space
2036 interface: resetting of DRBG entropy, and providing Additional Data.
2037 This should only be enabled for CAVP testing. You should say
2038 no unless you know what this is.
2040 config CRYPTO_USER_API_AEAD
2041 tristate "User-space interface for AEAD cipher algorithms"
2044 select CRYPTO_SKCIPHER
2046 select CRYPTO_USER_API
2048 This option enables the user-spaces interface for AEAD
2051 config CRYPTO_USER_API_ENABLE_OBSOLETE
2052 bool "Enable obsolete cryptographic algorithms for userspace"
2053 depends on CRYPTO_USER_API
2056 Allow obsolete cryptographic algorithms to be selected that have
2057 already been phased out from internal use by the kernel, and are
2058 only useful for userspace clients that still rely on them.
2061 bool "Crypto usage statistics for User-space"
2062 depends on CRYPTO_USER
2064 This option enables the gathering of crypto stats.
2066 - encrypt/decrypt size and numbers of symmeric operations
2067 - compress/decompress size and numbers of compress operations
2068 - size and numbers of hash operations
2069 - encrypt/decrypt/sign/verify numbers for asymmetric operations
2070 - generate/seed numbers for rng operations
2072 config CRYPTO_HASH_INFO
2075 source "drivers/crypto/Kconfig"
2076 source "crypto/asymmetric_keys/Kconfig"
2077 source "certs/Kconfig"