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
79 tristate "Cryptographic algorithm manager"
80 select CRYPTO_MANAGER2
82 Create default cryptographic template instantiations such as
85 config CRYPTO_MANAGER2
86 def_tristate CRYPTO_MANAGER || (CRYPTO_MANAGER!=n && CRYPTO_ALGAPI=y)
89 select CRYPTO_BLKCIPHER2
91 config CRYPTO_GF128MUL
92 tristate "GF(2^128) multiplication functions (EXPERIMENTAL)"
93 depends on EXPERIMENTAL
95 Efficient table driven implementation of multiplications in the
96 field GF(2^128). This is needed by some cypher modes. This
97 option will be selected automatically if you select such a
98 cipher mode. Only select this option by hand if you expect to load
99 an external module that requires these functions.
102 tristate "Null algorithms"
104 select CRYPTO_BLKCIPHER
107 These are 'Null' algorithms, used by IPsec, which do nothing.
109 config CRYPTO_WORKQUEUE
113 tristate "Software async crypto daemon"
114 select CRYPTO_BLKCIPHER
116 select CRYPTO_MANAGER
117 select CRYPTO_WORKQUEUE
119 This is a generic software asynchronous crypto daemon that
120 converts an arbitrary synchronous software crypto algorithm
121 into an asynchronous algorithm that executes in a kernel thread.
123 config CRYPTO_AUTHENC
124 tristate "Authenc support"
126 select CRYPTO_BLKCIPHER
127 select CRYPTO_MANAGER
130 Authenc: Combined mode wrapper for IPsec.
131 This is required for IPSec.
134 tristate "Testing module"
136 select CRYPTO_MANAGER
138 Quick & dirty crypto test module.
140 comment "Authenticated Encryption with Associated Data"
143 tristate "CCM support"
147 Support for Counter with CBC MAC. Required for IPsec.
150 tristate "GCM/GMAC support"
153 select CRYPTO_GF128MUL
155 Support for Galois/Counter Mode (GCM) and Galois Message
156 Authentication Code (GMAC). Required for IPSec.
159 tristate "Sequence Number IV Generator"
161 select CRYPTO_BLKCIPHER
164 This IV generator generates an IV based on a sequence number by
165 xoring it with a salt. This algorithm is mainly useful for CTR
167 comment "Block modes"
170 tristate "CBC support"
171 select CRYPTO_BLKCIPHER
172 select CRYPTO_MANAGER
174 CBC: Cipher Block Chaining mode
175 This block cipher algorithm is required for IPSec.
178 tristate "CTR support"
179 select CRYPTO_BLKCIPHER
181 select CRYPTO_MANAGER
184 This block cipher algorithm is required for IPSec.
187 tristate "CTS support"
188 select CRYPTO_BLKCIPHER
190 CTS: Cipher Text Stealing
191 This is the Cipher Text Stealing mode as described by
192 Section 8 of rfc2040 and referenced by rfc3962.
193 (rfc3962 includes errata information in its Appendix A)
194 This mode is required for Kerberos gss mechanism support
198 tristate "ECB support"
199 select CRYPTO_BLKCIPHER
200 select CRYPTO_MANAGER
202 ECB: Electronic CodeBook mode
203 This is the simplest block cipher algorithm. It simply encrypts
204 the input block by block.
207 tristate "LRW support (EXPERIMENTAL)"
208 depends on EXPERIMENTAL
209 select CRYPTO_BLKCIPHER
210 select CRYPTO_MANAGER
211 select CRYPTO_GF128MUL
213 LRW: Liskov Rivest Wagner, a tweakable, non malleable, non movable
214 narrow block cipher mode for dm-crypt. Use it with cipher
215 specification string aes-lrw-benbi, the key must be 256, 320 or 384.
216 The first 128, 192 or 256 bits in the key are used for AES and the
217 rest is used to tie each cipher block to its logical position.
220 tristate "PCBC support"
221 select CRYPTO_BLKCIPHER
222 select CRYPTO_MANAGER
224 PCBC: Propagating Cipher Block Chaining mode
225 This block cipher algorithm is required for RxRPC.
228 tristate "XTS support (EXPERIMENTAL)"
229 depends on EXPERIMENTAL
230 select CRYPTO_BLKCIPHER
231 select CRYPTO_MANAGER
232 select CRYPTO_GF128MUL
234 XTS: IEEE1619/D16 narrow block cipher use with aes-xts-plain,
235 key size 256, 384 or 512 bits. This implementation currently
236 can't handle a sectorsize which is not a multiple of 16 bytes.
241 tristate "HMAC support"
243 select CRYPTO_MANAGER
245 HMAC: Keyed-Hashing for Message Authentication (RFC2104).
246 This is required for IPSec.
249 tristate "XCBC support"
250 depends on EXPERIMENTAL
252 select CRYPTO_MANAGER
254 XCBC: Keyed-Hashing with encryption algorithm
255 http://www.ietf.org/rfc/rfc3566.txt
256 http://csrc.nist.gov/encryption/modes/proposedmodes/
257 xcbc-mac/xcbc-mac-spec.pdf
262 tristate "CRC32c CRC algorithm"
265 Castagnoli, et al Cyclic Redundancy-Check Algorithm. Used
266 by iSCSI for header and data digests and by others.
267 See Castagnoli93. Module will be crc32c.
269 config CRYPTO_CRC32C_INTEL
270 tristate "CRC32c INTEL hardware acceleration"
274 In Intel processor with SSE4.2 supported, the processor will
275 support CRC32C implementation using hardware accelerated CRC32
276 instruction. This option will create 'crc32c-intel' module,
277 which will enable any routine to use the CRC32 instruction to
278 gain performance compared with software implementation.
279 Module will be crc32c-intel.
282 tristate "MD4 digest algorithm"
285 MD4 message digest algorithm (RFC1320).
288 tristate "MD5 digest algorithm"
291 MD5 message digest algorithm (RFC1321).
293 config CRYPTO_MICHAEL_MIC
294 tristate "Michael MIC keyed digest algorithm"
297 Michael MIC is used for message integrity protection in TKIP
298 (IEEE 802.11i). This algorithm is required for TKIP, but it
299 should not be used for other purposes because of the weakness
303 tristate "RIPEMD-128 digest algorithm"
306 RIPEMD-128 (ISO/IEC 10118-3:2004).
308 RIPEMD-128 is a 128-bit cryptographic hash function. It should only
309 to be used as a secure replacement for RIPEMD. For other use cases
310 RIPEMD-160 should be used.
312 Developed by Hans Dobbertin, Antoon Bosselaers and Bart Preneel.
313 See <http://home.esat.kuleuven.be/~bosselae/ripemd160.html>
316 tristate "RIPEMD-160 digest algorithm"
319 RIPEMD-160 (ISO/IEC 10118-3:2004).
321 RIPEMD-160 is a 160-bit cryptographic hash function. It is intended
322 to be used as a secure replacement for the 128-bit hash functions
323 MD4, MD5 and it's predecessor RIPEMD
324 (not to be confused with RIPEMD-128).
326 It's speed is comparable to SHA1 and there are no known attacks
329 Developed by Hans Dobbertin, Antoon Bosselaers and Bart Preneel.
330 See <http://home.esat.kuleuven.be/~bosselae/ripemd160.html>
333 tristate "RIPEMD-256 digest algorithm"
336 RIPEMD-256 is an optional extension of RIPEMD-128 with a
337 256 bit hash. It is intended for applications that require
338 longer hash-results, without needing a larger security level
341 Developed by Hans Dobbertin, Antoon Bosselaers and Bart Preneel.
342 See <http://home.esat.kuleuven.be/~bosselae/ripemd160.html>
345 tristate "RIPEMD-320 digest algorithm"
348 RIPEMD-320 is an optional extension of RIPEMD-160 with a
349 320 bit hash. It is intended for applications that require
350 longer hash-results, without needing a larger security level
353 Developed by Hans Dobbertin, Antoon Bosselaers and Bart Preneel.
354 See <http://home.esat.kuleuven.be/~bosselae/ripemd160.html>
357 tristate "SHA1 digest algorithm"
360 SHA-1 secure hash standard (FIPS 180-1/DFIPS 180-2).
363 tristate "SHA224 and SHA256 digest algorithm"
366 SHA256 secure hash standard (DFIPS 180-2).
368 This version of SHA implements a 256 bit hash with 128 bits of
369 security against collision attacks.
371 This code also includes SHA-224, a 224 bit hash with 112 bits
372 of security against collision attacks.
375 tristate "SHA384 and SHA512 digest algorithms"
378 SHA512 secure hash standard (DFIPS 180-2).
380 This version of SHA implements a 512 bit hash with 256 bits of
381 security against collision attacks.
383 This code also includes SHA-384, a 384 bit hash with 192 bits
384 of security against collision attacks.
387 tristate "Tiger digest algorithms"
390 Tiger hash algorithm 192, 160 and 128-bit hashes
392 Tiger is a hash function optimized for 64-bit processors while
393 still having decent performance on 32-bit processors.
394 Tiger was developed by Ross Anderson and Eli Biham.
397 <http://www.cs.technion.ac.il/~biham/Reports/Tiger/>.
400 tristate "Whirlpool digest algorithms"
403 Whirlpool hash algorithm 512, 384 and 256-bit hashes
405 Whirlpool-512 is part of the NESSIE cryptographic primitives.
406 Whirlpool will be part of the ISO/IEC 10118-3:2003(E) standard
409 <http://planeta.terra.com.br/informatica/paulobarreto/WhirlpoolPage.html>
414 tristate "AES cipher algorithms"
417 AES cipher algorithms (FIPS-197). AES uses the Rijndael
420 Rijndael appears to be consistently a very good performer in
421 both hardware and software across a wide range of computing
422 environments regardless of its use in feedback or non-feedback
423 modes. Its key setup time is excellent, and its key agility is
424 good. Rijndael's very low memory requirements make it very well
425 suited for restricted-space environments, in which it also
426 demonstrates excellent performance. Rijndael's operations are
427 among the easiest to defend against power and timing attacks.
429 The AES specifies three key sizes: 128, 192 and 256 bits
431 See <http://csrc.nist.gov/CryptoToolkit/aes/> for more information.
433 config CRYPTO_AES_586
434 tristate "AES cipher algorithms (i586)"
435 depends on (X86 || UML_X86) && !64BIT
439 AES cipher algorithms (FIPS-197). AES uses the Rijndael
442 Rijndael appears to be consistently a very good performer in
443 both hardware and software across a wide range of computing
444 environments regardless of its use in feedback or non-feedback
445 modes. Its key setup time is excellent, and its key agility is
446 good. Rijndael's very low memory requirements make it very well
447 suited for restricted-space environments, in which it also
448 demonstrates excellent performance. Rijndael's operations are
449 among the easiest to defend against power and timing attacks.
451 The AES specifies three key sizes: 128, 192 and 256 bits
453 See <http://csrc.nist.gov/encryption/aes/> for more information.
455 config CRYPTO_AES_X86_64
456 tristate "AES cipher algorithms (x86_64)"
457 depends on (X86 || UML_X86) && 64BIT
461 AES cipher algorithms (FIPS-197). AES uses the Rijndael
464 Rijndael appears to be consistently a very good performer in
465 both hardware and software across a wide range of computing
466 environments regardless of its use in feedback or non-feedback
467 modes. Its key setup time is excellent, and its key agility is
468 good. Rijndael's very low memory requirements make it very well
469 suited for restricted-space environments, in which it also
470 demonstrates excellent performance. Rijndael's operations are
471 among the easiest to defend against power and timing attacks.
473 The AES specifies three key sizes: 128, 192 and 256 bits
475 See <http://csrc.nist.gov/encryption/aes/> for more information.
477 config CRYPTO_AES_NI_INTEL
478 tristate "AES cipher algorithms (AES-NI)"
479 depends on (X86 || UML_X86) && 64BIT
480 select CRYPTO_AES_X86_64
484 Use Intel AES-NI instructions for AES algorithm.
486 AES cipher algorithms (FIPS-197). AES uses the Rijndael
489 Rijndael appears to be consistently a very good performer in
490 both hardware and software across a wide range of computing
491 environments regardless of its use in feedback or non-feedback
492 modes. Its key setup time is excellent, and its key agility is
493 good. Rijndael's very low memory requirements make it very well
494 suited for restricted-space environments, in which it also
495 demonstrates excellent performance. Rijndael's operations are
496 among the easiest to defend against power and timing attacks.
498 The AES specifies three key sizes: 128, 192 and 256 bits
500 See <http://csrc.nist.gov/encryption/aes/> for more information.
503 tristate "Anubis cipher algorithm"
506 Anubis cipher algorithm.
508 Anubis is a variable key length cipher which can use keys from
509 128 bits to 320 bits in length. It was evaluated as a entrant
510 in the NESSIE competition.
513 <https://www.cosic.esat.kuleuven.ac.be/nessie/reports/>
514 <http://planeta.terra.com.br/informatica/paulobarreto/AnubisPage.html>
517 tristate "ARC4 cipher algorithm"
520 ARC4 cipher algorithm.
522 ARC4 is a stream cipher using keys ranging from 8 bits to 2048
523 bits in length. This algorithm is required for driver-based
524 WEP, but it should not be for other purposes because of the
525 weakness of the algorithm.
527 config CRYPTO_BLOWFISH
528 tristate "Blowfish cipher algorithm"
531 Blowfish cipher algorithm, by Bruce Schneier.
533 This is a variable key length cipher which can use keys from 32
534 bits to 448 bits in length. It's fast, simple and specifically
535 designed for use on "large microprocessors".
538 <http://www.schneier.com/blowfish.html>
540 config CRYPTO_CAMELLIA
541 tristate "Camellia cipher algorithms"
545 Camellia cipher algorithms module.
547 Camellia is a symmetric key block cipher developed jointly
548 at NTT and Mitsubishi Electric Corporation.
550 The Camellia specifies three key sizes: 128, 192 and 256 bits.
553 <https://info.isl.ntt.co.jp/crypt/eng/camellia/index_s.html>
556 tristate "CAST5 (CAST-128) cipher algorithm"
559 The CAST5 encryption algorithm (synonymous with CAST-128) is
560 described in RFC2144.
563 tristate "CAST6 (CAST-256) cipher algorithm"
566 The CAST6 encryption algorithm (synonymous with CAST-256) is
567 described in RFC2612.
570 tristate "DES and Triple DES EDE cipher algorithms"
573 DES cipher algorithm (FIPS 46-2), and Triple DES EDE (FIPS 46-3).
576 tristate "FCrypt cipher algorithm"
578 select CRYPTO_BLKCIPHER
580 FCrypt algorithm used by RxRPC.
583 tristate "Khazad cipher algorithm"
586 Khazad cipher algorithm.
588 Khazad was a finalist in the initial NESSIE competition. It is
589 an algorithm optimized for 64-bit processors with good performance
590 on 32-bit processors. Khazad uses an 128 bit key size.
593 <http://planeta.terra.com.br/informatica/paulobarreto/KhazadPage.html>
595 config CRYPTO_SALSA20
596 tristate "Salsa20 stream cipher algorithm (EXPERIMENTAL)"
597 depends on EXPERIMENTAL
598 select CRYPTO_BLKCIPHER
600 Salsa20 stream cipher algorithm.
602 Salsa20 is a stream cipher submitted to eSTREAM, the ECRYPT
603 Stream Cipher Project. See <http://www.ecrypt.eu.org/stream/>
605 The Salsa20 stream cipher algorithm is designed by Daniel J.
606 Bernstein <djb@cr.yp.to>. See <http://cr.yp.to/snuffle.html>
608 config CRYPTO_SALSA20_586
609 tristate "Salsa20 stream cipher algorithm (i586) (EXPERIMENTAL)"
610 depends on (X86 || UML_X86) && !64BIT
611 depends on EXPERIMENTAL
612 select CRYPTO_BLKCIPHER
614 Salsa20 stream cipher algorithm.
616 Salsa20 is a stream cipher submitted to eSTREAM, the ECRYPT
617 Stream Cipher Project. See <http://www.ecrypt.eu.org/stream/>
619 The Salsa20 stream cipher algorithm is designed by Daniel J.
620 Bernstein <djb@cr.yp.to>. See <http://cr.yp.to/snuffle.html>
622 config CRYPTO_SALSA20_X86_64
623 tristate "Salsa20 stream cipher algorithm (x86_64) (EXPERIMENTAL)"
624 depends on (X86 || UML_X86) && 64BIT
625 depends on EXPERIMENTAL
626 select CRYPTO_BLKCIPHER
628 Salsa20 stream cipher algorithm.
630 Salsa20 is a stream cipher submitted to eSTREAM, the ECRYPT
631 Stream Cipher Project. See <http://www.ecrypt.eu.org/stream/>
633 The Salsa20 stream cipher algorithm is designed by Daniel J.
634 Bernstein <djb@cr.yp.to>. See <http://cr.yp.to/snuffle.html>
637 tristate "SEED cipher algorithm"
640 SEED cipher algorithm (RFC4269).
642 SEED is a 128-bit symmetric key block cipher that has been
643 developed by KISA (Korea Information Security Agency) as a
644 national standard encryption algorithm of the Republic of Korea.
645 It is a 16 round block cipher with the key size of 128 bit.
648 <http://www.kisa.or.kr/kisa/seed/jsp/seed_eng.jsp>
650 config CRYPTO_SERPENT
651 tristate "Serpent cipher algorithm"
654 Serpent cipher algorithm, by Anderson, Biham & Knudsen.
656 Keys are allowed to be from 0 to 256 bits in length, in steps
657 of 8 bits. Also includes the 'Tnepres' algorithm, a reversed
658 variant of Serpent for compatibility with old kerneli.org code.
661 <http://www.cl.cam.ac.uk/~rja14/serpent.html>
664 tristate "TEA, XTEA and XETA cipher algorithms"
667 TEA cipher algorithm.
669 Tiny Encryption Algorithm is a simple cipher that uses
670 many rounds for security. It is very fast and uses
673 Xtendend Tiny Encryption Algorithm is a modification to
674 the TEA algorithm to address a potential key weakness
675 in the TEA algorithm.
677 Xtendend Encryption Tiny Algorithm is a mis-implementation
678 of the XTEA algorithm for compatibility purposes.
680 config CRYPTO_TWOFISH
681 tristate "Twofish cipher algorithm"
683 select CRYPTO_TWOFISH_COMMON
685 Twofish cipher algorithm.
687 Twofish was submitted as an AES (Advanced Encryption Standard)
688 candidate cipher by researchers at CounterPane Systems. It is a
689 16 round block cipher supporting key sizes of 128, 192, and 256
693 <http://www.schneier.com/twofish.html>
695 config CRYPTO_TWOFISH_COMMON
698 Common parts of the Twofish cipher algorithm shared by the
699 generic c and the assembler implementations.
701 config CRYPTO_TWOFISH_586
702 tristate "Twofish cipher algorithms (i586)"
703 depends on (X86 || UML_X86) && !64BIT
705 select CRYPTO_TWOFISH_COMMON
707 Twofish cipher algorithm.
709 Twofish was submitted as an AES (Advanced Encryption Standard)
710 candidate cipher by researchers at CounterPane Systems. It is a
711 16 round block cipher supporting key sizes of 128, 192, and 256
715 <http://www.schneier.com/twofish.html>
717 config CRYPTO_TWOFISH_X86_64
718 tristate "Twofish cipher algorithm (x86_64)"
719 depends on (X86 || UML_X86) && 64BIT
721 select CRYPTO_TWOFISH_COMMON
723 Twofish cipher algorithm (x86_64).
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 comment "Compression"
735 config CRYPTO_DEFLATE
736 tristate "Deflate compression algorithm"
741 This is the Deflate algorithm (RFC1951), specified for use in
742 IPSec with the IPCOMP protocol (RFC3173, RFC2394).
744 You will most probably want this if using IPSec.
747 tristate "LZO compression algorithm"
750 select LZO_DECOMPRESS
752 This is the LZO algorithm.
754 comment "Random Number Generation"
756 config CRYPTO_ANSI_CPRNG
757 tristate "Pseudo Random Number Generation for Cryptographic modules"
762 This option enables the generic pseudo random number generator
763 for cryptographic modules. Uses the Algorithm specified in
766 source "drivers/crypto/Kconfig"