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.
247 tristate "HMAC support"
249 select CRYPTO_MANAGER
251 HMAC: Keyed-Hashing for Message Authentication (RFC2104).
252 This is required for IPSec.
255 tristate "XCBC support"
256 depends on EXPERIMENTAL
258 select CRYPTO_MANAGER
260 XCBC: Keyed-Hashing with encryption algorithm
261 http://www.ietf.org/rfc/rfc3566.txt
262 http://csrc.nist.gov/encryption/modes/proposedmodes/
263 xcbc-mac/xcbc-mac-spec.pdf
268 tristate "CRC32c CRC algorithm"
271 Castagnoli, et al Cyclic Redundancy-Check Algorithm. Used
272 by iSCSI for header and data digests and by others.
273 See Castagnoli93. Module will be crc32c.
275 config CRYPTO_CRC32C_INTEL
276 tristate "CRC32c INTEL hardware acceleration"
280 In Intel processor with SSE4.2 supported, the processor will
281 support CRC32C implementation using hardware accelerated CRC32
282 instruction. This option will create 'crc32c-intel' module,
283 which will enable any routine to use the CRC32 instruction to
284 gain performance compared with software implementation.
285 Module will be crc32c-intel.
288 tristate "MD4 digest algorithm"
291 MD4 message digest algorithm (RFC1320).
294 tristate "MD5 digest algorithm"
297 MD5 message digest algorithm (RFC1321).
299 config CRYPTO_MICHAEL_MIC
300 tristate "Michael MIC keyed digest algorithm"
303 Michael MIC is used for message integrity protection in TKIP
304 (IEEE 802.11i). This algorithm is required for TKIP, but it
305 should not be used for other purposes because of the weakness
309 tristate "RIPEMD-128 digest algorithm"
312 RIPEMD-128 (ISO/IEC 10118-3:2004).
314 RIPEMD-128 is a 128-bit cryptographic hash function. It should only
315 to be used as a secure replacement for RIPEMD. For other use cases
316 RIPEMD-160 should be used.
318 Developed by Hans Dobbertin, Antoon Bosselaers and Bart Preneel.
319 See <http://home.esat.kuleuven.be/~bosselae/ripemd160.html>
322 tristate "RIPEMD-160 digest algorithm"
325 RIPEMD-160 (ISO/IEC 10118-3:2004).
327 RIPEMD-160 is a 160-bit cryptographic hash function. It is intended
328 to be used as a secure replacement for the 128-bit hash functions
329 MD4, MD5 and it's predecessor RIPEMD
330 (not to be confused with RIPEMD-128).
332 It's speed is comparable to SHA1 and there are no known attacks
335 Developed by Hans Dobbertin, Antoon Bosselaers and Bart Preneel.
336 See <http://home.esat.kuleuven.be/~bosselae/ripemd160.html>
339 tristate "RIPEMD-256 digest algorithm"
342 RIPEMD-256 is an optional extension of RIPEMD-128 with a
343 256 bit hash. It is intended for applications that require
344 longer hash-results, without needing a larger security level
347 Developed by Hans Dobbertin, Antoon Bosselaers and Bart Preneel.
348 See <http://home.esat.kuleuven.be/~bosselae/ripemd160.html>
351 tristate "RIPEMD-320 digest algorithm"
354 RIPEMD-320 is an optional extension of RIPEMD-160 with a
355 320 bit hash. It is intended for applications that require
356 longer hash-results, without needing a larger security level
359 Developed by Hans Dobbertin, Antoon Bosselaers and Bart Preneel.
360 See <http://home.esat.kuleuven.be/~bosselae/ripemd160.html>
363 tristate "SHA1 digest algorithm"
366 SHA-1 secure hash standard (FIPS 180-1/DFIPS 180-2).
369 tristate "SHA224 and SHA256 digest algorithm"
372 SHA256 secure hash standard (DFIPS 180-2).
374 This version of SHA implements a 256 bit hash with 128 bits of
375 security against collision attacks.
377 This code also includes SHA-224, a 224 bit hash with 112 bits
378 of security against collision attacks.
381 tristate "SHA384 and SHA512 digest algorithms"
384 SHA512 secure hash standard (DFIPS 180-2).
386 This version of SHA implements a 512 bit hash with 256 bits of
387 security against collision attacks.
389 This code also includes SHA-384, a 384 bit hash with 192 bits
390 of security against collision attacks.
393 tristate "Tiger digest algorithms"
396 Tiger hash algorithm 192, 160 and 128-bit hashes
398 Tiger is a hash function optimized for 64-bit processors while
399 still having decent performance on 32-bit processors.
400 Tiger was developed by Ross Anderson and Eli Biham.
403 <http://www.cs.technion.ac.il/~biham/Reports/Tiger/>.
406 tristate "Whirlpool digest algorithms"
409 Whirlpool hash algorithm 512, 384 and 256-bit hashes
411 Whirlpool-512 is part of the NESSIE cryptographic primitives.
412 Whirlpool will be part of the ISO/IEC 10118-3:2003(E) standard
415 <http://planeta.terra.com.br/informatica/paulobarreto/WhirlpoolPage.html>
420 tristate "AES cipher algorithms"
423 AES cipher algorithms (FIPS-197). AES uses the Rijndael
426 Rijndael appears to be consistently a very good performer in
427 both hardware and software across a wide range of computing
428 environments regardless of its use in feedback or non-feedback
429 modes. Its key setup time is excellent, and its key agility is
430 good. Rijndael's very low memory requirements make it very well
431 suited for restricted-space environments, in which it also
432 demonstrates excellent performance. Rijndael's operations are
433 among the easiest to defend against power and timing attacks.
435 The AES specifies three key sizes: 128, 192 and 256 bits
437 See <http://csrc.nist.gov/CryptoToolkit/aes/> for more information.
439 config CRYPTO_AES_586
440 tristate "AES cipher algorithms (i586)"
441 depends on (X86 || UML_X86) && !64BIT
445 AES cipher algorithms (FIPS-197). AES uses the Rijndael
448 Rijndael appears to be consistently a very good performer in
449 both hardware and software across a wide range of computing
450 environments regardless of its use in feedback or non-feedback
451 modes. Its key setup time is excellent, and its key agility is
452 good. Rijndael's very low memory requirements make it very well
453 suited for restricted-space environments, in which it also
454 demonstrates excellent performance. Rijndael's operations are
455 among the easiest to defend against power and timing attacks.
457 The AES specifies three key sizes: 128, 192 and 256 bits
459 See <http://csrc.nist.gov/encryption/aes/> for more information.
461 config CRYPTO_AES_X86_64
462 tristate "AES cipher algorithms (x86_64)"
463 depends on (X86 || UML_X86) && 64BIT
467 AES cipher algorithms (FIPS-197). AES uses the Rijndael
470 Rijndael appears to be consistently a very good performer in
471 both hardware and software across a wide range of computing
472 environments regardless of its use in feedback or non-feedback
473 modes. Its key setup time is excellent, and its key agility is
474 good. Rijndael's very low memory requirements make it very well
475 suited for restricted-space environments, in which it also
476 demonstrates excellent performance. Rijndael's operations are
477 among the easiest to defend against power and timing attacks.
479 The AES specifies three key sizes: 128, 192 and 256 bits
481 See <http://csrc.nist.gov/encryption/aes/> for more information.
483 config CRYPTO_AES_NI_INTEL
484 tristate "AES cipher algorithms (AES-NI)"
485 depends on (X86 || UML_X86) && 64BIT
486 select CRYPTO_AES_X86_64
490 Use Intel AES-NI instructions for AES algorithm.
492 AES cipher algorithms (FIPS-197). AES uses the Rijndael
495 Rijndael appears to be consistently a very good performer in
496 both hardware and software across a wide range of computing
497 environments regardless of its use in feedback or non-feedback
498 modes. Its key setup time is excellent, and its key agility is
499 good. Rijndael's very low memory requirements make it very well
500 suited for restricted-space environments, in which it also
501 demonstrates excellent performance. Rijndael's operations are
502 among the easiest to defend against power and timing attacks.
504 The AES specifies three key sizes: 128, 192 and 256 bits
506 See <http://csrc.nist.gov/encryption/aes/> for more information.
509 tristate "Anubis cipher algorithm"
512 Anubis cipher algorithm.
514 Anubis is a variable key length cipher which can use keys from
515 128 bits to 320 bits in length. It was evaluated as a entrant
516 in the NESSIE competition.
519 <https://www.cosic.esat.kuleuven.ac.be/nessie/reports/>
520 <http://planeta.terra.com.br/informatica/paulobarreto/AnubisPage.html>
523 tristate "ARC4 cipher algorithm"
526 ARC4 cipher algorithm.
528 ARC4 is a stream cipher using keys ranging from 8 bits to 2048
529 bits in length. This algorithm is required for driver-based
530 WEP, but it should not be for other purposes because of the
531 weakness of the algorithm.
533 config CRYPTO_BLOWFISH
534 tristate "Blowfish cipher algorithm"
537 Blowfish cipher algorithm, by Bruce Schneier.
539 This is a variable key length cipher which can use keys from 32
540 bits to 448 bits in length. It's fast, simple and specifically
541 designed for use on "large microprocessors".
544 <http://www.schneier.com/blowfish.html>
546 config CRYPTO_CAMELLIA
547 tristate "Camellia cipher algorithms"
551 Camellia cipher algorithms module.
553 Camellia is a symmetric key block cipher developed jointly
554 at NTT and Mitsubishi Electric Corporation.
556 The Camellia specifies three key sizes: 128, 192 and 256 bits.
559 <https://info.isl.ntt.co.jp/crypt/eng/camellia/index_s.html>
562 tristate "CAST5 (CAST-128) cipher algorithm"
565 The CAST5 encryption algorithm (synonymous with CAST-128) is
566 described in RFC2144.
569 tristate "CAST6 (CAST-256) cipher algorithm"
572 The CAST6 encryption algorithm (synonymous with CAST-256) is
573 described in RFC2612.
576 tristate "DES and Triple DES EDE cipher algorithms"
579 DES cipher algorithm (FIPS 46-2), and Triple DES EDE (FIPS 46-3).
582 tristate "FCrypt cipher algorithm"
584 select CRYPTO_BLKCIPHER
586 FCrypt algorithm used by RxRPC.
589 tristate "Khazad cipher algorithm"
592 Khazad cipher algorithm.
594 Khazad was a finalist in the initial NESSIE competition. It is
595 an algorithm optimized for 64-bit processors with good performance
596 on 32-bit processors. Khazad uses an 128 bit key size.
599 <http://planeta.terra.com.br/informatica/paulobarreto/KhazadPage.html>
601 config CRYPTO_SALSA20
602 tristate "Salsa20 stream cipher algorithm (EXPERIMENTAL)"
603 depends on EXPERIMENTAL
604 select CRYPTO_BLKCIPHER
606 Salsa20 stream cipher algorithm.
608 Salsa20 is a stream cipher submitted to eSTREAM, the ECRYPT
609 Stream Cipher Project. See <http://www.ecrypt.eu.org/stream/>
611 The Salsa20 stream cipher algorithm is designed by Daniel J.
612 Bernstein <djb@cr.yp.to>. See <http://cr.yp.to/snuffle.html>
614 config CRYPTO_SALSA20_586
615 tristate "Salsa20 stream cipher algorithm (i586) (EXPERIMENTAL)"
616 depends on (X86 || UML_X86) && !64BIT
617 depends on EXPERIMENTAL
618 select CRYPTO_BLKCIPHER
620 Salsa20 stream cipher algorithm.
622 Salsa20 is a stream cipher submitted to eSTREAM, the ECRYPT
623 Stream Cipher Project. See <http://www.ecrypt.eu.org/stream/>
625 The Salsa20 stream cipher algorithm is designed by Daniel J.
626 Bernstein <djb@cr.yp.to>. See <http://cr.yp.to/snuffle.html>
628 config CRYPTO_SALSA20_X86_64
629 tristate "Salsa20 stream cipher algorithm (x86_64) (EXPERIMENTAL)"
630 depends on (X86 || UML_X86) && 64BIT
631 depends on EXPERIMENTAL
632 select CRYPTO_BLKCIPHER
634 Salsa20 stream cipher algorithm.
636 Salsa20 is a stream cipher submitted to eSTREAM, the ECRYPT
637 Stream Cipher Project. See <http://www.ecrypt.eu.org/stream/>
639 The Salsa20 stream cipher algorithm is designed by Daniel J.
640 Bernstein <djb@cr.yp.to>. See <http://cr.yp.to/snuffle.html>
643 tristate "SEED cipher algorithm"
646 SEED cipher algorithm (RFC4269).
648 SEED is a 128-bit symmetric key block cipher that has been
649 developed by KISA (Korea Information Security Agency) as a
650 national standard encryption algorithm of the Republic of Korea.
651 It is a 16 round block cipher with the key size of 128 bit.
654 <http://www.kisa.or.kr/kisa/seed/jsp/seed_eng.jsp>
656 config CRYPTO_SERPENT
657 tristate "Serpent cipher algorithm"
660 Serpent cipher algorithm, by Anderson, Biham & Knudsen.
662 Keys are allowed to be from 0 to 256 bits in length, in steps
663 of 8 bits. Also includes the 'Tnepres' algorithm, a reversed
664 variant of Serpent for compatibility with old kerneli.org code.
667 <http://www.cl.cam.ac.uk/~rja14/serpent.html>
670 tristate "TEA, XTEA and XETA cipher algorithms"
673 TEA cipher algorithm.
675 Tiny Encryption Algorithm is a simple cipher that uses
676 many rounds for security. It is very fast and uses
679 Xtendend Tiny Encryption Algorithm is a modification to
680 the TEA algorithm to address a potential key weakness
681 in the TEA algorithm.
683 Xtendend Encryption Tiny Algorithm is a mis-implementation
684 of the XTEA algorithm for compatibility purposes.
686 config CRYPTO_TWOFISH
687 tristate "Twofish cipher algorithm"
689 select CRYPTO_TWOFISH_COMMON
691 Twofish cipher algorithm.
693 Twofish was submitted as an AES (Advanced Encryption Standard)
694 candidate cipher by researchers at CounterPane Systems. It is a
695 16 round block cipher supporting key sizes of 128, 192, and 256
699 <http://www.schneier.com/twofish.html>
701 config CRYPTO_TWOFISH_COMMON
704 Common parts of the Twofish cipher algorithm shared by the
705 generic c and the assembler implementations.
707 config CRYPTO_TWOFISH_586
708 tristate "Twofish cipher algorithms (i586)"
709 depends on (X86 || UML_X86) && !64BIT
711 select CRYPTO_TWOFISH_COMMON
713 Twofish cipher algorithm.
715 Twofish was submitted as an AES (Advanced Encryption Standard)
716 candidate cipher by researchers at CounterPane Systems. It is a
717 16 round block cipher supporting key sizes of 128, 192, and 256
721 <http://www.schneier.com/twofish.html>
723 config CRYPTO_TWOFISH_X86_64
724 tristate "Twofish cipher algorithm (x86_64)"
725 depends on (X86 || UML_X86) && 64BIT
727 select CRYPTO_TWOFISH_COMMON
729 Twofish cipher algorithm (x86_64).
731 Twofish was submitted as an AES (Advanced Encryption Standard)
732 candidate cipher by researchers at CounterPane Systems. It is a
733 16 round block cipher supporting key sizes of 128, 192, and 256
737 <http://www.schneier.com/twofish.html>
739 comment "Compression"
741 config CRYPTO_DEFLATE
742 tristate "Deflate compression algorithm"
747 This is the Deflate algorithm (RFC1951), specified for use in
748 IPSec with the IPCOMP protocol (RFC3173, RFC2394).
750 You will most probably want this if using IPSec.
753 tristate "Zlib compression algorithm"
759 This is the zlib algorithm.
762 tristate "LZO compression algorithm"
765 select LZO_DECOMPRESS
767 This is the LZO algorithm.
769 comment "Random Number Generation"
771 config CRYPTO_ANSI_CPRNG
772 tristate "Pseudo Random Number Generation for Cryptographic modules"
777 This option enables the generic pseudo random number generator
778 for cryptographic modules. Uses the Algorithm specified in
781 source "drivers/crypto/Kconfig"