2 # Generic algorithms support
8 # async_tx api: hardware offloaded memory transfer/transform support
10 source "crypto/async_tx/Kconfig"
13 # Cryptographic API Configuration
16 tristate "Cryptographic API"
18 This option provides the core Cryptographic API.
22 comment "Crypto core or helper"
25 bool "FIPS 200 compliance"
26 depends on CRYPTO_ANSI_CPRNG && !CRYPTO_MANAGER_DISABLE_TESTS
28 This options enables the fips boot option which is
29 required if you want to system to operate in a FIPS 200
30 certification. You should say no unless you know what
37 This option provides the API for cryptographic algorithms.
51 config CRYPTO_BLKCIPHER
53 select CRYPTO_BLKCIPHER2
56 config CRYPTO_BLKCIPHER2
60 select CRYPTO_WORKQUEUE
90 tristate "Cryptographic algorithm manager"
91 select CRYPTO_MANAGER2
93 Create default cryptographic template instantiations such as
96 config CRYPTO_MANAGER2
97 def_tristate CRYPTO_MANAGER || (CRYPTO_MANAGER!=n && CRYPTO_ALGAPI=y)
100 select CRYPTO_BLKCIPHER2
103 config CRYPTO_MANAGER_DISABLE_TESTS
104 bool "Disable run-time self tests"
106 depends on CRYPTO_MANAGER2
108 Disable run-time self tests that normally take place at
109 algorithm registration.
111 config CRYPTO_GF128MUL
112 tristate "GF(2^128) multiplication functions (EXPERIMENTAL)"
114 Efficient table driven implementation of multiplications in the
115 field GF(2^128). This is needed by some cypher modes. This
116 option will be selected automatically if you select such a
117 cipher mode. Only select this option by hand if you expect to load
118 an external module that requires these functions.
121 tristate "Null algorithms"
123 select CRYPTO_BLKCIPHER
126 These are 'Null' algorithms, used by IPsec, which do nothing.
129 tristate "Parallel crypto engine (EXPERIMENTAL)"
130 depends on SMP && EXPERIMENTAL
132 select CRYPTO_MANAGER
135 This converts an arbitrary crypto algorithm into a parallel
136 algorithm that executes in kernel threads.
138 config CRYPTO_WORKQUEUE
142 tristate "Software async crypto daemon"
143 select CRYPTO_BLKCIPHER
145 select CRYPTO_MANAGER
146 select CRYPTO_WORKQUEUE
148 This is a generic software asynchronous crypto daemon that
149 converts an arbitrary synchronous software crypto algorithm
150 into an asynchronous algorithm that executes in a kernel thread.
152 config CRYPTO_AUTHENC
153 tristate "Authenc support"
155 select CRYPTO_BLKCIPHER
156 select CRYPTO_MANAGER
159 Authenc: Combined mode wrapper for IPsec.
160 This is required for IPSec.
163 tristate "Testing module"
165 select CRYPTO_MANAGER
167 Quick & dirty crypto test module.
169 comment "Authenticated Encryption with Associated Data"
172 tristate "CCM support"
176 Support for Counter with CBC MAC. Required for IPsec.
179 tristate "GCM/GMAC support"
184 Support for Galois/Counter Mode (GCM) and Galois Message
185 Authentication Code (GMAC). Required for IPSec.
188 tristate "Sequence Number IV Generator"
190 select CRYPTO_BLKCIPHER
193 This IV generator generates an IV based on a sequence number by
194 xoring it with a salt. This algorithm is mainly useful for CTR
196 comment "Block modes"
199 tristate "CBC support"
200 select CRYPTO_BLKCIPHER
201 select CRYPTO_MANAGER
203 CBC: Cipher Block Chaining mode
204 This block cipher algorithm is required for IPSec.
207 tristate "CTR support"
208 select CRYPTO_BLKCIPHER
210 select CRYPTO_MANAGER
213 This block cipher algorithm is required for IPSec.
216 tristate "CTS support"
217 select CRYPTO_BLKCIPHER
219 CTS: Cipher Text Stealing
220 This is the Cipher Text Stealing mode as described by
221 Section 8 of rfc2040 and referenced by rfc3962.
222 (rfc3962 includes errata information in its Appendix A)
223 This mode is required for Kerberos gss mechanism support
227 tristate "ECB support"
228 select CRYPTO_BLKCIPHER
229 select CRYPTO_MANAGER
231 ECB: Electronic CodeBook mode
232 This is the simplest block cipher algorithm. It simply encrypts
233 the input block by block.
236 tristate "LRW support (EXPERIMENTAL)"
237 depends on EXPERIMENTAL
238 select CRYPTO_BLKCIPHER
239 select CRYPTO_MANAGER
240 select CRYPTO_GF128MUL
242 LRW: Liskov Rivest Wagner, a tweakable, non malleable, non movable
243 narrow block cipher mode for dm-crypt. Use it with cipher
244 specification string aes-lrw-benbi, the key must be 256, 320 or 384.
245 The first 128, 192 or 256 bits in the key are used for AES and the
246 rest is used to tie each cipher block to its logical position.
249 tristate "PCBC support"
250 select CRYPTO_BLKCIPHER
251 select CRYPTO_MANAGER
253 PCBC: Propagating Cipher Block Chaining mode
254 This block cipher algorithm is required for RxRPC.
257 tristate "XTS support (EXPERIMENTAL)"
258 depends on EXPERIMENTAL
259 select CRYPTO_BLKCIPHER
260 select CRYPTO_MANAGER
261 select CRYPTO_GF128MUL
263 XTS: IEEE1619/D16 narrow block cipher use with aes-xts-plain,
264 key size 256, 384 or 512 bits. This implementation currently
265 can't handle a sectorsize which is not a multiple of 16 bytes.
270 tristate "HMAC support"
272 select CRYPTO_MANAGER
274 HMAC: Keyed-Hashing for Message Authentication (RFC2104).
275 This is required for IPSec.
278 tristate "XCBC support"
279 depends on EXPERIMENTAL
281 select CRYPTO_MANAGER
283 XCBC: Keyed-Hashing with encryption algorithm
284 http://www.ietf.org/rfc/rfc3566.txt
285 http://csrc.nist.gov/encryption/modes/proposedmodes/
286 xcbc-mac/xcbc-mac-spec.pdf
289 tristate "VMAC support"
290 depends on EXPERIMENTAL
292 select CRYPTO_MANAGER
294 VMAC is a message authentication algorithm designed for
295 very high speed on 64-bit architectures.
298 <http://fastcrypto.org/vmac>
303 tristate "CRC32c CRC algorithm"
306 Castagnoli, et al Cyclic Redundancy-Check Algorithm. Used
307 by iSCSI for header and data digests and by others.
308 See Castagnoli93. Module will be crc32c.
310 config CRYPTO_CRC32C_INTEL
311 tristate "CRC32c INTEL hardware acceleration"
315 In Intel processor with SSE4.2 supported, the processor will
316 support CRC32C implementation using hardware accelerated CRC32
317 instruction. This option will create 'crc32c-intel' module,
318 which will enable any routine to use the CRC32 instruction to
319 gain performance compared with software implementation.
320 Module will be crc32c-intel.
323 tristate "GHASH digest algorithm"
324 select CRYPTO_GF128MUL
326 GHASH is message digest algorithm for GCM (Galois/Counter Mode).
329 tristate "MD4 digest algorithm"
332 MD4 message digest algorithm (RFC1320).
335 tristate "MD5 digest algorithm"
338 MD5 message digest algorithm (RFC1321).
340 config CRYPTO_MICHAEL_MIC
341 tristate "Michael MIC keyed digest algorithm"
344 Michael MIC is used for message integrity protection in TKIP
345 (IEEE 802.11i). This algorithm is required for TKIP, but it
346 should not be used for other purposes because of the weakness
350 tristate "RIPEMD-128 digest algorithm"
353 RIPEMD-128 (ISO/IEC 10118-3:2004).
355 RIPEMD-128 is a 128-bit cryptographic hash function. It should only
356 be used as a secure replacement for RIPEMD. For other use cases,
357 RIPEMD-160 should be used.
359 Developed by Hans Dobbertin, Antoon Bosselaers and Bart Preneel.
360 See <http://homes.esat.kuleuven.be/~bosselae/ripemd160.html>
363 tristate "RIPEMD-160 digest algorithm"
366 RIPEMD-160 (ISO/IEC 10118-3:2004).
368 RIPEMD-160 is a 160-bit cryptographic hash function. It is intended
369 to be used as a secure replacement for the 128-bit hash functions
370 MD4, MD5 and it's predecessor RIPEMD
371 (not to be confused with RIPEMD-128).
373 It's speed is comparable to SHA1 and there are no known attacks
376 Developed by Hans Dobbertin, Antoon Bosselaers and Bart Preneel.
377 See <http://homes.esat.kuleuven.be/~bosselae/ripemd160.html>
380 tristate "RIPEMD-256 digest algorithm"
383 RIPEMD-256 is an optional extension of RIPEMD-128 with a
384 256 bit hash. It is intended for applications that require
385 longer hash-results, without needing a larger security level
388 Developed by Hans Dobbertin, Antoon Bosselaers and Bart Preneel.
389 See <http://homes.esat.kuleuven.be/~bosselae/ripemd160.html>
392 tristate "RIPEMD-320 digest algorithm"
395 RIPEMD-320 is an optional extension of RIPEMD-160 with a
396 320 bit hash. It is intended for applications that require
397 longer hash-results, without needing a larger security level
400 Developed by Hans Dobbertin, Antoon Bosselaers and Bart Preneel.
401 See <http://homes.esat.kuleuven.be/~bosselae/ripemd160.html>
404 tristate "SHA1 digest algorithm"
407 SHA-1 secure hash standard (FIPS 180-1/DFIPS 180-2).
410 tristate "SHA224 and SHA256 digest algorithm"
413 SHA256 secure hash standard (DFIPS 180-2).
415 This version of SHA implements a 256 bit hash with 128 bits of
416 security against collision attacks.
418 This code also includes SHA-224, a 224 bit hash with 112 bits
419 of security against collision attacks.
422 tristate "SHA384 and SHA512 digest algorithms"
425 SHA512 secure hash standard (DFIPS 180-2).
427 This version of SHA implements a 512 bit hash with 256 bits of
428 security against collision attacks.
430 This code also includes SHA-384, a 384 bit hash with 192 bits
431 of security against collision attacks.
434 tristate "Tiger digest algorithms"
437 Tiger hash algorithm 192, 160 and 128-bit hashes
439 Tiger is a hash function optimized for 64-bit processors while
440 still having decent performance on 32-bit processors.
441 Tiger was developed by Ross Anderson and Eli Biham.
444 <http://www.cs.technion.ac.il/~biham/Reports/Tiger/>.
447 tristate "Whirlpool digest algorithms"
450 Whirlpool hash algorithm 512, 384 and 256-bit hashes
452 Whirlpool-512 is part of the NESSIE cryptographic primitives.
453 Whirlpool will be part of the ISO/IEC 10118-3:2003(E) standard
456 <http://www.larc.usp.br/~pbarreto/WhirlpoolPage.html>
458 config CRYPTO_GHASH_CLMUL_NI_INTEL
459 tristate "GHASH digest algorithm (CLMUL-NI accelerated)"
460 depends on X86 && 64BIT
463 GHASH is message digest algorithm for GCM (Galois/Counter Mode).
464 The implementation is accelerated by CLMUL-NI of Intel.
469 tristate "AES cipher algorithms"
472 AES cipher algorithms (FIPS-197). AES uses the Rijndael
475 Rijndael appears to be consistently a very good performer in
476 both hardware and software across a wide range of computing
477 environments regardless of its use in feedback or non-feedback
478 modes. Its key setup time is excellent, and its key agility is
479 good. Rijndael's very low memory requirements make it very well
480 suited for restricted-space environments, in which it also
481 demonstrates excellent performance. Rijndael's operations are
482 among the easiest to defend against power and timing attacks.
484 The AES specifies three key sizes: 128, 192 and 256 bits
486 See <http://csrc.nist.gov/CryptoToolkit/aes/> for more information.
488 config CRYPTO_AES_586
489 tristate "AES cipher algorithms (i586)"
490 depends on (X86 || UML_X86) && !64BIT
494 AES cipher algorithms (FIPS-197). AES uses the Rijndael
497 Rijndael appears to be consistently a very good performer in
498 both hardware and software across a wide range of computing
499 environments regardless of its use in feedback or non-feedback
500 modes. Its key setup time is excellent, and its key agility is
501 good. Rijndael's very low memory requirements make it very well
502 suited for restricted-space environments, in which it also
503 demonstrates excellent performance. Rijndael's operations are
504 among the easiest to defend against power and timing attacks.
506 The AES specifies three key sizes: 128, 192 and 256 bits
508 See <http://csrc.nist.gov/encryption/aes/> for more information.
510 config CRYPTO_AES_X86_64
511 tristate "AES cipher algorithms (x86_64)"
512 depends on (X86 || UML_X86) && 64BIT
516 AES cipher algorithms (FIPS-197). AES uses the Rijndael
519 Rijndael appears to be consistently a very good performer in
520 both hardware and software across a wide range of computing
521 environments regardless of its use in feedback or non-feedback
522 modes. Its key setup time is excellent, and its key agility is
523 good. Rijndael's very low memory requirements make it very well
524 suited for restricted-space environments, in which it also
525 demonstrates excellent performance. Rijndael's operations are
526 among the easiest to defend against power and timing attacks.
528 The AES specifies three key sizes: 128, 192 and 256 bits
530 See <http://csrc.nist.gov/encryption/aes/> for more information.
532 config CRYPTO_AES_NI_INTEL
533 tristate "AES cipher algorithms (AES-NI)"
535 select CRYPTO_AES_X86_64 if 64BIT
536 select CRYPTO_AES_586 if !64BIT
540 Use Intel AES-NI instructions for AES algorithm.
542 AES cipher algorithms (FIPS-197). AES uses the Rijndael
545 Rijndael appears to be consistently a very good performer in
546 both hardware and software across a wide range of computing
547 environments regardless of its use in feedback or non-feedback
548 modes. Its key setup time is excellent, and its key agility is
549 good. Rijndael's very low memory requirements make it very well
550 suited for restricted-space environments, in which it also
551 demonstrates excellent performance. Rijndael's operations are
552 among the easiest to defend against power and timing attacks.
554 The AES specifies three key sizes: 128, 192 and 256 bits
556 See <http://csrc.nist.gov/encryption/aes/> for more information.
558 In addition to AES cipher algorithm support, the acceleration
559 for some popular block cipher mode is supported too, including
560 ECB, CBC, LRW, PCBC, XTS. The 64 bit version has additional
561 acceleration for CTR.
564 tristate "Anubis cipher algorithm"
567 Anubis cipher algorithm.
569 Anubis is a variable key length cipher which can use keys from
570 128 bits to 320 bits in length. It was evaluated as a entrant
571 in the NESSIE competition.
574 <https://www.cosic.esat.kuleuven.be/nessie/reports/>
575 <http://www.larc.usp.br/~pbarreto/AnubisPage.html>
578 tristate "ARC4 cipher algorithm"
581 ARC4 cipher algorithm.
583 ARC4 is a stream cipher using keys ranging from 8 bits to 2048
584 bits in length. This algorithm is required for driver-based
585 WEP, but it should not be for other purposes because of the
586 weakness of the algorithm.
588 config CRYPTO_BLOWFISH
589 tristate "Blowfish cipher algorithm"
592 Blowfish cipher algorithm, by Bruce Schneier.
594 This is a variable key length cipher which can use keys from 32
595 bits to 448 bits in length. It's fast, simple and specifically
596 designed for use on "large microprocessors".
599 <http://www.schneier.com/blowfish.html>
601 config CRYPTO_CAMELLIA
602 tristate "Camellia cipher algorithms"
606 Camellia cipher algorithms module.
608 Camellia is a symmetric key block cipher developed jointly
609 at NTT and Mitsubishi Electric Corporation.
611 The Camellia specifies three key sizes: 128, 192 and 256 bits.
614 <https://info.isl.ntt.co.jp/crypt/eng/camellia/index_s.html>
617 tristate "CAST5 (CAST-128) cipher algorithm"
620 The CAST5 encryption algorithm (synonymous with CAST-128) is
621 described in RFC2144.
624 tristate "CAST6 (CAST-256) cipher algorithm"
627 The CAST6 encryption algorithm (synonymous with CAST-256) is
628 described in RFC2612.
631 tristate "DES and Triple DES EDE cipher algorithms"
634 DES cipher algorithm (FIPS 46-2), and Triple DES EDE (FIPS 46-3).
637 tristate "FCrypt cipher algorithm"
639 select CRYPTO_BLKCIPHER
641 FCrypt algorithm used by RxRPC.
644 tristate "Khazad cipher algorithm"
647 Khazad cipher algorithm.
649 Khazad was a finalist in the initial NESSIE competition. It is
650 an algorithm optimized for 64-bit processors with good performance
651 on 32-bit processors. Khazad uses an 128 bit key size.
654 <http://www.larc.usp.br/~pbarreto/KhazadPage.html>
656 config CRYPTO_SALSA20
657 tristate "Salsa20 stream cipher algorithm (EXPERIMENTAL)"
658 depends on EXPERIMENTAL
659 select CRYPTO_BLKCIPHER
661 Salsa20 stream cipher algorithm.
663 Salsa20 is a stream cipher submitted to eSTREAM, the ECRYPT
664 Stream Cipher Project. See <http://www.ecrypt.eu.org/stream/>
666 The Salsa20 stream cipher algorithm is designed by Daniel J.
667 Bernstein <djb@cr.yp.to>. See <http://cr.yp.to/snuffle.html>
669 config CRYPTO_SALSA20_586
670 tristate "Salsa20 stream cipher algorithm (i586) (EXPERIMENTAL)"
671 depends on (X86 || UML_X86) && !64BIT
672 depends on EXPERIMENTAL
673 select CRYPTO_BLKCIPHER
675 Salsa20 stream cipher algorithm.
677 Salsa20 is a stream cipher submitted to eSTREAM, the ECRYPT
678 Stream Cipher Project. See <http://www.ecrypt.eu.org/stream/>
680 The Salsa20 stream cipher algorithm is designed by Daniel J.
681 Bernstein <djb@cr.yp.to>. See <http://cr.yp.to/snuffle.html>
683 config CRYPTO_SALSA20_X86_64
684 tristate "Salsa20 stream cipher algorithm (x86_64) (EXPERIMENTAL)"
685 depends on (X86 || UML_X86) && 64BIT
686 depends on EXPERIMENTAL
687 select CRYPTO_BLKCIPHER
689 Salsa20 stream cipher algorithm.
691 Salsa20 is a stream cipher submitted to eSTREAM, the ECRYPT
692 Stream Cipher Project. See <http://www.ecrypt.eu.org/stream/>
694 The Salsa20 stream cipher algorithm is designed by Daniel J.
695 Bernstein <djb@cr.yp.to>. See <http://cr.yp.to/snuffle.html>
698 tristate "SEED cipher algorithm"
701 SEED cipher algorithm (RFC4269).
703 SEED is a 128-bit symmetric key block cipher that has been
704 developed by KISA (Korea Information Security Agency) as a
705 national standard encryption algorithm of the Republic of Korea.
706 It is a 16 round block cipher with the key size of 128 bit.
709 <http://www.kisa.or.kr/kisa/seed/jsp/seed_eng.jsp>
711 config CRYPTO_SERPENT
712 tristate "Serpent cipher algorithm"
715 Serpent cipher algorithm, by Anderson, Biham & Knudsen.
717 Keys are allowed to be from 0 to 256 bits in length, in steps
718 of 8 bits. Also includes the 'Tnepres' algorithm, a reversed
719 variant of Serpent for compatibility with old kerneli.org code.
722 <http://www.cl.cam.ac.uk/~rja14/serpent.html>
725 tristate "TEA, XTEA and XETA cipher algorithms"
728 TEA cipher algorithm.
730 Tiny Encryption Algorithm is a simple cipher that uses
731 many rounds for security. It is very fast and uses
734 Xtendend Tiny Encryption Algorithm is a modification to
735 the TEA algorithm to address a potential key weakness
736 in the TEA algorithm.
738 Xtendend Encryption Tiny Algorithm is a mis-implementation
739 of the XTEA algorithm for compatibility purposes.
741 config CRYPTO_TWOFISH
742 tristate "Twofish cipher algorithm"
744 select CRYPTO_TWOFISH_COMMON
746 Twofish cipher algorithm.
748 Twofish was submitted as an AES (Advanced Encryption Standard)
749 candidate cipher by researchers at CounterPane Systems. It is a
750 16 round block cipher supporting key sizes of 128, 192, and 256
754 <http://www.schneier.com/twofish.html>
756 config CRYPTO_TWOFISH_COMMON
759 Common parts of the Twofish cipher algorithm shared by the
760 generic c and the assembler implementations.
762 config CRYPTO_TWOFISH_586
763 tristate "Twofish cipher algorithms (i586)"
764 depends on (X86 || UML_X86) && !64BIT
766 select CRYPTO_TWOFISH_COMMON
768 Twofish cipher algorithm.
770 Twofish was submitted as an AES (Advanced Encryption Standard)
771 candidate cipher by researchers at CounterPane Systems. It is a
772 16 round block cipher supporting key sizes of 128, 192, and 256
776 <http://www.schneier.com/twofish.html>
778 config CRYPTO_TWOFISH_X86_64
779 tristate "Twofish cipher algorithm (x86_64)"
780 depends on (X86 || UML_X86) && 64BIT
782 select CRYPTO_TWOFISH_COMMON
784 Twofish cipher algorithm (x86_64).
786 Twofish was submitted as an AES (Advanced Encryption Standard)
787 candidate cipher by researchers at CounterPane Systems. It is a
788 16 round block cipher supporting key sizes of 128, 192, and 256
792 <http://www.schneier.com/twofish.html>
794 comment "Compression"
796 config CRYPTO_DEFLATE
797 tristate "Deflate compression algorithm"
802 This is the Deflate algorithm (RFC1951), specified for use in
803 IPSec with the IPCOMP protocol (RFC3173, RFC2394).
805 You will most probably want this if using IPSec.
808 tristate "Zlib compression algorithm"
814 This is the zlib algorithm.
817 tristate "LZO compression algorithm"
820 select LZO_DECOMPRESS
822 This is the LZO algorithm.
824 comment "Random Number Generation"
826 config CRYPTO_ANSI_CPRNG
827 tristate "Pseudo Random Number Generation for Cryptographic modules"
832 This option enables the generic pseudo random number generator
833 for cryptographic modules. Uses the Algorithm specified in
834 ANSI X9.31 A.2.4. Note that this option must be enabled if
835 CRYPTO_FIPS is selected
837 config CRYPTO_USER_API
840 config CRYPTO_USER_API_HASH
841 tristate "User-space interface for hash algorithms"
844 select CRYPTO_USER_API
846 This option enables the user-spaces interface for hash
849 config CRYPTO_USER_API_SKCIPHER
850 tristate "User-space interface for symmetric key cipher algorithms"
852 select CRYPTO_BLKCIPHER
853 select CRYPTO_USER_API
855 This option enables the user-spaces interface for symmetric
856 key cipher algorithms.
858 source "drivers/crypto/Kconfig"