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"
260 Castagnoli, et al Cyclic Redundancy-Check Algorithm. Used
261 by iSCSI for header and data digests and by others.
262 See Castagnoli93. Module will be crc32c.
264 config CRYPTO_CRC32C_INTEL
265 tristate "CRC32c INTEL hardware acceleration"
269 In Intel processor with SSE4.2 supported, the processor will
270 support CRC32C implementation using hardware accelerated CRC32
271 instruction. This option will create 'crc32c-intel' module,
272 which will enable any routine to use the CRC32 instruction to
273 gain performance compared with software implementation.
274 Module will be crc32c-intel.
277 tristate "MD4 digest algorithm"
280 MD4 message digest algorithm (RFC1320).
283 tristate "MD5 digest algorithm"
286 MD5 message digest algorithm (RFC1321).
288 config CRYPTO_MICHAEL_MIC
289 tristate "Michael MIC keyed digest algorithm"
292 Michael MIC is used for message integrity protection in TKIP
293 (IEEE 802.11i). This algorithm is required for TKIP, but it
294 should not be used for other purposes because of the weakness
298 tristate "RIPEMD-128 digest algorithm"
301 RIPEMD-128 (ISO/IEC 10118-3:2004).
303 RIPEMD-128 is a 128-bit cryptographic hash function. It should only
304 to be used as a secure replacement for RIPEMD. For other use cases
305 RIPEMD-160 should be used.
307 Developed by Hans Dobbertin, Antoon Bosselaers and Bart Preneel.
308 See <http://home.esat.kuleuven.be/~bosselae/ripemd160.html>
311 tristate "RIPEMD-160 digest algorithm"
314 RIPEMD-160 (ISO/IEC 10118-3:2004).
316 RIPEMD-160 is a 160-bit cryptographic hash function. It is intended
317 to be used as a secure replacement for the 128-bit hash functions
318 MD4, MD5 and it's predecessor RIPEMD
319 (not to be confused with RIPEMD-128).
321 It's speed is comparable to SHA1 and there are no known attacks
324 Developed by Hans Dobbertin, Antoon Bosselaers and Bart Preneel.
325 See <http://home.esat.kuleuven.be/~bosselae/ripemd160.html>
328 tristate "RIPEMD-256 digest algorithm"
331 RIPEMD-256 is an optional extension of RIPEMD-128 with a
332 256 bit hash. It is intended for applications that require
333 longer hash-results, without needing a larger security level
336 Developed by Hans Dobbertin, Antoon Bosselaers and Bart Preneel.
337 See <http://home.esat.kuleuven.be/~bosselae/ripemd160.html>
340 tristate "RIPEMD-320 digest algorithm"
343 RIPEMD-320 is an optional extension of RIPEMD-160 with a
344 320 bit hash. It is intended for applications that require
345 longer hash-results, without needing a larger security level
348 Developed by Hans Dobbertin, Antoon Bosselaers and Bart Preneel.
349 See <http://home.esat.kuleuven.be/~bosselae/ripemd160.html>
352 tristate "SHA1 digest algorithm"
355 SHA-1 secure hash standard (FIPS 180-1/DFIPS 180-2).
358 tristate "SHA224 and SHA256 digest algorithm"
361 SHA256 secure hash standard (DFIPS 180-2).
363 This version of SHA implements a 256 bit hash with 128 bits of
364 security against collision attacks.
366 This code also includes SHA-224, a 224 bit hash with 112 bits
367 of security against collision attacks.
370 tristate "SHA384 and SHA512 digest algorithms"
373 SHA512 secure hash standard (DFIPS 180-2).
375 This version of SHA implements a 512 bit hash with 256 bits of
376 security against collision attacks.
378 This code also includes SHA-384, a 384 bit hash with 192 bits
379 of security against collision attacks.
382 tristate "Tiger digest algorithms"
385 Tiger hash algorithm 192, 160 and 128-bit hashes
387 Tiger is a hash function optimized for 64-bit processors while
388 still having decent performance on 32-bit processors.
389 Tiger was developed by Ross Anderson and Eli Biham.
392 <http://www.cs.technion.ac.il/~biham/Reports/Tiger/>.
395 tristate "Whirlpool digest algorithms"
398 Whirlpool hash algorithm 512, 384 and 256-bit hashes
400 Whirlpool-512 is part of the NESSIE cryptographic primitives.
401 Whirlpool will be part of the ISO/IEC 10118-3:2003(E) standard
404 <http://planeta.terra.com.br/informatica/paulobarreto/WhirlpoolPage.html>
409 tristate "AES cipher algorithms"
412 AES cipher algorithms (FIPS-197). AES uses the Rijndael
415 Rijndael appears to be consistently a very good performer in
416 both hardware and software across a wide range of computing
417 environments regardless of its use in feedback or non-feedback
418 modes. Its key setup time is excellent, and its key agility is
419 good. Rijndael's very low memory requirements make it very well
420 suited for restricted-space environments, in which it also
421 demonstrates excellent performance. Rijndael's operations are
422 among the easiest to defend against power and timing attacks.
424 The AES specifies three key sizes: 128, 192 and 256 bits
426 See <http://csrc.nist.gov/CryptoToolkit/aes/> for more information.
428 config CRYPTO_AES_586
429 tristate "AES cipher algorithms (i586)"
430 depends on (X86 || UML_X86) && !64BIT
434 AES cipher algorithms (FIPS-197). AES uses the Rijndael
437 Rijndael appears to be consistently a very good performer in
438 both hardware and software across a wide range of computing
439 environments regardless of its use in feedback or non-feedback
440 modes. Its key setup time is excellent, and its key agility is
441 good. Rijndael's very low memory requirements make it very well
442 suited for restricted-space environments, in which it also
443 demonstrates excellent performance. Rijndael's operations are
444 among the easiest to defend against power and timing attacks.
446 The AES specifies three key sizes: 128, 192 and 256 bits
448 See <http://csrc.nist.gov/encryption/aes/> for more information.
450 config CRYPTO_AES_X86_64
451 tristate "AES cipher algorithms (x86_64)"
452 depends on (X86 || UML_X86) && 64BIT
456 AES cipher algorithms (FIPS-197). AES uses the Rijndael
459 Rijndael appears to be consistently a very good performer in
460 both hardware and software across a wide range of computing
461 environments regardless of its use in feedback or non-feedback
462 modes. Its key setup time is excellent, and its key agility is
463 good. Rijndael's very low memory requirements make it very well
464 suited for restricted-space environments, in which it also
465 demonstrates excellent performance. Rijndael's operations are
466 among the easiest to defend against power and timing attacks.
468 The AES specifies three key sizes: 128, 192 and 256 bits
470 See <http://csrc.nist.gov/encryption/aes/> for more information.
473 tristate "Anubis cipher algorithm"
476 Anubis cipher algorithm.
478 Anubis is a variable key length cipher which can use keys from
479 128 bits to 320 bits in length. It was evaluated as a entrant
480 in the NESSIE competition.
483 <https://www.cosic.esat.kuleuven.ac.be/nessie/reports/>
484 <http://planeta.terra.com.br/informatica/paulobarreto/AnubisPage.html>
487 tristate "ARC4 cipher algorithm"
490 ARC4 cipher algorithm.
492 ARC4 is a stream cipher using keys ranging from 8 bits to 2048
493 bits in length. This algorithm is required for driver-based
494 WEP, but it should not be for other purposes because of the
495 weakness of the algorithm.
497 config CRYPTO_BLOWFISH
498 tristate "Blowfish cipher algorithm"
501 Blowfish cipher algorithm, by Bruce Schneier.
503 This is a variable key length cipher which can use keys from 32
504 bits to 448 bits in length. It's fast, simple and specifically
505 designed for use on "large microprocessors".
508 <http://www.schneier.com/blowfish.html>
510 config CRYPTO_CAMELLIA
511 tristate "Camellia cipher algorithms"
515 Camellia cipher algorithms module.
517 Camellia is a symmetric key block cipher developed jointly
518 at NTT and Mitsubishi Electric Corporation.
520 The Camellia specifies three key sizes: 128, 192 and 256 bits.
523 <https://info.isl.ntt.co.jp/crypt/eng/camellia/index_s.html>
526 tristate "CAST5 (CAST-128) cipher algorithm"
529 The CAST5 encryption algorithm (synonymous with CAST-128) is
530 described in RFC2144.
533 tristate "CAST6 (CAST-256) cipher algorithm"
536 The CAST6 encryption algorithm (synonymous with CAST-256) is
537 described in RFC2612.
540 tristate "DES and Triple DES EDE cipher algorithms"
543 DES cipher algorithm (FIPS 46-2), and Triple DES EDE (FIPS 46-3).
546 tristate "FCrypt cipher algorithm"
548 select CRYPTO_BLKCIPHER
550 FCrypt algorithm used by RxRPC.
553 tristate "Khazad cipher algorithm"
556 Khazad cipher algorithm.
558 Khazad was a finalist in the initial NESSIE competition. It is
559 an algorithm optimized for 64-bit processors with good performance
560 on 32-bit processors. Khazad uses an 128 bit key size.
563 <http://planeta.terra.com.br/informatica/paulobarreto/KhazadPage.html>
565 config CRYPTO_SALSA20
566 tristate "Salsa20 stream cipher algorithm (EXPERIMENTAL)"
567 depends on EXPERIMENTAL
568 select CRYPTO_BLKCIPHER
570 Salsa20 stream cipher algorithm.
572 Salsa20 is a stream cipher submitted to eSTREAM, the ECRYPT
573 Stream Cipher Project. See <http://www.ecrypt.eu.org/stream/>
575 The Salsa20 stream cipher algorithm is designed by Daniel J.
576 Bernstein <djb@cr.yp.to>. See <http://cr.yp.to/snuffle.html>
578 config CRYPTO_SALSA20_586
579 tristate "Salsa20 stream cipher algorithm (i586) (EXPERIMENTAL)"
580 depends on (X86 || UML_X86) && !64BIT
581 depends on EXPERIMENTAL
582 select CRYPTO_BLKCIPHER
584 Salsa20 stream cipher algorithm.
586 Salsa20 is a stream cipher submitted to eSTREAM, the ECRYPT
587 Stream Cipher Project. See <http://www.ecrypt.eu.org/stream/>
589 The Salsa20 stream cipher algorithm is designed by Daniel J.
590 Bernstein <djb@cr.yp.to>. See <http://cr.yp.to/snuffle.html>
592 config CRYPTO_SALSA20_X86_64
593 tristate "Salsa20 stream cipher algorithm (x86_64) (EXPERIMENTAL)"
594 depends on (X86 || UML_X86) && 64BIT
595 depends on EXPERIMENTAL
596 select CRYPTO_BLKCIPHER
598 Salsa20 stream cipher algorithm.
600 Salsa20 is a stream cipher submitted to eSTREAM, the ECRYPT
601 Stream Cipher Project. See <http://www.ecrypt.eu.org/stream/>
603 The Salsa20 stream cipher algorithm is designed by Daniel J.
604 Bernstein <djb@cr.yp.to>. See <http://cr.yp.to/snuffle.html>
607 tristate "SEED cipher algorithm"
610 SEED cipher algorithm (RFC4269).
612 SEED is a 128-bit symmetric key block cipher that has been
613 developed by KISA (Korea Information Security Agency) as a
614 national standard encryption algorithm of the Republic of Korea.
615 It is a 16 round block cipher with the key size of 128 bit.
618 <http://www.kisa.or.kr/kisa/seed/jsp/seed_eng.jsp>
620 config CRYPTO_SERPENT
621 tristate "Serpent cipher algorithm"
624 Serpent cipher algorithm, by Anderson, Biham & Knudsen.
626 Keys are allowed to be from 0 to 256 bits in length, in steps
627 of 8 bits. Also includes the 'Tnepres' algorithm, a reversed
628 variant of Serpent for compatibility with old kerneli.org code.
631 <http://www.cl.cam.ac.uk/~rja14/serpent.html>
634 tristate "TEA, XTEA and XETA cipher algorithms"
637 TEA cipher algorithm.
639 Tiny Encryption Algorithm is a simple cipher that uses
640 many rounds for security. It is very fast and uses
643 Xtendend Tiny Encryption Algorithm is a modification to
644 the TEA algorithm to address a potential key weakness
645 in the TEA algorithm.
647 Xtendend Encryption Tiny Algorithm is a mis-implementation
648 of the XTEA algorithm for compatibility purposes.
650 config CRYPTO_TWOFISH
651 tristate "Twofish cipher algorithm"
653 select CRYPTO_TWOFISH_COMMON
655 Twofish cipher algorithm.
657 Twofish was submitted as an AES (Advanced Encryption Standard)
658 candidate cipher by researchers at CounterPane Systems. It is a
659 16 round block cipher supporting key sizes of 128, 192, and 256
663 <http://www.schneier.com/twofish.html>
665 config CRYPTO_TWOFISH_COMMON
668 Common parts of the Twofish cipher algorithm shared by the
669 generic c and the assembler implementations.
671 config CRYPTO_TWOFISH_586
672 tristate "Twofish cipher algorithms (i586)"
673 depends on (X86 || UML_X86) && !64BIT
675 select CRYPTO_TWOFISH_COMMON
677 Twofish cipher algorithm.
679 Twofish was submitted as an AES (Advanced Encryption Standard)
680 candidate cipher by researchers at CounterPane Systems. It is a
681 16 round block cipher supporting key sizes of 128, 192, and 256
685 <http://www.schneier.com/twofish.html>
687 config CRYPTO_TWOFISH_X86_64
688 tristate "Twofish cipher algorithm (x86_64)"
689 depends on (X86 || UML_X86) && 64BIT
691 select CRYPTO_TWOFISH_COMMON
693 Twofish cipher algorithm (x86_64).
695 Twofish was submitted as an AES (Advanced Encryption Standard)
696 candidate cipher by researchers at CounterPane Systems. It is a
697 16 round block cipher supporting key sizes of 128, 192, and 256
701 <http://www.schneier.com/twofish.html>
703 comment "Compression"
705 config CRYPTO_DEFLATE
706 tristate "Deflate compression algorithm"
711 This is the Deflate algorithm (RFC1951), specified for use in
712 IPSec with the IPCOMP protocol (RFC3173, RFC2394).
714 You will most probably want this if using IPSec.
717 tristate "LZO compression algorithm"
720 select LZO_DECOMPRESS
722 This is the LZO algorithm.
724 comment "Random Number Generation"
726 config CRYPTO_ANSI_CPRNG
727 tristate "Pseudo Random Number Generation for Cryptographic modules"
732 This option enables the generic pseudo random number generator
733 for cryptographic modules. Uses the Algorithm specified in
736 source "drivers/crypto/Kconfig"