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"
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.
246 select CRYPTO_BLKCIPHER
247 select CRYPTO_MANAGER
252 tristate "HMAC support"
254 select CRYPTO_MANAGER
256 HMAC: Keyed-Hashing for Message Authentication (RFC2104).
257 This is required for IPSec.
260 tristate "XCBC support"
261 depends on EXPERIMENTAL
263 select CRYPTO_MANAGER
265 XCBC: Keyed-Hashing with encryption algorithm
266 http://www.ietf.org/rfc/rfc3566.txt
267 http://csrc.nist.gov/encryption/modes/proposedmodes/
268 xcbc-mac/xcbc-mac-spec.pdf
273 tristate "CRC32c CRC algorithm"
276 Castagnoli, et al Cyclic Redundancy-Check Algorithm. Used
277 by iSCSI for header and data digests and by others.
278 See Castagnoli93. Module will be crc32c.
280 config CRYPTO_CRC32C_INTEL
281 tristate "CRC32c INTEL hardware acceleration"
285 In Intel processor with SSE4.2 supported, the processor will
286 support CRC32C implementation using hardware accelerated CRC32
287 instruction. This option will create 'crc32c-intel' module,
288 which will enable any routine to use the CRC32 instruction to
289 gain performance compared with software implementation.
290 Module will be crc32c-intel.
293 tristate "GHASH digest algorithm"
295 select CRYPTO_GF128MUL
297 GHASH is message digest algorithm for GCM (Galois/Counter Mode).
300 tristate "MD4 digest algorithm"
303 MD4 message digest algorithm (RFC1320).
306 tristate "MD5 digest algorithm"
309 MD5 message digest algorithm (RFC1321).
311 config CRYPTO_MICHAEL_MIC
312 tristate "Michael MIC keyed digest algorithm"
315 Michael MIC is used for message integrity protection in TKIP
316 (IEEE 802.11i). This algorithm is required for TKIP, but it
317 should not be used for other purposes because of the weakness
321 tristate "RIPEMD-128 digest algorithm"
324 RIPEMD-128 (ISO/IEC 10118-3:2004).
326 RIPEMD-128 is a 128-bit cryptographic hash function. It should only
327 to be used as a secure replacement for RIPEMD. For other use cases
328 RIPEMD-160 should be used.
330 Developed by Hans Dobbertin, Antoon Bosselaers and Bart Preneel.
331 See <http://home.esat.kuleuven.be/~bosselae/ripemd160.html>
334 tristate "RIPEMD-160 digest algorithm"
337 RIPEMD-160 (ISO/IEC 10118-3:2004).
339 RIPEMD-160 is a 160-bit cryptographic hash function. It is intended
340 to be used as a secure replacement for the 128-bit hash functions
341 MD4, MD5 and it's predecessor RIPEMD
342 (not to be confused with RIPEMD-128).
344 It's speed is comparable to SHA1 and there are no known attacks
347 Developed by Hans Dobbertin, Antoon Bosselaers and Bart Preneel.
348 See <http://home.esat.kuleuven.be/~bosselae/ripemd160.html>
351 tristate "RIPEMD-256 digest algorithm"
354 RIPEMD-256 is an optional extension of RIPEMD-128 with a
355 256 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 "RIPEMD-320 digest algorithm"
366 RIPEMD-320 is an optional extension of RIPEMD-160 with a
367 320 bit hash. It is intended for applications that require
368 longer hash-results, without needing a larger security level
371 Developed by Hans Dobbertin, Antoon Bosselaers and Bart Preneel.
372 See <http://home.esat.kuleuven.be/~bosselae/ripemd160.html>
375 tristate "SHA1 digest algorithm"
378 SHA-1 secure hash standard (FIPS 180-1/DFIPS 180-2).
381 tristate "SHA224 and SHA256 digest algorithm"
384 SHA256 secure hash standard (DFIPS 180-2).
386 This version of SHA implements a 256 bit hash with 128 bits of
387 security against collision attacks.
389 This code also includes SHA-224, a 224 bit hash with 112 bits
390 of security against collision attacks.
393 tristate "SHA384 and SHA512 digest algorithms"
396 SHA512 secure hash standard (DFIPS 180-2).
398 This version of SHA implements a 512 bit hash with 256 bits of
399 security against collision attacks.
401 This code also includes SHA-384, a 384 bit hash with 192 bits
402 of security against collision attacks.
405 tristate "Tiger digest algorithms"
408 Tiger hash algorithm 192, 160 and 128-bit hashes
410 Tiger is a hash function optimized for 64-bit processors while
411 still having decent performance on 32-bit processors.
412 Tiger was developed by Ross Anderson and Eli Biham.
415 <http://www.cs.technion.ac.il/~biham/Reports/Tiger/>.
418 tristate "Whirlpool digest algorithms"
421 Whirlpool hash algorithm 512, 384 and 256-bit hashes
423 Whirlpool-512 is part of the NESSIE cryptographic primitives.
424 Whirlpool will be part of the ISO/IEC 10118-3:2003(E) standard
427 <http://planeta.terra.com.br/informatica/paulobarreto/WhirlpoolPage.html>
432 tristate "AES cipher algorithms"
435 AES cipher algorithms (FIPS-197). AES uses the Rijndael
438 Rijndael appears to be consistently a very good performer in
439 both hardware and software across a wide range of computing
440 environments regardless of its use in feedback or non-feedback
441 modes. Its key setup time is excellent, and its key agility is
442 good. Rijndael's very low memory requirements make it very well
443 suited for restricted-space environments, in which it also
444 demonstrates excellent performance. Rijndael's operations are
445 among the easiest to defend against power and timing attacks.
447 The AES specifies three key sizes: 128, 192 and 256 bits
449 See <http://csrc.nist.gov/CryptoToolkit/aes/> for more information.
451 config CRYPTO_AES_586
452 tristate "AES cipher algorithms (i586)"
453 depends on (X86 || UML_X86) && !64BIT
457 AES cipher algorithms (FIPS-197). AES uses the Rijndael
460 Rijndael appears to be consistently a very good performer in
461 both hardware and software across a wide range of computing
462 environments regardless of its use in feedback or non-feedback
463 modes. Its key setup time is excellent, and its key agility is
464 good. Rijndael's very low memory requirements make it very well
465 suited for restricted-space environments, in which it also
466 demonstrates excellent performance. Rijndael's operations are
467 among the easiest to defend against power and timing attacks.
469 The AES specifies three key sizes: 128, 192 and 256 bits
471 See <http://csrc.nist.gov/encryption/aes/> for more information.
473 config CRYPTO_AES_X86_64
474 tristate "AES cipher algorithms (x86_64)"
475 depends on (X86 || UML_X86) && 64BIT
479 AES cipher algorithms (FIPS-197). AES uses the Rijndael
482 Rijndael appears to be consistently a very good performer in
483 both hardware and software across a wide range of computing
484 environments regardless of its use in feedback or non-feedback
485 modes. Its key setup time is excellent, and its key agility is
486 good. Rijndael's very low memory requirements make it very well
487 suited for restricted-space environments, in which it also
488 demonstrates excellent performance. Rijndael's operations are
489 among the easiest to defend against power and timing attacks.
491 The AES specifies three key sizes: 128, 192 and 256 bits
493 See <http://csrc.nist.gov/encryption/aes/> for more information.
495 config CRYPTO_AES_NI_INTEL
496 tristate "AES cipher algorithms (AES-NI)"
497 depends on (X86 || UML_X86) && 64BIT
498 select CRYPTO_AES_X86_64
503 Use Intel AES-NI instructions for AES algorithm.
505 AES cipher algorithms (FIPS-197). AES uses the Rijndael
508 Rijndael appears to be consistently a very good performer in
509 both hardware and software across a wide range of computing
510 environments regardless of its use in feedback or non-feedback
511 modes. Its key setup time is excellent, and its key agility is
512 good. Rijndael's very low memory requirements make it very well
513 suited for restricted-space environments, in which it also
514 demonstrates excellent performance. Rijndael's operations are
515 among the easiest to defend against power and timing attacks.
517 The AES specifies three key sizes: 128, 192 and 256 bits
519 See <http://csrc.nist.gov/encryption/aes/> for more information.
521 In addition to AES cipher algorithm support, the
522 acceleration for some popular block cipher mode is supported
523 too, including ECB, CBC, CTR, LRW, PCBC, XTS.
526 tristate "Anubis cipher algorithm"
529 Anubis cipher algorithm.
531 Anubis is a variable key length cipher which can use keys from
532 128 bits to 320 bits in length. It was evaluated as a entrant
533 in the NESSIE competition.
536 <https://www.cosic.esat.kuleuven.ac.be/nessie/reports/>
537 <http://planeta.terra.com.br/informatica/paulobarreto/AnubisPage.html>
540 tristate "ARC4 cipher algorithm"
543 ARC4 cipher algorithm.
545 ARC4 is a stream cipher using keys ranging from 8 bits to 2048
546 bits in length. This algorithm is required for driver-based
547 WEP, but it should not be for other purposes because of the
548 weakness of the algorithm.
550 config CRYPTO_BLOWFISH
551 tristate "Blowfish cipher algorithm"
554 Blowfish cipher algorithm, by Bruce Schneier.
556 This is a variable key length cipher which can use keys from 32
557 bits to 448 bits in length. It's fast, simple and specifically
558 designed for use on "large microprocessors".
561 <http://www.schneier.com/blowfish.html>
563 config CRYPTO_CAMELLIA
564 tristate "Camellia cipher algorithms"
568 Camellia cipher algorithms module.
570 Camellia is a symmetric key block cipher developed jointly
571 at NTT and Mitsubishi Electric Corporation.
573 The Camellia specifies three key sizes: 128, 192 and 256 bits.
576 <https://info.isl.ntt.co.jp/crypt/eng/camellia/index_s.html>
579 tristate "CAST5 (CAST-128) cipher algorithm"
582 The CAST5 encryption algorithm (synonymous with CAST-128) is
583 described in RFC2144.
586 tristate "CAST6 (CAST-256) cipher algorithm"
589 The CAST6 encryption algorithm (synonymous with CAST-256) is
590 described in RFC2612.
593 tristate "DES and Triple DES EDE cipher algorithms"
596 DES cipher algorithm (FIPS 46-2), and Triple DES EDE (FIPS 46-3).
599 tristate "FCrypt cipher algorithm"
601 select CRYPTO_BLKCIPHER
603 FCrypt algorithm used by RxRPC.
606 tristate "Khazad cipher algorithm"
609 Khazad cipher algorithm.
611 Khazad was a finalist in the initial NESSIE competition. It is
612 an algorithm optimized for 64-bit processors with good performance
613 on 32-bit processors. Khazad uses an 128 bit key size.
616 <http://planeta.terra.com.br/informatica/paulobarreto/KhazadPage.html>
618 config CRYPTO_SALSA20
619 tristate "Salsa20 stream cipher algorithm (EXPERIMENTAL)"
620 depends on EXPERIMENTAL
621 select CRYPTO_BLKCIPHER
623 Salsa20 stream cipher algorithm.
625 Salsa20 is a stream cipher submitted to eSTREAM, the ECRYPT
626 Stream Cipher Project. See <http://www.ecrypt.eu.org/stream/>
628 The Salsa20 stream cipher algorithm is designed by Daniel J.
629 Bernstein <djb@cr.yp.to>. See <http://cr.yp.to/snuffle.html>
631 config CRYPTO_SALSA20_586
632 tristate "Salsa20 stream cipher algorithm (i586) (EXPERIMENTAL)"
633 depends on (X86 || UML_X86) && !64BIT
634 depends on EXPERIMENTAL
635 select CRYPTO_BLKCIPHER
637 Salsa20 stream cipher algorithm.
639 Salsa20 is a stream cipher submitted to eSTREAM, the ECRYPT
640 Stream Cipher Project. See <http://www.ecrypt.eu.org/stream/>
642 The Salsa20 stream cipher algorithm is designed by Daniel J.
643 Bernstein <djb@cr.yp.to>. See <http://cr.yp.to/snuffle.html>
645 config CRYPTO_SALSA20_X86_64
646 tristate "Salsa20 stream cipher algorithm (x86_64) (EXPERIMENTAL)"
647 depends on (X86 || UML_X86) && 64BIT
648 depends on EXPERIMENTAL
649 select CRYPTO_BLKCIPHER
651 Salsa20 stream cipher algorithm.
653 Salsa20 is a stream cipher submitted to eSTREAM, the ECRYPT
654 Stream Cipher Project. See <http://www.ecrypt.eu.org/stream/>
656 The Salsa20 stream cipher algorithm is designed by Daniel J.
657 Bernstein <djb@cr.yp.to>. See <http://cr.yp.to/snuffle.html>
660 tristate "SEED cipher algorithm"
663 SEED cipher algorithm (RFC4269).
665 SEED is a 128-bit symmetric key block cipher that has been
666 developed by KISA (Korea Information Security Agency) as a
667 national standard encryption algorithm of the Republic of Korea.
668 It is a 16 round block cipher with the key size of 128 bit.
671 <http://www.kisa.or.kr/kisa/seed/jsp/seed_eng.jsp>
673 config CRYPTO_SERPENT
674 tristate "Serpent cipher algorithm"
677 Serpent cipher algorithm, by Anderson, Biham & Knudsen.
679 Keys are allowed to be from 0 to 256 bits in length, in steps
680 of 8 bits. Also includes the 'Tnepres' algorithm, a reversed
681 variant of Serpent for compatibility with old kerneli.org code.
684 <http://www.cl.cam.ac.uk/~rja14/serpent.html>
687 tristate "TEA, XTEA and XETA cipher algorithms"
690 TEA cipher algorithm.
692 Tiny Encryption Algorithm is a simple cipher that uses
693 many rounds for security. It is very fast and uses
696 Xtendend Tiny Encryption Algorithm is a modification to
697 the TEA algorithm to address a potential key weakness
698 in the TEA algorithm.
700 Xtendend Encryption Tiny Algorithm is a mis-implementation
701 of the XTEA algorithm for compatibility purposes.
703 config CRYPTO_TWOFISH
704 tristate "Twofish cipher algorithm"
706 select CRYPTO_TWOFISH_COMMON
708 Twofish cipher algorithm.
710 Twofish was submitted as an AES (Advanced Encryption Standard)
711 candidate cipher by researchers at CounterPane Systems. It is a
712 16 round block cipher supporting key sizes of 128, 192, and 256
716 <http://www.schneier.com/twofish.html>
718 config CRYPTO_TWOFISH_COMMON
721 Common parts of the Twofish cipher algorithm shared by the
722 generic c and the assembler implementations.
724 config CRYPTO_TWOFISH_586
725 tristate "Twofish cipher algorithms (i586)"
726 depends on (X86 || UML_X86) && !64BIT
728 select CRYPTO_TWOFISH_COMMON
730 Twofish cipher algorithm.
732 Twofish was submitted as an AES (Advanced Encryption Standard)
733 candidate cipher by researchers at CounterPane Systems. It is a
734 16 round block cipher supporting key sizes of 128, 192, and 256
738 <http://www.schneier.com/twofish.html>
740 config CRYPTO_TWOFISH_X86_64
741 tristate "Twofish cipher algorithm (x86_64)"
742 depends on (X86 || UML_X86) && 64BIT
744 select CRYPTO_TWOFISH_COMMON
746 Twofish cipher algorithm (x86_64).
748 Twofish was submitted as an AES (Advanced Encryption Standard)
749 candidate cipher by researchers at CounterPane Systems. It is a
750 16 round block cipher supporting key sizes of 128, 192, and 256
754 <http://www.schneier.com/twofish.html>
756 comment "Compression"
758 config CRYPTO_DEFLATE
759 tristate "Deflate compression algorithm"
764 This is the Deflate algorithm (RFC1951), specified for use in
765 IPSec with the IPCOMP protocol (RFC3173, RFC2394).
767 You will most probably want this if using IPSec.
770 tristate "Zlib compression algorithm"
776 This is the zlib algorithm.
779 tristate "LZO compression algorithm"
782 select LZO_DECOMPRESS
784 This is the LZO algorithm.
786 comment "Random Number Generation"
788 config CRYPTO_ANSI_CPRNG
789 tristate "Pseudo Random Number Generation for Cryptographic modules"
793 This option enables the generic pseudo random number generator
794 for cryptographic modules. Uses the Algorithm specified in
797 source "drivers/crypto/Kconfig"