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"
27 This options enables the fips boot option which is
28 required if you want to system to operate in a FIPS 200
29 certification. You should say no unless you know what
36 This option provides the API for cryptographic algorithms.
50 config CRYPTO_BLKCIPHER
52 select CRYPTO_BLKCIPHER2
55 config CRYPTO_BLKCIPHER2
59 select CRYPTO_WORKQUEUE
84 tristate "Cryptographic algorithm manager"
85 select CRYPTO_MANAGER2
87 Create default cryptographic template instantiations such as
90 config CRYPTO_MANAGER2
91 def_tristate CRYPTO_MANAGER || (CRYPTO_MANAGER!=n && CRYPTO_ALGAPI=y)
94 select CRYPTO_BLKCIPHER2
97 config CRYPTO_GF128MUL
98 tristate "GF(2^128) multiplication functions (EXPERIMENTAL)"
99 depends on EXPERIMENTAL
101 Efficient table driven implementation of multiplications in the
102 field GF(2^128). This is needed by some cypher modes. This
103 option will be selected automatically if you select such a
104 cipher mode. Only select this option by hand if you expect to load
105 an external module that requires these functions.
108 tristate "Null algorithms"
110 select CRYPTO_BLKCIPHER
113 These are 'Null' algorithms, used by IPsec, which do nothing.
115 config CRYPTO_WORKQUEUE
119 tristate "Software async crypto daemon"
120 select CRYPTO_BLKCIPHER
122 select CRYPTO_MANAGER
123 select CRYPTO_WORKQUEUE
125 This is a generic software asynchronous crypto daemon that
126 converts an arbitrary synchronous software crypto algorithm
127 into an asynchronous algorithm that executes in a kernel thread.
129 config CRYPTO_AUTHENC
130 tristate "Authenc support"
132 select CRYPTO_BLKCIPHER
133 select CRYPTO_MANAGER
136 Authenc: Combined mode wrapper for IPsec.
137 This is required for IPSec.
140 tristate "Testing module"
142 select CRYPTO_MANAGER
144 Quick & dirty crypto test module.
146 comment "Authenticated Encryption with Associated Data"
149 tristate "CCM support"
153 Support for Counter with CBC MAC. Required for IPsec.
156 tristate "GCM/GMAC support"
159 select CRYPTO_GF128MUL
161 Support for Galois/Counter Mode (GCM) and Galois Message
162 Authentication Code (GMAC). Required for IPSec.
165 tristate "Sequence Number IV Generator"
167 select CRYPTO_BLKCIPHER
170 This IV generator generates an IV based on a sequence number by
171 xoring it with a salt. This algorithm is mainly useful for CTR
173 comment "Block modes"
176 tristate "CBC support"
177 select CRYPTO_BLKCIPHER
178 select CRYPTO_MANAGER
180 CBC: Cipher Block Chaining mode
181 This block cipher algorithm is required for IPSec.
184 tristate "CTR support"
185 select CRYPTO_BLKCIPHER
187 select CRYPTO_MANAGER
190 This block cipher algorithm is required for IPSec.
193 tristate "CTS support"
194 select CRYPTO_BLKCIPHER
196 CTS: Cipher Text Stealing
197 This is the Cipher Text Stealing mode as described by
198 Section 8 of rfc2040 and referenced by rfc3962.
199 (rfc3962 includes errata information in its Appendix A)
200 This mode is required for Kerberos gss mechanism support
204 tristate "ECB support"
205 select CRYPTO_BLKCIPHER
206 select CRYPTO_MANAGER
208 ECB: Electronic CodeBook mode
209 This is the simplest block cipher algorithm. It simply encrypts
210 the input block by block.
213 tristate "LRW support (EXPERIMENTAL)"
214 depends on EXPERIMENTAL
215 select CRYPTO_BLKCIPHER
216 select CRYPTO_MANAGER
217 select CRYPTO_GF128MUL
219 LRW: Liskov Rivest Wagner, a tweakable, non malleable, non movable
220 narrow block cipher mode for dm-crypt. Use it with cipher
221 specification string aes-lrw-benbi, the key must be 256, 320 or 384.
222 The first 128, 192 or 256 bits in the key are used for AES and the
223 rest is used to tie each cipher block to its logical position.
226 tristate "PCBC support"
227 select CRYPTO_BLKCIPHER
228 select CRYPTO_MANAGER
230 PCBC: Propagating Cipher Block Chaining mode
231 This block cipher algorithm is required for RxRPC.
234 tristate "XTS support (EXPERIMENTAL)"
235 depends on EXPERIMENTAL
236 select CRYPTO_BLKCIPHER
237 select CRYPTO_MANAGER
238 select CRYPTO_GF128MUL
240 XTS: IEEE1619/D16 narrow block cipher use with aes-xts-plain,
241 key size 256, 384 or 512 bits. This implementation currently
242 can't handle a sectorsize which is not a multiple of 16 bytes.
246 select CRYPTO_BLKCIPHER
247 select CRYPTO_MANAGER
252 tristate "HMAC support"
254 select CRYPTO_MANAGER
256 HMAC: Keyed-Hashing for Message Authentication (RFC2104).
257 This is required for IPSec.
260 tristate "XCBC support"
261 depends on EXPERIMENTAL
263 select CRYPTO_MANAGER
265 XCBC: Keyed-Hashing with encryption algorithm
266 http://www.ietf.org/rfc/rfc3566.txt
267 http://csrc.nist.gov/encryption/modes/proposedmodes/
268 xcbc-mac/xcbc-mac-spec.pdf
273 tristate "CRC32c CRC algorithm"
276 Castagnoli, et al Cyclic Redundancy-Check Algorithm. Used
277 by iSCSI for header and data digests and by others.
278 See Castagnoli93. Module will be crc32c.
280 config CRYPTO_CRC32C_INTEL
281 tristate "CRC32c INTEL hardware acceleration"
285 In Intel processor with SSE4.2 supported, the processor will
286 support CRC32C implementation using hardware accelerated CRC32
287 instruction. This option will create 'crc32c-intel' module,
288 which will enable any routine to use the CRC32 instruction to
289 gain performance compared with software implementation.
290 Module will be crc32c-intel.
293 tristate "MD4 digest algorithm"
296 MD4 message digest algorithm (RFC1320).
299 tristate "MD5 digest algorithm"
302 MD5 message digest algorithm (RFC1321).
304 config CRYPTO_MICHAEL_MIC
305 tristate "Michael MIC keyed digest algorithm"
308 Michael MIC is used for message integrity protection in TKIP
309 (IEEE 802.11i). This algorithm is required for TKIP, but it
310 should not be used for other purposes because of the weakness
314 tristate "RIPEMD-128 digest algorithm"
317 RIPEMD-128 (ISO/IEC 10118-3:2004).
319 RIPEMD-128 is a 128-bit cryptographic hash function. It should only
320 to be used as a secure replacement for RIPEMD. For other use cases
321 RIPEMD-160 should be used.
323 Developed by Hans Dobbertin, Antoon Bosselaers and Bart Preneel.
324 See <http://home.esat.kuleuven.be/~bosselae/ripemd160.html>
327 tristate "RIPEMD-160 digest algorithm"
330 RIPEMD-160 (ISO/IEC 10118-3:2004).
332 RIPEMD-160 is a 160-bit cryptographic hash function. It is intended
333 to be used as a secure replacement for the 128-bit hash functions
334 MD4, MD5 and it's predecessor RIPEMD
335 (not to be confused with RIPEMD-128).
337 It's speed is comparable to SHA1 and there are no known attacks
340 Developed by Hans Dobbertin, Antoon Bosselaers and Bart Preneel.
341 See <http://home.esat.kuleuven.be/~bosselae/ripemd160.html>
344 tristate "RIPEMD-256 digest algorithm"
347 RIPEMD-256 is an optional extension of RIPEMD-128 with a
348 256 bit hash. It is intended for applications that require
349 longer hash-results, without needing a larger security level
352 Developed by Hans Dobbertin, Antoon Bosselaers and Bart Preneel.
353 See <http://home.esat.kuleuven.be/~bosselae/ripemd160.html>
356 tristate "RIPEMD-320 digest algorithm"
359 RIPEMD-320 is an optional extension of RIPEMD-160 with a
360 320 bit hash. It is intended for applications that require
361 longer hash-results, without needing a larger security level
364 Developed by Hans Dobbertin, Antoon Bosselaers and Bart Preneel.
365 See <http://home.esat.kuleuven.be/~bosselae/ripemd160.html>
368 tristate "SHA1 digest algorithm"
371 SHA-1 secure hash standard (FIPS 180-1/DFIPS 180-2).
374 tristate "SHA224 and SHA256 digest algorithm"
377 SHA256 secure hash standard (DFIPS 180-2).
379 This version of SHA implements a 256 bit hash with 128 bits of
380 security against collision attacks.
382 This code also includes SHA-224, a 224 bit hash with 112 bits
383 of security against collision attacks.
386 tristate "SHA384 and SHA512 digest algorithms"
389 SHA512 secure hash standard (DFIPS 180-2).
391 This version of SHA implements a 512 bit hash with 256 bits of
392 security against collision attacks.
394 This code also includes SHA-384, a 384 bit hash with 192 bits
395 of security against collision attacks.
398 tristate "Tiger digest algorithms"
401 Tiger hash algorithm 192, 160 and 128-bit hashes
403 Tiger is a hash function optimized for 64-bit processors while
404 still having decent performance on 32-bit processors.
405 Tiger was developed by Ross Anderson and Eli Biham.
408 <http://www.cs.technion.ac.il/~biham/Reports/Tiger/>.
411 tristate "Whirlpool digest algorithms"
414 Whirlpool hash algorithm 512, 384 and 256-bit hashes
416 Whirlpool-512 is part of the NESSIE cryptographic primitives.
417 Whirlpool will be part of the ISO/IEC 10118-3:2003(E) standard
420 <http://planeta.terra.com.br/informatica/paulobarreto/WhirlpoolPage.html>
425 tristate "AES cipher algorithms"
428 AES cipher algorithms (FIPS-197). AES uses the Rijndael
431 Rijndael appears to be consistently a very good performer in
432 both hardware and software across a wide range of computing
433 environments regardless of its use in feedback or non-feedback
434 modes. Its key setup time is excellent, and its key agility is
435 good. Rijndael's very low memory requirements make it very well
436 suited for restricted-space environments, in which it also
437 demonstrates excellent performance. Rijndael's operations are
438 among the easiest to defend against power and timing attacks.
440 The AES specifies three key sizes: 128, 192 and 256 bits
442 See <http://csrc.nist.gov/CryptoToolkit/aes/> for more information.
444 config CRYPTO_AES_586
445 tristate "AES cipher algorithms (i586)"
446 depends on (X86 || UML_X86) && !64BIT
450 AES cipher algorithms (FIPS-197). AES uses the Rijndael
453 Rijndael appears to be consistently a very good performer in
454 both hardware and software across a wide range of computing
455 environments regardless of its use in feedback or non-feedback
456 modes. Its key setup time is excellent, and its key agility is
457 good. Rijndael's very low memory requirements make it very well
458 suited for restricted-space environments, in which it also
459 demonstrates excellent performance. Rijndael's operations are
460 among the easiest to defend against power and timing attacks.
462 The AES specifies three key sizes: 128, 192 and 256 bits
464 See <http://csrc.nist.gov/encryption/aes/> for more information.
466 config CRYPTO_AES_X86_64
467 tristate "AES cipher algorithms (x86_64)"
468 depends on (X86 || UML_X86) && 64BIT
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/encryption/aes/> for more information.
488 config CRYPTO_AES_NI_INTEL
489 tristate "AES cipher algorithms (AES-NI)"
490 depends on (X86 || UML_X86) && 64BIT
491 select CRYPTO_AES_X86_64
496 Use Intel AES-NI instructions for AES algorithm.
498 AES cipher algorithms (FIPS-197). AES uses the Rijndael
501 Rijndael appears to be consistently a very good performer in
502 both hardware and software across a wide range of computing
503 environments regardless of its use in feedback or non-feedback
504 modes. Its key setup time is excellent, and its key agility is
505 good. Rijndael's very low memory requirements make it very well
506 suited for restricted-space environments, in which it also
507 demonstrates excellent performance. Rijndael's operations are
508 among the easiest to defend against power and timing attacks.
510 The AES specifies three key sizes: 128, 192 and 256 bits
512 See <http://csrc.nist.gov/encryption/aes/> for more information.
514 In addition to AES cipher algorithm support, the
515 acceleration for some popular block cipher mode is supported
516 too, including ECB, CBC, CTR, LRW, PCBC, XTS.
519 tristate "Anubis cipher algorithm"
522 Anubis cipher algorithm.
524 Anubis is a variable key length cipher which can use keys from
525 128 bits to 320 bits in length. It was evaluated as a entrant
526 in the NESSIE competition.
529 <https://www.cosic.esat.kuleuven.ac.be/nessie/reports/>
530 <http://planeta.terra.com.br/informatica/paulobarreto/AnubisPage.html>
533 tristate "ARC4 cipher algorithm"
536 ARC4 cipher algorithm.
538 ARC4 is a stream cipher using keys ranging from 8 bits to 2048
539 bits in length. This algorithm is required for driver-based
540 WEP, but it should not be for other purposes because of the
541 weakness of the algorithm.
543 config CRYPTO_BLOWFISH
544 tristate "Blowfish cipher algorithm"
547 Blowfish cipher algorithm, by Bruce Schneier.
549 This is a variable key length cipher which can use keys from 32
550 bits to 448 bits in length. It's fast, simple and specifically
551 designed for use on "large microprocessors".
554 <http://www.schneier.com/blowfish.html>
556 config CRYPTO_CAMELLIA
557 tristate "Camellia cipher algorithms"
561 Camellia cipher algorithms module.
563 Camellia is a symmetric key block cipher developed jointly
564 at NTT and Mitsubishi Electric Corporation.
566 The Camellia specifies three key sizes: 128, 192 and 256 bits.
569 <https://info.isl.ntt.co.jp/crypt/eng/camellia/index_s.html>
572 tristate "CAST5 (CAST-128) cipher algorithm"
575 The CAST5 encryption algorithm (synonymous with CAST-128) is
576 described in RFC2144.
579 tristate "CAST6 (CAST-256) cipher algorithm"
582 The CAST6 encryption algorithm (synonymous with CAST-256) is
583 described in RFC2612.
586 tristate "DES and Triple DES EDE cipher algorithms"
589 DES cipher algorithm (FIPS 46-2), and Triple DES EDE (FIPS 46-3).
592 tristate "FCrypt cipher algorithm"
594 select CRYPTO_BLKCIPHER
596 FCrypt algorithm used by RxRPC.
599 tristate "Khazad cipher algorithm"
602 Khazad cipher algorithm.
604 Khazad was a finalist in the initial NESSIE competition. It is
605 an algorithm optimized for 64-bit processors with good performance
606 on 32-bit processors. Khazad uses an 128 bit key size.
609 <http://planeta.terra.com.br/informatica/paulobarreto/KhazadPage.html>
611 config CRYPTO_SALSA20
612 tristate "Salsa20 stream cipher algorithm (EXPERIMENTAL)"
613 depends on EXPERIMENTAL
614 select CRYPTO_BLKCIPHER
616 Salsa20 stream cipher algorithm.
618 Salsa20 is a stream cipher submitted to eSTREAM, the ECRYPT
619 Stream Cipher Project. See <http://www.ecrypt.eu.org/stream/>
621 The Salsa20 stream cipher algorithm is designed by Daniel J.
622 Bernstein <djb@cr.yp.to>. See <http://cr.yp.to/snuffle.html>
624 config CRYPTO_SALSA20_586
625 tristate "Salsa20 stream cipher algorithm (i586) (EXPERIMENTAL)"
626 depends on (X86 || UML_X86) && !64BIT
627 depends on EXPERIMENTAL
628 select CRYPTO_BLKCIPHER
630 Salsa20 stream cipher algorithm.
632 Salsa20 is a stream cipher submitted to eSTREAM, the ECRYPT
633 Stream Cipher Project. See <http://www.ecrypt.eu.org/stream/>
635 The Salsa20 stream cipher algorithm is designed by Daniel J.
636 Bernstein <djb@cr.yp.to>. See <http://cr.yp.to/snuffle.html>
638 config CRYPTO_SALSA20_X86_64
639 tristate "Salsa20 stream cipher algorithm (x86_64) (EXPERIMENTAL)"
640 depends on (X86 || UML_X86) && 64BIT
641 depends on EXPERIMENTAL
642 select CRYPTO_BLKCIPHER
644 Salsa20 stream cipher algorithm.
646 Salsa20 is a stream cipher submitted to eSTREAM, the ECRYPT
647 Stream Cipher Project. See <http://www.ecrypt.eu.org/stream/>
649 The Salsa20 stream cipher algorithm is designed by Daniel J.
650 Bernstein <djb@cr.yp.to>. See <http://cr.yp.to/snuffle.html>
653 tristate "SEED cipher algorithm"
656 SEED cipher algorithm (RFC4269).
658 SEED is a 128-bit symmetric key block cipher that has been
659 developed by KISA (Korea Information Security Agency) as a
660 national standard encryption algorithm of the Republic of Korea.
661 It is a 16 round block cipher with the key size of 128 bit.
664 <http://www.kisa.or.kr/kisa/seed/jsp/seed_eng.jsp>
666 config CRYPTO_SERPENT
667 tristate "Serpent cipher algorithm"
670 Serpent cipher algorithm, by Anderson, Biham & Knudsen.
672 Keys are allowed to be from 0 to 256 bits in length, in steps
673 of 8 bits. Also includes the 'Tnepres' algorithm, a reversed
674 variant of Serpent for compatibility with old kerneli.org code.
677 <http://www.cl.cam.ac.uk/~rja14/serpent.html>
680 tristate "TEA, XTEA and XETA cipher algorithms"
683 TEA cipher algorithm.
685 Tiny Encryption Algorithm is a simple cipher that uses
686 many rounds for security. It is very fast and uses
689 Xtendend Tiny Encryption Algorithm is a modification to
690 the TEA algorithm to address a potential key weakness
691 in the TEA algorithm.
693 Xtendend Encryption Tiny Algorithm is a mis-implementation
694 of the XTEA algorithm for compatibility purposes.
696 config CRYPTO_TWOFISH
697 tristate "Twofish cipher algorithm"
699 select CRYPTO_TWOFISH_COMMON
701 Twofish cipher algorithm.
703 Twofish was submitted as an AES (Advanced Encryption Standard)
704 candidate cipher by researchers at CounterPane Systems. It is a
705 16 round block cipher supporting key sizes of 128, 192, and 256
709 <http://www.schneier.com/twofish.html>
711 config CRYPTO_TWOFISH_COMMON
714 Common parts of the Twofish cipher algorithm shared by the
715 generic c and the assembler implementations.
717 config CRYPTO_TWOFISH_586
718 tristate "Twofish cipher algorithms (i586)"
719 depends on (X86 || UML_X86) && !64BIT
721 select CRYPTO_TWOFISH_COMMON
723 Twofish cipher algorithm.
725 Twofish was submitted as an AES (Advanced Encryption Standard)
726 candidate cipher by researchers at CounterPane Systems. It is a
727 16 round block cipher supporting key sizes of 128, 192, and 256
731 <http://www.schneier.com/twofish.html>
733 config CRYPTO_TWOFISH_X86_64
734 tristate "Twofish cipher algorithm (x86_64)"
735 depends on (X86 || UML_X86) && 64BIT
737 select CRYPTO_TWOFISH_COMMON
739 Twofish cipher algorithm (x86_64).
741 Twofish was submitted as an AES (Advanced Encryption Standard)
742 candidate cipher by researchers at CounterPane Systems. It is a
743 16 round block cipher supporting key sizes of 128, 192, and 256
747 <http://www.schneier.com/twofish.html>
749 comment "Compression"
751 config CRYPTO_DEFLATE
752 tristate "Deflate compression algorithm"
757 This is the Deflate algorithm (RFC1951), specified for use in
758 IPSec with the IPCOMP protocol (RFC3173, RFC2394).
760 You will most probably want this if using IPSec.
763 tristate "Zlib compression algorithm"
769 This is the zlib algorithm.
772 tristate "LZO compression algorithm"
775 select LZO_DECOMPRESS
777 This is the LZO algorithm.
779 comment "Random Number Generation"
781 config CRYPTO_ANSI_CPRNG
782 tristate "Pseudo Random Number Generation for Cryptographic modules"
787 This option enables the generic pseudo random number generator
788 for cryptographic modules. Uses the Algorithm specified in
791 source "drivers/crypto/Kconfig"