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
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
31 this is. Note that CRYPTO_ANSI_CPRNG is required if this
38 This option provides the API for cryptographic algorithms.
52 config CRYPTO_BLKCIPHER
54 select CRYPTO_BLKCIPHER2
57 config CRYPTO_BLKCIPHER2
61 select CRYPTO_WORKQUEUE
91 tristate "Cryptographic algorithm manager"
92 select CRYPTO_MANAGER2
94 Create default cryptographic template instantiations such as
97 config CRYPTO_MANAGER2
98 def_tristate CRYPTO_MANAGER || (CRYPTO_MANAGER!=n && CRYPTO_ALGAPI=y)
101 select CRYPTO_BLKCIPHER2
104 config CRYPTO_MANAGER_DISABLE_TESTS
105 bool "Disable run-time self tests"
107 depends on CRYPTO_MANAGER2
109 Disable run-time self tests that normally take place at
110 algorithm registration.
112 config CRYPTO_GF128MUL
113 tristate "GF(2^128) multiplication functions (EXPERIMENTAL)"
114 depends on EXPERIMENTAL
116 Efficient table driven implementation of multiplications in the
117 field GF(2^128). This is needed by some cypher modes. This
118 option will be selected automatically if you select such a
119 cipher mode. Only select this option by hand if you expect to load
120 an external module that requires these functions.
123 tristate "Null algorithms"
125 select CRYPTO_BLKCIPHER
128 These are 'Null' algorithms, used by IPsec, which do nothing.
131 tristate "Parallel crypto engine (EXPERIMENTAL)"
132 depends on SMP && EXPERIMENTAL
134 select CRYPTO_MANAGER
137 This converts an arbitrary crypto algorithm into a parallel
138 algorithm that executes in kernel threads.
140 config CRYPTO_WORKQUEUE
144 tristate "Software async crypto daemon"
145 select CRYPTO_BLKCIPHER
147 select CRYPTO_MANAGER
148 select CRYPTO_WORKQUEUE
150 This is a generic software asynchronous crypto daemon that
151 converts an arbitrary synchronous software crypto algorithm
152 into an asynchronous algorithm that executes in a kernel thread.
154 config CRYPTO_AUTHENC
155 tristate "Authenc support"
157 select CRYPTO_BLKCIPHER
158 select CRYPTO_MANAGER
161 Authenc: Combined mode wrapper for IPsec.
162 This is required for IPSec.
165 tristate "Testing module"
167 select CRYPTO_MANAGER
169 Quick & dirty crypto test module.
171 comment "Authenticated Encryption with Associated Data"
174 tristate "CCM support"
178 Support for Counter with CBC MAC. Required for IPsec.
181 tristate "GCM/GMAC support"
186 Support for Galois/Counter Mode (GCM) and Galois Message
187 Authentication Code (GMAC). Required for IPSec.
190 tristate "Sequence Number IV Generator"
192 select CRYPTO_BLKCIPHER
195 This IV generator generates an IV based on a sequence number by
196 xoring it with a salt. This algorithm is mainly useful for CTR
198 comment "Block modes"
201 tristate "CBC support"
202 select CRYPTO_BLKCIPHER
203 select CRYPTO_MANAGER
205 CBC: Cipher Block Chaining mode
206 This block cipher algorithm is required for IPSec.
209 tristate "CTR support"
210 select CRYPTO_BLKCIPHER
212 select CRYPTO_MANAGER
215 This block cipher algorithm is required for IPSec.
218 tristate "CTS support"
219 select CRYPTO_BLKCIPHER
221 CTS: Cipher Text Stealing
222 This is the Cipher Text Stealing mode as described by
223 Section 8 of rfc2040 and referenced by rfc3962.
224 (rfc3962 includes errata information in its Appendix A)
225 This mode is required for Kerberos gss mechanism support
229 tristate "ECB support"
230 select CRYPTO_BLKCIPHER
231 select CRYPTO_MANAGER
233 ECB: Electronic CodeBook mode
234 This is the simplest block cipher algorithm. It simply encrypts
235 the input block by block.
238 tristate "LRW support (EXPERIMENTAL)"
239 depends on EXPERIMENTAL
240 select CRYPTO_BLKCIPHER
241 select CRYPTO_MANAGER
242 select CRYPTO_GF128MUL
244 LRW: Liskov Rivest Wagner, a tweakable, non malleable, non movable
245 narrow block cipher mode for dm-crypt. Use it with cipher
246 specification string aes-lrw-benbi, the key must be 256, 320 or 384.
247 The first 128, 192 or 256 bits in the key are used for AES and the
248 rest is used to tie each cipher block to its logical position.
251 tristate "PCBC support"
252 select CRYPTO_BLKCIPHER
253 select CRYPTO_MANAGER
255 PCBC: Propagating Cipher Block Chaining mode
256 This block cipher algorithm is required for RxRPC.
259 tristate "XTS support (EXPERIMENTAL)"
260 depends on EXPERIMENTAL
261 select CRYPTO_BLKCIPHER
262 select CRYPTO_MANAGER
263 select CRYPTO_GF128MUL
265 XTS: IEEE1619/D16 narrow block cipher use with aes-xts-plain,
266 key size 256, 384 or 512 bits. This implementation currently
267 can't handle a sectorsize which is not a multiple of 16 bytes.
271 select CRYPTO_BLKCIPHER
272 select CRYPTO_MANAGER
277 tristate "HMAC support"
279 select CRYPTO_MANAGER
281 HMAC: Keyed-Hashing for Message Authentication (RFC2104).
282 This is required for IPSec.
285 tristate "XCBC support"
286 depends on EXPERIMENTAL
288 select CRYPTO_MANAGER
290 XCBC: Keyed-Hashing with encryption algorithm
291 http://www.ietf.org/rfc/rfc3566.txt
292 http://csrc.nist.gov/encryption/modes/proposedmodes/
293 xcbc-mac/xcbc-mac-spec.pdf
296 tristate "VMAC support"
297 depends on EXPERIMENTAL
299 select CRYPTO_MANAGER
301 VMAC is a message authentication algorithm designed for
302 very high speed on 64-bit architectures.
305 <http://fastcrypto.org/vmac>
310 tristate "CRC32c CRC algorithm"
313 Castagnoli, et al Cyclic Redundancy-Check Algorithm. Used
314 by iSCSI for header and data digests and by others.
315 See Castagnoli93. Module will be crc32c.
317 config CRYPTO_CRC32C_INTEL
318 tristate "CRC32c INTEL hardware acceleration"
322 In Intel processor with SSE4.2 supported, the processor will
323 support CRC32C implementation using hardware accelerated CRC32
324 instruction. This option will create 'crc32c-intel' module,
325 which will enable any routine to use the CRC32 instruction to
326 gain performance compared with software implementation.
327 Module will be crc32c-intel.
330 tristate "GHASH digest algorithm"
332 select CRYPTO_GF128MUL
334 GHASH is message digest algorithm for GCM (Galois/Counter Mode).
337 tristate "MD4 digest algorithm"
340 MD4 message digest algorithm (RFC1320).
343 tristate "MD5 digest algorithm"
346 MD5 message digest algorithm (RFC1321).
348 config CRYPTO_MICHAEL_MIC
349 tristate "Michael MIC keyed digest algorithm"
352 Michael MIC is used for message integrity protection in TKIP
353 (IEEE 802.11i). This algorithm is required for TKIP, but it
354 should not be used for other purposes because of the weakness
358 tristate "RIPEMD-128 digest algorithm"
361 RIPEMD-128 (ISO/IEC 10118-3:2004).
363 RIPEMD-128 is a 128-bit cryptographic hash function. It should only
364 to be used as a secure replacement for RIPEMD. For other use cases
365 RIPEMD-160 should be used.
367 Developed by Hans Dobbertin, Antoon Bosselaers and Bart Preneel.
368 See <http://home.esat.kuleuven.be/~bosselae/ripemd160.html>
371 tristate "RIPEMD-160 digest algorithm"
374 RIPEMD-160 (ISO/IEC 10118-3:2004).
376 RIPEMD-160 is a 160-bit cryptographic hash function. It is intended
377 to be used as a secure replacement for the 128-bit hash functions
378 MD4, MD5 and it's predecessor RIPEMD
379 (not to be confused with RIPEMD-128).
381 It's speed is comparable to SHA1 and there are no known attacks
384 Developed by Hans Dobbertin, Antoon Bosselaers and Bart Preneel.
385 See <http://home.esat.kuleuven.be/~bosselae/ripemd160.html>
388 tristate "RIPEMD-256 digest algorithm"
391 RIPEMD-256 is an optional extension of RIPEMD-128 with a
392 256 bit hash. It is intended for applications that require
393 longer hash-results, without needing a larger security level
396 Developed by Hans Dobbertin, Antoon Bosselaers and Bart Preneel.
397 See <http://home.esat.kuleuven.be/~bosselae/ripemd160.html>
400 tristate "RIPEMD-320 digest algorithm"
403 RIPEMD-320 is an optional extension of RIPEMD-160 with a
404 320 bit hash. It is intended for applications that require
405 longer hash-results, without needing a larger security level
408 Developed by Hans Dobbertin, Antoon Bosselaers and Bart Preneel.
409 See <http://home.esat.kuleuven.be/~bosselae/ripemd160.html>
412 tristate "SHA1 digest algorithm"
415 SHA-1 secure hash standard (FIPS 180-1/DFIPS 180-2).
418 tristate "SHA224 and SHA256 digest algorithm"
421 SHA256 secure hash standard (DFIPS 180-2).
423 This version of SHA implements a 256 bit hash with 128 bits of
424 security against collision attacks.
426 This code also includes SHA-224, a 224 bit hash with 112 bits
427 of security against collision attacks.
430 tristate "SHA384 and SHA512 digest algorithms"
433 SHA512 secure hash standard (DFIPS 180-2).
435 This version of SHA implements a 512 bit hash with 256 bits of
436 security against collision attacks.
438 This code also includes SHA-384, a 384 bit hash with 192 bits
439 of security against collision attacks.
442 tristate "Tiger digest algorithms"
445 Tiger hash algorithm 192, 160 and 128-bit hashes
447 Tiger is a hash function optimized for 64-bit processors while
448 still having decent performance on 32-bit processors.
449 Tiger was developed by Ross Anderson and Eli Biham.
452 <http://www.cs.technion.ac.il/~biham/Reports/Tiger/>.
455 tristate "Whirlpool digest algorithms"
458 Whirlpool hash algorithm 512, 384 and 256-bit hashes
460 Whirlpool-512 is part of the NESSIE cryptographic primitives.
461 Whirlpool will be part of the ISO/IEC 10118-3:2003(E) standard
464 <http://planeta.terra.com.br/informatica/paulobarreto/WhirlpoolPage.html>
466 config CRYPTO_GHASH_CLMUL_NI_INTEL
467 tristate "GHASH digest algorithm (CLMUL-NI accelerated)"
468 depends on (X86 || UML_X86) && 64BIT
472 GHASH is message digest algorithm for GCM (Galois/Counter Mode).
473 The implementation is accelerated by CLMUL-NI of Intel.
478 tristate "AES cipher algorithms"
481 AES cipher algorithms (FIPS-197). AES uses the Rijndael
484 Rijndael appears to be consistently a very good performer in
485 both hardware and software across a wide range of computing
486 environments regardless of its use in feedback or non-feedback
487 modes. Its key setup time is excellent, and its key agility is
488 good. Rijndael's very low memory requirements make it very well
489 suited for restricted-space environments, in which it also
490 demonstrates excellent performance. Rijndael's operations are
491 among the easiest to defend against power and timing attacks.
493 The AES specifies three key sizes: 128, 192 and 256 bits
495 See <http://csrc.nist.gov/CryptoToolkit/aes/> for more information.
497 config CRYPTO_AES_586
498 tristate "AES cipher algorithms (i586)"
499 depends on (X86 || UML_X86) && !64BIT
503 AES cipher algorithms (FIPS-197). AES uses the Rijndael
506 Rijndael appears to be consistently a very good performer in
507 both hardware and software across a wide range of computing
508 environments regardless of its use in feedback or non-feedback
509 modes. Its key setup time is excellent, and its key agility is
510 good. Rijndael's very low memory requirements make it very well
511 suited for restricted-space environments, in which it also
512 demonstrates excellent performance. Rijndael's operations are
513 among the easiest to defend against power and timing attacks.
515 The AES specifies three key sizes: 128, 192 and 256 bits
517 See <http://csrc.nist.gov/encryption/aes/> for more information.
519 config CRYPTO_AES_X86_64
520 tristate "AES cipher algorithms (x86_64)"
521 depends on (X86 || UML_X86) && 64BIT
525 AES cipher algorithms (FIPS-197). AES uses the Rijndael
528 Rijndael appears to be consistently a very good performer in
529 both hardware and software across a wide range of computing
530 environments regardless of its use in feedback or non-feedback
531 modes. Its key setup time is excellent, and its key agility is
532 good. Rijndael's very low memory requirements make it very well
533 suited for restricted-space environments, in which it also
534 demonstrates excellent performance. Rijndael's operations are
535 among the easiest to defend against power and timing attacks.
537 The AES specifies three key sizes: 128, 192 and 256 bits
539 See <http://csrc.nist.gov/encryption/aes/> for more information.
541 config CRYPTO_AES_NI_INTEL
542 tristate "AES cipher algorithms (AES-NI)"
543 depends on (X86 || UML_X86) && 64BIT
544 select CRYPTO_AES_X86_64
549 Use Intel AES-NI instructions for AES algorithm.
551 AES cipher algorithms (FIPS-197). AES uses the Rijndael
554 Rijndael appears to be consistently a very good performer in
555 both hardware and software across a wide range of computing
556 environments regardless of its use in feedback or non-feedback
557 modes. Its key setup time is excellent, and its key agility is
558 good. Rijndael's very low memory requirements make it very well
559 suited for restricted-space environments, in which it also
560 demonstrates excellent performance. Rijndael's operations are
561 among the easiest to defend against power and timing attacks.
563 The AES specifies three key sizes: 128, 192 and 256 bits
565 See <http://csrc.nist.gov/encryption/aes/> for more information.
567 In addition to AES cipher algorithm support, the
568 acceleration for some popular block cipher mode is supported
569 too, including ECB, CBC, CTR, LRW, PCBC, XTS.
572 tristate "Anubis cipher algorithm"
575 Anubis cipher algorithm.
577 Anubis is a variable key length cipher which can use keys from
578 128 bits to 320 bits in length. It was evaluated as a entrant
579 in the NESSIE competition.
582 <https://www.cosic.esat.kuleuven.ac.be/nessie/reports/>
583 <http://planeta.terra.com.br/informatica/paulobarreto/AnubisPage.html>
586 tristate "ARC4 cipher algorithm"
589 ARC4 cipher algorithm.
591 ARC4 is a stream cipher using keys ranging from 8 bits to 2048
592 bits in length. This algorithm is required for driver-based
593 WEP, but it should not be for other purposes because of the
594 weakness of the algorithm.
596 config CRYPTO_BLOWFISH
597 tristate "Blowfish cipher algorithm"
600 Blowfish cipher algorithm, by Bruce Schneier.
602 This is a variable key length cipher which can use keys from 32
603 bits to 448 bits in length. It's fast, simple and specifically
604 designed for use on "large microprocessors".
607 <http://www.schneier.com/blowfish.html>
609 config CRYPTO_CAMELLIA
610 tristate "Camellia cipher algorithms"
614 Camellia cipher algorithms module.
616 Camellia is a symmetric key block cipher developed jointly
617 at NTT and Mitsubishi Electric Corporation.
619 The Camellia specifies three key sizes: 128, 192 and 256 bits.
622 <https://info.isl.ntt.co.jp/crypt/eng/camellia/index_s.html>
625 tristate "CAST5 (CAST-128) cipher algorithm"
628 The CAST5 encryption algorithm (synonymous with CAST-128) is
629 described in RFC2144.
632 tristate "CAST6 (CAST-256) cipher algorithm"
635 The CAST6 encryption algorithm (synonymous with CAST-256) is
636 described in RFC2612.
639 tristate "DES and Triple DES EDE cipher algorithms"
642 DES cipher algorithm (FIPS 46-2), and Triple DES EDE (FIPS 46-3).
645 tristate "FCrypt cipher algorithm"
647 select CRYPTO_BLKCIPHER
649 FCrypt algorithm used by RxRPC.
652 tristate "Khazad cipher algorithm"
655 Khazad cipher algorithm.
657 Khazad was a finalist in the initial NESSIE competition. It is
658 an algorithm optimized for 64-bit processors with good performance
659 on 32-bit processors. Khazad uses an 128 bit key size.
662 <http://planeta.terra.com.br/informatica/paulobarreto/KhazadPage.html>
664 config CRYPTO_SALSA20
665 tristate "Salsa20 stream cipher algorithm (EXPERIMENTAL)"
666 depends on EXPERIMENTAL
667 select CRYPTO_BLKCIPHER
669 Salsa20 stream cipher algorithm.
671 Salsa20 is a stream cipher submitted to eSTREAM, the ECRYPT
672 Stream Cipher Project. See <http://www.ecrypt.eu.org/stream/>
674 The Salsa20 stream cipher algorithm is designed by Daniel J.
675 Bernstein <djb@cr.yp.to>. See <http://cr.yp.to/snuffle.html>
677 config CRYPTO_SALSA20_586
678 tristate "Salsa20 stream cipher algorithm (i586) (EXPERIMENTAL)"
679 depends on (X86 || UML_X86) && !64BIT
680 depends on EXPERIMENTAL
681 select CRYPTO_BLKCIPHER
683 Salsa20 stream cipher algorithm.
685 Salsa20 is a stream cipher submitted to eSTREAM, the ECRYPT
686 Stream Cipher Project. See <http://www.ecrypt.eu.org/stream/>
688 The Salsa20 stream cipher algorithm is designed by Daniel J.
689 Bernstein <djb@cr.yp.to>. See <http://cr.yp.to/snuffle.html>
691 config CRYPTO_SALSA20_X86_64
692 tristate "Salsa20 stream cipher algorithm (x86_64) (EXPERIMENTAL)"
693 depends on (X86 || UML_X86) && 64BIT
694 depends on EXPERIMENTAL
695 select CRYPTO_BLKCIPHER
697 Salsa20 stream cipher algorithm.
699 Salsa20 is a stream cipher submitted to eSTREAM, the ECRYPT
700 Stream Cipher Project. See <http://www.ecrypt.eu.org/stream/>
702 The Salsa20 stream cipher algorithm is designed by Daniel J.
703 Bernstein <djb@cr.yp.to>. See <http://cr.yp.to/snuffle.html>
706 tristate "SEED cipher algorithm"
709 SEED cipher algorithm (RFC4269).
711 SEED is a 128-bit symmetric key block cipher that has been
712 developed by KISA (Korea Information Security Agency) as a
713 national standard encryption algorithm of the Republic of Korea.
714 It is a 16 round block cipher with the key size of 128 bit.
717 <http://www.kisa.or.kr/kisa/seed/jsp/seed_eng.jsp>
719 config CRYPTO_SERPENT
720 tristate "Serpent cipher algorithm"
723 Serpent cipher algorithm, by Anderson, Biham & Knudsen.
725 Keys are allowed to be from 0 to 256 bits in length, in steps
726 of 8 bits. Also includes the 'Tnepres' algorithm, a reversed
727 variant of Serpent for compatibility with old kerneli.org code.
730 <http://www.cl.cam.ac.uk/~rja14/serpent.html>
733 tristate "TEA, XTEA and XETA cipher algorithms"
736 TEA cipher algorithm.
738 Tiny Encryption Algorithm is a simple cipher that uses
739 many rounds for security. It is very fast and uses
742 Xtendend Tiny Encryption Algorithm is a modification to
743 the TEA algorithm to address a potential key weakness
744 in the TEA algorithm.
746 Xtendend Encryption Tiny Algorithm is a mis-implementation
747 of the XTEA algorithm for compatibility purposes.
749 config CRYPTO_TWOFISH
750 tristate "Twofish cipher algorithm"
752 select CRYPTO_TWOFISH_COMMON
754 Twofish cipher algorithm.
756 Twofish was submitted as an AES (Advanced Encryption Standard)
757 candidate cipher by researchers at CounterPane Systems. It is a
758 16 round block cipher supporting key sizes of 128, 192, and 256
762 <http://www.schneier.com/twofish.html>
764 config CRYPTO_TWOFISH_COMMON
767 Common parts of the Twofish cipher algorithm shared by the
768 generic c and the assembler implementations.
770 config CRYPTO_TWOFISH_586
771 tristate "Twofish cipher algorithms (i586)"
772 depends on (X86 || UML_X86) && !64BIT
774 select CRYPTO_TWOFISH_COMMON
776 Twofish cipher algorithm.
778 Twofish was submitted as an AES (Advanced Encryption Standard)
779 candidate cipher by researchers at CounterPane Systems. It is a
780 16 round block cipher supporting key sizes of 128, 192, and 256
784 <http://www.schneier.com/twofish.html>
786 config CRYPTO_TWOFISH_X86_64
787 tristate "Twofish cipher algorithm (x86_64)"
788 depends on (X86 || UML_X86) && 64BIT
790 select CRYPTO_TWOFISH_COMMON
792 Twofish cipher algorithm (x86_64).
794 Twofish was submitted as an AES (Advanced Encryption Standard)
795 candidate cipher by researchers at CounterPane Systems. It is a
796 16 round block cipher supporting key sizes of 128, 192, and 256
800 <http://www.schneier.com/twofish.html>
802 comment "Compression"
804 config CRYPTO_DEFLATE
805 tristate "Deflate compression algorithm"
810 This is the Deflate algorithm (RFC1951), specified for use in
811 IPSec with the IPCOMP protocol (RFC3173, RFC2394).
813 You will most probably want this if using IPSec.
816 tristate "Zlib compression algorithm"
822 This is the zlib algorithm.
825 tristate "LZO compression algorithm"
828 select LZO_DECOMPRESS
830 This is the LZO algorithm.
832 comment "Random Number Generation"
834 config CRYPTO_ANSI_CPRNG
835 tristate "Pseudo Random Number Generation for Cryptographic modules"
840 This option enables the generic pseudo random number generator
841 for cryptographic modules. Uses the Algorithm specified in
842 ANSI X9.31 A.2.4. Note that this option must be enabled if
843 CRYPTO_FIPS is selected
845 source "drivers/crypto/Kconfig"