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
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.
118 tristate "Parallel crypto engine (EXPERIMENTAL)"
119 depends on SMP && EXPERIMENTAL
121 select CRYPTO_MANAGER
124 This converts an arbitrary crypto algorithm into a parallel
125 algorithm that executes in kernel threads.
127 config CRYPTO_WORKQUEUE
131 tristate "Software async crypto daemon"
132 select CRYPTO_BLKCIPHER
134 select CRYPTO_MANAGER
135 select CRYPTO_WORKQUEUE
137 This is a generic software asynchronous crypto daemon that
138 converts an arbitrary synchronous software crypto algorithm
139 into an asynchronous algorithm that executes in a kernel thread.
141 config CRYPTO_AUTHENC
142 tristate "Authenc support"
144 select CRYPTO_BLKCIPHER
145 select CRYPTO_MANAGER
148 Authenc: Combined mode wrapper for IPsec.
149 This is required for IPSec.
152 tristate "Testing module"
154 select CRYPTO_MANAGER
156 Quick & dirty crypto test module.
158 comment "Authenticated Encryption with Associated Data"
161 tristate "CCM support"
165 Support for Counter with CBC MAC. Required for IPsec.
168 tristate "GCM/GMAC support"
173 Support for Galois/Counter Mode (GCM) and Galois Message
174 Authentication Code (GMAC). Required for IPSec.
177 tristate "Sequence Number IV Generator"
179 select CRYPTO_BLKCIPHER
182 This IV generator generates an IV based on a sequence number by
183 xoring it with a salt. This algorithm is mainly useful for CTR
185 comment "Block modes"
188 tristate "CBC support"
189 select CRYPTO_BLKCIPHER
190 select CRYPTO_MANAGER
192 CBC: Cipher Block Chaining mode
193 This block cipher algorithm is required for IPSec.
196 tristate "CTR support"
197 select CRYPTO_BLKCIPHER
199 select CRYPTO_MANAGER
202 This block cipher algorithm is required for IPSec.
205 tristate "CTS support"
206 select CRYPTO_BLKCIPHER
208 CTS: Cipher Text Stealing
209 This is the Cipher Text Stealing mode as described by
210 Section 8 of rfc2040 and referenced by rfc3962.
211 (rfc3962 includes errata information in its Appendix A)
212 This mode is required for Kerberos gss mechanism support
216 tristate "ECB support"
217 select CRYPTO_BLKCIPHER
218 select CRYPTO_MANAGER
220 ECB: Electronic CodeBook mode
221 This is the simplest block cipher algorithm. It simply encrypts
222 the input block by block.
225 tristate "LRW support (EXPERIMENTAL)"
226 depends on EXPERIMENTAL
227 select CRYPTO_BLKCIPHER
228 select CRYPTO_MANAGER
229 select CRYPTO_GF128MUL
231 LRW: Liskov Rivest Wagner, a tweakable, non malleable, non movable
232 narrow block cipher mode for dm-crypt. Use it with cipher
233 specification string aes-lrw-benbi, the key must be 256, 320 or 384.
234 The first 128, 192 or 256 bits in the key are used for AES and the
235 rest is used to tie each cipher block to its logical position.
238 tristate "PCBC support"
239 select CRYPTO_BLKCIPHER
240 select CRYPTO_MANAGER
242 PCBC: Propagating Cipher Block Chaining mode
243 This block cipher algorithm is required for RxRPC.
246 tristate "XTS support (EXPERIMENTAL)"
247 depends on EXPERIMENTAL
248 select CRYPTO_BLKCIPHER
249 select CRYPTO_MANAGER
250 select CRYPTO_GF128MUL
252 XTS: IEEE1619/D16 narrow block cipher use with aes-xts-plain,
253 key size 256, 384 or 512 bits. This implementation currently
254 can't handle a sectorsize which is not a multiple of 16 bytes.
258 select CRYPTO_BLKCIPHER
259 select CRYPTO_MANAGER
264 tristate "HMAC support"
266 select CRYPTO_MANAGER
268 HMAC: Keyed-Hashing for Message Authentication (RFC2104).
269 This is required for IPSec.
272 tristate "XCBC support"
273 depends on EXPERIMENTAL
275 select CRYPTO_MANAGER
277 XCBC: Keyed-Hashing with encryption algorithm
278 http://www.ietf.org/rfc/rfc3566.txt
279 http://csrc.nist.gov/encryption/modes/proposedmodes/
280 xcbc-mac/xcbc-mac-spec.pdf
283 tristate "VMAC support"
284 depends on EXPERIMENTAL
286 select CRYPTO_MANAGER
288 VMAC is a message authentication algorithm designed for
289 very high speed on 64-bit architectures.
292 <http://fastcrypto.org/vmac>
297 tristate "CRC32c CRC algorithm"
300 Castagnoli, et al Cyclic Redundancy-Check Algorithm. Used
301 by iSCSI for header and data digests and by others.
302 See Castagnoli93. Module will be crc32c.
304 config CRYPTO_CRC32C_INTEL
305 tristate "CRC32c INTEL hardware acceleration"
309 In Intel processor with SSE4.2 supported, the processor will
310 support CRC32C implementation using hardware accelerated CRC32
311 instruction. This option will create 'crc32c-intel' module,
312 which will enable any routine to use the CRC32 instruction to
313 gain performance compared with software implementation.
314 Module will be crc32c-intel.
317 tristate "GHASH digest algorithm"
319 select CRYPTO_GF128MUL
321 GHASH is message digest algorithm for GCM (Galois/Counter Mode).
324 tristate "MD4 digest algorithm"
327 MD4 message digest algorithm (RFC1320).
330 tristate "MD5 digest algorithm"
333 MD5 message digest algorithm (RFC1321).
335 config CRYPTO_MICHAEL_MIC
336 tristate "Michael MIC keyed digest algorithm"
339 Michael MIC is used for message integrity protection in TKIP
340 (IEEE 802.11i). This algorithm is required for TKIP, but it
341 should not be used for other purposes because of the weakness
345 tristate "RIPEMD-128 digest algorithm"
348 RIPEMD-128 (ISO/IEC 10118-3:2004).
350 RIPEMD-128 is a 128-bit cryptographic hash function. It should only
351 to be used as a secure replacement for RIPEMD. For other use cases
352 RIPEMD-160 should be used.
354 Developed by Hans Dobbertin, Antoon Bosselaers and Bart Preneel.
355 See <http://home.esat.kuleuven.be/~bosselae/ripemd160.html>
358 tristate "RIPEMD-160 digest algorithm"
361 RIPEMD-160 (ISO/IEC 10118-3:2004).
363 RIPEMD-160 is a 160-bit cryptographic hash function. It is intended
364 to be used as a secure replacement for the 128-bit hash functions
365 MD4, MD5 and it's predecessor RIPEMD
366 (not to be confused with RIPEMD-128).
368 It's speed is comparable to SHA1 and there are no known attacks
371 Developed by Hans Dobbertin, Antoon Bosselaers and Bart Preneel.
372 See <http://home.esat.kuleuven.be/~bosselae/ripemd160.html>
375 tristate "RIPEMD-256 digest algorithm"
378 RIPEMD-256 is an optional extension of RIPEMD-128 with a
379 256 bit hash. It is intended for applications that require
380 longer hash-results, without needing a larger security level
383 Developed by Hans Dobbertin, Antoon Bosselaers and Bart Preneel.
384 See <http://home.esat.kuleuven.be/~bosselae/ripemd160.html>
387 tristate "RIPEMD-320 digest algorithm"
390 RIPEMD-320 is an optional extension of RIPEMD-160 with a
391 320 bit hash. It is intended for applications that require
392 longer hash-results, without needing a larger security level
395 Developed by Hans Dobbertin, Antoon Bosselaers and Bart Preneel.
396 See <http://home.esat.kuleuven.be/~bosselae/ripemd160.html>
399 tristate "SHA1 digest algorithm"
402 SHA-1 secure hash standard (FIPS 180-1/DFIPS 180-2).
405 tristate "SHA224 and SHA256 digest algorithm"
408 SHA256 secure hash standard (DFIPS 180-2).
410 This version of SHA implements a 256 bit hash with 128 bits of
411 security against collision attacks.
413 This code also includes SHA-224, a 224 bit hash with 112 bits
414 of security against collision attacks.
417 tristate "SHA384 and SHA512 digest algorithms"
420 SHA512 secure hash standard (DFIPS 180-2).
422 This version of SHA implements a 512 bit hash with 256 bits of
423 security against collision attacks.
425 This code also includes SHA-384, a 384 bit hash with 192 bits
426 of security against collision attacks.
429 tristate "Tiger digest algorithms"
432 Tiger hash algorithm 192, 160 and 128-bit hashes
434 Tiger is a hash function optimized for 64-bit processors while
435 still having decent performance on 32-bit processors.
436 Tiger was developed by Ross Anderson and Eli Biham.
439 <http://www.cs.technion.ac.il/~biham/Reports/Tiger/>.
442 tristate "Whirlpool digest algorithms"
445 Whirlpool hash algorithm 512, 384 and 256-bit hashes
447 Whirlpool-512 is part of the NESSIE cryptographic primitives.
448 Whirlpool will be part of the ISO/IEC 10118-3:2003(E) standard
451 <http://planeta.terra.com.br/informatica/paulobarreto/WhirlpoolPage.html>
453 config CRYPTO_GHASH_CLMUL_NI_INTEL
454 tristate "GHASH digest algorithm (CLMUL-NI accelerated)"
455 depends on (X86 || UML_X86) && 64BIT
459 GHASH is message digest algorithm for GCM (Galois/Counter Mode).
460 The implementation is accelerated by CLMUL-NI of Intel.
465 tristate "AES cipher algorithms"
468 AES cipher algorithms (FIPS-197). AES uses the Rijndael
471 Rijndael appears to be consistently a very good performer in
472 both hardware and software across a wide range of computing
473 environments regardless of its use in feedback or non-feedback
474 modes. Its key setup time is excellent, and its key agility is
475 good. Rijndael's very low memory requirements make it very well
476 suited for restricted-space environments, in which it also
477 demonstrates excellent performance. Rijndael's operations are
478 among the easiest to defend against power and timing attacks.
480 The AES specifies three key sizes: 128, 192 and 256 bits
482 See <http://csrc.nist.gov/CryptoToolkit/aes/> for more information.
484 config CRYPTO_AES_586
485 tristate "AES cipher algorithms (i586)"
486 depends on (X86 || UML_X86) && !64BIT
490 AES cipher algorithms (FIPS-197). AES uses the Rijndael
493 Rijndael appears to be consistently a very good performer in
494 both hardware and software across a wide range of computing
495 environments regardless of its use in feedback or non-feedback
496 modes. Its key setup time is excellent, and its key agility is
497 good. Rijndael's very low memory requirements make it very well
498 suited for restricted-space environments, in which it also
499 demonstrates excellent performance. Rijndael's operations are
500 among the easiest to defend against power and timing attacks.
502 The AES specifies three key sizes: 128, 192 and 256 bits
504 See <http://csrc.nist.gov/encryption/aes/> for more information.
506 config CRYPTO_AES_X86_64
507 tristate "AES cipher algorithms (x86_64)"
508 depends on (X86 || UML_X86) && 64BIT
512 AES cipher algorithms (FIPS-197). AES uses the Rijndael
515 Rijndael appears to be consistently a very good performer in
516 both hardware and software across a wide range of computing
517 environments regardless of its use in feedback or non-feedback
518 modes. Its key setup time is excellent, and its key agility is
519 good. Rijndael's very low memory requirements make it very well
520 suited for restricted-space environments, in which it also
521 demonstrates excellent performance. Rijndael's operations are
522 among the easiest to defend against power and timing attacks.
524 The AES specifies three key sizes: 128, 192 and 256 bits
526 See <http://csrc.nist.gov/encryption/aes/> for more information.
528 config CRYPTO_AES_NI_INTEL
529 tristate "AES cipher algorithms (AES-NI)"
530 depends on (X86 || UML_X86) && 64BIT
531 select CRYPTO_AES_X86_64
536 Use Intel AES-NI instructions for AES algorithm.
538 AES cipher algorithms (FIPS-197). AES uses the Rijndael
541 Rijndael appears to be consistently a very good performer in
542 both hardware and software across a wide range of computing
543 environments regardless of its use in feedback or non-feedback
544 modes. Its key setup time is excellent, and its key agility is
545 good. Rijndael's very low memory requirements make it very well
546 suited for restricted-space environments, in which it also
547 demonstrates excellent performance. Rijndael's operations are
548 among the easiest to defend against power and timing attacks.
550 The AES specifies three key sizes: 128, 192 and 256 bits
552 See <http://csrc.nist.gov/encryption/aes/> for more information.
554 In addition to AES cipher algorithm support, the
555 acceleration for some popular block cipher mode is supported
556 too, including ECB, CBC, CTR, LRW, PCBC, XTS.
559 tristate "Anubis cipher algorithm"
562 Anubis cipher algorithm.
564 Anubis is a variable key length cipher which can use keys from
565 128 bits to 320 bits in length. It was evaluated as a entrant
566 in the NESSIE competition.
569 <https://www.cosic.esat.kuleuven.ac.be/nessie/reports/>
570 <http://planeta.terra.com.br/informatica/paulobarreto/AnubisPage.html>
573 tristate "ARC4 cipher algorithm"
576 ARC4 cipher algorithm.
578 ARC4 is a stream cipher using keys ranging from 8 bits to 2048
579 bits in length. This algorithm is required for driver-based
580 WEP, but it should not be for other purposes because of the
581 weakness of the algorithm.
583 config CRYPTO_BLOWFISH
584 tristate "Blowfish cipher algorithm"
587 Blowfish cipher algorithm, by Bruce Schneier.
589 This is a variable key length cipher which can use keys from 32
590 bits to 448 bits in length. It's fast, simple and specifically
591 designed for use on "large microprocessors".
594 <http://www.schneier.com/blowfish.html>
596 config CRYPTO_CAMELLIA
597 tristate "Camellia cipher algorithms"
601 Camellia cipher algorithms module.
603 Camellia is a symmetric key block cipher developed jointly
604 at NTT and Mitsubishi Electric Corporation.
606 The Camellia specifies three key sizes: 128, 192 and 256 bits.
609 <https://info.isl.ntt.co.jp/crypt/eng/camellia/index_s.html>
612 tristate "CAST5 (CAST-128) cipher algorithm"
615 The CAST5 encryption algorithm (synonymous with CAST-128) is
616 described in RFC2144.
619 tristate "CAST6 (CAST-256) cipher algorithm"
622 The CAST6 encryption algorithm (synonymous with CAST-256) is
623 described in RFC2612.
626 tristate "DES and Triple DES EDE cipher algorithms"
629 DES cipher algorithm (FIPS 46-2), and Triple DES EDE (FIPS 46-3).
632 tristate "FCrypt cipher algorithm"
634 select CRYPTO_BLKCIPHER
636 FCrypt algorithm used by RxRPC.
639 tristate "Khazad cipher algorithm"
642 Khazad cipher algorithm.
644 Khazad was a finalist in the initial NESSIE competition. It is
645 an algorithm optimized for 64-bit processors with good performance
646 on 32-bit processors. Khazad uses an 128 bit key size.
649 <http://planeta.terra.com.br/informatica/paulobarreto/KhazadPage.html>
651 config CRYPTO_SALSA20
652 tristate "Salsa20 stream cipher algorithm (EXPERIMENTAL)"
653 depends on EXPERIMENTAL
654 select CRYPTO_BLKCIPHER
656 Salsa20 stream cipher algorithm.
658 Salsa20 is a stream cipher submitted to eSTREAM, the ECRYPT
659 Stream Cipher Project. See <http://www.ecrypt.eu.org/stream/>
661 The Salsa20 stream cipher algorithm is designed by Daniel J.
662 Bernstein <djb@cr.yp.to>. See <http://cr.yp.to/snuffle.html>
664 config CRYPTO_SALSA20_586
665 tristate "Salsa20 stream cipher algorithm (i586) (EXPERIMENTAL)"
666 depends on (X86 || UML_X86) && !64BIT
667 depends on EXPERIMENTAL
668 select CRYPTO_BLKCIPHER
670 Salsa20 stream cipher algorithm.
672 Salsa20 is a stream cipher submitted to eSTREAM, the ECRYPT
673 Stream Cipher Project. See <http://www.ecrypt.eu.org/stream/>
675 The Salsa20 stream cipher algorithm is designed by Daniel J.
676 Bernstein <djb@cr.yp.to>. See <http://cr.yp.to/snuffle.html>
678 config CRYPTO_SALSA20_X86_64
679 tristate "Salsa20 stream cipher algorithm (x86_64) (EXPERIMENTAL)"
680 depends on (X86 || UML_X86) && 64BIT
681 depends on EXPERIMENTAL
682 select CRYPTO_BLKCIPHER
684 Salsa20 stream cipher algorithm.
686 Salsa20 is a stream cipher submitted to eSTREAM, the ECRYPT
687 Stream Cipher Project. See <http://www.ecrypt.eu.org/stream/>
689 The Salsa20 stream cipher algorithm is designed by Daniel J.
690 Bernstein <djb@cr.yp.to>. See <http://cr.yp.to/snuffle.html>
693 tristate "SEED cipher algorithm"
696 SEED cipher algorithm (RFC4269).
698 SEED is a 128-bit symmetric key block cipher that has been
699 developed by KISA (Korea Information Security Agency) as a
700 national standard encryption algorithm of the Republic of Korea.
701 It is a 16 round block cipher with the key size of 128 bit.
704 <http://www.kisa.or.kr/kisa/seed/jsp/seed_eng.jsp>
706 config CRYPTO_SERPENT
707 tristate "Serpent cipher algorithm"
710 Serpent cipher algorithm, by Anderson, Biham & Knudsen.
712 Keys are allowed to be from 0 to 256 bits in length, in steps
713 of 8 bits. Also includes the 'Tnepres' algorithm, a reversed
714 variant of Serpent for compatibility with old kerneli.org code.
717 <http://www.cl.cam.ac.uk/~rja14/serpent.html>
720 tristate "TEA, XTEA and XETA cipher algorithms"
723 TEA cipher algorithm.
725 Tiny Encryption Algorithm is a simple cipher that uses
726 many rounds for security. It is very fast and uses
729 Xtendend Tiny Encryption Algorithm is a modification to
730 the TEA algorithm to address a potential key weakness
731 in the TEA algorithm.
733 Xtendend Encryption Tiny Algorithm is a mis-implementation
734 of the XTEA algorithm for compatibility purposes.
736 config CRYPTO_TWOFISH
737 tristate "Twofish cipher algorithm"
739 select CRYPTO_TWOFISH_COMMON
741 Twofish cipher algorithm.
743 Twofish was submitted as an AES (Advanced Encryption Standard)
744 candidate cipher by researchers at CounterPane Systems. It is a
745 16 round block cipher supporting key sizes of 128, 192, and 256
749 <http://www.schneier.com/twofish.html>
751 config CRYPTO_TWOFISH_COMMON
754 Common parts of the Twofish cipher algorithm shared by the
755 generic c and the assembler implementations.
757 config CRYPTO_TWOFISH_586
758 tristate "Twofish cipher algorithms (i586)"
759 depends on (X86 || UML_X86) && !64BIT
761 select CRYPTO_TWOFISH_COMMON
763 Twofish cipher algorithm.
765 Twofish was submitted as an AES (Advanced Encryption Standard)
766 candidate cipher by researchers at CounterPane Systems. It is a
767 16 round block cipher supporting key sizes of 128, 192, and 256
771 <http://www.schneier.com/twofish.html>
773 config CRYPTO_TWOFISH_X86_64
774 tristate "Twofish cipher algorithm (x86_64)"
775 depends on (X86 || UML_X86) && 64BIT
777 select CRYPTO_TWOFISH_COMMON
779 Twofish cipher algorithm (x86_64).
781 Twofish was submitted as an AES (Advanced Encryption Standard)
782 candidate cipher by researchers at CounterPane Systems. It is a
783 16 round block cipher supporting key sizes of 128, 192, and 256
787 <http://www.schneier.com/twofish.html>
789 comment "Compression"
791 config CRYPTO_DEFLATE
792 tristate "Deflate compression algorithm"
797 This is the Deflate algorithm (RFC1951), specified for use in
798 IPSec with the IPCOMP protocol (RFC3173, RFC2394).
800 You will most probably want this if using IPSec.
803 tristate "Zlib compression algorithm"
809 This is the zlib algorithm.
812 tristate "LZO compression algorithm"
815 select LZO_DECOMPRESS
817 This is the LZO algorithm.
819 comment "Random Number Generation"
821 config CRYPTO_ANSI_CPRNG
822 tristate "Pseudo Random Number Generation for Cryptographic modules"
827 This option enables the generic pseudo random number generator
828 for cryptographic modules. Uses the Algorithm specified in
829 ANSI X9.31 A.2.4. Note that this option must be enabled if
830 CRYPTO_FIPS is selected
832 source "drivers/crypto/Kconfig"