1 # SPDX-License-Identifier: GPL-2.0
3 # Generic algorithms support
9 # async_tx api: hardware offloaded memory transfer/transform support
11 source "crypto/async_tx/Kconfig"
14 # Cryptographic API Configuration
17 tristate "Cryptographic API"
19 This option provides the core Cryptographic API.
23 comment "Crypto core or helper"
26 bool "FIPS 200 compliance"
27 depends on (CRYPTO_ANSI_CPRNG || CRYPTO_DRBG) && !CRYPTO_MANAGER_DISABLE_TESTS
28 depends on (MODULE_SIG || !MODULES)
30 This option enables the fips boot option which is
31 required if you want the system to operate in a FIPS 200
32 certification. You should say no unless you know what
39 This option provides the API for cryptographic algorithms.
55 config CRYPTO_SKCIPHER
57 select CRYPTO_SKCIPHER2
60 config CRYPTO_SKCIPHER2
83 config CRYPTO_RNG_DEFAULT
85 select CRYPTO_DRBG_MENU
87 config CRYPTO_AKCIPHER2
91 config CRYPTO_AKCIPHER
93 select CRYPTO_AKCIPHER2
107 select CRYPTO_ALGAPI2
115 config CRYPTO_MANAGER
116 tristate "Cryptographic algorithm manager"
117 select CRYPTO_MANAGER2
119 Create default cryptographic template instantiations such as
122 config CRYPTO_MANAGER2
123 def_tristate CRYPTO_MANAGER || (CRYPTO_MANAGER!=n && CRYPTO_ALGAPI=y)
126 select CRYPTO_SKCIPHER2
127 select CRYPTO_AKCIPHER2
132 tristate "Userspace cryptographic algorithm configuration"
134 select CRYPTO_MANAGER
136 Userspace configuration for cryptographic instantiations such as
139 config CRYPTO_MANAGER_DISABLE_TESTS
140 bool "Disable run-time self tests"
143 Disable run-time self tests that normally take place at
144 algorithm registration.
146 config CRYPTO_MANAGER_EXTRA_TESTS
147 bool "Enable extra run-time crypto self tests"
148 depends on DEBUG_KERNEL && !CRYPTO_MANAGER_DISABLE_TESTS
150 Enable extra run-time self tests of registered crypto algorithms,
151 including randomized fuzz tests.
153 This is intended for developer use only, as these tests take much
154 longer to run than the normal self tests.
156 config CRYPTO_GF128MUL
160 tristate "Null algorithms"
163 These are 'Null' algorithms, used by IPsec, which do nothing.
167 select CRYPTO_ALGAPI2
168 select CRYPTO_SKCIPHER2
172 tristate "Parallel crypto engine"
175 select CRYPTO_MANAGER
178 This converts an arbitrary crypto algorithm into a parallel
179 algorithm that executes in kernel threads.
182 tristate "Software async crypto daemon"
183 select CRYPTO_SKCIPHER
185 select CRYPTO_MANAGER
187 This is a generic software asynchronous crypto daemon that
188 converts an arbitrary synchronous software crypto algorithm
189 into an asynchronous algorithm that executes in a kernel thread.
191 config CRYPTO_AUTHENC
192 tristate "Authenc support"
194 select CRYPTO_SKCIPHER
195 select CRYPTO_MANAGER
199 Authenc: Combined mode wrapper for IPsec.
200 This is required for IPSec.
203 tristate "Testing module"
205 select CRYPTO_MANAGER
207 Quick & dirty crypto test module.
213 config CRYPTO_GLUE_HELPER_X86
216 select CRYPTO_SKCIPHER
221 comment "Public-key cryptography"
224 tristate "RSA algorithm"
225 select CRYPTO_AKCIPHER
226 select CRYPTO_MANAGER
230 Generic implementation of the RSA public key algorithm.
233 tristate "Diffie-Hellman algorithm"
237 Generic implementation of the Diffie-Hellman algorithm.
243 tristate "ECDH algorithm"
246 select CRYPTO_RNG_DEFAULT
248 Generic implementation of the ECDH algorithm
251 tristate "EC-RDSA (GOST 34.10) algorithm"
253 select CRYPTO_AKCIPHER
254 select CRYPTO_STREEBOG
258 Elliptic Curve Russian Digital Signature Algorithm (GOST R 34.10-2012,
259 RFC 7091, ISO/IEC 14888-3:2018) is one of the Russian cryptographic
260 standard algorithms (called GOST algorithms). Only signature verification
263 config CRYPTO_CURVE25519
264 tristate "Curve25519 algorithm"
266 select CRYPTO_LIB_CURVE25519_GENERIC
268 config CRYPTO_CURVE25519_X86
269 tristate "x86_64 accelerated Curve25519 scalar multiplication library"
270 depends on X86 && 64BIT
271 select CRYPTO_LIB_CURVE25519_GENERIC
272 select CRYPTO_ARCH_HAVE_LIB_CURVE25519
274 comment "Authenticated Encryption with Associated Data"
277 tristate "CCM support"
281 select CRYPTO_MANAGER
283 Support for Counter with CBC MAC. Required for IPsec.
286 tristate "GCM/GMAC support"
291 select CRYPTO_MANAGER
293 Support for Galois/Counter Mode (GCM) and Galois Message
294 Authentication Code (GMAC). Required for IPSec.
296 config CRYPTO_CHACHA20POLY1305
297 tristate "ChaCha20-Poly1305 AEAD support"
298 select CRYPTO_CHACHA20
299 select CRYPTO_POLY1305
301 select CRYPTO_MANAGER
303 ChaCha20-Poly1305 AEAD support, RFC7539.
305 Support for the AEAD wrapper using the ChaCha20 stream cipher combined
306 with the Poly1305 authenticator. It is defined in RFC7539 for use in
309 config CRYPTO_AEGIS128
310 tristate "AEGIS-128 AEAD algorithm"
312 select CRYPTO_AES # for AES S-box tables
314 Support for the AEGIS-128 dedicated AEAD algorithm.
316 config CRYPTO_AEGIS128_SIMD
317 bool "Support SIMD acceleration for AEGIS-128"
318 depends on CRYPTO_AEGIS128 && ((ARM || ARM64) && KERNEL_MODE_NEON)
319 depends on !ARM || CC_IS_CLANG || GCC_VERSION >= 40800
322 config CRYPTO_AEGIS128_AESNI_SSE2
323 tristate "AEGIS-128 AEAD algorithm (x86_64 AESNI+SSE2 implementation)"
324 depends on X86 && 64BIT
328 AESNI+SSE2 implementation of the AEGIS-128 dedicated AEAD algorithm.
331 tristate "Sequence Number IV Generator"
333 select CRYPTO_SKCIPHER
335 select CRYPTO_RNG_DEFAULT
336 select CRYPTO_MANAGER
338 This IV generator generates an IV based on a sequence number by
339 xoring it with a salt. This algorithm is mainly useful for CTR
341 config CRYPTO_ECHAINIV
342 tristate "Encrypted Chain IV Generator"
345 select CRYPTO_RNG_DEFAULT
346 select CRYPTO_MANAGER
348 This IV generator generates an IV based on the encryption of
349 a sequence number xored with a salt. This is the default
352 comment "Block modes"
355 tristate "CBC support"
356 select CRYPTO_SKCIPHER
357 select CRYPTO_MANAGER
359 CBC: Cipher Block Chaining mode
360 This block cipher algorithm is required for IPSec.
363 tristate "CFB support"
364 select CRYPTO_SKCIPHER
365 select CRYPTO_MANAGER
367 CFB: Cipher FeedBack mode
368 This block cipher algorithm is required for TPM2 Cryptography.
371 tristate "CTR support"
372 select CRYPTO_SKCIPHER
373 select CRYPTO_MANAGER
376 This block cipher algorithm is required for IPSec.
379 tristate "CTS support"
380 select CRYPTO_SKCIPHER
381 select CRYPTO_MANAGER
383 CTS: Cipher Text Stealing
384 This is the Cipher Text Stealing mode as described by
385 Section 8 of rfc2040 and referenced by rfc3962
386 (rfc3962 includes errata information in its Appendix A) or
387 CBC-CS3 as defined by NIST in Sp800-38A addendum from Oct 2010.
388 This mode is required for Kerberos gss mechanism support
391 See: https://csrc.nist.gov/publications/detail/sp/800-38a/addendum/final
394 tristate "ECB support"
395 select CRYPTO_SKCIPHER
396 select CRYPTO_MANAGER
398 ECB: Electronic CodeBook mode
399 This is the simplest block cipher algorithm. It simply encrypts
400 the input block by block.
403 tristate "LRW support"
404 select CRYPTO_SKCIPHER
405 select CRYPTO_MANAGER
406 select CRYPTO_GF128MUL
408 LRW: Liskov Rivest Wagner, a tweakable, non malleable, non movable
409 narrow block cipher mode for dm-crypt. Use it with cipher
410 specification string aes-lrw-benbi, the key must be 256, 320 or 384.
411 The first 128, 192 or 256 bits in the key are used for AES and the
412 rest is used to tie each cipher block to its logical position.
415 tristate "OFB support"
416 select CRYPTO_SKCIPHER
417 select CRYPTO_MANAGER
419 OFB: the Output Feedback mode makes a block cipher into a synchronous
420 stream cipher. It generates keystream blocks, which are then XORed
421 with the plaintext blocks to get the ciphertext. Flipping a bit in the
422 ciphertext produces a flipped bit in the plaintext at the same
423 location. This property allows many error correcting codes to function
424 normally even when applied before encryption.
427 tristate "PCBC support"
428 select CRYPTO_SKCIPHER
429 select CRYPTO_MANAGER
431 PCBC: Propagating Cipher Block Chaining mode
432 This block cipher algorithm is required for RxRPC.
435 tristate "XTS support"
436 select CRYPTO_SKCIPHER
437 select CRYPTO_MANAGER
440 XTS: IEEE1619/D16 narrow block cipher use with aes-xts-plain,
441 key size 256, 384 or 512 bits. This implementation currently
442 can't handle a sectorsize which is not a multiple of 16 bytes.
444 config CRYPTO_KEYWRAP
445 tristate "Key wrapping support"
446 select CRYPTO_SKCIPHER
447 select CRYPTO_MANAGER
449 Support for key wrapping (NIST SP800-38F / RFC3394) without
452 config CRYPTO_NHPOLY1305
455 select CRYPTO_LIB_POLY1305_GENERIC
457 config CRYPTO_NHPOLY1305_SSE2
458 tristate "NHPoly1305 hash function (x86_64 SSE2 implementation)"
459 depends on X86 && 64BIT
460 select CRYPTO_NHPOLY1305
462 SSE2 optimized implementation of the hash function used by the
463 Adiantum encryption mode.
465 config CRYPTO_NHPOLY1305_AVX2
466 tristate "NHPoly1305 hash function (x86_64 AVX2 implementation)"
467 depends on X86 && 64BIT
468 select CRYPTO_NHPOLY1305
470 AVX2 optimized implementation of the hash function used by the
471 Adiantum encryption mode.
473 config CRYPTO_ADIANTUM
474 tristate "Adiantum support"
475 select CRYPTO_CHACHA20
476 select CRYPTO_LIB_POLY1305_GENERIC
477 select CRYPTO_NHPOLY1305
478 select CRYPTO_MANAGER
480 Adiantum is a tweakable, length-preserving encryption mode
481 designed for fast and secure disk encryption, especially on
482 CPUs without dedicated crypto instructions. It encrypts
483 each sector using the XChaCha12 stream cipher, two passes of
484 an ε-almost-∆-universal hash function, and an invocation of
485 the AES-256 block cipher on a single 16-byte block. On CPUs
486 without AES instructions, Adiantum is much faster than
489 Adiantum's security is provably reducible to that of its
490 underlying stream and block ciphers, subject to a security
491 bound. Unlike XTS, Adiantum is a true wide-block encryption
492 mode, so it actually provides an even stronger notion of
493 security than XTS, subject to the security bound.
498 tristate "ESSIV support for block encryption"
499 select CRYPTO_AUTHENC
501 Encrypted salt-sector initialization vector (ESSIV) is an IV
502 generation method that is used in some cases by fscrypt and/or
503 dm-crypt. It uses the hash of the block encryption key as the
504 symmetric key for a block encryption pass applied to the input
505 IV, making low entropy IV sources more suitable for block
508 This driver implements a crypto API template that can be
509 instantiated either as an skcipher or as an AEAD (depending on the
510 type of the first template argument), and which defers encryption
511 and decryption requests to the encapsulated cipher after applying
512 ESSIV to the input IV. Note that in the AEAD case, it is assumed
513 that the keys are presented in the same format used by the authenc
514 template, and that the IV appears at the end of the authenticated
515 associated data (AAD) region (which is how dm-crypt uses it.)
517 Note that the use of ESSIV is not recommended for new deployments,
518 and so this only needs to be enabled when interoperability with
519 existing encrypted volumes of filesystems is required, or when
520 building for a particular system that requires it (e.g., when
521 the SoC in question has accelerated CBC but not XTS, making CBC
522 combined with ESSIV the only feasible mode for h/w accelerated
528 tristate "CMAC support"
530 select CRYPTO_MANAGER
532 Cipher-based Message Authentication Code (CMAC) specified by
533 The National Institute of Standards and Technology (NIST).
535 https://tools.ietf.org/html/rfc4493
536 http://csrc.nist.gov/publications/nistpubs/800-38B/SP_800-38B.pdf
539 tristate "HMAC support"
541 select CRYPTO_MANAGER
543 HMAC: Keyed-Hashing for Message Authentication (RFC2104).
544 This is required for IPSec.
547 tristate "XCBC support"
549 select CRYPTO_MANAGER
551 XCBC: Keyed-Hashing with encryption algorithm
552 http://www.ietf.org/rfc/rfc3566.txt
553 http://csrc.nist.gov/encryption/modes/proposedmodes/
554 xcbc-mac/xcbc-mac-spec.pdf
557 tristate "VMAC support"
559 select CRYPTO_MANAGER
561 VMAC is a message authentication algorithm designed for
562 very high speed on 64-bit architectures.
565 <http://fastcrypto.org/vmac>
570 tristate "CRC32c CRC algorithm"
574 Castagnoli, et al Cyclic Redundancy-Check Algorithm. Used
575 by iSCSI for header and data digests and by others.
576 See Castagnoli93. Module will be crc32c.
578 config CRYPTO_CRC32C_INTEL
579 tristate "CRC32c INTEL hardware acceleration"
583 In Intel processor with SSE4.2 supported, the processor will
584 support CRC32C implementation using hardware accelerated CRC32
585 instruction. This option will create 'crc32c-intel' module,
586 which will enable any routine to use the CRC32 instruction to
587 gain performance compared with software implementation.
588 Module will be crc32c-intel.
590 config CRYPTO_CRC32C_VPMSUM
591 tristate "CRC32c CRC algorithm (powerpc64)"
592 depends on PPC64 && ALTIVEC
596 CRC32c algorithm implemented using vector polynomial multiply-sum
597 (vpmsum) instructions, introduced in POWER8. Enable on POWER8
598 and newer processors for improved performance.
601 config CRYPTO_CRC32C_SPARC64
602 tristate "CRC32c CRC algorithm (SPARC64)"
607 CRC32c CRC algorithm implemented using sparc64 crypto instructions,
611 tristate "CRC32 CRC algorithm"
615 CRC-32-IEEE 802.3 cyclic redundancy-check algorithm.
616 Shash crypto api wrappers to crc32_le function.
618 config CRYPTO_CRC32_PCLMUL
619 tristate "CRC32 PCLMULQDQ hardware acceleration"
624 From Intel Westmere and AMD Bulldozer processor with SSE4.2
625 and PCLMULQDQ supported, the processor will support
626 CRC32 PCLMULQDQ implementation using hardware accelerated PCLMULQDQ
627 instruction. This option will create 'crc32-pclmul' module,
628 which will enable any routine to use the CRC-32-IEEE 802.3 checksum
629 and gain better performance as compared with the table implementation.
631 config CRYPTO_CRC32_MIPS
632 tristate "CRC32c and CRC32 CRC algorithm (MIPS)"
633 depends on MIPS_CRC_SUPPORT
636 CRC32c and CRC32 CRC algorithms implemented using mips crypto
637 instructions, when available.
641 tristate "xxHash hash algorithm"
645 xxHash non-cryptographic hash algorithm. Extremely fast, working at
646 speeds close to RAM limits.
648 config CRYPTO_BLAKE2B
649 tristate "BLAKE2b digest algorithm"
652 Implementation of cryptographic hash function BLAKE2b (or just BLAKE2),
653 optimized for 64bit platforms and can produce digests of any size
654 between 1 to 64. The keyed hash is also implemented.
656 This module provides the following algorithms:
663 See https://blake2.net for further information.
665 config CRYPTO_BLAKE2S
666 tristate "BLAKE2s digest algorithm"
667 select CRYPTO_LIB_BLAKE2S_GENERIC
670 Implementation of cryptographic hash function BLAKE2s
671 optimized for 8-32bit platforms and can produce digests of any size
672 between 1 to 32. The keyed hash is also implemented.
674 This module provides the following algorithms:
681 See https://blake2.net for further information.
683 config CRYPTO_BLAKE2S_X86
684 tristate "BLAKE2s digest algorithm (x86 accelerated version)"
685 depends on X86 && 64BIT
686 select CRYPTO_LIB_BLAKE2S_GENERIC
687 select CRYPTO_ARCH_HAVE_LIB_BLAKE2S
689 config CRYPTO_CRCT10DIF
690 tristate "CRCT10DIF algorithm"
693 CRC T10 Data Integrity Field computation is being cast as
694 a crypto transform. This allows for faster crc t10 diff
695 transforms to be used if they are available.
697 config CRYPTO_CRCT10DIF_PCLMUL
698 tristate "CRCT10DIF PCLMULQDQ hardware acceleration"
699 depends on X86 && 64BIT && CRC_T10DIF
702 For x86_64 processors with SSE4.2 and PCLMULQDQ supported,
703 CRC T10 DIF PCLMULQDQ computation can be hardware
704 accelerated PCLMULQDQ instruction. This option will create
705 'crct10dif-pclmul' module, which is faster when computing the
706 crct10dif checksum as compared with the generic table implementation.
708 config CRYPTO_CRCT10DIF_VPMSUM
709 tristate "CRC32T10DIF powerpc64 hardware acceleration"
710 depends on PPC64 && ALTIVEC && CRC_T10DIF
713 CRC10T10DIF algorithm implemented using vector polynomial
714 multiply-sum (vpmsum) instructions, introduced in POWER8. Enable on
715 POWER8 and newer processors for improved performance.
717 config CRYPTO_VPMSUM_TESTER
718 tristate "Powerpc64 vpmsum hardware acceleration tester"
719 depends on CRYPTO_CRCT10DIF_VPMSUM && CRYPTO_CRC32C_VPMSUM
721 Stress test for CRC32c and CRC-T10DIF algorithms implemented with
722 POWER8 vpmsum instructions.
723 Unless you are testing these algorithms, you don't need this.
726 tristate "GHASH hash function"
727 select CRYPTO_GF128MUL
730 GHASH is the hash function used in GCM (Galois/Counter Mode).
731 It is not a general-purpose cryptographic hash function.
733 config CRYPTO_POLY1305
734 tristate "Poly1305 authenticator algorithm"
736 select CRYPTO_LIB_POLY1305_GENERIC
738 Poly1305 authenticator algorithm, RFC7539.
740 Poly1305 is an authenticator algorithm designed by Daniel J. Bernstein.
741 It is used for the ChaCha20-Poly1305 AEAD, specified in RFC7539 for use
742 in IETF protocols. This is the portable C implementation of Poly1305.
744 config CRYPTO_POLY1305_X86_64
745 tristate "Poly1305 authenticator algorithm (x86_64/SSE2/AVX2)"
746 depends on X86 && 64BIT
747 select CRYPTO_LIB_POLY1305_GENERIC
748 select CRYPTO_ARCH_HAVE_LIB_POLY1305
750 Poly1305 authenticator algorithm, RFC7539.
752 Poly1305 is an authenticator algorithm designed by Daniel J. Bernstein.
753 It is used for the ChaCha20-Poly1305 AEAD, specified in RFC7539 for use
754 in IETF protocols. This is the x86_64 assembler implementation using SIMD
757 config CRYPTO_POLY1305_MIPS
758 tristate "Poly1305 authenticator algorithm (MIPS optimized)"
759 depends on CPU_MIPS32 || (CPU_MIPS64 && 64BIT)
760 select CRYPTO_ARCH_HAVE_LIB_POLY1305
763 tristate "MD4 digest algorithm"
766 MD4 message digest algorithm (RFC1320).
769 tristate "MD5 digest algorithm"
772 MD5 message digest algorithm (RFC1321).
774 config CRYPTO_MD5_OCTEON
775 tristate "MD5 digest algorithm (OCTEON)"
776 depends on CPU_CAVIUM_OCTEON
780 MD5 message digest algorithm (RFC1321) implemented
781 using OCTEON crypto instructions, when available.
783 config CRYPTO_MD5_PPC
784 tristate "MD5 digest algorithm (PPC)"
788 MD5 message digest algorithm (RFC1321) implemented
791 config CRYPTO_MD5_SPARC64
792 tristate "MD5 digest algorithm (SPARC64)"
797 MD5 message digest algorithm (RFC1321) implemented
798 using sparc64 crypto instructions, when available.
800 config CRYPTO_MICHAEL_MIC
801 tristate "Michael MIC keyed digest algorithm"
804 Michael MIC is used for message integrity protection in TKIP
805 (IEEE 802.11i). This algorithm is required for TKIP, but it
806 should not be used for other purposes because of the weakness
810 tristate "RIPEMD-128 digest algorithm"
813 RIPEMD-128 (ISO/IEC 10118-3:2004).
815 RIPEMD-128 is a 128-bit cryptographic hash function. It should only
816 be used as a secure replacement for RIPEMD. For other use cases,
817 RIPEMD-160 should be used.
819 Developed by Hans Dobbertin, Antoon Bosselaers and Bart Preneel.
820 See <http://homes.esat.kuleuven.be/~bosselae/ripemd160.html>
823 tristate "RIPEMD-160 digest algorithm"
826 RIPEMD-160 (ISO/IEC 10118-3:2004).
828 RIPEMD-160 is a 160-bit cryptographic hash function. It is intended
829 to be used as a secure replacement for the 128-bit hash functions
830 MD4, MD5 and it's predecessor RIPEMD
831 (not to be confused with RIPEMD-128).
833 It's speed is comparable to SHA1 and there are no known attacks
836 Developed by Hans Dobbertin, Antoon Bosselaers and Bart Preneel.
837 See <http://homes.esat.kuleuven.be/~bosselae/ripemd160.html>
840 tristate "RIPEMD-256 digest algorithm"
843 RIPEMD-256 is an optional extension of RIPEMD-128 with a
844 256 bit hash. It is intended for applications that require
845 longer hash-results, without needing a larger security level
848 Developed by Hans Dobbertin, Antoon Bosselaers and Bart Preneel.
849 See <http://homes.esat.kuleuven.be/~bosselae/ripemd160.html>
852 tristate "RIPEMD-320 digest algorithm"
855 RIPEMD-320 is an optional extension of RIPEMD-160 with a
856 320 bit hash. It is intended for applications that require
857 longer hash-results, without needing a larger security level
860 Developed by Hans Dobbertin, Antoon Bosselaers and Bart Preneel.
861 See <http://homes.esat.kuleuven.be/~bosselae/ripemd160.html>
864 tristate "SHA1 digest algorithm"
867 SHA-1 secure hash standard (FIPS 180-1/DFIPS 180-2).
869 config CRYPTO_SHA1_SSSE3
870 tristate "SHA1 digest algorithm (SSSE3/AVX/AVX2/SHA-NI)"
871 depends on X86 && 64BIT
875 SHA-1 secure hash standard (FIPS 180-1/DFIPS 180-2) implemented
876 using Supplemental SSE3 (SSSE3) instructions or Advanced Vector
877 Extensions (AVX/AVX2) or SHA-NI(SHA Extensions New Instructions),
880 config CRYPTO_SHA256_SSSE3
881 tristate "SHA256 digest algorithm (SSSE3/AVX/AVX2/SHA-NI)"
882 depends on X86 && 64BIT
886 SHA-256 secure hash standard (DFIPS 180-2) implemented
887 using Supplemental SSE3 (SSSE3) instructions, or Advanced Vector
888 Extensions version 1 (AVX1), or Advanced Vector Extensions
889 version 2 (AVX2) instructions, or SHA-NI (SHA Extensions New
890 Instructions) when available.
892 config CRYPTO_SHA512_SSSE3
893 tristate "SHA512 digest algorithm (SSSE3/AVX/AVX2)"
894 depends on X86 && 64BIT
898 SHA-512 secure hash standard (DFIPS 180-2) implemented
899 using Supplemental SSE3 (SSSE3) instructions, or Advanced Vector
900 Extensions version 1 (AVX1), or Advanced Vector Extensions
901 version 2 (AVX2) instructions, when available.
903 config CRYPTO_SHA1_OCTEON
904 tristate "SHA1 digest algorithm (OCTEON)"
905 depends on CPU_CAVIUM_OCTEON
909 SHA-1 secure hash standard (FIPS 180-1/DFIPS 180-2) implemented
910 using OCTEON crypto instructions, when available.
912 config CRYPTO_SHA1_SPARC64
913 tristate "SHA1 digest algorithm (SPARC64)"
918 SHA-1 secure hash standard (FIPS 180-1/DFIPS 180-2) implemented
919 using sparc64 crypto instructions, when available.
921 config CRYPTO_SHA1_PPC
922 tristate "SHA1 digest algorithm (powerpc)"
925 This is the powerpc hardware accelerated implementation of the
926 SHA-1 secure hash standard (FIPS 180-1/DFIPS 180-2).
928 config CRYPTO_SHA1_PPC_SPE
929 tristate "SHA1 digest algorithm (PPC SPE)"
930 depends on PPC && SPE
932 SHA-1 secure hash standard (DFIPS 180-4) implemented
933 using powerpc SPE SIMD instruction set.
936 tristate "SHA224 and SHA256 digest algorithm"
938 select CRYPTO_LIB_SHA256
940 SHA256 secure hash standard (DFIPS 180-2).
942 This version of SHA implements a 256 bit hash with 128 bits of
943 security against collision attacks.
945 This code also includes SHA-224, a 224 bit hash with 112 bits
946 of security against collision attacks.
948 config CRYPTO_SHA256_PPC_SPE
949 tristate "SHA224 and SHA256 digest algorithm (PPC SPE)"
950 depends on PPC && SPE
954 SHA224 and SHA256 secure hash standard (DFIPS 180-2)
955 implemented using powerpc SPE SIMD instruction set.
957 config CRYPTO_SHA256_OCTEON
958 tristate "SHA224 and SHA256 digest algorithm (OCTEON)"
959 depends on CPU_CAVIUM_OCTEON
963 SHA-256 secure hash standard (DFIPS 180-2) implemented
964 using OCTEON crypto instructions, when available.
966 config CRYPTO_SHA256_SPARC64
967 tristate "SHA224 and SHA256 digest algorithm (SPARC64)"
972 SHA-256 secure hash standard (DFIPS 180-2) implemented
973 using sparc64 crypto instructions, when available.
976 tristate "SHA384 and SHA512 digest algorithms"
979 SHA512 secure hash standard (DFIPS 180-2).
981 This version of SHA implements a 512 bit hash with 256 bits of
982 security against collision attacks.
984 This code also includes SHA-384, a 384 bit hash with 192 bits
985 of security against collision attacks.
987 config CRYPTO_SHA512_OCTEON
988 tristate "SHA384 and SHA512 digest algorithms (OCTEON)"
989 depends on CPU_CAVIUM_OCTEON
993 SHA-512 secure hash standard (DFIPS 180-2) implemented
994 using OCTEON crypto instructions, when available.
996 config CRYPTO_SHA512_SPARC64
997 tristate "SHA384 and SHA512 digest algorithm (SPARC64)"
1002 SHA-512 secure hash standard (DFIPS 180-2) implemented
1003 using sparc64 crypto instructions, when available.
1006 tristate "SHA3 digest algorithm"
1009 SHA-3 secure hash standard (DFIPS 202). It's based on
1010 cryptographic sponge function family called Keccak.
1013 http://keccak.noekeon.org/
1016 tristate "SM3 digest algorithm"
1019 SM3 secure hash function as defined by OSCCA GM/T 0004-2012 SM3).
1020 It is part of the Chinese Commercial Cryptography suite.
1023 http://www.oscca.gov.cn/UpFile/20101222141857786.pdf
1024 https://datatracker.ietf.org/doc/html/draft-shen-sm3-hash
1026 config CRYPTO_STREEBOG
1027 tristate "Streebog Hash Function"
1030 Streebog Hash Function (GOST R 34.11-2012, RFC 6986) is one of the Russian
1031 cryptographic standard algorithms (called GOST algorithms).
1032 This setting enables two hash algorithms with 256 and 512 bits output.
1035 https://tc26.ru/upload/iblock/fed/feddbb4d26b685903faa2ba11aea43f6.pdf
1036 https://tools.ietf.org/html/rfc6986
1038 config CRYPTO_TGR192
1039 tristate "Tiger digest algorithms"
1042 Tiger hash algorithm 192, 160 and 128-bit hashes
1044 Tiger is a hash function optimized for 64-bit processors while
1045 still having decent performance on 32-bit processors.
1046 Tiger was developed by Ross Anderson and Eli Biham.
1049 <http://www.cs.technion.ac.il/~biham/Reports/Tiger/>.
1052 tristate "Whirlpool digest algorithms"
1055 Whirlpool hash algorithm 512, 384 and 256-bit hashes
1057 Whirlpool-512 is part of the NESSIE cryptographic primitives.
1058 Whirlpool will be part of the ISO/IEC 10118-3:2003(E) standard
1061 <http://www.larc.usp.br/~pbarreto/WhirlpoolPage.html>
1063 config CRYPTO_GHASH_CLMUL_NI_INTEL
1064 tristate "GHASH hash function (CLMUL-NI accelerated)"
1065 depends on X86 && 64BIT
1066 select CRYPTO_CRYPTD
1068 This is the x86_64 CLMUL-NI accelerated implementation of
1069 GHASH, the hash function used in GCM (Galois/Counter mode).
1074 tristate "AES cipher algorithms"
1075 select CRYPTO_ALGAPI
1076 select CRYPTO_LIB_AES
1078 AES cipher algorithms (FIPS-197). AES uses the Rijndael
1081 Rijndael appears to be consistently a very good performer in
1082 both hardware and software across a wide range of computing
1083 environments regardless of its use in feedback or non-feedback
1084 modes. Its key setup time is excellent, and its key agility is
1085 good. Rijndael's very low memory requirements make it very well
1086 suited for restricted-space environments, in which it also
1087 demonstrates excellent performance. Rijndael's operations are
1088 among the easiest to defend against power and timing attacks.
1090 The AES specifies three key sizes: 128, 192 and 256 bits
1092 See <http://csrc.nist.gov/CryptoToolkit/aes/> for more information.
1094 config CRYPTO_AES_TI
1095 tristate "Fixed time AES cipher"
1096 select CRYPTO_ALGAPI
1097 select CRYPTO_LIB_AES
1099 This is a generic implementation of AES that attempts to eliminate
1100 data dependent latencies as much as possible without affecting
1101 performance too much. It is intended for use by the generic CCM
1102 and GCM drivers, and other CTR or CMAC/XCBC based modes that rely
1103 solely on encryption (although decryption is supported as well, but
1104 with a more dramatic performance hit)
1106 Instead of using 16 lookup tables of 1 KB each, (8 for encryption and
1107 8 for decryption), this implementation only uses just two S-boxes of
1108 256 bytes each, and attempts to eliminate data dependent latencies by
1109 prefetching the entire table into the cache at the start of each
1110 block. Interrupts are also disabled to avoid races where cachelines
1111 are evicted when the CPU is interrupted to do something else.
1113 config CRYPTO_AES_NI_INTEL
1114 tristate "AES cipher algorithms (AES-NI)"
1117 select CRYPTO_LIB_AES
1118 select CRYPTO_ALGAPI
1119 select CRYPTO_SKCIPHER
1120 select CRYPTO_GLUE_HELPER_X86 if 64BIT
1123 Use Intel AES-NI instructions for AES algorithm.
1125 AES cipher algorithms (FIPS-197). AES uses the Rijndael
1128 Rijndael appears to be consistently a very good performer in
1129 both hardware and software across a wide range of computing
1130 environments regardless of its use in feedback or non-feedback
1131 modes. Its key setup time is excellent, and its key agility is
1132 good. Rijndael's very low memory requirements make it very well
1133 suited for restricted-space environments, in which it also
1134 demonstrates excellent performance. Rijndael's operations are
1135 among the easiest to defend against power and timing attacks.
1137 The AES specifies three key sizes: 128, 192 and 256 bits
1139 See <http://csrc.nist.gov/encryption/aes/> for more information.
1141 In addition to AES cipher algorithm support, the acceleration
1142 for some popular block cipher mode is supported too, including
1143 ECB, CBC, LRW, XTS. The 64 bit version has additional
1144 acceleration for CTR.
1146 config CRYPTO_AES_SPARC64
1147 tristate "AES cipher algorithms (SPARC64)"
1149 select CRYPTO_SKCIPHER
1151 Use SPARC64 crypto opcodes for AES algorithm.
1153 AES cipher algorithms (FIPS-197). AES uses the Rijndael
1156 Rijndael appears to be consistently a very good performer in
1157 both hardware and software across a wide range of computing
1158 environments regardless of its use in feedback or non-feedback
1159 modes. Its key setup time is excellent, and its key agility is
1160 good. Rijndael's very low memory requirements make it very well
1161 suited for restricted-space environments, in which it also
1162 demonstrates excellent performance. Rijndael's operations are
1163 among the easiest to defend against power and timing attacks.
1165 The AES specifies three key sizes: 128, 192 and 256 bits
1167 See <http://csrc.nist.gov/encryption/aes/> for more information.
1169 In addition to AES cipher algorithm support, the acceleration
1170 for some popular block cipher mode is supported too, including
1173 config CRYPTO_AES_PPC_SPE
1174 tristate "AES cipher algorithms (PPC SPE)"
1175 depends on PPC && SPE
1176 select CRYPTO_SKCIPHER
1178 AES cipher algorithms (FIPS-197). Additionally the acceleration
1179 for popular block cipher modes ECB, CBC, CTR and XTS is supported.
1180 This module should only be used for low power (router) devices
1181 without hardware AES acceleration (e.g. caam crypto). It reduces the
1182 size of the AES tables from 16KB to 8KB + 256 bytes and mitigates
1183 timining attacks. Nevertheless it might be not as secure as other
1184 architecture specific assembler implementations that work on 1KB
1185 tables or 256 bytes S-boxes.
1187 config CRYPTO_ANUBIS
1188 tristate "Anubis cipher algorithm"
1189 select CRYPTO_ALGAPI
1191 Anubis cipher algorithm.
1193 Anubis is a variable key length cipher which can use keys from
1194 128 bits to 320 bits in length. It was evaluated as a entrant
1195 in the NESSIE competition.
1198 <https://www.cosic.esat.kuleuven.be/nessie/reports/>
1199 <http://www.larc.usp.br/~pbarreto/AnubisPage.html>
1202 tristate "ARC4 cipher algorithm"
1203 select CRYPTO_SKCIPHER
1204 select CRYPTO_LIB_ARC4
1206 ARC4 cipher algorithm.
1208 ARC4 is a stream cipher using keys ranging from 8 bits to 2048
1209 bits in length. This algorithm is required for driver-based
1210 WEP, but it should not be for other purposes because of the
1211 weakness of the algorithm.
1213 config CRYPTO_BLOWFISH
1214 tristate "Blowfish cipher algorithm"
1215 select CRYPTO_ALGAPI
1216 select CRYPTO_BLOWFISH_COMMON
1218 Blowfish cipher algorithm, by Bruce Schneier.
1220 This is a variable key length cipher which can use keys from 32
1221 bits to 448 bits in length. It's fast, simple and specifically
1222 designed for use on "large microprocessors".
1225 <http://www.schneier.com/blowfish.html>
1227 config CRYPTO_BLOWFISH_COMMON
1230 Common parts of the Blowfish cipher algorithm shared by the
1231 generic c and the assembler implementations.
1234 <http://www.schneier.com/blowfish.html>
1236 config CRYPTO_BLOWFISH_X86_64
1237 tristate "Blowfish cipher algorithm (x86_64)"
1238 depends on X86 && 64BIT
1239 select CRYPTO_SKCIPHER
1240 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 <http://www.schneier.com/blowfish.html>
1251 config CRYPTO_CAMELLIA
1252 tristate "Camellia cipher algorithms"
1254 select CRYPTO_ALGAPI
1256 Camellia cipher algorithms module.
1258 Camellia is a symmetric key block cipher developed jointly
1259 at NTT and Mitsubishi Electric Corporation.
1261 The Camellia specifies three key sizes: 128, 192 and 256 bits.
1264 <https://info.isl.ntt.co.jp/crypt/eng/camellia/index_s.html>
1266 config CRYPTO_CAMELLIA_X86_64
1267 tristate "Camellia cipher algorithm (x86_64)"
1268 depends on X86 && 64BIT
1270 select CRYPTO_SKCIPHER
1271 select CRYPTO_GLUE_HELPER_X86
1273 Camellia cipher algorithm module (x86_64).
1275 Camellia is a symmetric key block cipher developed jointly
1276 at NTT and Mitsubishi Electric Corporation.
1278 The Camellia specifies three key sizes: 128, 192 and 256 bits.
1281 <https://info.isl.ntt.co.jp/crypt/eng/camellia/index_s.html>
1283 config CRYPTO_CAMELLIA_AESNI_AVX_X86_64
1284 tristate "Camellia cipher algorithm (x86_64/AES-NI/AVX)"
1285 depends on X86 && 64BIT
1287 select CRYPTO_SKCIPHER
1288 select CRYPTO_CAMELLIA_X86_64
1289 select CRYPTO_GLUE_HELPER_X86
1293 Camellia cipher algorithm module (x86_64/AES-NI/AVX).
1295 Camellia is a symmetric key block cipher developed jointly
1296 at NTT and Mitsubishi Electric Corporation.
1298 The Camellia specifies three key sizes: 128, 192 and 256 bits.
1301 <https://info.isl.ntt.co.jp/crypt/eng/camellia/index_s.html>
1303 config CRYPTO_CAMELLIA_AESNI_AVX2_X86_64
1304 tristate "Camellia cipher algorithm (x86_64/AES-NI/AVX2)"
1305 depends on X86 && 64BIT
1307 select CRYPTO_CAMELLIA_AESNI_AVX_X86_64
1309 Camellia cipher algorithm module (x86_64/AES-NI/AVX2).
1311 Camellia is a symmetric key block cipher developed jointly
1312 at NTT and Mitsubishi Electric Corporation.
1314 The Camellia specifies three key sizes: 128, 192 and 256 bits.
1317 <https://info.isl.ntt.co.jp/crypt/eng/camellia/index_s.html>
1319 config CRYPTO_CAMELLIA_SPARC64
1320 tristate "Camellia cipher algorithm (SPARC64)"
1323 select CRYPTO_ALGAPI
1324 select CRYPTO_SKCIPHER
1326 Camellia cipher algorithm module (SPARC64).
1328 Camellia is a symmetric key block cipher developed jointly
1329 at NTT and Mitsubishi Electric Corporation.
1331 The Camellia specifies three key sizes: 128, 192 and 256 bits.
1334 <https://info.isl.ntt.co.jp/crypt/eng/camellia/index_s.html>
1336 config CRYPTO_CAST_COMMON
1339 Common parts of the CAST cipher algorithms shared by the
1340 generic c and the assembler implementations.
1343 tristate "CAST5 (CAST-128) cipher algorithm"
1344 select CRYPTO_ALGAPI
1345 select CRYPTO_CAST_COMMON
1347 The CAST5 encryption algorithm (synonymous with CAST-128) is
1348 described in RFC2144.
1350 config CRYPTO_CAST5_AVX_X86_64
1351 tristate "CAST5 (CAST-128) cipher algorithm (x86_64/AVX)"
1352 depends on X86 && 64BIT
1353 select CRYPTO_SKCIPHER
1355 select CRYPTO_CAST_COMMON
1358 The CAST5 encryption algorithm (synonymous with CAST-128) is
1359 described in RFC2144.
1361 This module provides the Cast5 cipher algorithm that processes
1362 sixteen blocks parallel using the AVX instruction set.
1365 tristate "CAST6 (CAST-256) cipher algorithm"
1366 select CRYPTO_ALGAPI
1367 select CRYPTO_CAST_COMMON
1369 The CAST6 encryption algorithm (synonymous with CAST-256) is
1370 described in RFC2612.
1372 config CRYPTO_CAST6_AVX_X86_64
1373 tristate "CAST6 (CAST-256) cipher algorithm (x86_64/AVX)"
1374 depends on X86 && 64BIT
1375 select CRYPTO_SKCIPHER
1377 select CRYPTO_CAST_COMMON
1378 select CRYPTO_GLUE_HELPER_X86
1382 The CAST6 encryption algorithm (synonymous with CAST-256) is
1383 described in RFC2612.
1385 This module provides the Cast6 cipher algorithm that processes
1386 eight blocks parallel using the AVX instruction set.
1389 tristate "DES and Triple DES EDE cipher algorithms"
1390 select CRYPTO_ALGAPI
1391 select CRYPTO_LIB_DES
1393 DES cipher algorithm (FIPS 46-2), and Triple DES EDE (FIPS 46-3).
1395 config CRYPTO_DES_SPARC64
1396 tristate "DES and Triple DES EDE cipher algorithms (SPARC64)"
1398 select CRYPTO_ALGAPI
1399 select CRYPTO_LIB_DES
1400 select CRYPTO_SKCIPHER
1402 DES cipher algorithm (FIPS 46-2), and Triple DES EDE (FIPS 46-3),
1403 optimized using SPARC64 crypto opcodes.
1405 config CRYPTO_DES3_EDE_X86_64
1406 tristate "Triple DES EDE cipher algorithm (x86-64)"
1407 depends on X86 && 64BIT
1408 select CRYPTO_SKCIPHER
1409 select CRYPTO_LIB_DES
1411 Triple DES EDE (FIPS 46-3) algorithm.
1413 This module provides implementation of the Triple DES EDE cipher
1414 algorithm that is optimized for x86-64 processors. Two versions of
1415 algorithm are provided; regular processing one input block and
1416 one that processes three blocks parallel.
1418 config CRYPTO_FCRYPT
1419 tristate "FCrypt cipher algorithm"
1420 select CRYPTO_ALGAPI
1421 select CRYPTO_SKCIPHER
1423 FCrypt algorithm used by RxRPC.
1425 config CRYPTO_KHAZAD
1426 tristate "Khazad cipher algorithm"
1427 select CRYPTO_ALGAPI
1429 Khazad cipher algorithm.
1431 Khazad was a finalist in the initial NESSIE competition. It is
1432 an algorithm optimized for 64-bit processors with good performance
1433 on 32-bit processors. Khazad uses an 128 bit key size.
1436 <http://www.larc.usp.br/~pbarreto/KhazadPage.html>
1438 config CRYPTO_SALSA20
1439 tristate "Salsa20 stream cipher algorithm"
1440 select CRYPTO_SKCIPHER
1442 Salsa20 stream cipher algorithm.
1444 Salsa20 is a stream cipher submitted to eSTREAM, the ECRYPT
1445 Stream Cipher Project. See <http://www.ecrypt.eu.org/stream/>
1447 The Salsa20 stream cipher algorithm is designed by Daniel J.
1450 config CRYPTO_CHACHA20
1451 tristate "ChaCha stream cipher algorithms"
1452 select CRYPTO_LIB_CHACHA_GENERIC
1453 select CRYPTO_SKCIPHER
1455 The ChaCha20, XChaCha20, and XChaCha12 stream cipher algorithms.
1457 ChaCha20 is a 256-bit high-speed stream cipher designed by Daniel J.
1458 Bernstein and further specified in RFC7539 for use in IETF protocols.
1459 This is the portable C implementation of ChaCha20. See also:
1460 <http://cr.yp.to/chacha/chacha-20080128.pdf>
1462 XChaCha20 is the application of the XSalsa20 construction to ChaCha20
1463 rather than to Salsa20. XChaCha20 extends ChaCha20's nonce length
1464 from 64 bits (or 96 bits using the RFC7539 convention) to 192 bits,
1465 while provably retaining ChaCha20's security. See also:
1466 <https://cr.yp.to/snuffle/xsalsa-20081128.pdf>
1468 XChaCha12 is XChaCha20 reduced to 12 rounds, with correspondingly
1469 reduced security margin but increased performance. It can be needed
1470 in some performance-sensitive scenarios.
1472 config CRYPTO_CHACHA20_X86_64
1473 tristate "ChaCha stream cipher algorithms (x86_64/SSSE3/AVX2/AVX-512VL)"
1474 depends on X86 && 64BIT
1475 select CRYPTO_SKCIPHER
1476 select CRYPTO_LIB_CHACHA_GENERIC
1477 select CRYPTO_ARCH_HAVE_LIB_CHACHA
1479 SSSE3, AVX2, and AVX-512VL optimized implementations of the ChaCha20,
1480 XChaCha20, and XChaCha12 stream ciphers.
1482 config CRYPTO_CHACHA_MIPS
1483 tristate "ChaCha stream cipher algorithms (MIPS 32r2 optimized)"
1484 depends on CPU_MIPS32_R2
1485 select CRYPTO_SKCIPHER
1486 select CRYPTO_ARCH_HAVE_LIB_CHACHA
1489 tristate "SEED cipher algorithm"
1490 select CRYPTO_ALGAPI
1492 SEED cipher algorithm (RFC4269).
1494 SEED is a 128-bit symmetric key block cipher that has been
1495 developed by KISA (Korea Information Security Agency) as a
1496 national standard encryption algorithm of the Republic of Korea.
1497 It is a 16 round block cipher with the key size of 128 bit.
1500 <http://www.kisa.or.kr/kisa/seed/jsp/seed_eng.jsp>
1502 config CRYPTO_SERPENT
1503 tristate "Serpent cipher algorithm"
1504 select CRYPTO_ALGAPI
1506 Serpent cipher algorithm, by Anderson, Biham & Knudsen.
1508 Keys are allowed to be from 0 to 256 bits in length, in steps
1509 of 8 bits. Also includes the 'Tnepres' algorithm, a reversed
1510 variant of Serpent for compatibility with old kerneli.org code.
1513 <http://www.cl.cam.ac.uk/~rja14/serpent.html>
1515 config CRYPTO_SERPENT_SSE2_X86_64
1516 tristate "Serpent cipher algorithm (x86_64/SSE2)"
1517 depends on X86 && 64BIT
1518 select CRYPTO_SKCIPHER
1519 select CRYPTO_GLUE_HELPER_X86
1520 select CRYPTO_SERPENT
1523 Serpent cipher algorithm, by Anderson, Biham & Knudsen.
1525 Keys are allowed to be from 0 to 256 bits in length, in steps
1528 This module provides Serpent cipher algorithm that processes eight
1529 blocks parallel using SSE2 instruction set.
1532 <http://www.cl.cam.ac.uk/~rja14/serpent.html>
1534 config CRYPTO_SERPENT_SSE2_586
1535 tristate "Serpent cipher algorithm (i586/SSE2)"
1536 depends on X86 && !64BIT
1537 select CRYPTO_SKCIPHER
1538 select CRYPTO_GLUE_HELPER_X86
1539 select CRYPTO_SERPENT
1542 Serpent cipher algorithm, by Anderson, Biham & Knudsen.
1544 Keys are allowed to be from 0 to 256 bits in length, in steps
1547 This module provides Serpent cipher algorithm that processes four
1548 blocks parallel using SSE2 instruction set.
1551 <http://www.cl.cam.ac.uk/~rja14/serpent.html>
1553 config CRYPTO_SERPENT_AVX_X86_64
1554 tristate "Serpent cipher algorithm (x86_64/AVX)"
1555 depends on X86 && 64BIT
1556 select CRYPTO_SKCIPHER
1557 select CRYPTO_GLUE_HELPER_X86
1558 select CRYPTO_SERPENT
1562 Serpent cipher algorithm, by Anderson, Biham & Knudsen.
1564 Keys are allowed to be from 0 to 256 bits in length, in steps
1567 This module provides the Serpent cipher algorithm that processes
1568 eight blocks parallel using the AVX instruction set.
1571 <http://www.cl.cam.ac.uk/~rja14/serpent.html>
1573 config CRYPTO_SERPENT_AVX2_X86_64
1574 tristate "Serpent cipher algorithm (x86_64/AVX2)"
1575 depends on X86 && 64BIT
1576 select CRYPTO_SERPENT_AVX_X86_64
1578 Serpent cipher algorithm, by Anderson, Biham & Knudsen.
1580 Keys are allowed to be from 0 to 256 bits in length, in steps
1583 This module provides Serpent cipher algorithm that processes 16
1584 blocks parallel using AVX2 instruction set.
1587 <http://www.cl.cam.ac.uk/~rja14/serpent.html>
1590 tristate "SM4 cipher algorithm"
1591 select CRYPTO_ALGAPI
1593 SM4 cipher algorithms (OSCCA GB/T 32907-2016).
1595 SM4 (GBT.32907-2016) is a cryptographic standard issued by the
1596 Organization of State Commercial Administration of China (OSCCA)
1597 as an authorized cryptographic algorithms for the use within China.
1599 SMS4 was originally created for use in protecting wireless
1600 networks, and is mandated in the Chinese National Standard for
1601 Wireless LAN WAPI (Wired Authentication and Privacy Infrastructure)
1604 The latest SM4 standard (GBT.32907-2016) was proposed by OSCCA and
1605 standardized through TC 260 of the Standardization Administration
1606 of the People's Republic of China (SAC).
1608 The input, output, and key of SMS4 are each 128 bits.
1610 See also: <https://eprint.iacr.org/2008/329.pdf>
1615 tristate "TEA, XTEA and XETA cipher algorithms"
1616 select CRYPTO_ALGAPI
1618 TEA cipher algorithm.
1620 Tiny Encryption Algorithm is a simple cipher that uses
1621 many rounds for security. It is very fast and uses
1624 Xtendend Tiny Encryption Algorithm is a modification to
1625 the TEA algorithm to address a potential key weakness
1626 in the TEA algorithm.
1628 Xtendend Encryption Tiny Algorithm is a mis-implementation
1629 of the XTEA algorithm for compatibility purposes.
1631 config CRYPTO_TWOFISH
1632 tristate "Twofish cipher algorithm"
1633 select CRYPTO_ALGAPI
1634 select CRYPTO_TWOFISH_COMMON
1636 Twofish cipher algorithm.
1638 Twofish was submitted as an AES (Advanced Encryption Standard)
1639 candidate cipher by researchers at CounterPane Systems. It is a
1640 16 round block cipher supporting key sizes of 128, 192, and 256
1644 <http://www.schneier.com/twofish.html>
1646 config CRYPTO_TWOFISH_COMMON
1649 Common parts of the Twofish cipher algorithm shared by the
1650 generic c and the assembler implementations.
1652 config CRYPTO_TWOFISH_586
1653 tristate "Twofish cipher algorithms (i586)"
1654 depends on (X86 || UML_X86) && !64BIT
1655 select CRYPTO_ALGAPI
1656 select CRYPTO_TWOFISH_COMMON
1658 Twofish cipher algorithm.
1660 Twofish was submitted as an AES (Advanced Encryption Standard)
1661 candidate cipher by researchers at CounterPane Systems. It is a
1662 16 round block cipher supporting key sizes of 128, 192, and 256
1666 <http://www.schneier.com/twofish.html>
1668 config CRYPTO_TWOFISH_X86_64
1669 tristate "Twofish cipher algorithm (x86_64)"
1670 depends on (X86 || UML_X86) && 64BIT
1671 select CRYPTO_ALGAPI
1672 select CRYPTO_TWOFISH_COMMON
1674 Twofish cipher algorithm (x86_64).
1676 Twofish was submitted as an AES (Advanced Encryption Standard)
1677 candidate cipher by researchers at CounterPane Systems. It is a
1678 16 round block cipher supporting key sizes of 128, 192, and 256
1682 <http://www.schneier.com/twofish.html>
1684 config CRYPTO_TWOFISH_X86_64_3WAY
1685 tristate "Twofish cipher algorithm (x86_64, 3-way parallel)"
1686 depends on X86 && 64BIT
1687 select CRYPTO_SKCIPHER
1688 select CRYPTO_TWOFISH_COMMON
1689 select CRYPTO_TWOFISH_X86_64
1690 select CRYPTO_GLUE_HELPER_X86
1692 Twofish cipher algorithm (x86_64, 3-way parallel).
1694 Twofish was submitted as an AES (Advanced Encryption Standard)
1695 candidate cipher by researchers at CounterPane Systems. It is a
1696 16 round block cipher supporting key sizes of 128, 192, and 256
1699 This module provides Twofish cipher algorithm that processes three
1700 blocks parallel, utilizing resources of out-of-order CPUs better.
1703 <http://www.schneier.com/twofish.html>
1705 config CRYPTO_TWOFISH_AVX_X86_64
1706 tristate "Twofish cipher algorithm (x86_64/AVX)"
1707 depends on X86 && 64BIT
1708 select CRYPTO_SKCIPHER
1709 select CRYPTO_GLUE_HELPER_X86
1711 select CRYPTO_TWOFISH_COMMON
1712 select CRYPTO_TWOFISH_X86_64
1713 select CRYPTO_TWOFISH_X86_64_3WAY
1715 Twofish cipher algorithm (x86_64/AVX).
1717 Twofish was submitted as an AES (Advanced Encryption Standard)
1718 candidate cipher by researchers at CounterPane Systems. It is a
1719 16 round block cipher supporting key sizes of 128, 192, and 256
1722 This module provides the Twofish cipher algorithm that processes
1723 eight blocks parallel using the AVX Instruction Set.
1726 <http://www.schneier.com/twofish.html>
1728 comment "Compression"
1730 config CRYPTO_DEFLATE
1731 tristate "Deflate compression algorithm"
1732 select CRYPTO_ALGAPI
1733 select CRYPTO_ACOMP2
1737 This is the Deflate algorithm (RFC1951), specified for use in
1738 IPSec with the IPCOMP protocol (RFC3173, RFC2394).
1740 You will most probably want this if using IPSec.
1743 tristate "LZO compression algorithm"
1744 select CRYPTO_ALGAPI
1745 select CRYPTO_ACOMP2
1747 select LZO_DECOMPRESS
1749 This is the LZO algorithm.
1752 tristate "842 compression algorithm"
1753 select CRYPTO_ALGAPI
1754 select CRYPTO_ACOMP2
1756 select 842_DECOMPRESS
1758 This is the 842 algorithm.
1761 tristate "LZ4 compression algorithm"
1762 select CRYPTO_ALGAPI
1763 select CRYPTO_ACOMP2
1765 select LZ4_DECOMPRESS
1767 This is the LZ4 algorithm.
1770 tristate "LZ4HC compression algorithm"
1771 select CRYPTO_ALGAPI
1772 select CRYPTO_ACOMP2
1773 select LZ4HC_COMPRESS
1774 select LZ4_DECOMPRESS
1776 This is the LZ4 high compression mode algorithm.
1779 tristate "Zstd compression algorithm"
1780 select CRYPTO_ALGAPI
1781 select CRYPTO_ACOMP2
1782 select ZSTD_COMPRESS
1783 select ZSTD_DECOMPRESS
1785 This is the zstd algorithm.
1787 comment "Random Number Generation"
1789 config CRYPTO_ANSI_CPRNG
1790 tristate "Pseudo Random Number Generation for Cryptographic modules"
1794 This option enables the generic pseudo random number generator
1795 for cryptographic modules. Uses the Algorithm specified in
1796 ANSI X9.31 A.2.4. Note that this option must be enabled if
1797 CRYPTO_FIPS is selected
1799 menuconfig CRYPTO_DRBG_MENU
1800 tristate "NIST SP800-90A DRBG"
1802 NIST SP800-90A compliant DRBG. In the following submenu, one or
1803 more of the DRBG types must be selected.
1807 config CRYPTO_DRBG_HMAC
1811 select CRYPTO_SHA256
1813 config CRYPTO_DRBG_HASH
1814 bool "Enable Hash DRBG"
1815 select CRYPTO_SHA256
1817 Enable the Hash DRBG variant as defined in NIST SP800-90A.
1819 config CRYPTO_DRBG_CTR
1820 bool "Enable CTR DRBG"
1822 depends on CRYPTO_CTR
1824 Enable the CTR DRBG variant as defined in NIST SP800-90A.
1828 default CRYPTO_DRBG_MENU
1830 select CRYPTO_JITTERENTROPY
1832 endif # if CRYPTO_DRBG_MENU
1834 config CRYPTO_JITTERENTROPY
1835 tristate "Jitterentropy Non-Deterministic Random Number Generator"
1838 The Jitterentropy RNG is a noise that is intended
1839 to provide seed to another RNG. The RNG does not
1840 perform any cryptographic whitening of the generated
1841 random numbers. This Jitterentropy RNG registers with
1842 the kernel crypto API and can be used by any caller.
1844 config CRYPTO_USER_API
1847 config CRYPTO_USER_API_HASH
1848 tristate "User-space interface for hash algorithms"
1851 select CRYPTO_USER_API
1853 This option enables the user-spaces interface for hash
1856 config CRYPTO_USER_API_SKCIPHER
1857 tristate "User-space interface for symmetric key cipher algorithms"
1859 select CRYPTO_SKCIPHER
1860 select CRYPTO_USER_API
1862 This option enables the user-spaces interface for symmetric
1863 key cipher algorithms.
1865 config CRYPTO_USER_API_RNG
1866 tristate "User-space interface for random number generator algorithms"
1869 select CRYPTO_USER_API
1871 This option enables the user-spaces interface for random
1872 number generator algorithms.
1874 config CRYPTO_USER_API_AEAD
1875 tristate "User-space interface for AEAD cipher algorithms"
1878 select CRYPTO_SKCIPHER
1880 select CRYPTO_USER_API
1882 This option enables the user-spaces interface for AEAD
1886 bool "Crypto usage statistics for User-space"
1887 depends on CRYPTO_USER
1889 This option enables the gathering of crypto stats.
1891 - encrypt/decrypt size and numbers of symmeric operations
1892 - compress/decompress size and numbers of compress operations
1893 - size and numbers of hash operations
1894 - encrypt/decrypt/sign/verify numbers for asymmetric operations
1895 - generate/seed numbers for rng operations
1897 config CRYPTO_HASH_INFO
1900 source "lib/crypto/Kconfig"
1901 source "drivers/crypto/Kconfig"
1902 source "crypto/asymmetric_keys/Kconfig"
1903 source "certs/Kconfig"