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 select 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
37 This option provides the API for cryptographic algorithms.
51 config CRYPTO_BLKCIPHER
53 select CRYPTO_BLKCIPHER2
56 config CRYPTO_BLKCIPHER2
60 select CRYPTO_WORKQUEUE
85 tristate "Cryptographic algorithm manager"
86 select CRYPTO_MANAGER2
88 Create default cryptographic template instantiations such as
91 config CRYPTO_MANAGER2
92 def_tristate CRYPTO_MANAGER || (CRYPTO_MANAGER!=n && CRYPTO_ALGAPI=y)
95 select CRYPTO_BLKCIPHER2
98 config CRYPTO_GF128MUL
99 tristate "GF(2^128) multiplication functions (EXPERIMENTAL)"
100 depends on EXPERIMENTAL
102 Efficient table driven implementation of multiplications in the
103 field GF(2^128). This is needed by some cypher modes. This
104 option will be selected automatically if you select such a
105 cipher mode. Only select this option by hand if you expect to load
106 an external module that requires these functions.
109 tristate "Null algorithms"
111 select CRYPTO_BLKCIPHER
114 These are 'Null' algorithms, used by IPsec, which do nothing.
116 config CRYPTO_WORKQUEUE
120 tristate "Software async crypto daemon"
121 select CRYPTO_BLKCIPHER
123 select CRYPTO_MANAGER
124 select CRYPTO_WORKQUEUE
126 This is a generic software asynchronous crypto daemon that
127 converts an arbitrary synchronous software crypto algorithm
128 into an asynchronous algorithm that executes in a kernel thread.
130 config CRYPTO_AUTHENC
131 tristate "Authenc support"
133 select CRYPTO_BLKCIPHER
134 select CRYPTO_MANAGER
137 Authenc: Combined mode wrapper for IPsec.
138 This is required for IPSec.
141 tristate "Testing module"
143 select CRYPTO_MANAGER
145 Quick & dirty crypto test module.
147 comment "Authenticated Encryption with Associated Data"
150 tristate "CCM support"
154 Support for Counter with CBC MAC. Required for IPsec.
157 tristate "GCM/GMAC support"
160 select CRYPTO_GF128MUL
162 Support for Galois/Counter Mode (GCM) and Galois Message
163 Authentication Code (GMAC). Required for IPSec.
166 tristate "Sequence Number IV Generator"
168 select CRYPTO_BLKCIPHER
171 This IV generator generates an IV based on a sequence number by
172 xoring it with a salt. This algorithm is mainly useful for CTR
174 comment "Block modes"
177 tristate "CBC support"
178 select CRYPTO_BLKCIPHER
179 select CRYPTO_MANAGER
181 CBC: Cipher Block Chaining mode
182 This block cipher algorithm is required for IPSec.
185 tristate "CTR support"
186 select CRYPTO_BLKCIPHER
188 select CRYPTO_MANAGER
191 This block cipher algorithm is required for IPSec.
194 tristate "CTS support"
195 select CRYPTO_BLKCIPHER
197 CTS: Cipher Text Stealing
198 This is the Cipher Text Stealing mode as described by
199 Section 8 of rfc2040 and referenced by rfc3962.
200 (rfc3962 includes errata information in its Appendix A)
201 This mode is required for Kerberos gss mechanism support
205 tristate "ECB support"
206 select CRYPTO_BLKCIPHER
207 select CRYPTO_MANAGER
209 ECB: Electronic CodeBook mode
210 This is the simplest block cipher algorithm. It simply encrypts
211 the input block by block.
214 tristate "LRW support (EXPERIMENTAL)"
215 depends on EXPERIMENTAL
216 select CRYPTO_BLKCIPHER
217 select CRYPTO_MANAGER
218 select CRYPTO_GF128MUL
220 LRW: Liskov Rivest Wagner, a tweakable, non malleable, non movable
221 narrow block cipher mode for dm-crypt. Use it with cipher
222 specification string aes-lrw-benbi, the key must be 256, 320 or 384.
223 The first 128, 192 or 256 bits in the key are used for AES and the
224 rest is used to tie each cipher block to its logical position.
227 tristate "PCBC support"
228 select CRYPTO_BLKCIPHER
229 select CRYPTO_MANAGER
231 PCBC: Propagating Cipher Block Chaining mode
232 This block cipher algorithm is required for RxRPC.
235 tristate "XTS support (EXPERIMENTAL)"
236 depends on EXPERIMENTAL
237 select CRYPTO_BLKCIPHER
238 select CRYPTO_MANAGER
239 select CRYPTO_GF128MUL
241 XTS: IEEE1619/D16 narrow block cipher use with aes-xts-plain,
242 key size 256, 384 or 512 bits. This implementation currently
243 can't handle a sectorsize which is not a multiple of 16 bytes.
247 select CRYPTO_BLKCIPHER
248 select CRYPTO_MANAGER
253 tristate "HMAC support"
255 select CRYPTO_MANAGER
257 HMAC: Keyed-Hashing for Message Authentication (RFC2104).
258 This is required for IPSec.
261 tristate "XCBC support"
262 depends on EXPERIMENTAL
264 select CRYPTO_MANAGER
266 XCBC: Keyed-Hashing with encryption algorithm
267 http://www.ietf.org/rfc/rfc3566.txt
268 http://csrc.nist.gov/encryption/modes/proposedmodes/
269 xcbc-mac/xcbc-mac-spec.pdf
274 tristate "CRC32c CRC algorithm"
277 Castagnoli, et al Cyclic Redundancy-Check Algorithm. Used
278 by iSCSI for header and data digests and by others.
279 See Castagnoli93. Module will be crc32c.
281 config CRYPTO_CRC32C_INTEL
282 tristate "CRC32c INTEL hardware acceleration"
286 In Intel processor with SSE4.2 supported, the processor will
287 support CRC32C implementation using hardware accelerated CRC32
288 instruction. This option will create 'crc32c-intel' module,
289 which will enable any routine to use the CRC32 instruction to
290 gain performance compared with software implementation.
291 Module will be crc32c-intel.
294 tristate "MD4 digest algorithm"
297 MD4 message digest algorithm (RFC1320).
300 tristate "MD5 digest algorithm"
303 MD5 message digest algorithm (RFC1321).
305 config CRYPTO_MICHAEL_MIC
306 tristate "Michael MIC keyed digest algorithm"
309 Michael MIC is used for message integrity protection in TKIP
310 (IEEE 802.11i). This algorithm is required for TKIP, but it
311 should not be used for other purposes because of the weakness
315 tristate "RIPEMD-128 digest algorithm"
318 RIPEMD-128 (ISO/IEC 10118-3:2004).
320 RIPEMD-128 is a 128-bit cryptographic hash function. It should only
321 to be used as a secure replacement for RIPEMD. For other use cases
322 RIPEMD-160 should be used.
324 Developed by Hans Dobbertin, Antoon Bosselaers and Bart Preneel.
325 See <http://home.esat.kuleuven.be/~bosselae/ripemd160.html>
328 tristate "RIPEMD-160 digest algorithm"
331 RIPEMD-160 (ISO/IEC 10118-3:2004).
333 RIPEMD-160 is a 160-bit cryptographic hash function. It is intended
334 to be used as a secure replacement for the 128-bit hash functions
335 MD4, MD5 and it's predecessor RIPEMD
336 (not to be confused with RIPEMD-128).
338 It's speed is comparable to SHA1 and there are no known attacks
341 Developed by Hans Dobbertin, Antoon Bosselaers and Bart Preneel.
342 See <http://home.esat.kuleuven.be/~bosselae/ripemd160.html>
345 tristate "RIPEMD-256 digest algorithm"
348 RIPEMD-256 is an optional extension of RIPEMD-128 with a
349 256 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 "RIPEMD-320 digest algorithm"
360 RIPEMD-320 is an optional extension of RIPEMD-160 with a
361 320 bit hash. It is intended for applications that require
362 longer hash-results, without needing a larger security level
365 Developed by Hans Dobbertin, Antoon Bosselaers and Bart Preneel.
366 See <http://home.esat.kuleuven.be/~bosselae/ripemd160.html>
369 tristate "SHA1 digest algorithm"
372 SHA-1 secure hash standard (FIPS 180-1/DFIPS 180-2).
375 tristate "SHA224 and SHA256 digest algorithm"
378 SHA256 secure hash standard (DFIPS 180-2).
380 This version of SHA implements a 256 bit hash with 128 bits of
381 security against collision attacks.
383 This code also includes SHA-224, a 224 bit hash with 112 bits
384 of security against collision attacks.
387 tristate "SHA384 and SHA512 digest algorithms"
390 SHA512 secure hash standard (DFIPS 180-2).
392 This version of SHA implements a 512 bit hash with 256 bits of
393 security against collision attacks.
395 This code also includes SHA-384, a 384 bit hash with 192 bits
396 of security against collision attacks.
399 tristate "Tiger digest algorithms"
402 Tiger hash algorithm 192, 160 and 128-bit hashes
404 Tiger is a hash function optimized for 64-bit processors while
405 still having decent performance on 32-bit processors.
406 Tiger was developed by Ross Anderson and Eli Biham.
409 <http://www.cs.technion.ac.il/~biham/Reports/Tiger/>.
412 tristate "Whirlpool digest algorithms"
415 Whirlpool hash algorithm 512, 384 and 256-bit hashes
417 Whirlpool-512 is part of the NESSIE cryptographic primitives.
418 Whirlpool will be part of the ISO/IEC 10118-3:2003(E) standard
421 <http://planeta.terra.com.br/informatica/paulobarreto/WhirlpoolPage.html>
426 tristate "AES cipher algorithms"
429 AES cipher algorithms (FIPS-197). AES uses the Rijndael
432 Rijndael appears to be consistently a very good performer in
433 both hardware and software across a wide range of computing
434 environments regardless of its use in feedback or non-feedback
435 modes. Its key setup time is excellent, and its key agility is
436 good. Rijndael's very low memory requirements make it very well
437 suited for restricted-space environments, in which it also
438 demonstrates excellent performance. Rijndael's operations are
439 among the easiest to defend against power and timing attacks.
441 The AES specifies three key sizes: 128, 192 and 256 bits
443 See <http://csrc.nist.gov/CryptoToolkit/aes/> for more information.
445 config CRYPTO_AES_586
446 tristate "AES cipher algorithms (i586)"
447 depends on (X86 || UML_X86) && !64BIT
451 AES cipher algorithms (FIPS-197). AES uses the Rijndael
454 Rijndael appears to be consistently a very good performer in
455 both hardware and software across a wide range of computing
456 environments regardless of its use in feedback or non-feedback
457 modes. Its key setup time is excellent, and its key agility is
458 good. Rijndael's very low memory requirements make it very well
459 suited for restricted-space environments, in which it also
460 demonstrates excellent performance. Rijndael's operations are
461 among the easiest to defend against power and timing attacks.
463 The AES specifies three key sizes: 128, 192 and 256 bits
465 See <http://csrc.nist.gov/encryption/aes/> for more information.
467 config CRYPTO_AES_X86_64
468 tristate "AES cipher algorithms (x86_64)"
469 depends on (X86 || UML_X86) && 64BIT
473 AES cipher algorithms (FIPS-197). AES uses the Rijndael
476 Rijndael appears to be consistently a very good performer in
477 both hardware and software across a wide range of computing
478 environments regardless of its use in feedback or non-feedback
479 modes. Its key setup time is excellent, and its key agility is
480 good. Rijndael's very low memory requirements make it very well
481 suited for restricted-space environments, in which it also
482 demonstrates excellent performance. Rijndael's operations are
483 among the easiest to defend against power and timing attacks.
485 The AES specifies three key sizes: 128, 192 and 256 bits
487 See <http://csrc.nist.gov/encryption/aes/> for more information.
489 config CRYPTO_AES_NI_INTEL
490 tristate "AES cipher algorithms (AES-NI)"
491 depends on (X86 || UML_X86) && 64BIT
492 select CRYPTO_AES_X86_64
497 Use Intel AES-NI instructions for AES algorithm.
499 AES cipher algorithms (FIPS-197). AES uses the Rijndael
502 Rijndael appears to be consistently a very good performer in
503 both hardware and software across a wide range of computing
504 environments regardless of its use in feedback or non-feedback
505 modes. Its key setup time is excellent, and its key agility is
506 good. Rijndael's very low memory requirements make it very well
507 suited for restricted-space environments, in which it also
508 demonstrates excellent performance. Rijndael's operations are
509 among the easiest to defend against power and timing attacks.
511 The AES specifies three key sizes: 128, 192 and 256 bits
513 See <http://csrc.nist.gov/encryption/aes/> for more information.
515 In addition to AES cipher algorithm support, the
516 acceleration for some popular block cipher mode is supported
517 too, including ECB, CBC, CTR, LRW, PCBC, XTS.
520 tristate "Anubis cipher algorithm"
523 Anubis cipher algorithm.
525 Anubis is a variable key length cipher which can use keys from
526 128 bits to 320 bits in length. It was evaluated as a entrant
527 in the NESSIE competition.
530 <https://www.cosic.esat.kuleuven.ac.be/nessie/reports/>
531 <http://planeta.terra.com.br/informatica/paulobarreto/AnubisPage.html>
534 tristate "ARC4 cipher algorithm"
537 ARC4 cipher algorithm.
539 ARC4 is a stream cipher using keys ranging from 8 bits to 2048
540 bits in length. This algorithm is required for driver-based
541 WEP, but it should not be for other purposes because of the
542 weakness of the algorithm.
544 config CRYPTO_BLOWFISH
545 tristate "Blowfish cipher algorithm"
548 Blowfish cipher algorithm, by Bruce Schneier.
550 This is a variable key length cipher which can use keys from 32
551 bits to 448 bits in length. It's fast, simple and specifically
552 designed for use on "large microprocessors".
555 <http://www.schneier.com/blowfish.html>
557 config CRYPTO_CAMELLIA
558 tristate "Camellia cipher algorithms"
562 Camellia cipher algorithms module.
564 Camellia is a symmetric key block cipher developed jointly
565 at NTT and Mitsubishi Electric Corporation.
567 The Camellia specifies three key sizes: 128, 192 and 256 bits.
570 <https://info.isl.ntt.co.jp/crypt/eng/camellia/index_s.html>
573 tristate "CAST5 (CAST-128) cipher algorithm"
576 The CAST5 encryption algorithm (synonymous with CAST-128) is
577 described in RFC2144.
580 tristate "CAST6 (CAST-256) cipher algorithm"
583 The CAST6 encryption algorithm (synonymous with CAST-256) is
584 described in RFC2612.
587 tristate "DES and Triple DES EDE cipher algorithms"
590 DES cipher algorithm (FIPS 46-2), and Triple DES EDE (FIPS 46-3).
593 tristate "FCrypt cipher algorithm"
595 select CRYPTO_BLKCIPHER
597 FCrypt algorithm used by RxRPC.
600 tristate "Khazad cipher algorithm"
603 Khazad cipher algorithm.
605 Khazad was a finalist in the initial NESSIE competition. It is
606 an algorithm optimized for 64-bit processors with good performance
607 on 32-bit processors. Khazad uses an 128 bit key size.
610 <http://planeta.terra.com.br/informatica/paulobarreto/KhazadPage.html>
612 config CRYPTO_SALSA20
613 tristate "Salsa20 stream cipher algorithm (EXPERIMENTAL)"
614 depends on EXPERIMENTAL
615 select CRYPTO_BLKCIPHER
617 Salsa20 stream cipher algorithm.
619 Salsa20 is a stream cipher submitted to eSTREAM, the ECRYPT
620 Stream Cipher Project. See <http://www.ecrypt.eu.org/stream/>
622 The Salsa20 stream cipher algorithm is designed by Daniel J.
623 Bernstein <djb@cr.yp.to>. See <http://cr.yp.to/snuffle.html>
625 config CRYPTO_SALSA20_586
626 tristate "Salsa20 stream cipher algorithm (i586) (EXPERIMENTAL)"
627 depends on (X86 || UML_X86) && !64BIT
628 depends on EXPERIMENTAL
629 select CRYPTO_BLKCIPHER
631 Salsa20 stream cipher algorithm.
633 Salsa20 is a stream cipher submitted to eSTREAM, the ECRYPT
634 Stream Cipher Project. See <http://www.ecrypt.eu.org/stream/>
636 The Salsa20 stream cipher algorithm is designed by Daniel J.
637 Bernstein <djb@cr.yp.to>. See <http://cr.yp.to/snuffle.html>
639 config CRYPTO_SALSA20_X86_64
640 tristate "Salsa20 stream cipher algorithm (x86_64) (EXPERIMENTAL)"
641 depends on (X86 || UML_X86) && 64BIT
642 depends on EXPERIMENTAL
643 select CRYPTO_BLKCIPHER
645 Salsa20 stream cipher algorithm.
647 Salsa20 is a stream cipher submitted to eSTREAM, the ECRYPT
648 Stream Cipher Project. See <http://www.ecrypt.eu.org/stream/>
650 The Salsa20 stream cipher algorithm is designed by Daniel J.
651 Bernstein <djb@cr.yp.to>. See <http://cr.yp.to/snuffle.html>
654 tristate "SEED cipher algorithm"
657 SEED cipher algorithm (RFC4269).
659 SEED is a 128-bit symmetric key block cipher that has been
660 developed by KISA (Korea Information Security Agency) as a
661 national standard encryption algorithm of the Republic of Korea.
662 It is a 16 round block cipher with the key size of 128 bit.
665 <http://www.kisa.or.kr/kisa/seed/jsp/seed_eng.jsp>
667 config CRYPTO_SERPENT
668 tristate "Serpent cipher algorithm"
671 Serpent cipher algorithm, by Anderson, Biham & Knudsen.
673 Keys are allowed to be from 0 to 256 bits in length, in steps
674 of 8 bits. Also includes the 'Tnepres' algorithm, a reversed
675 variant of Serpent for compatibility with old kerneli.org code.
678 <http://www.cl.cam.ac.uk/~rja14/serpent.html>
681 tristate "TEA, XTEA and XETA cipher algorithms"
684 TEA cipher algorithm.
686 Tiny Encryption Algorithm is a simple cipher that uses
687 many rounds for security. It is very fast and uses
690 Xtendend Tiny Encryption Algorithm is a modification to
691 the TEA algorithm to address a potential key weakness
692 in the TEA algorithm.
694 Xtendend Encryption Tiny Algorithm is a mis-implementation
695 of the XTEA algorithm for compatibility purposes.
697 config CRYPTO_TWOFISH
698 tristate "Twofish cipher algorithm"
700 select CRYPTO_TWOFISH_COMMON
702 Twofish cipher algorithm.
704 Twofish was submitted as an AES (Advanced Encryption Standard)
705 candidate cipher by researchers at CounterPane Systems. It is a
706 16 round block cipher supporting key sizes of 128, 192, and 256
710 <http://www.schneier.com/twofish.html>
712 config CRYPTO_TWOFISH_COMMON
715 Common parts of the Twofish cipher algorithm shared by the
716 generic c and the assembler implementations.
718 config CRYPTO_TWOFISH_586
719 tristate "Twofish cipher algorithms (i586)"
720 depends on (X86 || UML_X86) && !64BIT
722 select CRYPTO_TWOFISH_COMMON
724 Twofish cipher algorithm.
726 Twofish was submitted as an AES (Advanced Encryption Standard)
727 candidate cipher by researchers at CounterPane Systems. It is a
728 16 round block cipher supporting key sizes of 128, 192, and 256
732 <http://www.schneier.com/twofish.html>
734 config CRYPTO_TWOFISH_X86_64
735 tristate "Twofish cipher algorithm (x86_64)"
736 depends on (X86 || UML_X86) && 64BIT
738 select CRYPTO_TWOFISH_COMMON
740 Twofish cipher algorithm (x86_64).
742 Twofish was submitted as an AES (Advanced Encryption Standard)
743 candidate cipher by researchers at CounterPane Systems. It is a
744 16 round block cipher supporting key sizes of 128, 192, and 256
748 <http://www.schneier.com/twofish.html>
750 comment "Compression"
752 config CRYPTO_DEFLATE
753 tristate "Deflate compression algorithm"
758 This is the Deflate algorithm (RFC1951), specified for use in
759 IPSec with the IPCOMP protocol (RFC3173, RFC2394).
761 You will most probably want this if using IPSec.
764 tristate "Zlib compression algorithm"
770 This is the zlib algorithm.
773 tristate "LZO compression algorithm"
776 select LZO_DECOMPRESS
778 This is the LZO algorithm.
780 comment "Random Number Generation"
782 config CRYPTO_ANSI_CPRNG
783 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"