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 "GHASH digest algorithm"
296 select CRYPTO_GF128MUL
298 GHASH is message digest algorithm for GCM (Galois/Counter Mode).
301 tristate "MD4 digest algorithm"
304 MD4 message digest algorithm (RFC1320).
307 tristate "MD5 digest algorithm"
310 MD5 message digest algorithm (RFC1321).
312 config CRYPTO_MICHAEL_MIC
313 tristate "Michael MIC keyed digest algorithm"
316 Michael MIC is used for message integrity protection in TKIP
317 (IEEE 802.11i). This algorithm is required for TKIP, but it
318 should not be used for other purposes because of the weakness
322 tristate "RIPEMD-128 digest algorithm"
325 RIPEMD-128 (ISO/IEC 10118-3:2004).
327 RIPEMD-128 is a 128-bit cryptographic hash function. It should only
328 to be used as a secure replacement for RIPEMD. For other use cases
329 RIPEMD-160 should be used.
331 Developed by Hans Dobbertin, Antoon Bosselaers and Bart Preneel.
332 See <http://home.esat.kuleuven.be/~bosselae/ripemd160.html>
335 tristate "RIPEMD-160 digest algorithm"
338 RIPEMD-160 (ISO/IEC 10118-3:2004).
340 RIPEMD-160 is a 160-bit cryptographic hash function. It is intended
341 to be used as a secure replacement for the 128-bit hash functions
342 MD4, MD5 and it's predecessor RIPEMD
343 (not to be confused with RIPEMD-128).
345 It's speed is comparable to SHA1 and there are no known attacks
348 Developed by Hans Dobbertin, Antoon Bosselaers and Bart Preneel.
349 See <http://home.esat.kuleuven.be/~bosselae/ripemd160.html>
352 tristate "RIPEMD-256 digest algorithm"
355 RIPEMD-256 is an optional extension of RIPEMD-128 with a
356 256 bit hash. It is intended for applications that require
357 longer hash-results, without needing a larger security level
360 Developed by Hans Dobbertin, Antoon Bosselaers and Bart Preneel.
361 See <http://home.esat.kuleuven.be/~bosselae/ripemd160.html>
364 tristate "RIPEMD-320 digest algorithm"
367 RIPEMD-320 is an optional extension of RIPEMD-160 with a
368 320 bit hash. It is intended for applications that require
369 longer hash-results, without needing a larger security level
372 Developed by Hans Dobbertin, Antoon Bosselaers and Bart Preneel.
373 See <http://home.esat.kuleuven.be/~bosselae/ripemd160.html>
376 tristate "SHA1 digest algorithm"
379 SHA-1 secure hash standard (FIPS 180-1/DFIPS 180-2).
382 tristate "SHA224 and SHA256 digest algorithm"
385 SHA256 secure hash standard (DFIPS 180-2).
387 This version of SHA implements a 256 bit hash with 128 bits of
388 security against collision attacks.
390 This code also includes SHA-224, a 224 bit hash with 112 bits
391 of security against collision attacks.
394 tristate "SHA384 and SHA512 digest algorithms"
397 SHA512 secure hash standard (DFIPS 180-2).
399 This version of SHA implements a 512 bit hash with 256 bits of
400 security against collision attacks.
402 This code also includes SHA-384, a 384 bit hash with 192 bits
403 of security against collision attacks.
406 tristate "Tiger digest algorithms"
409 Tiger hash algorithm 192, 160 and 128-bit hashes
411 Tiger is a hash function optimized for 64-bit processors while
412 still having decent performance on 32-bit processors.
413 Tiger was developed by Ross Anderson and Eli Biham.
416 <http://www.cs.technion.ac.il/~biham/Reports/Tiger/>.
419 tristate "Whirlpool digest algorithms"
422 Whirlpool hash algorithm 512, 384 and 256-bit hashes
424 Whirlpool-512 is part of the NESSIE cryptographic primitives.
425 Whirlpool will be part of the ISO/IEC 10118-3:2003(E) standard
428 <http://planeta.terra.com.br/informatica/paulobarreto/WhirlpoolPage.html>
433 tristate "AES cipher algorithms"
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/CryptoToolkit/aes/> for more information.
452 config CRYPTO_AES_586
453 tristate "AES cipher algorithms (i586)"
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.
474 config CRYPTO_AES_X86_64
475 tristate "AES cipher algorithms (x86_64)"
476 depends on (X86 || UML_X86) && 64BIT
480 AES cipher algorithms (FIPS-197). AES uses the Rijndael
483 Rijndael appears to be consistently a very good performer in
484 both hardware and software across a wide range of computing
485 environments regardless of its use in feedback or non-feedback
486 modes. Its key setup time is excellent, and its key agility is
487 good. Rijndael's very low memory requirements make it very well
488 suited for restricted-space environments, in which it also
489 demonstrates excellent performance. Rijndael's operations are
490 among the easiest to defend against power and timing attacks.
492 The AES specifies three key sizes: 128, 192 and 256 bits
494 See <http://csrc.nist.gov/encryption/aes/> for more information.
496 config CRYPTO_AES_NI_INTEL
497 tristate "AES cipher algorithms (AES-NI)"
498 depends on (X86 || UML_X86) && 64BIT
499 select CRYPTO_AES_X86_64
504 Use Intel AES-NI instructions for AES algorithm.
506 AES cipher algorithms (FIPS-197). AES uses the Rijndael
509 Rijndael appears to be consistently a very good performer in
510 both hardware and software across a wide range of computing
511 environments regardless of its use in feedback or non-feedback
512 modes. Its key setup time is excellent, and its key agility is
513 good. Rijndael's very low memory requirements make it very well
514 suited for restricted-space environments, in which it also
515 demonstrates excellent performance. Rijndael's operations are
516 among the easiest to defend against power and timing attacks.
518 The AES specifies three key sizes: 128, 192 and 256 bits
520 See <http://csrc.nist.gov/encryption/aes/> for more information.
522 In addition to AES cipher algorithm support, the
523 acceleration for some popular block cipher mode is supported
524 too, including ECB, CBC, CTR, LRW, PCBC, XTS.
527 tristate "Anubis cipher algorithm"
530 Anubis cipher algorithm.
532 Anubis is a variable key length cipher which can use keys from
533 128 bits to 320 bits in length. It was evaluated as a entrant
534 in the NESSIE competition.
537 <https://www.cosic.esat.kuleuven.ac.be/nessie/reports/>
538 <http://planeta.terra.com.br/informatica/paulobarreto/AnubisPage.html>
541 tristate "ARC4 cipher algorithm"
544 ARC4 cipher algorithm.
546 ARC4 is a stream cipher using keys ranging from 8 bits to 2048
547 bits in length. This algorithm is required for driver-based
548 WEP, but it should not be for other purposes because of the
549 weakness of the algorithm.
551 config CRYPTO_BLOWFISH
552 tristate "Blowfish cipher algorithm"
555 Blowfish cipher algorithm, by Bruce Schneier.
557 This is a variable key length cipher which can use keys from 32
558 bits to 448 bits in length. It's fast, simple and specifically
559 designed for use on "large microprocessors".
562 <http://www.schneier.com/blowfish.html>
564 config CRYPTO_CAMELLIA
565 tristate "Camellia cipher algorithms"
569 Camellia cipher algorithms module.
571 Camellia is a symmetric key block cipher developed jointly
572 at NTT and Mitsubishi Electric Corporation.
574 The Camellia specifies three key sizes: 128, 192 and 256 bits.
577 <https://info.isl.ntt.co.jp/crypt/eng/camellia/index_s.html>
580 tristate "CAST5 (CAST-128) cipher algorithm"
583 The CAST5 encryption algorithm (synonymous with CAST-128) is
584 described in RFC2144.
587 tristate "CAST6 (CAST-256) cipher algorithm"
590 The CAST6 encryption algorithm (synonymous with CAST-256) is
591 described in RFC2612.
594 tristate "DES and Triple DES EDE cipher algorithms"
597 DES cipher algorithm (FIPS 46-2), and Triple DES EDE (FIPS 46-3).
600 tristate "FCrypt cipher algorithm"
602 select CRYPTO_BLKCIPHER
604 FCrypt algorithm used by RxRPC.
607 tristate "Khazad cipher algorithm"
610 Khazad cipher algorithm.
612 Khazad was a finalist in the initial NESSIE competition. It is
613 an algorithm optimized for 64-bit processors with good performance
614 on 32-bit processors. Khazad uses an 128 bit key size.
617 <http://planeta.terra.com.br/informatica/paulobarreto/KhazadPage.html>
619 config CRYPTO_SALSA20
620 tristate "Salsa20 stream cipher algorithm (EXPERIMENTAL)"
621 depends on EXPERIMENTAL
622 select CRYPTO_BLKCIPHER
624 Salsa20 stream cipher algorithm.
626 Salsa20 is a stream cipher submitted to eSTREAM, the ECRYPT
627 Stream Cipher Project. See <http://www.ecrypt.eu.org/stream/>
629 The Salsa20 stream cipher algorithm is designed by Daniel J.
630 Bernstein <djb@cr.yp.to>. See <http://cr.yp.to/snuffle.html>
632 config CRYPTO_SALSA20_586
633 tristate "Salsa20 stream cipher algorithm (i586) (EXPERIMENTAL)"
634 depends on (X86 || UML_X86) && !64BIT
635 depends on EXPERIMENTAL
636 select CRYPTO_BLKCIPHER
638 Salsa20 stream cipher algorithm.
640 Salsa20 is a stream cipher submitted to eSTREAM, the ECRYPT
641 Stream Cipher Project. See <http://www.ecrypt.eu.org/stream/>
643 The Salsa20 stream cipher algorithm is designed by Daniel J.
644 Bernstein <djb@cr.yp.to>. See <http://cr.yp.to/snuffle.html>
646 config CRYPTO_SALSA20_X86_64
647 tristate "Salsa20 stream cipher algorithm (x86_64) (EXPERIMENTAL)"
648 depends on (X86 || UML_X86) && 64BIT
649 depends on EXPERIMENTAL
650 select CRYPTO_BLKCIPHER
652 Salsa20 stream cipher algorithm.
654 Salsa20 is a stream cipher submitted to eSTREAM, the ECRYPT
655 Stream Cipher Project. See <http://www.ecrypt.eu.org/stream/>
657 The Salsa20 stream cipher algorithm is designed by Daniel J.
658 Bernstein <djb@cr.yp.to>. See <http://cr.yp.to/snuffle.html>
661 tristate "SEED cipher algorithm"
664 SEED cipher algorithm (RFC4269).
666 SEED is a 128-bit symmetric key block cipher that has been
667 developed by KISA (Korea Information Security Agency) as a
668 national standard encryption algorithm of the Republic of Korea.
669 It is a 16 round block cipher with the key size of 128 bit.
672 <http://www.kisa.or.kr/kisa/seed/jsp/seed_eng.jsp>
674 config CRYPTO_SERPENT
675 tristate "Serpent cipher algorithm"
678 Serpent cipher algorithm, by Anderson, Biham & Knudsen.
680 Keys are allowed to be from 0 to 256 bits in length, in steps
681 of 8 bits. Also includes the 'Tnepres' algorithm, a reversed
682 variant of Serpent for compatibility with old kerneli.org code.
685 <http://www.cl.cam.ac.uk/~rja14/serpent.html>
688 tristate "TEA, XTEA and XETA cipher algorithms"
691 TEA cipher algorithm.
693 Tiny Encryption Algorithm is a simple cipher that uses
694 many rounds for security. It is very fast and uses
697 Xtendend Tiny Encryption Algorithm is a modification to
698 the TEA algorithm to address a potential key weakness
699 in the TEA algorithm.
701 Xtendend Encryption Tiny Algorithm is a mis-implementation
702 of the XTEA algorithm for compatibility purposes.
704 config CRYPTO_TWOFISH
705 tristate "Twofish cipher algorithm"
707 select CRYPTO_TWOFISH_COMMON
709 Twofish cipher algorithm.
711 Twofish was submitted as an AES (Advanced Encryption Standard)
712 candidate cipher by researchers at CounterPane Systems. It is a
713 16 round block cipher supporting key sizes of 128, 192, and 256
717 <http://www.schneier.com/twofish.html>
719 config CRYPTO_TWOFISH_COMMON
722 Common parts of the Twofish cipher algorithm shared by the
723 generic c and the assembler implementations.
725 config CRYPTO_TWOFISH_586
726 tristate "Twofish cipher algorithms (i586)"
727 depends on (X86 || UML_X86) && !64BIT
729 select CRYPTO_TWOFISH_COMMON
731 Twofish cipher algorithm.
733 Twofish was submitted as an AES (Advanced Encryption Standard)
734 candidate cipher by researchers at CounterPane Systems. It is a
735 16 round block cipher supporting key sizes of 128, 192, and 256
739 <http://www.schneier.com/twofish.html>
741 config CRYPTO_TWOFISH_X86_64
742 tristate "Twofish cipher algorithm (x86_64)"
743 depends on (X86 || UML_X86) && 64BIT
745 select CRYPTO_TWOFISH_COMMON
747 Twofish cipher algorithm (x86_64).
749 Twofish was submitted as an AES (Advanced Encryption Standard)
750 candidate cipher by researchers at CounterPane Systems. It is a
751 16 round block cipher supporting key sizes of 128, 192, and 256
755 <http://www.schneier.com/twofish.html>
757 comment "Compression"
759 config CRYPTO_DEFLATE
760 tristate "Deflate compression algorithm"
765 This is the Deflate algorithm (RFC1951), specified for use in
766 IPSec with the IPCOMP protocol (RFC3173, RFC2394).
768 You will most probably want this if using IPSec.
771 tristate "Zlib compression algorithm"
777 This is the zlib algorithm.
780 tristate "LZO compression algorithm"
783 select LZO_DECOMPRESS
785 This is the LZO algorithm.
787 comment "Random Number Generation"
789 config CRYPTO_ANSI_CPRNG
790 tristate "Pseudo Random Number Generation for Cryptographic modules"
794 This option enables the generic pseudo random number generator
795 for cryptographic modules. Uses the Algorithm specified in
798 source "drivers/crypto/Kconfig"