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
118 This is a generic software asynchronous crypto daemon that
119 converts an arbitrary synchronous software crypto algorithm
120 into an asynchronous algorithm that executes in a kernel thread.
122 config CRYPTO_AUTHENC
123 tristate "Authenc support"
125 select CRYPTO_BLKCIPHER
126 select CRYPTO_MANAGER
129 Authenc: Combined mode wrapper for IPsec.
130 This is required for IPSec.
133 tristate "Testing module"
135 select CRYPTO_MANAGER
137 Quick & dirty crypto test module.
139 comment "Authenticated Encryption with Associated Data"
142 tristate "CCM support"
146 Support for Counter with CBC MAC. Required for IPsec.
149 tristate "GCM/GMAC support"
152 select CRYPTO_GF128MUL
154 Support for Galois/Counter Mode (GCM) and Galois Message
155 Authentication Code (GMAC). Required for IPSec.
158 tristate "Sequence Number IV Generator"
160 select CRYPTO_BLKCIPHER
163 This IV generator generates an IV based on a sequence number by
164 xoring it with a salt. This algorithm is mainly useful for CTR
166 comment "Block modes"
169 tristate "CBC support"
170 select CRYPTO_BLKCIPHER
171 select CRYPTO_MANAGER
173 CBC: Cipher Block Chaining mode
174 This block cipher algorithm is required for IPSec.
177 tristate "CTR support"
178 select CRYPTO_BLKCIPHER
180 select CRYPTO_MANAGER
183 This block cipher algorithm is required for IPSec.
186 tristate "CTS support"
187 select CRYPTO_BLKCIPHER
189 CTS: Cipher Text Stealing
190 This is the Cipher Text Stealing mode as described by
191 Section 8 of rfc2040 and referenced by rfc3962.
192 (rfc3962 includes errata information in its Appendix A)
193 This mode is required for Kerberos gss mechanism support
197 tristate "ECB support"
198 select CRYPTO_BLKCIPHER
199 select CRYPTO_MANAGER
201 ECB: Electronic CodeBook mode
202 This is the simplest block cipher algorithm. It simply encrypts
203 the input block by block.
206 tristate "LRW support (EXPERIMENTAL)"
207 depends on EXPERIMENTAL
208 select CRYPTO_BLKCIPHER
209 select CRYPTO_MANAGER
210 select CRYPTO_GF128MUL
212 LRW: Liskov Rivest Wagner, a tweakable, non malleable, non movable
213 narrow block cipher mode for dm-crypt. Use it with cipher
214 specification string aes-lrw-benbi, the key must be 256, 320 or 384.
215 The first 128, 192 or 256 bits in the key are used for AES and the
216 rest is used to tie each cipher block to its logical position.
219 tristate "PCBC support"
220 select CRYPTO_BLKCIPHER
221 select CRYPTO_MANAGER
223 PCBC: Propagating Cipher Block Chaining mode
224 This block cipher algorithm is required for RxRPC.
227 tristate "XTS support (EXPERIMENTAL)"
228 depends on EXPERIMENTAL
229 select CRYPTO_BLKCIPHER
230 select CRYPTO_MANAGER
231 select CRYPTO_GF128MUL
233 XTS: IEEE1619/D16 narrow block cipher use with aes-xts-plain,
234 key size 256, 384 or 512 bits. This implementation currently
235 can't handle a sectorsize which is not a multiple of 16 bytes.
240 tristate "HMAC support"
242 select CRYPTO_MANAGER
244 HMAC: Keyed-Hashing for Message Authentication (RFC2104).
245 This is required for IPSec.
248 tristate "XCBC support"
249 depends on EXPERIMENTAL
251 select CRYPTO_MANAGER
253 XCBC: Keyed-Hashing with encryption algorithm
254 http://www.ietf.org/rfc/rfc3566.txt
255 http://csrc.nist.gov/encryption/modes/proposedmodes/
256 xcbc-mac/xcbc-mac-spec.pdf
261 tristate "CRC32c CRC algorithm"
264 Castagnoli, et al Cyclic Redundancy-Check Algorithm. Used
265 by iSCSI for header and data digests and by others.
266 See Castagnoli93. Module will be crc32c.
268 config CRYPTO_CRC32C_INTEL
269 tristate "CRC32c INTEL hardware acceleration"
273 In Intel processor with SSE4.2 supported, the processor will
274 support CRC32C implementation using hardware accelerated CRC32
275 instruction. This option will create 'crc32c-intel' module,
276 which will enable any routine to use the CRC32 instruction to
277 gain performance compared with software implementation.
278 Module will be crc32c-intel.
281 tristate "MD4 digest algorithm"
284 MD4 message digest algorithm (RFC1320).
287 tristate "MD5 digest algorithm"
290 MD5 message digest algorithm (RFC1321).
292 config CRYPTO_MICHAEL_MIC
293 tristate "Michael MIC keyed digest algorithm"
296 Michael MIC is used for message integrity protection in TKIP
297 (IEEE 802.11i). This algorithm is required for TKIP, but it
298 should not be used for other purposes because of the weakness
302 tristate "RIPEMD-128 digest algorithm"
305 RIPEMD-128 (ISO/IEC 10118-3:2004).
307 RIPEMD-128 is a 128-bit cryptographic hash function. It should only
308 to be used as a secure replacement for RIPEMD. For other use cases
309 RIPEMD-160 should be used.
311 Developed by Hans Dobbertin, Antoon Bosselaers and Bart Preneel.
312 See <http://home.esat.kuleuven.be/~bosselae/ripemd160.html>
315 tristate "RIPEMD-160 digest algorithm"
318 RIPEMD-160 (ISO/IEC 10118-3:2004).
320 RIPEMD-160 is a 160-bit cryptographic hash function. It is intended
321 to be used as a secure replacement for the 128-bit hash functions
322 MD4, MD5 and it's predecessor RIPEMD
323 (not to be confused with RIPEMD-128).
325 It's speed is comparable to SHA1 and there are no known attacks
328 Developed by Hans Dobbertin, Antoon Bosselaers and Bart Preneel.
329 See <http://home.esat.kuleuven.be/~bosselae/ripemd160.html>
332 tristate "RIPEMD-256 digest algorithm"
335 RIPEMD-256 is an optional extension of RIPEMD-128 with a
336 256 bit hash. It is intended for applications that require
337 longer hash-results, without needing a larger security level
340 Developed by Hans Dobbertin, Antoon Bosselaers and Bart Preneel.
341 See <http://home.esat.kuleuven.be/~bosselae/ripemd160.html>
344 tristate "RIPEMD-320 digest algorithm"
347 RIPEMD-320 is an optional extension of RIPEMD-160 with a
348 320 bit hash. It is intended for applications that require
349 longer hash-results, without needing a larger security level
352 Developed by Hans Dobbertin, Antoon Bosselaers and Bart Preneel.
353 See <http://home.esat.kuleuven.be/~bosselae/ripemd160.html>
356 tristate "SHA1 digest algorithm"
359 SHA-1 secure hash standard (FIPS 180-1/DFIPS 180-2).
362 tristate "SHA224 and SHA256 digest algorithm"
365 SHA256 secure hash standard (DFIPS 180-2).
367 This version of SHA implements a 256 bit hash with 128 bits of
368 security against collision attacks.
370 This code also includes SHA-224, a 224 bit hash with 112 bits
371 of security against collision attacks.
374 tristate "SHA384 and SHA512 digest algorithms"
377 SHA512 secure hash standard (DFIPS 180-2).
379 This version of SHA implements a 512 bit hash with 256 bits of
380 security against collision attacks.
382 This code also includes SHA-384, a 384 bit hash with 192 bits
383 of security against collision attacks.
386 tristate "Tiger digest algorithms"
389 Tiger hash algorithm 192, 160 and 128-bit hashes
391 Tiger is a hash function optimized for 64-bit processors while
392 still having decent performance on 32-bit processors.
393 Tiger was developed by Ross Anderson and Eli Biham.
396 <http://www.cs.technion.ac.il/~biham/Reports/Tiger/>.
399 tristate "Whirlpool digest algorithms"
402 Whirlpool hash algorithm 512, 384 and 256-bit hashes
404 Whirlpool-512 is part of the NESSIE cryptographic primitives.
405 Whirlpool will be part of the ISO/IEC 10118-3:2003(E) standard
408 <http://planeta.terra.com.br/informatica/paulobarreto/WhirlpoolPage.html>
413 tristate "AES cipher algorithms"
416 AES cipher algorithms (FIPS-197). AES uses the Rijndael
419 Rijndael appears to be consistently a very good performer in
420 both hardware and software across a wide range of computing
421 environments regardless of its use in feedback or non-feedback
422 modes. Its key setup time is excellent, and its key agility is
423 good. Rijndael's very low memory requirements make it very well
424 suited for restricted-space environments, in which it also
425 demonstrates excellent performance. Rijndael's operations are
426 among the easiest to defend against power and timing attacks.
428 The AES specifies three key sizes: 128, 192 and 256 bits
430 See <http://csrc.nist.gov/CryptoToolkit/aes/> for more information.
432 config CRYPTO_AES_586
433 tristate "AES cipher algorithms (i586)"
434 depends on (X86 || UML_X86) && !64BIT
438 AES cipher algorithms (FIPS-197). AES uses the Rijndael
441 Rijndael appears to be consistently a very good performer in
442 both hardware and software across a wide range of computing
443 environments regardless of its use in feedback or non-feedback
444 modes. Its key setup time is excellent, and its key agility is
445 good. Rijndael's very low memory requirements make it very well
446 suited for restricted-space environments, in which it also
447 demonstrates excellent performance. Rijndael's operations are
448 among the easiest to defend against power and timing attacks.
450 The AES specifies three key sizes: 128, 192 and 256 bits
452 See <http://csrc.nist.gov/encryption/aes/> for more information.
454 config CRYPTO_AES_X86_64
455 tristate "AES cipher algorithms (x86_64)"
456 depends on (X86 || UML_X86) && 64BIT
460 AES cipher algorithms (FIPS-197). AES uses the Rijndael
463 Rijndael appears to be consistently a very good performer in
464 both hardware and software across a wide range of computing
465 environments regardless of its use in feedback or non-feedback
466 modes. Its key setup time is excellent, and its key agility is
467 good. Rijndael's very low memory requirements make it very well
468 suited for restricted-space environments, in which it also
469 demonstrates excellent performance. Rijndael's operations are
470 among the easiest to defend against power and timing attacks.
472 The AES specifies three key sizes: 128, 192 and 256 bits
474 See <http://csrc.nist.gov/encryption/aes/> for more information.
476 config CRYPTO_AES_NI_INTEL
477 tristate "AES cipher algorithms (AES-NI)"
478 depends on (X86 || UML_X86) && 64BIT
479 select CRYPTO_AES_X86_64
483 Use Intel AES-NI instructions for AES algorithm.
485 AES cipher algorithms (FIPS-197). AES uses the Rijndael
488 Rijndael appears to be consistently a very good performer in
489 both hardware and software across a wide range of computing
490 environments regardless of its use in feedback or non-feedback
491 modes. Its key setup time is excellent, and its key agility is
492 good. Rijndael's very low memory requirements make it very well
493 suited for restricted-space environments, in which it also
494 demonstrates excellent performance. Rijndael's operations are
495 among the easiest to defend against power and timing attacks.
497 The AES specifies three key sizes: 128, 192 and 256 bits
499 See <http://csrc.nist.gov/encryption/aes/> for more information.
502 tristate "Anubis cipher algorithm"
505 Anubis cipher algorithm.
507 Anubis is a variable key length cipher which can use keys from
508 128 bits to 320 bits in length. It was evaluated as a entrant
509 in the NESSIE competition.
512 <https://www.cosic.esat.kuleuven.ac.be/nessie/reports/>
513 <http://planeta.terra.com.br/informatica/paulobarreto/AnubisPage.html>
516 tristate "ARC4 cipher algorithm"
519 ARC4 cipher algorithm.
521 ARC4 is a stream cipher using keys ranging from 8 bits to 2048
522 bits in length. This algorithm is required for driver-based
523 WEP, but it should not be for other purposes because of the
524 weakness of the algorithm.
526 config CRYPTO_BLOWFISH
527 tristate "Blowfish cipher algorithm"
530 Blowfish cipher algorithm, by Bruce Schneier.
532 This is a variable key length cipher which can use keys from 32
533 bits to 448 bits in length. It's fast, simple and specifically
534 designed for use on "large microprocessors".
537 <http://www.schneier.com/blowfish.html>
539 config CRYPTO_CAMELLIA
540 tristate "Camellia cipher algorithms"
544 Camellia cipher algorithms module.
546 Camellia is a symmetric key block cipher developed jointly
547 at NTT and Mitsubishi Electric Corporation.
549 The Camellia specifies three key sizes: 128, 192 and 256 bits.
552 <https://info.isl.ntt.co.jp/crypt/eng/camellia/index_s.html>
555 tristate "CAST5 (CAST-128) cipher algorithm"
558 The CAST5 encryption algorithm (synonymous with CAST-128) is
559 described in RFC2144.
562 tristate "CAST6 (CAST-256) cipher algorithm"
565 The CAST6 encryption algorithm (synonymous with CAST-256) is
566 described in RFC2612.
569 tristate "DES and Triple DES EDE cipher algorithms"
572 DES cipher algorithm (FIPS 46-2), and Triple DES EDE (FIPS 46-3).
575 tristate "FCrypt cipher algorithm"
577 select CRYPTO_BLKCIPHER
579 FCrypt algorithm used by RxRPC.
582 tristate "Khazad cipher algorithm"
585 Khazad cipher algorithm.
587 Khazad was a finalist in the initial NESSIE competition. It is
588 an algorithm optimized for 64-bit processors with good performance
589 on 32-bit processors. Khazad uses an 128 bit key size.
592 <http://planeta.terra.com.br/informatica/paulobarreto/KhazadPage.html>
594 config CRYPTO_SALSA20
595 tristate "Salsa20 stream cipher algorithm (EXPERIMENTAL)"
596 depends on EXPERIMENTAL
597 select CRYPTO_BLKCIPHER
599 Salsa20 stream cipher algorithm.
601 Salsa20 is a stream cipher submitted to eSTREAM, the ECRYPT
602 Stream Cipher Project. See <http://www.ecrypt.eu.org/stream/>
604 The Salsa20 stream cipher algorithm is designed by Daniel J.
605 Bernstein <djb@cr.yp.to>. See <http://cr.yp.to/snuffle.html>
607 config CRYPTO_SALSA20_586
608 tristate "Salsa20 stream cipher algorithm (i586) (EXPERIMENTAL)"
609 depends on (X86 || UML_X86) && !64BIT
610 depends on EXPERIMENTAL
611 select CRYPTO_BLKCIPHER
613 Salsa20 stream cipher algorithm.
615 Salsa20 is a stream cipher submitted to eSTREAM, the ECRYPT
616 Stream Cipher Project. See <http://www.ecrypt.eu.org/stream/>
618 The Salsa20 stream cipher algorithm is designed by Daniel J.
619 Bernstein <djb@cr.yp.to>. See <http://cr.yp.to/snuffle.html>
621 config CRYPTO_SALSA20_X86_64
622 tristate "Salsa20 stream cipher algorithm (x86_64) (EXPERIMENTAL)"
623 depends on (X86 || UML_X86) && 64BIT
624 depends on EXPERIMENTAL
625 select CRYPTO_BLKCIPHER
627 Salsa20 stream cipher algorithm.
629 Salsa20 is a stream cipher submitted to eSTREAM, the ECRYPT
630 Stream Cipher Project. See <http://www.ecrypt.eu.org/stream/>
632 The Salsa20 stream cipher algorithm is designed by Daniel J.
633 Bernstein <djb@cr.yp.to>. See <http://cr.yp.to/snuffle.html>
636 tristate "SEED cipher algorithm"
639 SEED cipher algorithm (RFC4269).
641 SEED is a 128-bit symmetric key block cipher that has been
642 developed by KISA (Korea Information Security Agency) as a
643 national standard encryption algorithm of the Republic of Korea.
644 It is a 16 round block cipher with the key size of 128 bit.
647 <http://www.kisa.or.kr/kisa/seed/jsp/seed_eng.jsp>
649 config CRYPTO_SERPENT
650 tristate "Serpent cipher algorithm"
653 Serpent cipher algorithm, by Anderson, Biham & Knudsen.
655 Keys are allowed to be from 0 to 256 bits in length, in steps
656 of 8 bits. Also includes the 'Tnepres' algorithm, a reversed
657 variant of Serpent for compatibility with old kerneli.org code.
660 <http://www.cl.cam.ac.uk/~rja14/serpent.html>
663 tristate "TEA, XTEA and XETA cipher algorithms"
666 TEA cipher algorithm.
668 Tiny Encryption Algorithm is a simple cipher that uses
669 many rounds for security. It is very fast and uses
672 Xtendend Tiny Encryption Algorithm is a modification to
673 the TEA algorithm to address a potential key weakness
674 in the TEA algorithm.
676 Xtendend Encryption Tiny Algorithm is a mis-implementation
677 of the XTEA algorithm for compatibility purposes.
679 config CRYPTO_TWOFISH
680 tristate "Twofish cipher algorithm"
682 select CRYPTO_TWOFISH_COMMON
684 Twofish cipher algorithm.
686 Twofish was submitted as an AES (Advanced Encryption Standard)
687 candidate cipher by researchers at CounterPane Systems. It is a
688 16 round block cipher supporting key sizes of 128, 192, and 256
692 <http://www.schneier.com/twofish.html>
694 config CRYPTO_TWOFISH_COMMON
697 Common parts of the Twofish cipher algorithm shared by the
698 generic c and the assembler implementations.
700 config CRYPTO_TWOFISH_586
701 tristate "Twofish cipher algorithms (i586)"
702 depends on (X86 || UML_X86) && !64BIT
704 select CRYPTO_TWOFISH_COMMON
706 Twofish cipher algorithm.
708 Twofish was submitted as an AES (Advanced Encryption Standard)
709 candidate cipher by researchers at CounterPane Systems. It is a
710 16 round block cipher supporting key sizes of 128, 192, and 256
714 <http://www.schneier.com/twofish.html>
716 config CRYPTO_TWOFISH_X86_64
717 tristate "Twofish cipher algorithm (x86_64)"
718 depends on (X86 || UML_X86) && 64BIT
720 select CRYPTO_TWOFISH_COMMON
722 Twofish cipher algorithm (x86_64).
724 Twofish was submitted as an AES (Advanced Encryption Standard)
725 candidate cipher by researchers at CounterPane Systems. It is a
726 16 round block cipher supporting key sizes of 128, 192, and 256
730 <http://www.schneier.com/twofish.html>
732 comment "Compression"
734 config CRYPTO_DEFLATE
735 tristate "Deflate compression algorithm"
740 This is the Deflate algorithm (RFC1951), specified for use in
741 IPSec with the IPCOMP protocol (RFC3173, RFC2394).
743 You will most probably want this if using IPSec.
746 tristate "LZO compression algorithm"
749 select LZO_DECOMPRESS
751 This is the LZO algorithm.
753 comment "Random Number Generation"
755 config CRYPTO_ANSI_CPRNG
756 tristate "Pseudo Random Number Generation for Cryptographic modules"
761 This option enables the generic pseudo random number generator
762 for cryptographic modules. Uses the Algorithm specified in
765 source "drivers/crypto/Kconfig"