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 requred 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
86 tristate "Cryptographic algorithm manager"
87 select CRYPTO_MANAGER2
89 Create default cryptographic template instantiations such as
92 config CRYPTO_MANAGER2
93 def_tristate CRYPTO_MANAGER || (CRYPTO_MANAGER!=n && CRYPTO_ALGAPI=y)
96 select CRYPTO_BLKCIPHER2
99 config CRYPTO_GF128MUL
100 tristate "GF(2^128) multiplication functions (EXPERIMENTAL)"
101 depends on EXPERIMENTAL
103 Efficient table driven implementation of multiplications in the
104 field GF(2^128). This is needed by some cypher modes. This
105 option will be selected automatically if you select such a
106 cipher mode. Only select this option by hand if you expect to load
107 an external module that requires these functions.
110 tristate "Null algorithms"
112 select CRYPTO_BLKCIPHER
115 These are 'Null' algorithms, used by IPsec, which do nothing.
117 config CRYPTO_WORKQUEUE
121 tristate "Software async crypto daemon"
122 select CRYPTO_BLKCIPHER
124 select CRYPTO_MANAGER
125 select CRYPTO_WORKQUEUE
127 This is a generic software asynchronous crypto daemon that
128 converts an arbitrary synchronous software crypto algorithm
129 into an asynchronous algorithm that executes in a kernel thread.
131 config CRYPTO_AUTHENC
132 tristate "Authenc support"
134 select CRYPTO_BLKCIPHER
135 select CRYPTO_MANAGER
138 Authenc: Combined mode wrapper for IPsec.
139 This is required for IPSec.
142 tristate "Testing module"
144 select CRYPTO_MANAGER
146 Quick & dirty crypto test module.
148 comment "Authenticated Encryption with Associated Data"
151 tristate "CCM support"
155 Support for Counter with CBC MAC. Required for IPsec.
158 tristate "GCM/GMAC support"
163 Support for Galois/Counter Mode (GCM) and Galois Message
164 Authentication Code (GMAC). Required for IPSec.
167 tristate "Sequence Number IV Generator"
169 select CRYPTO_BLKCIPHER
172 This IV generator generates an IV based on a sequence number by
173 xoring it with a salt. This algorithm is mainly useful for CTR
175 comment "Block modes"
178 tristate "CBC support"
179 select CRYPTO_BLKCIPHER
180 select CRYPTO_MANAGER
182 CBC: Cipher Block Chaining mode
183 This block cipher algorithm is required for IPSec.
186 tristate "CTR support"
187 select CRYPTO_BLKCIPHER
189 select CRYPTO_MANAGER
192 This block cipher algorithm is required for IPSec.
195 tristate "CTS support"
196 select CRYPTO_BLKCIPHER
198 CTS: Cipher Text Stealing
199 This is the Cipher Text Stealing mode as described by
200 Section 8 of rfc2040 and referenced by rfc3962.
201 (rfc3962 includes errata information in its Appendix A)
202 This mode is required for Kerberos gss mechanism support
206 tristate "ECB support"
207 select CRYPTO_BLKCIPHER
208 select CRYPTO_MANAGER
210 ECB: Electronic CodeBook mode
211 This is the simplest block cipher algorithm. It simply encrypts
212 the input block by block.
215 tristate "LRW support (EXPERIMENTAL)"
216 depends on EXPERIMENTAL
217 select CRYPTO_BLKCIPHER
218 select CRYPTO_MANAGER
219 select CRYPTO_GF128MUL
221 LRW: Liskov Rivest Wagner, a tweakable, non malleable, non movable
222 narrow block cipher mode for dm-crypt. Use it with cipher
223 specification string aes-lrw-benbi, the key must be 256, 320 or 384.
224 The first 128, 192 or 256 bits in the key are used for AES and the
225 rest is used to tie each cipher block to its logical position.
228 tristate "PCBC support"
229 select CRYPTO_BLKCIPHER
230 select CRYPTO_MANAGER
232 PCBC: Propagating Cipher Block Chaining mode
233 This block cipher algorithm is required for RxRPC.
236 tristate "XTS support (EXPERIMENTAL)"
237 depends on EXPERIMENTAL
238 select CRYPTO_BLKCIPHER
239 select CRYPTO_MANAGER
240 select CRYPTO_GF128MUL
242 XTS: IEEE1619/D16 narrow block cipher use with aes-xts-plain,
243 key size 256, 384 or 512 bits. This implementation currently
244 can't handle a sectorsize which is not a multiple of 16 bytes.
248 select CRYPTO_BLKCIPHER
249 select CRYPTO_MANAGER
254 tristate "HMAC support"
256 select CRYPTO_MANAGER
258 HMAC: Keyed-Hashing for Message Authentication (RFC2104).
259 This is required for IPSec.
262 tristate "XCBC support"
263 depends on EXPERIMENTAL
265 select CRYPTO_MANAGER
267 XCBC: Keyed-Hashing with encryption algorithm
268 http://www.ietf.org/rfc/rfc3566.txt
269 http://csrc.nist.gov/encryption/modes/proposedmodes/
270 xcbc-mac/xcbc-mac-spec.pdf
273 tristate "VMAC support"
274 depends on EXPERIMENTAL
276 select CRYPTO_MANAGER
278 VMAC is a message authentication algorithm designed for
279 very high speed on 64-bit architectures.
282 <http://fastcrypto.org/vmac>
287 tristate "CRC32c CRC algorithm"
290 Castagnoli, et al Cyclic Redundancy-Check Algorithm. Used
291 by iSCSI for header and data digests and by others.
292 See Castagnoli93. Module will be crc32c.
294 config CRYPTO_CRC32C_INTEL
295 tristate "CRC32c INTEL hardware acceleration"
299 In Intel processor with SSE4.2 supported, the processor will
300 support CRC32C implementation using hardware accelerated CRC32
301 instruction. This option will create 'crc32c-intel' module,
302 which will enable any routine to use the CRC32 instruction to
303 gain performance compared with software implementation.
304 Module will be crc32c-intel.
307 tristate "GHASH digest algorithm"
309 select CRYPTO_GF128MUL
311 GHASH is message digest algorithm for GCM (Galois/Counter Mode).
314 tristate "MD4 digest algorithm"
317 MD4 message digest algorithm (RFC1320).
320 tristate "MD5 digest algorithm"
323 MD5 message digest algorithm (RFC1321).
325 config CRYPTO_MICHAEL_MIC
326 tristate "Michael MIC keyed digest algorithm"
329 Michael MIC is used for message integrity protection in TKIP
330 (IEEE 802.11i). This algorithm is required for TKIP, but it
331 should not be used for other purposes because of the weakness
335 tristate "RIPEMD-128 digest algorithm"
338 RIPEMD-128 (ISO/IEC 10118-3:2004).
340 RIPEMD-128 is a 128-bit cryptographic hash function. It should only
341 to be used as a secure replacement for RIPEMD. For other use cases
342 RIPEMD-160 should be used.
344 Developed by Hans Dobbertin, Antoon Bosselaers and Bart Preneel.
345 See <http://home.esat.kuleuven.be/~bosselae/ripemd160.html>
348 tristate "RIPEMD-160 digest algorithm"
351 RIPEMD-160 (ISO/IEC 10118-3:2004).
353 RIPEMD-160 is a 160-bit cryptographic hash function. It is intended
354 to be used as a secure replacement for the 128-bit hash functions
355 MD4, MD5 and it's predecessor RIPEMD
356 (not to be confused with RIPEMD-128).
358 It's speed is comparable to SHA1 and there are no known attacks
361 Developed by Hans Dobbertin, Antoon Bosselaers and Bart Preneel.
362 See <http://home.esat.kuleuven.be/~bosselae/ripemd160.html>
365 tristate "RIPEMD-256 digest algorithm"
368 RIPEMD-256 is an optional extension of RIPEMD-128 with a
369 256 bit hash. It is intended for applications that require
370 longer hash-results, without needing a larger security level
373 Developed by Hans Dobbertin, Antoon Bosselaers and Bart Preneel.
374 See <http://home.esat.kuleuven.be/~bosselae/ripemd160.html>
377 tristate "RIPEMD-320 digest algorithm"
380 RIPEMD-320 is an optional extension of RIPEMD-160 with a
381 320 bit hash. It is intended for applications that require
382 longer hash-results, without needing a larger security level
385 Developed by Hans Dobbertin, Antoon Bosselaers and Bart Preneel.
386 See <http://home.esat.kuleuven.be/~bosselae/ripemd160.html>
389 tristate "SHA1 digest algorithm"
392 SHA-1 secure hash standard (FIPS 180-1/DFIPS 180-2).
395 tristate "SHA224 and SHA256 digest algorithm"
398 SHA256 secure hash standard (DFIPS 180-2).
400 This version of SHA implements a 256 bit hash with 128 bits of
401 security against collision attacks.
403 This code also includes SHA-224, a 224 bit hash with 112 bits
404 of security against collision attacks.
407 tristate "SHA384 and SHA512 digest algorithms"
410 SHA512 secure hash standard (DFIPS 180-2).
412 This version of SHA implements a 512 bit hash with 256 bits of
413 security against collision attacks.
415 This code also includes SHA-384, a 384 bit hash with 192 bits
416 of security against collision attacks.
419 tristate "Tiger digest algorithms"
422 Tiger hash algorithm 192, 160 and 128-bit hashes
424 Tiger is a hash function optimized for 64-bit processors while
425 still having decent performance on 32-bit processors.
426 Tiger was developed by Ross Anderson and Eli Biham.
429 <http://www.cs.technion.ac.il/~biham/Reports/Tiger/>.
432 tristate "Whirlpool digest algorithms"
435 Whirlpool hash algorithm 512, 384 and 256-bit hashes
437 Whirlpool-512 is part of the NESSIE cryptographic primitives.
438 Whirlpool will be part of the ISO/IEC 10118-3:2003(E) standard
441 <http://planeta.terra.com.br/informatica/paulobarreto/WhirlpoolPage.html>
443 config CRYPTO_GHASH_CLMUL_NI_INTEL
444 tristate "GHASH digest algorithm (CLMUL-NI accelerated)"
445 depends on (X86 || UML_X86) && 64BIT
449 GHASH is message digest algorithm for GCM (Galois/Counter Mode).
450 The implementation is accelerated by CLMUL-NI of Intel.
455 tristate "AES cipher algorithms"
458 AES cipher algorithms (FIPS-197). AES uses the Rijndael
461 Rijndael appears to be consistently a very good performer in
462 both hardware and software across a wide range of computing
463 environments regardless of its use in feedback or non-feedback
464 modes. Its key setup time is excellent, and its key agility is
465 good. Rijndael's very low memory requirements make it very well
466 suited for restricted-space environments, in which it also
467 demonstrates excellent performance. Rijndael's operations are
468 among the easiest to defend against power and timing attacks.
470 The AES specifies three key sizes: 128, 192 and 256 bits
472 See <http://csrc.nist.gov/CryptoToolkit/aes/> for more information.
474 config CRYPTO_AES_586
475 tristate "AES cipher algorithms (i586)"
476 depends on (X86 || UML_X86) && !64BIT
480 AES cipher algorithms (FIPS-197). AES uses the Rijndael
483 Rijndael appears to be consistently a very good performer in
484 both hardware and software across a wide range of computing
485 environments regardless of its use in feedback or non-feedback
486 modes. Its key setup time is excellent, and its key agility is
487 good. Rijndael's very low memory requirements make it very well
488 suited for restricted-space environments, in which it also
489 demonstrates excellent performance. Rijndael's operations are
490 among the easiest to defend against power and timing attacks.
492 The AES specifies three key sizes: 128, 192 and 256 bits
494 See <http://csrc.nist.gov/encryption/aes/> for more information.
496 config CRYPTO_AES_X86_64
497 tristate "AES cipher algorithms (x86_64)"
498 depends on (X86 || UML_X86) && 64BIT
502 AES cipher algorithms (FIPS-197). AES uses the Rijndael
505 Rijndael appears to be consistently a very good performer in
506 both hardware and software across a wide range of computing
507 environments regardless of its use in feedback or non-feedback
508 modes. Its key setup time is excellent, and its key agility is
509 good. Rijndael's very low memory requirements make it very well
510 suited for restricted-space environments, in which it also
511 demonstrates excellent performance. Rijndael's operations are
512 among the easiest to defend against power and timing attacks.
514 The AES specifies three key sizes: 128, 192 and 256 bits
516 See <http://csrc.nist.gov/encryption/aes/> for more information.
518 config CRYPTO_AES_NI_INTEL
519 tristate "AES cipher algorithms (AES-NI)"
520 depends on (X86 || UML_X86) && 64BIT
521 select CRYPTO_AES_X86_64
526 Use Intel AES-NI instructions for AES algorithm.
528 AES cipher algorithms (FIPS-197). AES uses the Rijndael
531 Rijndael appears to be consistently a very good performer in
532 both hardware and software across a wide range of computing
533 environments regardless of its use in feedback or non-feedback
534 modes. Its key setup time is excellent, and its key agility is
535 good. Rijndael's very low memory requirements make it very well
536 suited for restricted-space environments, in which it also
537 demonstrates excellent performance. Rijndael's operations are
538 among the easiest to defend against power and timing attacks.
540 The AES specifies three key sizes: 128, 192 and 256 bits
542 See <http://csrc.nist.gov/encryption/aes/> for more information.
544 In addition to AES cipher algorithm support, the
545 acceleration for some popular block cipher mode is supported
546 too, including ECB, CBC, CTR, LRW, PCBC, XTS.
549 tristate "Anubis cipher algorithm"
552 Anubis cipher algorithm.
554 Anubis is a variable key length cipher which can use keys from
555 128 bits to 320 bits in length. It was evaluated as a entrant
556 in the NESSIE competition.
559 <https://www.cosic.esat.kuleuven.ac.be/nessie/reports/>
560 <http://planeta.terra.com.br/informatica/paulobarreto/AnubisPage.html>
563 tristate "ARC4 cipher algorithm"
566 ARC4 cipher algorithm.
568 ARC4 is a stream cipher using keys ranging from 8 bits to 2048
569 bits in length. This algorithm is required for driver-based
570 WEP, but it should not be for other purposes because of the
571 weakness of the algorithm.
573 config CRYPTO_BLOWFISH
574 tristate "Blowfish cipher algorithm"
577 Blowfish cipher algorithm, by Bruce Schneier.
579 This is a variable key length cipher which can use keys from 32
580 bits to 448 bits in length. It's fast, simple and specifically
581 designed for use on "large microprocessors".
584 <http://www.schneier.com/blowfish.html>
586 config CRYPTO_CAMELLIA
587 tristate "Camellia cipher algorithms"
591 Camellia cipher algorithms module.
593 Camellia is a symmetric key block cipher developed jointly
594 at NTT and Mitsubishi Electric Corporation.
596 The Camellia specifies three key sizes: 128, 192 and 256 bits.
599 <https://info.isl.ntt.co.jp/crypt/eng/camellia/index_s.html>
602 tristate "CAST5 (CAST-128) cipher algorithm"
605 The CAST5 encryption algorithm (synonymous with CAST-128) is
606 described in RFC2144.
609 tristate "CAST6 (CAST-256) cipher algorithm"
612 The CAST6 encryption algorithm (synonymous with CAST-256) is
613 described in RFC2612.
616 tristate "DES and Triple DES EDE cipher algorithms"
619 DES cipher algorithm (FIPS 46-2), and Triple DES EDE (FIPS 46-3).
622 tristate "FCrypt cipher algorithm"
624 select CRYPTO_BLKCIPHER
626 FCrypt algorithm used by RxRPC.
629 tristate "Khazad cipher algorithm"
632 Khazad cipher algorithm.
634 Khazad was a finalist in the initial NESSIE competition. It is
635 an algorithm optimized for 64-bit processors with good performance
636 on 32-bit processors. Khazad uses an 128 bit key size.
639 <http://planeta.terra.com.br/informatica/paulobarreto/KhazadPage.html>
641 config CRYPTO_SALSA20
642 tristate "Salsa20 stream cipher algorithm (EXPERIMENTAL)"
643 depends on EXPERIMENTAL
644 select CRYPTO_BLKCIPHER
646 Salsa20 stream cipher algorithm.
648 Salsa20 is a stream cipher submitted to eSTREAM, the ECRYPT
649 Stream Cipher Project. See <http://www.ecrypt.eu.org/stream/>
651 The Salsa20 stream cipher algorithm is designed by Daniel J.
652 Bernstein <djb@cr.yp.to>. See <http://cr.yp.to/snuffle.html>
654 config CRYPTO_SALSA20_586
655 tristate "Salsa20 stream cipher algorithm (i586) (EXPERIMENTAL)"
656 depends on (X86 || UML_X86) && !64BIT
657 depends on EXPERIMENTAL
658 select CRYPTO_BLKCIPHER
660 Salsa20 stream cipher algorithm.
662 Salsa20 is a stream cipher submitted to eSTREAM, the ECRYPT
663 Stream Cipher Project. See <http://www.ecrypt.eu.org/stream/>
665 The Salsa20 stream cipher algorithm is designed by Daniel J.
666 Bernstein <djb@cr.yp.to>. See <http://cr.yp.to/snuffle.html>
668 config CRYPTO_SALSA20_X86_64
669 tristate "Salsa20 stream cipher algorithm (x86_64) (EXPERIMENTAL)"
670 depends on (X86 || UML_X86) && 64BIT
671 depends on EXPERIMENTAL
672 select CRYPTO_BLKCIPHER
674 Salsa20 stream cipher algorithm.
676 Salsa20 is a stream cipher submitted to eSTREAM, the ECRYPT
677 Stream Cipher Project. See <http://www.ecrypt.eu.org/stream/>
679 The Salsa20 stream cipher algorithm is designed by Daniel J.
680 Bernstein <djb@cr.yp.to>. See <http://cr.yp.to/snuffle.html>
683 tristate "SEED cipher algorithm"
686 SEED cipher algorithm (RFC4269).
688 SEED is a 128-bit symmetric key block cipher that has been
689 developed by KISA (Korea Information Security Agency) as a
690 national standard encryption algorithm of the Republic of Korea.
691 It is a 16 round block cipher with the key size of 128 bit.
694 <http://www.kisa.or.kr/kisa/seed/jsp/seed_eng.jsp>
696 config CRYPTO_SERPENT
697 tristate "Serpent cipher algorithm"
700 Serpent cipher algorithm, by Anderson, Biham & Knudsen.
702 Keys are allowed to be from 0 to 256 bits in length, in steps
703 of 8 bits. Also includes the 'Tnepres' algorithm, a reversed
704 variant of Serpent for compatibility with old kerneli.org code.
707 <http://www.cl.cam.ac.uk/~rja14/serpent.html>
710 tristate "TEA, XTEA and XETA cipher algorithms"
713 TEA cipher algorithm.
715 Tiny Encryption Algorithm is a simple cipher that uses
716 many rounds for security. It is very fast and uses
719 Xtendend Tiny Encryption Algorithm is a modification to
720 the TEA algorithm to address a potential key weakness
721 in the TEA algorithm.
723 Xtendend Encryption Tiny Algorithm is a mis-implementation
724 of the XTEA algorithm for compatibility purposes.
726 config CRYPTO_TWOFISH
727 tristate "Twofish cipher algorithm"
729 select CRYPTO_TWOFISH_COMMON
731 Twofish cipher algorithm.
733 Twofish was submitted as an AES (Advanced Encryption Standard)
734 candidate cipher by researchers at CounterPane Systems. It is a
735 16 round block cipher supporting key sizes of 128, 192, and 256
739 <http://www.schneier.com/twofish.html>
741 config CRYPTO_TWOFISH_COMMON
744 Common parts of the Twofish cipher algorithm shared by the
745 generic c and the assembler implementations.
747 config CRYPTO_TWOFISH_586
748 tristate "Twofish cipher algorithms (i586)"
749 depends on (X86 || UML_X86) && !64BIT
751 select CRYPTO_TWOFISH_COMMON
753 Twofish cipher algorithm.
755 Twofish was submitted as an AES (Advanced Encryption Standard)
756 candidate cipher by researchers at CounterPane Systems. It is a
757 16 round block cipher supporting key sizes of 128, 192, and 256
761 <http://www.schneier.com/twofish.html>
763 config CRYPTO_TWOFISH_X86_64
764 tristate "Twofish cipher algorithm (x86_64)"
765 depends on (X86 || UML_X86) && 64BIT
767 select CRYPTO_TWOFISH_COMMON
769 Twofish cipher algorithm (x86_64).
771 Twofish was submitted as an AES (Advanced Encryption Standard)
772 candidate cipher by researchers at CounterPane Systems. It is a
773 16 round block cipher supporting key sizes of 128, 192, and 256
777 <http://www.schneier.com/twofish.html>
779 comment "Compression"
781 config CRYPTO_DEFLATE
782 tristate "Deflate compression algorithm"
787 This is the Deflate algorithm (RFC1951), specified for use in
788 IPSec with the IPCOMP protocol (RFC3173, RFC2394).
790 You will most probably want this if using IPSec.
793 tristate "Zlib compression algorithm"
799 This is the zlib algorithm.
802 tristate "LZO compression algorithm"
805 select LZO_DECOMPRESS
807 This is the LZO algorithm.
809 comment "Random Number Generation"
811 config CRYPTO_ANSI_CPRNG
812 tristate "Pseudo Random Number Generation for Cryptographic modules"
817 This option enables the generic pseudo random number generator
818 for cryptographic modules. Uses the Algorithm specified in
819 ANSI X9.31 A.2.4. Not this option must be enabled if CRYPTO_FIPS
822 source "drivers/crypto/Kconfig"