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
106 These are 'Null' algorithms, used by IPsec, which do nothing.
109 tristate "Software async crypto daemon"
110 select CRYPTO_BLKCIPHER
112 select CRYPTO_MANAGER
114 This is a generic software asynchronous crypto daemon that
115 converts an arbitrary synchronous software crypto algorithm
116 into an asynchronous algorithm that executes in a kernel thread.
118 config CRYPTO_AUTHENC
119 tristate "Authenc support"
121 select CRYPTO_BLKCIPHER
122 select CRYPTO_MANAGER
125 Authenc: Combined mode wrapper for IPsec.
126 This is required for IPSec.
129 tristate "Testing module"
131 select CRYPTO_MANAGER
133 Quick & dirty crypto test module.
135 comment "Authenticated Encryption with Associated Data"
138 tristate "CCM support"
142 Support for Counter with CBC MAC. Required for IPsec.
145 tristate "GCM/GMAC support"
148 select CRYPTO_GF128MUL
150 Support for Galois/Counter Mode (GCM) and Galois Message
151 Authentication Code (GMAC). Required for IPSec.
154 tristate "Sequence Number IV Generator"
156 select CRYPTO_BLKCIPHER
159 This IV generator generates an IV based on a sequence number by
160 xoring it with a salt. This algorithm is mainly useful for CTR
162 comment "Block modes"
165 tristate "CBC support"
166 select CRYPTO_BLKCIPHER
167 select CRYPTO_MANAGER
169 CBC: Cipher Block Chaining mode
170 This block cipher algorithm is required for IPSec.
173 tristate "CTR support"
174 select CRYPTO_BLKCIPHER
176 select CRYPTO_MANAGER
179 This block cipher algorithm is required for IPSec.
182 tristate "CTS support"
183 select CRYPTO_BLKCIPHER
185 CTS: Cipher Text Stealing
186 This is the Cipher Text Stealing mode as described by
187 Section 8 of rfc2040 and referenced by rfc3962.
188 (rfc3962 includes errata information in its Appendix A)
189 This mode is required for Kerberos gss mechanism support
193 tristate "ECB support"
194 select CRYPTO_BLKCIPHER
195 select CRYPTO_MANAGER
197 ECB: Electronic CodeBook mode
198 This is the simplest block cipher algorithm. It simply encrypts
199 the input block by block.
202 tristate "LRW support (EXPERIMENTAL)"
203 depends on EXPERIMENTAL
204 select CRYPTO_BLKCIPHER
205 select CRYPTO_MANAGER
206 select CRYPTO_GF128MUL
208 LRW: Liskov Rivest Wagner, a tweakable, non malleable, non movable
209 narrow block cipher mode for dm-crypt. Use it with cipher
210 specification string aes-lrw-benbi, the key must be 256, 320 or 384.
211 The first 128, 192 or 256 bits in the key are used for AES and the
212 rest is used to tie each cipher block to its logical position.
215 tristate "PCBC support"
216 select CRYPTO_BLKCIPHER
217 select CRYPTO_MANAGER
219 PCBC: Propagating Cipher Block Chaining mode
220 This block cipher algorithm is required for RxRPC.
223 tristate "XTS support (EXPERIMENTAL)"
224 depends on EXPERIMENTAL
225 select CRYPTO_BLKCIPHER
226 select CRYPTO_MANAGER
227 select CRYPTO_GF128MUL
229 XTS: IEEE1619/D16 narrow block cipher use with aes-xts-plain,
230 key size 256, 384 or 512 bits. This implementation currently
231 can't handle a sectorsize which is not a multiple of 16 bytes.
236 tristate "HMAC support"
238 select CRYPTO_MANAGER
240 HMAC: Keyed-Hashing for Message Authentication (RFC2104).
241 This is required for IPSec.
244 tristate "XCBC support"
245 depends on EXPERIMENTAL
247 select CRYPTO_MANAGER
249 XCBC: Keyed-Hashing with encryption algorithm
250 http://www.ietf.org/rfc/rfc3566.txt
251 http://csrc.nist.gov/encryption/modes/proposedmodes/
252 xcbc-mac/xcbc-mac-spec.pdf
257 tristate "CRC32c CRC algorithm"
261 Castagnoli, et al Cyclic Redundancy-Check Algorithm. Used
262 by iSCSI for header and data digests and by others.
263 See Castagnoli93. This implementation uses lib/libcrc32c.
264 Module will be crc32c.
266 config CRYPTO_CRC32C_INTEL
267 tristate "CRC32c INTEL hardware acceleration"
271 In Intel processor with SSE4.2 supported, the processor will
272 support CRC32C implementation using hardware accelerated CRC32
273 instruction. This option will create 'crc32c-intel' module,
274 which will enable any routine to use the CRC32 instruction to
275 gain performance compared with software implementation.
276 Module will be crc32c-intel.
279 tristate "MD4 digest algorithm"
282 MD4 message digest algorithm (RFC1320).
285 tristate "MD5 digest algorithm"
288 MD5 message digest algorithm (RFC1321).
290 config CRYPTO_MICHAEL_MIC
291 tristate "Michael MIC keyed digest algorithm"
294 Michael MIC is used for message integrity protection in TKIP
295 (IEEE 802.11i). This algorithm is required for TKIP, but it
296 should not be used for other purposes because of the weakness
300 tristate "RIPEMD-128 digest algorithm"
303 RIPEMD-128 (ISO/IEC 10118-3:2004).
305 RIPEMD-128 is a 128-bit cryptographic hash function. It should only
306 to be used as a secure replacement for RIPEMD. For other use cases
307 RIPEMD-160 should be used.
309 Developed by Hans Dobbertin, Antoon Bosselaers and Bart Preneel.
310 See <http://home.esat.kuleuven.be/~bosselae/ripemd160.html>
313 tristate "RIPEMD-160 digest algorithm"
316 RIPEMD-160 (ISO/IEC 10118-3:2004).
318 RIPEMD-160 is a 160-bit cryptographic hash function. It is intended
319 to be used as a secure replacement for the 128-bit hash functions
320 MD4, MD5 and it's predecessor RIPEMD
321 (not to be confused with RIPEMD-128).
323 It's speed is comparable to SHA1 and there are no known attacks
326 Developed by Hans Dobbertin, Antoon Bosselaers and Bart Preneel.
327 See <http://home.esat.kuleuven.be/~bosselae/ripemd160.html>
330 tristate "RIPEMD-256 digest algorithm"
333 RIPEMD-256 is an optional extension of RIPEMD-128 with a
334 256 bit hash. It is intended for applications that require
335 longer hash-results, without needing a larger security level
338 Developed by Hans Dobbertin, Antoon Bosselaers and Bart Preneel.
339 See <http://home.esat.kuleuven.be/~bosselae/ripemd160.html>
342 tristate "RIPEMD-320 digest algorithm"
345 RIPEMD-320 is an optional extension of RIPEMD-160 with a
346 320 bit hash. It is intended for applications that require
347 longer hash-results, without needing a larger security level
350 Developed by Hans Dobbertin, Antoon Bosselaers and Bart Preneel.
351 See <http://home.esat.kuleuven.be/~bosselae/ripemd160.html>
354 tristate "SHA1 digest algorithm"
357 SHA-1 secure hash standard (FIPS 180-1/DFIPS 180-2).
360 tristate "SHA224 and SHA256 digest algorithm"
363 SHA256 secure hash standard (DFIPS 180-2).
365 This version of SHA implements a 256 bit hash with 128 bits of
366 security against collision attacks.
368 This code also includes SHA-224, a 224 bit hash with 112 bits
369 of security against collision attacks.
372 tristate "SHA384 and SHA512 digest algorithms"
375 SHA512 secure hash standard (DFIPS 180-2).
377 This version of SHA implements a 512 bit hash with 256 bits of
378 security against collision attacks.
380 This code also includes SHA-384, a 384 bit hash with 192 bits
381 of security against collision attacks.
384 tristate "Tiger digest algorithms"
387 Tiger hash algorithm 192, 160 and 128-bit hashes
389 Tiger is a hash function optimized for 64-bit processors while
390 still having decent performance on 32-bit processors.
391 Tiger was developed by Ross Anderson and Eli Biham.
394 <http://www.cs.technion.ac.il/~biham/Reports/Tiger/>.
397 tristate "Whirlpool digest algorithms"
400 Whirlpool hash algorithm 512, 384 and 256-bit hashes
402 Whirlpool-512 is part of the NESSIE cryptographic primitives.
403 Whirlpool will be part of the ISO/IEC 10118-3:2003(E) standard
406 <http://planeta.terra.com.br/informatica/paulobarreto/WhirlpoolPage.html>
411 tristate "AES cipher algorithms"
414 AES cipher algorithms (FIPS-197). AES uses the Rijndael
417 Rijndael appears to be consistently a very good performer in
418 both hardware and software across a wide range of computing
419 environments regardless of its use in feedback or non-feedback
420 modes. Its key setup time is excellent, and its key agility is
421 good. Rijndael's very low memory requirements make it very well
422 suited for restricted-space environments, in which it also
423 demonstrates excellent performance. Rijndael's operations are
424 among the easiest to defend against power and timing attacks.
426 The AES specifies three key sizes: 128, 192 and 256 bits
428 See <http://csrc.nist.gov/CryptoToolkit/aes/> for more information.
430 config CRYPTO_AES_586
431 tristate "AES cipher algorithms (i586)"
432 depends on (X86 || UML_X86) && !64BIT
436 AES cipher algorithms (FIPS-197). AES uses the Rijndael
439 Rijndael appears to be consistently a very good performer in
440 both hardware and software across a wide range of computing
441 environments regardless of its use in feedback or non-feedback
442 modes. Its key setup time is excellent, and its key agility is
443 good. Rijndael's very low memory requirements make it very well
444 suited for restricted-space environments, in which it also
445 demonstrates excellent performance. Rijndael's operations are
446 among the easiest to defend against power and timing attacks.
448 The AES specifies three key sizes: 128, 192 and 256 bits
450 See <http://csrc.nist.gov/encryption/aes/> for more information.
452 config CRYPTO_AES_X86_64
453 tristate "AES cipher algorithms (x86_64)"
454 depends on (X86 || UML_X86) && 64BIT
458 AES cipher algorithms (FIPS-197). AES uses the Rijndael
461 Rijndael appears to be consistently a very good performer in
462 both hardware and software across a wide range of computing
463 environments regardless of its use in feedback or non-feedback
464 modes. Its key setup time is excellent, and its key agility is
465 good. Rijndael's very low memory requirements make it very well
466 suited for restricted-space environments, in which it also
467 demonstrates excellent performance. Rijndael's operations are
468 among the easiest to defend against power and timing attacks.
470 The AES specifies three key sizes: 128, 192 and 256 bits
472 See <http://csrc.nist.gov/encryption/aes/> for more information.
475 tristate "Anubis cipher algorithm"
478 Anubis cipher algorithm.
480 Anubis is a variable key length cipher which can use keys from
481 128 bits to 320 bits in length. It was evaluated as a entrant
482 in the NESSIE competition.
485 <https://www.cosic.esat.kuleuven.ac.be/nessie/reports/>
486 <http://planeta.terra.com.br/informatica/paulobarreto/AnubisPage.html>
489 tristate "ARC4 cipher algorithm"
492 ARC4 cipher algorithm.
494 ARC4 is a stream cipher using keys ranging from 8 bits to 2048
495 bits in length. This algorithm is required for driver-based
496 WEP, but it should not be for other purposes because of the
497 weakness of the algorithm.
499 config CRYPTO_BLOWFISH
500 tristate "Blowfish cipher algorithm"
503 Blowfish cipher algorithm, by Bruce Schneier.
505 This is a variable key length cipher which can use keys from 32
506 bits to 448 bits in length. It's fast, simple and specifically
507 designed for use on "large microprocessors".
510 <http://www.schneier.com/blowfish.html>
512 config CRYPTO_CAMELLIA
513 tristate "Camellia cipher algorithms"
517 Camellia cipher algorithms module.
519 Camellia is a symmetric key block cipher developed jointly
520 at NTT and Mitsubishi Electric Corporation.
522 The Camellia specifies three key sizes: 128, 192 and 256 bits.
525 <https://info.isl.ntt.co.jp/crypt/eng/camellia/index_s.html>
528 tristate "CAST5 (CAST-128) cipher algorithm"
531 The CAST5 encryption algorithm (synonymous with CAST-128) is
532 described in RFC2144.
535 tristate "CAST6 (CAST-256) cipher algorithm"
538 The CAST6 encryption algorithm (synonymous with CAST-256) is
539 described in RFC2612.
542 tristate "DES and Triple DES EDE cipher algorithms"
545 DES cipher algorithm (FIPS 46-2), and Triple DES EDE (FIPS 46-3).
548 tristate "FCrypt cipher algorithm"
550 select CRYPTO_BLKCIPHER
552 FCrypt algorithm used by RxRPC.
555 tristate "Khazad cipher algorithm"
558 Khazad cipher algorithm.
560 Khazad was a finalist in the initial NESSIE competition. It is
561 an algorithm optimized for 64-bit processors with good performance
562 on 32-bit processors. Khazad uses an 128 bit key size.
565 <http://planeta.terra.com.br/informatica/paulobarreto/KhazadPage.html>
567 config CRYPTO_SALSA20
568 tristate "Salsa20 stream cipher algorithm (EXPERIMENTAL)"
569 depends on EXPERIMENTAL
570 select CRYPTO_BLKCIPHER
572 Salsa20 stream cipher algorithm.
574 Salsa20 is a stream cipher submitted to eSTREAM, the ECRYPT
575 Stream Cipher Project. See <http://www.ecrypt.eu.org/stream/>
577 The Salsa20 stream cipher algorithm is designed by Daniel J.
578 Bernstein <djb@cr.yp.to>. See <http://cr.yp.to/snuffle.html>
580 config CRYPTO_SALSA20_586
581 tristate "Salsa20 stream cipher algorithm (i586) (EXPERIMENTAL)"
582 depends on (X86 || UML_X86) && !64BIT
583 depends on EXPERIMENTAL
584 select CRYPTO_BLKCIPHER
586 Salsa20 stream cipher algorithm.
588 Salsa20 is a stream cipher submitted to eSTREAM, the ECRYPT
589 Stream Cipher Project. See <http://www.ecrypt.eu.org/stream/>
591 The Salsa20 stream cipher algorithm is designed by Daniel J.
592 Bernstein <djb@cr.yp.to>. See <http://cr.yp.to/snuffle.html>
594 config CRYPTO_SALSA20_X86_64
595 tristate "Salsa20 stream cipher algorithm (x86_64) (EXPERIMENTAL)"
596 depends on (X86 || UML_X86) && 64BIT
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>
609 tristate "SEED cipher algorithm"
612 SEED cipher algorithm (RFC4269).
614 SEED is a 128-bit symmetric key block cipher that has been
615 developed by KISA (Korea Information Security Agency) as a
616 national standard encryption algorithm of the Republic of Korea.
617 It is a 16 round block cipher with the key size of 128 bit.
620 <http://www.kisa.or.kr/kisa/seed/jsp/seed_eng.jsp>
622 config CRYPTO_SERPENT
623 tristate "Serpent cipher algorithm"
626 Serpent cipher algorithm, by Anderson, Biham & Knudsen.
628 Keys are allowed to be from 0 to 256 bits in length, in steps
629 of 8 bits. Also includes the 'Tnepres' algorithm, a reversed
630 variant of Serpent for compatibility with old kerneli.org code.
633 <http://www.cl.cam.ac.uk/~rja14/serpent.html>
636 tristate "TEA, XTEA and XETA cipher algorithms"
639 TEA cipher algorithm.
641 Tiny Encryption Algorithm is a simple cipher that uses
642 many rounds for security. It is very fast and uses
645 Xtendend Tiny Encryption Algorithm is a modification to
646 the TEA algorithm to address a potential key weakness
647 in the TEA algorithm.
649 Xtendend Encryption Tiny Algorithm is a mis-implementation
650 of the XTEA algorithm for compatibility purposes.
652 config CRYPTO_TWOFISH
653 tristate "Twofish cipher algorithm"
655 select CRYPTO_TWOFISH_COMMON
657 Twofish cipher algorithm.
659 Twofish was submitted as an AES (Advanced Encryption Standard)
660 candidate cipher by researchers at CounterPane Systems. It is a
661 16 round block cipher supporting key sizes of 128, 192, and 256
665 <http://www.schneier.com/twofish.html>
667 config CRYPTO_TWOFISH_COMMON
670 Common parts of the Twofish cipher algorithm shared by the
671 generic c and the assembler implementations.
673 config CRYPTO_TWOFISH_586
674 tristate "Twofish cipher algorithms (i586)"
675 depends on (X86 || UML_X86) && !64BIT
677 select CRYPTO_TWOFISH_COMMON
679 Twofish cipher algorithm.
681 Twofish was submitted as an AES (Advanced Encryption Standard)
682 candidate cipher by researchers at CounterPane Systems. It is a
683 16 round block cipher supporting key sizes of 128, 192, and 256
687 <http://www.schneier.com/twofish.html>
689 config CRYPTO_TWOFISH_X86_64
690 tristate "Twofish cipher algorithm (x86_64)"
691 depends on (X86 || UML_X86) && 64BIT
693 select CRYPTO_TWOFISH_COMMON
695 Twofish cipher algorithm (x86_64).
697 Twofish was submitted as an AES (Advanced Encryption Standard)
698 candidate cipher by researchers at CounterPane Systems. It is a
699 16 round block cipher supporting key sizes of 128, 192, and 256
703 <http://www.schneier.com/twofish.html>
705 comment "Compression"
707 config CRYPTO_DEFLATE
708 tristate "Deflate compression algorithm"
713 This is the Deflate algorithm (RFC1951), specified for use in
714 IPSec with the IPCOMP protocol (RFC3173, RFC2394).
716 You will most probably want this if using IPSec.
719 tristate "LZO compression algorithm"
722 select LZO_DECOMPRESS
724 This is the LZO algorithm.
726 comment "Random Number Generation"
728 config CRYPTO_ANSI_CPRNG
729 tristate "Pseudo Random Number Generation for Cryptographic modules"
734 This option enables the generic pseudo random number generator
735 for cryptographic modules. Uses the Algorithm specified in
738 source "drivers/crypto/Kconfig"