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 && CRYPTO_MANAGER
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"
204 depends on m || EXPERT
205 select CRYPTO_MANAGER
207 Quick & dirty crypto test module.
216 comment "Public-key cryptography"
219 tristate "RSA algorithm"
220 select CRYPTO_AKCIPHER
221 select CRYPTO_MANAGER
225 Generic implementation of the RSA public key algorithm.
228 tristate "Diffie-Hellman algorithm"
232 Generic implementation of the Diffie-Hellman algorithm.
234 config CRYPTO_DH_RFC7919_GROUPS
235 bool "Support for RFC 7919 FFDHE group parameters"
237 select CRYPTO_RNG_DEFAULT
239 Provide support for RFC 7919 FFDHE group parameters. If unsure, say N.
243 select CRYPTO_RNG_DEFAULT
246 tristate "ECDH algorithm"
250 Generic implementation of the ECDH algorithm
253 tristate "ECDSA (NIST P192, P256 etc.) algorithm"
255 select CRYPTO_AKCIPHER
258 Elliptic Curve Digital Signature Algorithm (NIST P192, P256 etc.)
259 is A NIST cryptographic standard algorithm. Only signature verification
263 tristate "EC-RDSA (GOST 34.10) algorithm"
265 select CRYPTO_AKCIPHER
266 select CRYPTO_STREEBOG
270 Elliptic Curve Russian Digital Signature Algorithm (GOST R 34.10-2012,
271 RFC 7091, ISO/IEC 14888-3:2018) is one of the Russian cryptographic
272 standard algorithms (called GOST algorithms). Only signature verification
276 tristate "SM2 algorithm"
277 select CRYPTO_LIB_SM3
278 select CRYPTO_AKCIPHER
279 select CRYPTO_MANAGER
283 Generic implementation of the SM2 public key algorithm. It was
284 published by State Encryption Management Bureau, China.
285 as specified by OSCCA GM/T 0003.1-2012 -- 0003.5-2012.
288 https://tools.ietf.org/html/draft-shen-sm2-ecdsa-02
289 http://www.oscca.gov.cn/sca/xxgk/2010-12/17/content_1002386.shtml
290 http://www.gmbz.org.cn/main/bzlb.html
292 config CRYPTO_CURVE25519
293 tristate "Curve25519 algorithm"
295 select CRYPTO_LIB_CURVE25519_GENERIC
297 config CRYPTO_CURVE25519_X86
298 tristate "x86_64 accelerated Curve25519 scalar multiplication library"
299 depends on X86 && 64BIT
300 select CRYPTO_LIB_CURVE25519_GENERIC
301 select CRYPTO_ARCH_HAVE_LIB_CURVE25519
303 comment "Authenticated Encryption with Associated Data"
306 tristate "CCM support"
310 select CRYPTO_MANAGER
312 Support for Counter with CBC MAC. Required for IPsec.
315 tristate "GCM/GMAC support"
320 select CRYPTO_MANAGER
322 Support for Galois/Counter Mode (GCM) and Galois Message
323 Authentication Code (GMAC). Required for IPSec.
325 config CRYPTO_CHACHA20POLY1305
326 tristate "ChaCha20-Poly1305 AEAD support"
327 select CRYPTO_CHACHA20
328 select CRYPTO_POLY1305
330 select CRYPTO_MANAGER
332 ChaCha20-Poly1305 AEAD support, RFC7539.
334 Support for the AEAD wrapper using the ChaCha20 stream cipher combined
335 with the Poly1305 authenticator. It is defined in RFC7539 for use in
338 config CRYPTO_AEGIS128
339 tristate "AEGIS-128 AEAD algorithm"
341 select CRYPTO_AES # for AES S-box tables
343 Support for the AEGIS-128 dedicated AEAD algorithm.
345 config CRYPTO_AEGIS128_SIMD
346 bool "Support SIMD acceleration for AEGIS-128"
347 depends on CRYPTO_AEGIS128 && ((ARM || ARM64) && KERNEL_MODE_NEON)
350 config CRYPTO_AEGIS128_AESNI_SSE2
351 tristate "AEGIS-128 AEAD algorithm (x86_64 AESNI+SSE2 implementation)"
352 depends on X86 && 64BIT
356 AESNI+SSE2 implementation of the AEGIS-128 dedicated AEAD algorithm.
359 tristate "Sequence Number IV Generator"
361 select CRYPTO_SKCIPHER
363 select CRYPTO_RNG_DEFAULT
364 select CRYPTO_MANAGER
366 This IV generator generates an IV based on a sequence number by
367 xoring it with a salt. This algorithm is mainly useful for CTR
369 config CRYPTO_ECHAINIV
370 tristate "Encrypted Chain IV Generator"
373 select CRYPTO_RNG_DEFAULT
374 select CRYPTO_MANAGER
376 This IV generator generates an IV based on the encryption of
377 a sequence number xored with a salt. This is the default
380 comment "Block modes"
383 tristate "CBC support"
384 select CRYPTO_SKCIPHER
385 select CRYPTO_MANAGER
387 CBC: Cipher Block Chaining mode
388 This block cipher algorithm is required for IPSec.
391 tristate "CFB support"
392 select CRYPTO_SKCIPHER
393 select CRYPTO_MANAGER
395 CFB: Cipher FeedBack mode
396 This block cipher algorithm is required for TPM2 Cryptography.
399 tristate "CTR support"
400 select CRYPTO_SKCIPHER
401 select CRYPTO_MANAGER
404 This block cipher algorithm is required for IPSec.
407 tristate "CTS support"
408 select CRYPTO_SKCIPHER
409 select CRYPTO_MANAGER
411 CTS: Cipher Text Stealing
412 This is the Cipher Text Stealing mode as described by
413 Section 8 of rfc2040 and referenced by rfc3962
414 (rfc3962 includes errata information in its Appendix A) or
415 CBC-CS3 as defined by NIST in Sp800-38A addendum from Oct 2010.
416 This mode is required for Kerberos gss mechanism support
419 See: https://csrc.nist.gov/publications/detail/sp/800-38a/addendum/final
422 tristate "ECB support"
423 select CRYPTO_SKCIPHER
424 select CRYPTO_MANAGER
426 ECB: Electronic CodeBook mode
427 This is the simplest block cipher algorithm. It simply encrypts
428 the input block by block.
431 tristate "LRW support"
432 select CRYPTO_SKCIPHER
433 select CRYPTO_MANAGER
434 select CRYPTO_GF128MUL
437 LRW: Liskov Rivest Wagner, a tweakable, non malleable, non movable
438 narrow block cipher mode for dm-crypt. Use it with cipher
439 specification string aes-lrw-benbi, the key must be 256, 320 or 384.
440 The first 128, 192 or 256 bits in the key are used for AES and the
441 rest is used to tie each cipher block to its logical position.
444 tristate "OFB support"
445 select CRYPTO_SKCIPHER
446 select CRYPTO_MANAGER
448 OFB: the Output Feedback mode makes a block cipher into a synchronous
449 stream cipher. It generates keystream blocks, which are then XORed
450 with the plaintext blocks to get the ciphertext. Flipping a bit in the
451 ciphertext produces a flipped bit in the plaintext at the same
452 location. This property allows many error correcting codes to function
453 normally even when applied before encryption.
456 tristate "PCBC support"
457 select CRYPTO_SKCIPHER
458 select CRYPTO_MANAGER
460 PCBC: Propagating Cipher Block Chaining mode
461 This block cipher algorithm is required for RxRPC.
464 tristate "XTS support"
465 select CRYPTO_SKCIPHER
466 select CRYPTO_MANAGER
469 XTS: IEEE1619/D16 narrow block cipher use with aes-xts-plain,
470 key size 256, 384 or 512 bits. This implementation currently
471 can't handle a sectorsize which is not a multiple of 16 bytes.
473 config CRYPTO_KEYWRAP
474 tristate "Key wrapping support"
475 select CRYPTO_SKCIPHER
476 select CRYPTO_MANAGER
478 Support for key wrapping (NIST SP800-38F / RFC3394) without
481 config CRYPTO_NHPOLY1305
484 select CRYPTO_LIB_POLY1305_GENERIC
486 config CRYPTO_NHPOLY1305_SSE2
487 tristate "NHPoly1305 hash function (x86_64 SSE2 implementation)"
488 depends on X86 && 64BIT
489 select CRYPTO_NHPOLY1305
491 SSE2 optimized implementation of the hash function used by the
492 Adiantum encryption mode.
494 config CRYPTO_NHPOLY1305_AVX2
495 tristate "NHPoly1305 hash function (x86_64 AVX2 implementation)"
496 depends on X86 && 64BIT
497 select CRYPTO_NHPOLY1305
499 AVX2 optimized implementation of the hash function used by the
500 Adiantum encryption mode.
502 config CRYPTO_ADIANTUM
503 tristate "Adiantum support"
504 select CRYPTO_CHACHA20
505 select CRYPTO_LIB_POLY1305_GENERIC
506 select CRYPTO_NHPOLY1305
507 select CRYPTO_MANAGER
509 Adiantum is a tweakable, length-preserving encryption mode
510 designed for fast and secure disk encryption, especially on
511 CPUs without dedicated crypto instructions. It encrypts
512 each sector using the XChaCha12 stream cipher, two passes of
513 an ε-almost-∆-universal hash function, and an invocation of
514 the AES-256 block cipher on a single 16-byte block. On CPUs
515 without AES instructions, Adiantum is much faster than
518 Adiantum's security is provably reducible to that of its
519 underlying stream and block ciphers, subject to a security
520 bound. Unlike XTS, Adiantum is a true wide-block encryption
521 mode, so it actually provides an even stronger notion of
522 security than XTS, subject to the security bound.
527 tristate "ESSIV support for block encryption"
528 select CRYPTO_AUTHENC
530 Encrypted salt-sector initialization vector (ESSIV) is an IV
531 generation method that is used in some cases by fscrypt and/or
532 dm-crypt. It uses the hash of the block encryption key as the
533 symmetric key for a block encryption pass applied to the input
534 IV, making low entropy IV sources more suitable for block
537 This driver implements a crypto API template that can be
538 instantiated either as an skcipher or as an AEAD (depending on the
539 type of the first template argument), and which defers encryption
540 and decryption requests to the encapsulated cipher after applying
541 ESSIV to the input IV. Note that in the AEAD case, it is assumed
542 that the keys are presented in the same format used by the authenc
543 template, and that the IV appears at the end of the authenticated
544 associated data (AAD) region (which is how dm-crypt uses it.)
546 Note that the use of ESSIV is not recommended for new deployments,
547 and so this only needs to be enabled when interoperability with
548 existing encrypted volumes of filesystems is required, or when
549 building for a particular system that requires it (e.g., when
550 the SoC in question has accelerated CBC but not XTS, making CBC
551 combined with ESSIV the only feasible mode for h/w accelerated
557 tristate "CMAC support"
559 select CRYPTO_MANAGER
561 Cipher-based Message Authentication Code (CMAC) specified by
562 The National Institute of Standards and Technology (NIST).
564 https://tools.ietf.org/html/rfc4493
565 http://csrc.nist.gov/publications/nistpubs/800-38B/SP_800-38B.pdf
568 tristate "HMAC support"
570 select CRYPTO_MANAGER
572 HMAC: Keyed-Hashing for Message Authentication (RFC2104).
573 This is required for IPSec.
576 tristate "XCBC support"
578 select CRYPTO_MANAGER
580 XCBC: Keyed-Hashing with encryption algorithm
581 https://www.ietf.org/rfc/rfc3566.txt
582 http://csrc.nist.gov/encryption/modes/proposedmodes/
583 xcbc-mac/xcbc-mac-spec.pdf
586 tristate "VMAC support"
588 select CRYPTO_MANAGER
590 VMAC is a message authentication algorithm designed for
591 very high speed on 64-bit architectures.
594 <https://fastcrypto.org/vmac>
599 tristate "CRC32c CRC algorithm"
603 Castagnoli, et al Cyclic Redundancy-Check Algorithm. Used
604 by iSCSI for header and data digests and by others.
605 See Castagnoli93. Module will be crc32c.
607 config CRYPTO_CRC32C_INTEL
608 tristate "CRC32c INTEL hardware acceleration"
612 In Intel processor with SSE4.2 supported, the processor will
613 support CRC32C implementation using hardware accelerated CRC32
614 instruction. This option will create 'crc32c-intel' module,
615 which will enable any routine to use the CRC32 instruction to
616 gain performance compared with software implementation.
617 Module will be crc32c-intel.
619 config CRYPTO_CRC32C_VPMSUM
620 tristate "CRC32c CRC algorithm (powerpc64)"
621 depends on PPC64 && ALTIVEC
625 CRC32c algorithm implemented using vector polynomial multiply-sum
626 (vpmsum) instructions, introduced in POWER8. Enable on POWER8
627 and newer processors for improved performance.
630 config CRYPTO_CRC32C_SPARC64
631 tristate "CRC32c CRC algorithm (SPARC64)"
636 CRC32c CRC algorithm implemented using sparc64 crypto instructions,
640 tristate "CRC32 CRC algorithm"
644 CRC-32-IEEE 802.3 cyclic redundancy-check algorithm.
645 Shash crypto api wrappers to crc32_le function.
647 config CRYPTO_CRC32_PCLMUL
648 tristate "CRC32 PCLMULQDQ hardware acceleration"
653 From Intel Westmere and AMD Bulldozer processor with SSE4.2
654 and PCLMULQDQ supported, the processor will support
655 CRC32 PCLMULQDQ implementation using hardware accelerated PCLMULQDQ
656 instruction. This option will create 'crc32-pclmul' module,
657 which will enable any routine to use the CRC-32-IEEE 802.3 checksum
658 and gain better performance as compared with the table implementation.
660 config CRYPTO_CRC32_MIPS
661 tristate "CRC32c and CRC32 CRC algorithm (MIPS)"
662 depends on MIPS_CRC_SUPPORT
665 CRC32c and CRC32 CRC algorithms implemented using mips crypto
666 instructions, when available.
670 tristate "xxHash hash algorithm"
674 xxHash non-cryptographic hash algorithm. Extremely fast, working at
675 speeds close to RAM limits.
677 config CRYPTO_BLAKE2B
678 tristate "BLAKE2b digest algorithm"
681 Implementation of cryptographic hash function BLAKE2b (or just BLAKE2),
682 optimized for 64bit platforms and can produce digests of any size
683 between 1 to 64. The keyed hash is also implemented.
685 This module provides the following algorithms:
692 See https://blake2.net for further information.
694 config CRYPTO_BLAKE2S
695 tristate "BLAKE2s digest algorithm"
696 select CRYPTO_LIB_BLAKE2S_GENERIC
699 Implementation of cryptographic hash function BLAKE2s
700 optimized for 8-32bit platforms and can produce digests of any size
701 between 1 to 32. The keyed hash is also implemented.
703 This module provides the following algorithms:
710 See https://blake2.net for further information.
712 config CRYPTO_BLAKE2S_X86
713 tristate "BLAKE2s digest algorithm (x86 accelerated version)"
714 depends on X86 && 64BIT
715 select CRYPTO_LIB_BLAKE2S_GENERIC
716 select CRYPTO_ARCH_HAVE_LIB_BLAKE2S
718 config CRYPTO_CRCT10DIF
719 tristate "CRCT10DIF algorithm"
722 CRC T10 Data Integrity Field computation is being cast as
723 a crypto transform. This allows for faster crc t10 diff
724 transforms to be used if they are available.
726 config CRYPTO_CRCT10DIF_PCLMUL
727 tristate "CRCT10DIF PCLMULQDQ hardware acceleration"
728 depends on X86 && 64BIT && CRC_T10DIF
731 For x86_64 processors with SSE4.2 and PCLMULQDQ supported,
732 CRC T10 DIF PCLMULQDQ computation can be hardware
733 accelerated PCLMULQDQ instruction. This option will create
734 'crct10dif-pclmul' module, which is faster when computing the
735 crct10dif checksum as compared with the generic table implementation.
737 config CRYPTO_CRCT10DIF_VPMSUM
738 tristate "CRC32T10DIF powerpc64 hardware acceleration"
739 depends on PPC64 && ALTIVEC && CRC_T10DIF
742 CRC10T10DIF algorithm implemented using vector polynomial
743 multiply-sum (vpmsum) instructions, introduced in POWER8. Enable on
744 POWER8 and newer processors for improved performance.
746 config CRYPTO_CRC64_ROCKSOFT
747 tristate "Rocksoft Model CRC64 algorithm"
751 config CRYPTO_VPMSUM_TESTER
752 tristate "Powerpc64 vpmsum hardware acceleration tester"
753 depends on CRYPTO_CRCT10DIF_VPMSUM && CRYPTO_CRC32C_VPMSUM
755 Stress test for CRC32c and CRC-T10DIF algorithms implemented with
756 POWER8 vpmsum instructions.
757 Unless you are testing these algorithms, you don't need this.
760 tristate "GHASH hash function"
761 select CRYPTO_GF128MUL
764 GHASH is the hash function used in GCM (Galois/Counter Mode).
765 It is not a general-purpose cryptographic hash function.
767 config CRYPTO_POLY1305
768 tristate "Poly1305 authenticator algorithm"
770 select CRYPTO_LIB_POLY1305_GENERIC
772 Poly1305 authenticator algorithm, RFC7539.
774 Poly1305 is an authenticator algorithm designed by Daniel J. Bernstein.
775 It is used for the ChaCha20-Poly1305 AEAD, specified in RFC7539 for use
776 in IETF protocols. This is the portable C implementation of Poly1305.
778 config CRYPTO_POLY1305_X86_64
779 tristate "Poly1305 authenticator algorithm (x86_64/SSE2/AVX2)"
780 depends on X86 && 64BIT
781 select CRYPTO_LIB_POLY1305_GENERIC
782 select CRYPTO_ARCH_HAVE_LIB_POLY1305
784 Poly1305 authenticator algorithm, RFC7539.
786 Poly1305 is an authenticator algorithm designed by Daniel J. Bernstein.
787 It is used for the ChaCha20-Poly1305 AEAD, specified in RFC7539 for use
788 in IETF protocols. This is the x86_64 assembler implementation using SIMD
791 config CRYPTO_POLY1305_MIPS
792 tristate "Poly1305 authenticator algorithm (MIPS optimized)"
794 select CRYPTO_ARCH_HAVE_LIB_POLY1305
797 tristate "MD4 digest algorithm"
800 MD4 message digest algorithm (RFC1320).
803 tristate "MD5 digest algorithm"
806 MD5 message digest algorithm (RFC1321).
808 config CRYPTO_MD5_OCTEON
809 tristate "MD5 digest algorithm (OCTEON)"
810 depends on CPU_CAVIUM_OCTEON
814 MD5 message digest algorithm (RFC1321) implemented
815 using OCTEON crypto instructions, when available.
817 config CRYPTO_MD5_PPC
818 tristate "MD5 digest algorithm (PPC)"
822 MD5 message digest algorithm (RFC1321) implemented
825 config CRYPTO_MD5_SPARC64
826 tristate "MD5 digest algorithm (SPARC64)"
831 MD5 message digest algorithm (RFC1321) implemented
832 using sparc64 crypto instructions, when available.
834 config CRYPTO_MICHAEL_MIC
835 tristate "Michael MIC keyed digest algorithm"
838 Michael MIC is used for message integrity protection in TKIP
839 (IEEE 802.11i). This algorithm is required for TKIP, but it
840 should not be used for other purposes because of the weakness
844 tristate "RIPEMD-160 digest algorithm"
847 RIPEMD-160 (ISO/IEC 10118-3:2004).
849 RIPEMD-160 is a 160-bit cryptographic hash function. It is intended
850 to be used as a secure replacement for the 128-bit hash functions
851 MD4, MD5 and it's predecessor RIPEMD
852 (not to be confused with RIPEMD-128).
854 It's speed is comparable to SHA1 and there are no known attacks
857 Developed by Hans Dobbertin, Antoon Bosselaers and Bart Preneel.
858 See <https://homes.esat.kuleuven.be/~bosselae/ripemd160.html>
861 tristate "SHA1 digest algorithm"
864 SHA-1 secure hash standard (FIPS 180-1/DFIPS 180-2).
866 config CRYPTO_SHA1_SSSE3
867 tristate "SHA1 digest algorithm (SSSE3/AVX/AVX2/SHA-NI)"
868 depends on X86 && 64BIT
872 SHA-1 secure hash standard (FIPS 180-1/DFIPS 180-2) implemented
873 using Supplemental SSE3 (SSSE3) instructions or Advanced Vector
874 Extensions (AVX/AVX2) or SHA-NI(SHA Extensions New Instructions),
877 config CRYPTO_SHA256_SSSE3
878 tristate "SHA256 digest algorithm (SSSE3/AVX/AVX2/SHA-NI)"
879 depends on X86 && 64BIT
883 SHA-256 secure hash standard (DFIPS 180-2) implemented
884 using Supplemental SSE3 (SSSE3) instructions, or Advanced Vector
885 Extensions version 1 (AVX1), or Advanced Vector Extensions
886 version 2 (AVX2) instructions, or SHA-NI (SHA Extensions New
887 Instructions) when available.
889 config CRYPTO_SHA512_SSSE3
890 tristate "SHA512 digest algorithm (SSSE3/AVX/AVX2)"
891 depends on X86 && 64BIT
895 SHA-512 secure hash standard (DFIPS 180-2) implemented
896 using Supplemental SSE3 (SSSE3) instructions, or Advanced Vector
897 Extensions version 1 (AVX1), or Advanced Vector Extensions
898 version 2 (AVX2) instructions, when available.
900 config CRYPTO_SHA1_OCTEON
901 tristate "SHA1 digest algorithm (OCTEON)"
902 depends on CPU_CAVIUM_OCTEON
906 SHA-1 secure hash standard (FIPS 180-1/DFIPS 180-2) implemented
907 using OCTEON crypto instructions, when available.
909 config CRYPTO_SHA1_SPARC64
910 tristate "SHA1 digest algorithm (SPARC64)"
915 SHA-1 secure hash standard (FIPS 180-1/DFIPS 180-2) implemented
916 using sparc64 crypto instructions, when available.
918 config CRYPTO_SHA1_PPC
919 tristate "SHA1 digest algorithm (powerpc)"
922 This is the powerpc hardware accelerated implementation of the
923 SHA-1 secure hash standard (FIPS 180-1/DFIPS 180-2).
925 config CRYPTO_SHA1_PPC_SPE
926 tristate "SHA1 digest algorithm (PPC SPE)"
927 depends on PPC && SPE
929 SHA-1 secure hash standard (DFIPS 180-4) implemented
930 using powerpc SPE SIMD instruction set.
933 tristate "SHA224 and SHA256 digest algorithm"
935 select CRYPTO_LIB_SHA256
937 SHA256 secure hash standard (DFIPS 180-2).
939 This version of SHA implements a 256 bit hash with 128 bits of
940 security against collision attacks.
942 This code also includes SHA-224, a 224 bit hash with 112 bits
943 of security against collision attacks.
945 config CRYPTO_SHA256_PPC_SPE
946 tristate "SHA224 and SHA256 digest algorithm (PPC SPE)"
947 depends on PPC && SPE
951 SHA224 and SHA256 secure hash standard (DFIPS 180-2)
952 implemented using powerpc SPE SIMD instruction set.
954 config CRYPTO_SHA256_OCTEON
955 tristate "SHA224 and SHA256 digest algorithm (OCTEON)"
956 depends on CPU_CAVIUM_OCTEON
960 SHA-256 secure hash standard (DFIPS 180-2) implemented
961 using OCTEON crypto instructions, when available.
963 config CRYPTO_SHA256_SPARC64
964 tristate "SHA224 and SHA256 digest algorithm (SPARC64)"
969 SHA-256 secure hash standard (DFIPS 180-2) implemented
970 using sparc64 crypto instructions, when available.
973 tristate "SHA384 and SHA512 digest algorithms"
976 SHA512 secure hash standard (DFIPS 180-2).
978 This version of SHA implements a 512 bit hash with 256 bits of
979 security against collision attacks.
981 This code also includes SHA-384, a 384 bit hash with 192 bits
982 of security against collision attacks.
984 config CRYPTO_SHA512_OCTEON
985 tristate "SHA384 and SHA512 digest algorithms (OCTEON)"
986 depends on CPU_CAVIUM_OCTEON
990 SHA-512 secure hash standard (DFIPS 180-2) implemented
991 using OCTEON crypto instructions, when available.
993 config CRYPTO_SHA512_SPARC64
994 tristate "SHA384 and SHA512 digest algorithm (SPARC64)"
999 SHA-512 secure hash standard (DFIPS 180-2) implemented
1000 using sparc64 crypto instructions, when available.
1003 tristate "SHA3 digest algorithm"
1006 SHA-3 secure hash standard (DFIPS 202). It's based on
1007 cryptographic sponge function family called Keccak.
1010 http://keccak.noekeon.org/
1013 tristate "SM3 digest algorithm"
1015 select CRYPTO_LIB_SM3
1017 SM3 secure hash function as defined by OSCCA GM/T 0004-2012 SM3).
1018 It is part of the Chinese Commercial Cryptography suite.
1021 http://www.oscca.gov.cn/UpFile/20101222141857786.pdf
1022 https://datatracker.ietf.org/doc/html/draft-shen-sm3-hash
1024 config CRYPTO_SM3_AVX_X86_64
1025 tristate "SM3 digest algorithm (x86_64/AVX)"
1026 depends on X86 && 64BIT
1028 select CRYPTO_LIB_SM3
1030 SM3 secure hash function as defined by OSCCA GM/T 0004-2012 SM3).
1031 It is part of the Chinese Commercial Cryptography suite. This is
1032 SM3 optimized implementation using Advanced Vector Extensions (AVX)
1037 config CRYPTO_STREEBOG
1038 tristate "Streebog Hash Function"
1041 Streebog Hash Function (GOST R 34.11-2012, RFC 6986) is one of the Russian
1042 cryptographic standard algorithms (called GOST algorithms).
1043 This setting enables two hash algorithms with 256 and 512 bits output.
1046 https://tc26.ru/upload/iblock/fed/feddbb4d26b685903faa2ba11aea43f6.pdf
1047 https://tools.ietf.org/html/rfc6986
1050 tristate "Whirlpool digest algorithms"
1053 Whirlpool hash algorithm 512, 384 and 256-bit hashes
1055 Whirlpool-512 is part of the NESSIE cryptographic primitives.
1056 Whirlpool will be part of the ISO/IEC 10118-3:2003(E) standard
1059 <http://www.larc.usp.br/~pbarreto/WhirlpoolPage.html>
1061 config CRYPTO_GHASH_CLMUL_NI_INTEL
1062 tristate "GHASH hash function (CLMUL-NI accelerated)"
1063 depends on X86 && 64BIT
1064 select CRYPTO_CRYPTD
1066 This is the x86_64 CLMUL-NI accelerated implementation of
1067 GHASH, the hash function used in GCM (Galois/Counter mode).
1072 tristate "AES cipher algorithms"
1073 select CRYPTO_ALGAPI
1074 select CRYPTO_LIB_AES
1076 AES cipher algorithms (FIPS-197). AES uses the Rijndael
1079 Rijndael appears to be consistently a very good performer in
1080 both hardware and software across a wide range of computing
1081 environments regardless of its use in feedback or non-feedback
1082 modes. Its key setup time is excellent, and its key agility is
1083 good. Rijndael's very low memory requirements make it very well
1084 suited for restricted-space environments, in which it also
1085 demonstrates excellent performance. Rijndael's operations are
1086 among the easiest to defend against power and timing attacks.
1088 The AES specifies three key sizes: 128, 192 and 256 bits
1090 See <http://csrc.nist.gov/CryptoToolkit/aes/> for more information.
1092 config CRYPTO_AES_TI
1093 tristate "Fixed time AES cipher"
1094 select CRYPTO_ALGAPI
1095 select CRYPTO_LIB_AES
1097 This is a generic implementation of AES that attempts to eliminate
1098 data dependent latencies as much as possible without affecting
1099 performance too much. It is intended for use by the generic CCM
1100 and GCM drivers, and other CTR or CMAC/XCBC based modes that rely
1101 solely on encryption (although decryption is supported as well, but
1102 with a more dramatic performance hit)
1104 Instead of using 16 lookup tables of 1 KB each, (8 for encryption and
1105 8 for decryption), this implementation only uses just two S-boxes of
1106 256 bytes each, and attempts to eliminate data dependent latencies by
1107 prefetching the entire table into the cache at the start of each
1108 block. Interrupts are also disabled to avoid races where cachelines
1109 are evicted when the CPU is interrupted to do something else.
1111 config CRYPTO_AES_NI_INTEL
1112 tristate "AES cipher algorithms (AES-NI)"
1115 select CRYPTO_LIB_AES
1116 select CRYPTO_ALGAPI
1117 select CRYPTO_SKCIPHER
1120 Use Intel AES-NI instructions for AES algorithm.
1122 AES cipher algorithms (FIPS-197). AES uses the Rijndael
1125 Rijndael appears to be consistently a very good performer in
1126 both hardware and software across a wide range of computing
1127 environments regardless of its use in feedback or non-feedback
1128 modes. Its key setup time is excellent, and its key agility is
1129 good. Rijndael's very low memory requirements make it very well
1130 suited for restricted-space environments, in which it also
1131 demonstrates excellent performance. Rijndael's operations are
1132 among the easiest to defend against power and timing attacks.
1134 The AES specifies three key sizes: 128, 192 and 256 bits
1136 See <http://csrc.nist.gov/encryption/aes/> for more information.
1138 In addition to AES cipher algorithm support, the acceleration
1139 for some popular block cipher mode is supported too, including
1140 ECB, CBC, LRW, XTS. The 64 bit version has additional
1141 acceleration for CTR.
1143 config CRYPTO_AES_SPARC64
1144 tristate "AES cipher algorithms (SPARC64)"
1146 select CRYPTO_SKCIPHER
1148 Use SPARC64 crypto opcodes for AES algorithm.
1150 AES cipher algorithms (FIPS-197). AES uses the Rijndael
1153 Rijndael appears to be consistently a very good performer in
1154 both hardware and software across a wide range of computing
1155 environments regardless of its use in feedback or non-feedback
1156 modes. Its key setup time is excellent, and its key agility is
1157 good. Rijndael's very low memory requirements make it very well
1158 suited for restricted-space environments, in which it also
1159 demonstrates excellent performance. Rijndael's operations are
1160 among the easiest to defend against power and timing attacks.
1162 The AES specifies three key sizes: 128, 192 and 256 bits
1164 See <http://csrc.nist.gov/encryption/aes/> for more information.
1166 In addition to AES cipher algorithm support, the acceleration
1167 for some popular block cipher mode is supported too, including
1170 config CRYPTO_AES_PPC_SPE
1171 tristate "AES cipher algorithms (PPC SPE)"
1172 depends on PPC && SPE
1173 select CRYPTO_SKCIPHER
1175 AES cipher algorithms (FIPS-197). Additionally the acceleration
1176 for popular block cipher modes ECB, CBC, CTR and XTS is supported.
1177 This module should only be used for low power (router) devices
1178 without hardware AES acceleration (e.g. caam crypto). It reduces the
1179 size of the AES tables from 16KB to 8KB + 256 bytes and mitigates
1180 timining attacks. Nevertheless it might be not as secure as other
1181 architecture specific assembler implementations that work on 1KB
1182 tables or 256 bytes S-boxes.
1184 config CRYPTO_ANUBIS
1185 tristate "Anubis cipher algorithm"
1186 depends on CRYPTO_USER_API_ENABLE_OBSOLETE
1187 select CRYPTO_ALGAPI
1189 Anubis cipher algorithm.
1191 Anubis is a variable key length cipher which can use keys from
1192 128 bits to 320 bits in length. It was evaluated as a entrant
1193 in the NESSIE competition.
1196 <https://www.cosic.esat.kuleuven.be/nessie/reports/>
1197 <http://www.larc.usp.br/~pbarreto/AnubisPage.html>
1200 tristate "ARC4 cipher algorithm"
1201 depends on CRYPTO_USER_API_ENABLE_OBSOLETE
1202 select CRYPTO_SKCIPHER
1203 select CRYPTO_LIB_ARC4
1205 ARC4 cipher algorithm.
1207 ARC4 is a stream cipher using keys ranging from 8 bits to 2048
1208 bits in length. This algorithm is required for driver-based
1209 WEP, but it should not be for other purposes because of the
1210 weakness of the algorithm.
1212 config CRYPTO_BLOWFISH
1213 tristate "Blowfish cipher algorithm"
1214 select CRYPTO_ALGAPI
1215 select CRYPTO_BLOWFISH_COMMON
1217 Blowfish cipher algorithm, by Bruce Schneier.
1219 This is a variable key length cipher which can use keys from 32
1220 bits to 448 bits in length. It's fast, simple and specifically
1221 designed for use on "large microprocessors".
1224 <https://www.schneier.com/blowfish.html>
1226 config CRYPTO_BLOWFISH_COMMON
1229 Common parts of the Blowfish cipher algorithm shared by the
1230 generic c and the assembler implementations.
1233 <https://www.schneier.com/blowfish.html>
1235 config CRYPTO_BLOWFISH_X86_64
1236 tristate "Blowfish cipher algorithm (x86_64)"
1237 depends on X86 && 64BIT
1238 select CRYPTO_SKCIPHER
1239 select CRYPTO_BLOWFISH_COMMON
1242 Blowfish cipher algorithm (x86_64), by Bruce Schneier.
1244 This is a variable key length cipher which can use keys from 32
1245 bits to 448 bits in length. It's fast, simple and specifically
1246 designed for use on "large microprocessors".
1249 <https://www.schneier.com/blowfish.html>
1251 config CRYPTO_CAMELLIA
1252 tristate "Camellia cipher algorithms"
1253 select CRYPTO_ALGAPI
1255 Camellia cipher algorithms module.
1257 Camellia is a symmetric key block cipher developed jointly
1258 at NTT and Mitsubishi Electric Corporation.
1260 The Camellia specifies three key sizes: 128, 192 and 256 bits.
1263 <https://info.isl.ntt.co.jp/crypt/eng/camellia/index_s.html>
1265 config CRYPTO_CAMELLIA_X86_64
1266 tristate "Camellia cipher algorithm (x86_64)"
1267 depends on X86 && 64BIT
1268 select CRYPTO_SKCIPHER
1271 Camellia cipher algorithm module (x86_64).
1273 Camellia is a symmetric key block cipher developed jointly
1274 at NTT and Mitsubishi Electric Corporation.
1276 The Camellia specifies three key sizes: 128, 192 and 256 bits.
1279 <https://info.isl.ntt.co.jp/crypt/eng/camellia/index_s.html>
1281 config CRYPTO_CAMELLIA_AESNI_AVX_X86_64
1282 tristate "Camellia cipher algorithm (x86_64/AES-NI/AVX)"
1283 depends on X86 && 64BIT
1284 select CRYPTO_SKCIPHER
1285 select CRYPTO_CAMELLIA_X86_64
1289 Camellia cipher algorithm module (x86_64/AES-NI/AVX).
1291 Camellia is a symmetric key block cipher developed jointly
1292 at NTT and Mitsubishi Electric Corporation.
1294 The Camellia specifies three key sizes: 128, 192 and 256 bits.
1297 <https://info.isl.ntt.co.jp/crypt/eng/camellia/index_s.html>
1299 config CRYPTO_CAMELLIA_AESNI_AVX2_X86_64
1300 tristate "Camellia cipher algorithm (x86_64/AES-NI/AVX2)"
1301 depends on X86 && 64BIT
1302 select CRYPTO_CAMELLIA_AESNI_AVX_X86_64
1304 Camellia cipher algorithm module (x86_64/AES-NI/AVX2).
1306 Camellia is a symmetric key block cipher developed jointly
1307 at NTT and Mitsubishi Electric Corporation.
1309 The Camellia specifies three key sizes: 128, 192 and 256 bits.
1312 <https://info.isl.ntt.co.jp/crypt/eng/camellia/index_s.html>
1314 config CRYPTO_CAMELLIA_SPARC64
1315 tristate "Camellia cipher algorithm (SPARC64)"
1317 select CRYPTO_ALGAPI
1318 select CRYPTO_SKCIPHER
1320 Camellia cipher algorithm module (SPARC64).
1322 Camellia is a symmetric key block cipher developed jointly
1323 at NTT and Mitsubishi Electric Corporation.
1325 The Camellia specifies three key sizes: 128, 192 and 256 bits.
1328 <https://info.isl.ntt.co.jp/crypt/eng/camellia/index_s.html>
1330 config CRYPTO_CAST_COMMON
1333 Common parts of the CAST cipher algorithms shared by the
1334 generic c and the assembler implementations.
1337 tristate "CAST5 (CAST-128) cipher algorithm"
1338 select CRYPTO_ALGAPI
1339 select CRYPTO_CAST_COMMON
1341 The CAST5 encryption algorithm (synonymous with CAST-128) is
1342 described in RFC2144.
1344 config CRYPTO_CAST5_AVX_X86_64
1345 tristate "CAST5 (CAST-128) cipher algorithm (x86_64/AVX)"
1346 depends on X86 && 64BIT
1347 select CRYPTO_SKCIPHER
1349 select CRYPTO_CAST_COMMON
1353 The CAST5 encryption algorithm (synonymous with CAST-128) is
1354 described in RFC2144.
1356 This module provides the Cast5 cipher algorithm that processes
1357 sixteen blocks parallel using the AVX instruction set.
1360 tristate "CAST6 (CAST-256) cipher algorithm"
1361 select CRYPTO_ALGAPI
1362 select CRYPTO_CAST_COMMON
1364 The CAST6 encryption algorithm (synonymous with CAST-256) is
1365 described in RFC2612.
1367 config CRYPTO_CAST6_AVX_X86_64
1368 tristate "CAST6 (CAST-256) cipher algorithm (x86_64/AVX)"
1369 depends on X86 && 64BIT
1370 select CRYPTO_SKCIPHER
1372 select CRYPTO_CAST_COMMON
1377 The CAST6 encryption algorithm (synonymous with CAST-256) is
1378 described in RFC2612.
1380 This module provides the Cast6 cipher algorithm that processes
1381 eight blocks parallel using the AVX instruction set.
1384 tristate "DES and Triple DES EDE cipher algorithms"
1385 select CRYPTO_ALGAPI
1386 select CRYPTO_LIB_DES
1388 DES cipher algorithm (FIPS 46-2), and Triple DES EDE (FIPS 46-3).
1390 config CRYPTO_DES_SPARC64
1391 tristate "DES and Triple DES EDE cipher algorithms (SPARC64)"
1393 select CRYPTO_ALGAPI
1394 select CRYPTO_LIB_DES
1395 select CRYPTO_SKCIPHER
1397 DES cipher algorithm (FIPS 46-2), and Triple DES EDE (FIPS 46-3),
1398 optimized using SPARC64 crypto opcodes.
1400 config CRYPTO_DES3_EDE_X86_64
1401 tristate "Triple DES EDE cipher algorithm (x86-64)"
1402 depends on X86 && 64BIT
1403 select CRYPTO_SKCIPHER
1404 select CRYPTO_LIB_DES
1407 Triple DES EDE (FIPS 46-3) algorithm.
1409 This module provides implementation of the Triple DES EDE cipher
1410 algorithm that is optimized for x86-64 processors. Two versions of
1411 algorithm are provided; regular processing one input block and
1412 one that processes three blocks parallel.
1414 config CRYPTO_FCRYPT
1415 tristate "FCrypt cipher algorithm"
1416 select CRYPTO_ALGAPI
1417 select CRYPTO_SKCIPHER
1419 FCrypt algorithm used by RxRPC.
1421 config CRYPTO_KHAZAD
1422 tristate "Khazad cipher algorithm"
1423 depends on CRYPTO_USER_API_ENABLE_OBSOLETE
1424 select CRYPTO_ALGAPI
1426 Khazad cipher algorithm.
1428 Khazad was a finalist in the initial NESSIE competition. It is
1429 an algorithm optimized for 64-bit processors with good performance
1430 on 32-bit processors. Khazad uses an 128 bit key size.
1433 <http://www.larc.usp.br/~pbarreto/KhazadPage.html>
1435 config CRYPTO_CHACHA20
1436 tristate "ChaCha stream cipher algorithms"
1437 select CRYPTO_LIB_CHACHA_GENERIC
1438 select CRYPTO_SKCIPHER
1440 The ChaCha20, XChaCha20, and XChaCha12 stream cipher algorithms.
1442 ChaCha20 is a 256-bit high-speed stream cipher designed by Daniel J.
1443 Bernstein and further specified in RFC7539 for use in IETF protocols.
1444 This is the portable C implementation of ChaCha20. See also:
1445 <https://cr.yp.to/chacha/chacha-20080128.pdf>
1447 XChaCha20 is the application of the XSalsa20 construction to ChaCha20
1448 rather than to Salsa20. XChaCha20 extends ChaCha20's nonce length
1449 from 64 bits (or 96 bits using the RFC7539 convention) to 192 bits,
1450 while provably retaining ChaCha20's security. See also:
1451 <https://cr.yp.to/snuffle/xsalsa-20081128.pdf>
1453 XChaCha12 is XChaCha20 reduced to 12 rounds, with correspondingly
1454 reduced security margin but increased performance. It can be needed
1455 in some performance-sensitive scenarios.
1457 config CRYPTO_CHACHA20_X86_64
1458 tristate "ChaCha stream cipher algorithms (x86_64/SSSE3/AVX2/AVX-512VL)"
1459 depends on X86 && 64BIT
1460 select CRYPTO_SKCIPHER
1461 select CRYPTO_LIB_CHACHA_GENERIC
1462 select CRYPTO_ARCH_HAVE_LIB_CHACHA
1464 SSSE3, AVX2, and AVX-512VL optimized implementations of the ChaCha20,
1465 XChaCha20, and XChaCha12 stream ciphers.
1467 config CRYPTO_CHACHA_MIPS
1468 tristate "ChaCha stream cipher algorithms (MIPS 32r2 optimized)"
1469 depends on CPU_MIPS32_R2
1470 select CRYPTO_SKCIPHER
1471 select CRYPTO_ARCH_HAVE_LIB_CHACHA
1474 tristate "SEED cipher algorithm"
1475 depends on CRYPTO_USER_API_ENABLE_OBSOLETE
1476 select CRYPTO_ALGAPI
1478 SEED cipher algorithm (RFC4269).
1480 SEED is a 128-bit symmetric key block cipher that has been
1481 developed by KISA (Korea Information Security Agency) as a
1482 national standard encryption algorithm of the Republic of Korea.
1483 It is a 16 round block cipher with the key size of 128 bit.
1486 <http://www.kisa.or.kr/kisa/seed/jsp/seed_eng.jsp>
1488 config CRYPTO_SERPENT
1489 tristate "Serpent cipher algorithm"
1490 select CRYPTO_ALGAPI
1492 Serpent cipher algorithm, by Anderson, Biham & Knudsen.
1494 Keys are allowed to be from 0 to 256 bits in length, in steps
1498 <https://www.cl.cam.ac.uk/~rja14/serpent.html>
1500 config CRYPTO_SERPENT_SSE2_X86_64
1501 tristate "Serpent cipher algorithm (x86_64/SSE2)"
1502 depends on X86 && 64BIT
1503 select CRYPTO_SKCIPHER
1504 select CRYPTO_SERPENT
1508 Serpent cipher algorithm, by Anderson, Biham & Knudsen.
1510 Keys are allowed to be from 0 to 256 bits in length, in steps
1513 This module provides Serpent cipher algorithm that processes eight
1514 blocks parallel using SSE2 instruction set.
1517 <https://www.cl.cam.ac.uk/~rja14/serpent.html>
1519 config CRYPTO_SERPENT_SSE2_586
1520 tristate "Serpent cipher algorithm (i586/SSE2)"
1521 depends on X86 && !64BIT
1522 select CRYPTO_SKCIPHER
1523 select CRYPTO_SERPENT
1527 Serpent cipher algorithm, by Anderson, Biham & Knudsen.
1529 Keys are allowed to be from 0 to 256 bits in length, in steps
1532 This module provides Serpent cipher algorithm that processes four
1533 blocks parallel using SSE2 instruction set.
1536 <https://www.cl.cam.ac.uk/~rja14/serpent.html>
1538 config CRYPTO_SERPENT_AVX_X86_64
1539 tristate "Serpent cipher algorithm (x86_64/AVX)"
1540 depends on X86 && 64BIT
1541 select CRYPTO_SKCIPHER
1542 select CRYPTO_SERPENT
1547 Serpent cipher algorithm, by Anderson, Biham & Knudsen.
1549 Keys are allowed to be from 0 to 256 bits in length, in steps
1552 This module provides the Serpent cipher algorithm that processes
1553 eight blocks parallel using the AVX instruction set.
1556 <https://www.cl.cam.ac.uk/~rja14/serpent.html>
1558 config CRYPTO_SERPENT_AVX2_X86_64
1559 tristate "Serpent cipher algorithm (x86_64/AVX2)"
1560 depends on X86 && 64BIT
1561 select CRYPTO_SERPENT_AVX_X86_64
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 Serpent cipher algorithm that processes 16
1569 blocks parallel using AVX2 instruction set.
1572 <https://www.cl.cam.ac.uk/~rja14/serpent.html>
1575 tristate "SM4 cipher algorithm"
1576 select CRYPTO_ALGAPI
1577 select CRYPTO_LIB_SM4
1579 SM4 cipher algorithms (OSCCA GB/T 32907-2016).
1581 SM4 (GBT.32907-2016) is a cryptographic standard issued by the
1582 Organization of State Commercial Administration of China (OSCCA)
1583 as an authorized cryptographic algorithms for the use within China.
1585 SMS4 was originally created for use in protecting wireless
1586 networks, and is mandated in the Chinese National Standard for
1587 Wireless LAN WAPI (Wired Authentication and Privacy Infrastructure)
1590 The latest SM4 standard (GBT.32907-2016) was proposed by OSCCA and
1591 standardized through TC 260 of the Standardization Administration
1592 of the People's Republic of China (SAC).
1594 The input, output, and key of SMS4 are each 128 bits.
1596 See also: <https://eprint.iacr.org/2008/329.pdf>
1600 config CRYPTO_SM4_AESNI_AVX_X86_64
1601 tristate "SM4 cipher algorithm (x86_64/AES-NI/AVX)"
1602 depends on X86 && 64BIT
1603 select CRYPTO_SKCIPHER
1605 select CRYPTO_ALGAPI
1606 select CRYPTO_LIB_SM4
1608 SM4 cipher algorithms (OSCCA GB/T 32907-2016) (x86_64/AES-NI/AVX).
1610 SM4 (GBT.32907-2016) is a cryptographic standard issued by the
1611 Organization of State Commercial Administration of China (OSCCA)
1612 as an authorized cryptographic algorithms for the use within China.
1614 This is SM4 optimized implementation using AES-NI/AVX/x86_64
1615 instruction set for block cipher. Through two affine transforms,
1616 we can use the AES S-Box to simulate the SM4 S-Box to achieve the
1617 effect of instruction acceleration.
1621 config CRYPTO_SM4_AESNI_AVX2_X86_64
1622 tristate "SM4 cipher algorithm (x86_64/AES-NI/AVX2)"
1623 depends on X86 && 64BIT
1624 select CRYPTO_SKCIPHER
1626 select CRYPTO_ALGAPI
1627 select CRYPTO_LIB_SM4
1628 select CRYPTO_SM4_AESNI_AVX_X86_64
1630 SM4 cipher algorithms (OSCCA GB/T 32907-2016) (x86_64/AES-NI/AVX2).
1632 SM4 (GBT.32907-2016) is a cryptographic standard issued by the
1633 Organization of State Commercial Administration of China (OSCCA)
1634 as an authorized cryptographic algorithms for the use within China.
1636 This is SM4 optimized implementation using AES-NI/AVX2/x86_64
1637 instruction set for block cipher. Through two affine transforms,
1638 we can use the AES S-Box to simulate the SM4 S-Box to achieve the
1639 effect of instruction acceleration.
1644 tristate "TEA, XTEA and XETA cipher algorithms"
1645 depends on CRYPTO_USER_API_ENABLE_OBSOLETE
1646 select CRYPTO_ALGAPI
1648 TEA cipher algorithm.
1650 Tiny Encryption Algorithm is a simple cipher that uses
1651 many rounds for security. It is very fast and uses
1654 Xtendend Tiny Encryption Algorithm is a modification to
1655 the TEA algorithm to address a potential key weakness
1656 in the TEA algorithm.
1658 Xtendend Encryption Tiny Algorithm is a mis-implementation
1659 of the XTEA algorithm for compatibility purposes.
1661 config CRYPTO_TWOFISH
1662 tristate "Twofish cipher algorithm"
1663 select CRYPTO_ALGAPI
1664 select CRYPTO_TWOFISH_COMMON
1666 Twofish cipher algorithm.
1668 Twofish was submitted as an AES (Advanced Encryption Standard)
1669 candidate cipher by researchers at CounterPane Systems. It is a
1670 16 round block cipher supporting key sizes of 128, 192, and 256
1674 <https://www.schneier.com/twofish.html>
1676 config CRYPTO_TWOFISH_COMMON
1679 Common parts of the Twofish cipher algorithm shared by the
1680 generic c and the assembler implementations.
1682 config CRYPTO_TWOFISH_586
1683 tristate "Twofish cipher algorithms (i586)"
1684 depends on (X86 || UML_X86) && !64BIT
1685 select CRYPTO_ALGAPI
1686 select CRYPTO_TWOFISH_COMMON
1689 Twofish cipher algorithm.
1691 Twofish was submitted as an AES (Advanced Encryption Standard)
1692 candidate cipher by researchers at CounterPane Systems. It is a
1693 16 round block cipher supporting key sizes of 128, 192, and 256
1697 <https://www.schneier.com/twofish.html>
1699 config CRYPTO_TWOFISH_X86_64
1700 tristate "Twofish cipher algorithm (x86_64)"
1701 depends on (X86 || UML_X86) && 64BIT
1702 select CRYPTO_ALGAPI
1703 select CRYPTO_TWOFISH_COMMON
1706 Twofish cipher algorithm (x86_64).
1708 Twofish was submitted as an AES (Advanced Encryption Standard)
1709 candidate cipher by researchers at CounterPane Systems. It is a
1710 16 round block cipher supporting key sizes of 128, 192, and 256
1714 <https://www.schneier.com/twofish.html>
1716 config CRYPTO_TWOFISH_X86_64_3WAY
1717 tristate "Twofish cipher algorithm (x86_64, 3-way parallel)"
1718 depends on X86 && 64BIT
1719 select CRYPTO_SKCIPHER
1720 select CRYPTO_TWOFISH_COMMON
1721 select CRYPTO_TWOFISH_X86_64
1723 Twofish cipher algorithm (x86_64, 3-way parallel).
1725 Twofish was submitted as an AES (Advanced Encryption Standard)
1726 candidate cipher by researchers at CounterPane Systems. It is a
1727 16 round block cipher supporting key sizes of 128, 192, and 256
1730 This module provides Twofish cipher algorithm that processes three
1731 blocks parallel, utilizing resources of out-of-order CPUs better.
1734 <https://www.schneier.com/twofish.html>
1736 config CRYPTO_TWOFISH_AVX_X86_64
1737 tristate "Twofish cipher algorithm (x86_64/AVX)"
1738 depends on X86 && 64BIT
1739 select CRYPTO_SKCIPHER
1741 select CRYPTO_TWOFISH_COMMON
1742 select CRYPTO_TWOFISH_X86_64
1743 select CRYPTO_TWOFISH_X86_64_3WAY
1746 Twofish cipher algorithm (x86_64/AVX).
1748 Twofish was submitted as an AES (Advanced Encryption Standard)
1749 candidate cipher by researchers at CounterPane Systems. It is a
1750 16 round block cipher supporting key sizes of 128, 192, and 256
1753 This module provides the Twofish cipher algorithm that processes
1754 eight blocks parallel using the AVX Instruction Set.
1757 <https://www.schneier.com/twofish.html>
1759 comment "Compression"
1761 config CRYPTO_DEFLATE
1762 tristate "Deflate compression algorithm"
1763 select CRYPTO_ALGAPI
1764 select CRYPTO_ACOMP2
1768 This is the Deflate algorithm (RFC1951), specified for use in
1769 IPSec with the IPCOMP protocol (RFC3173, RFC2394).
1771 You will most probably want this if using IPSec.
1774 tristate "LZO compression algorithm"
1775 select CRYPTO_ALGAPI
1776 select CRYPTO_ACOMP2
1778 select LZO_DECOMPRESS
1780 This is the LZO algorithm.
1783 tristate "842 compression algorithm"
1784 select CRYPTO_ALGAPI
1785 select CRYPTO_ACOMP2
1787 select 842_DECOMPRESS
1789 This is the 842 algorithm.
1792 tristate "LZ4 compression algorithm"
1793 select CRYPTO_ALGAPI
1794 select CRYPTO_ACOMP2
1796 select LZ4_DECOMPRESS
1798 This is the LZ4 algorithm.
1801 tristate "LZ4HC compression algorithm"
1802 select CRYPTO_ALGAPI
1803 select CRYPTO_ACOMP2
1804 select LZ4HC_COMPRESS
1805 select LZ4_DECOMPRESS
1807 This is the LZ4 high compression mode algorithm.
1810 tristate "Zstd compression algorithm"
1811 select CRYPTO_ALGAPI
1812 select CRYPTO_ACOMP2
1813 select ZSTD_COMPRESS
1814 select ZSTD_DECOMPRESS
1816 This is the zstd algorithm.
1818 comment "Random Number Generation"
1820 config CRYPTO_ANSI_CPRNG
1821 tristate "Pseudo Random Number Generation for Cryptographic modules"
1825 This option enables the generic pseudo random number generator
1826 for cryptographic modules. Uses the Algorithm specified in
1827 ANSI X9.31 A.2.4. Note that this option must be enabled if
1828 CRYPTO_FIPS is selected
1830 menuconfig CRYPTO_DRBG_MENU
1831 tristate "NIST SP800-90A DRBG"
1833 NIST SP800-90A compliant DRBG. In the following submenu, one or
1834 more of the DRBG types must be selected.
1838 config CRYPTO_DRBG_HMAC
1842 select CRYPTO_SHA512
1844 config CRYPTO_DRBG_HASH
1845 bool "Enable Hash DRBG"
1846 select CRYPTO_SHA256
1848 Enable the Hash DRBG variant as defined in NIST SP800-90A.
1850 config CRYPTO_DRBG_CTR
1851 bool "Enable CTR DRBG"
1855 Enable the CTR DRBG variant as defined in NIST SP800-90A.
1859 default CRYPTO_DRBG_MENU
1861 select CRYPTO_JITTERENTROPY
1863 endif # if CRYPTO_DRBG_MENU
1865 config CRYPTO_JITTERENTROPY
1866 tristate "Jitterentropy Non-Deterministic Random Number Generator"
1869 The Jitterentropy RNG is a noise that is intended
1870 to provide seed to another RNG. The RNG does not
1871 perform any cryptographic whitening of the generated
1872 random numbers. This Jitterentropy RNG registers with
1873 the kernel crypto API and can be used by any caller.
1875 config CRYPTO_KDF800108_CTR
1878 select CRYPTO_SHA256
1880 config CRYPTO_USER_API
1883 config CRYPTO_USER_API_HASH
1884 tristate "User-space interface for hash algorithms"
1887 select CRYPTO_USER_API
1889 This option enables the user-spaces interface for hash
1892 config CRYPTO_USER_API_SKCIPHER
1893 tristate "User-space interface for symmetric key cipher algorithms"
1895 select CRYPTO_SKCIPHER
1896 select CRYPTO_USER_API
1898 This option enables the user-spaces interface for symmetric
1899 key cipher algorithms.
1901 config CRYPTO_USER_API_RNG
1902 tristate "User-space interface for random number generator algorithms"
1905 select CRYPTO_USER_API
1907 This option enables the user-spaces interface for random
1908 number generator algorithms.
1910 config CRYPTO_USER_API_RNG_CAVP
1911 bool "Enable CAVP testing of DRBG"
1912 depends on CRYPTO_USER_API_RNG && CRYPTO_DRBG
1914 This option enables extra API for CAVP testing via the user-space
1915 interface: resetting of DRBG entropy, and providing Additional Data.
1916 This should only be enabled for CAVP testing. You should say
1917 no unless you know what this is.
1919 config CRYPTO_USER_API_AEAD
1920 tristate "User-space interface for AEAD cipher algorithms"
1923 select CRYPTO_SKCIPHER
1925 select CRYPTO_USER_API
1927 This option enables the user-spaces interface for AEAD
1930 config CRYPTO_USER_API_ENABLE_OBSOLETE
1931 bool "Enable obsolete cryptographic algorithms for userspace"
1932 depends on CRYPTO_USER_API
1935 Allow obsolete cryptographic algorithms to be selected that have
1936 already been phased out from internal use by the kernel, and are
1937 only useful for userspace clients that still rely on them.
1940 bool "Crypto usage statistics for User-space"
1941 depends on CRYPTO_USER
1943 This option enables the gathering of crypto stats.
1945 - encrypt/decrypt size and numbers of symmeric operations
1946 - compress/decompress size and numbers of compress operations
1947 - size and numbers of hash operations
1948 - encrypt/decrypt/sign/verify numbers for asymmetric operations
1949 - generate/seed numbers for rng operations
1951 config CRYPTO_HASH_INFO
1954 source "drivers/crypto/Kconfig"
1955 source "crypto/asymmetric_keys/Kconfig"
1956 source "certs/Kconfig"