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 depends on CRYPTO_ANSI_CPRNG && !CRYPTO_MANAGER_DISABLE_TESTS
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
90 tristate "Cryptographic algorithm manager"
91 select CRYPTO_MANAGER2
93 Create default cryptographic template instantiations such as
96 config CRYPTO_MANAGER2
97 def_tristate CRYPTO_MANAGER || (CRYPTO_MANAGER!=n && CRYPTO_ALGAPI=y)
100 select CRYPTO_BLKCIPHER2
103 config CRYPTO_MANAGER_DISABLE_TESTS
104 bool "Disable run-time self tests"
106 depends on CRYPTO_MANAGER2
108 Disable run-time self tests that normally take place at
109 algorithm registration.
111 config CRYPTO_GF128MUL
112 tristate "GF(2^128) multiplication functions (EXPERIMENTAL)"
114 Efficient table driven implementation of multiplications in the
115 field GF(2^128). This is needed by some cypher modes. This
116 option will be selected automatically if you select such a
117 cipher mode. Only select this option by hand if you expect to load
118 an external module that requires these functions.
121 tristate "Null algorithms"
123 select CRYPTO_BLKCIPHER
126 These are 'Null' algorithms, used by IPsec, which do nothing.
129 tristate "Parallel crypto engine (EXPERIMENTAL)"
130 depends on SMP && EXPERIMENTAL
132 select CRYPTO_MANAGER
135 This converts an arbitrary crypto algorithm into a parallel
136 algorithm that executes in kernel threads.
138 config CRYPTO_WORKQUEUE
142 tristate "Software async crypto daemon"
143 select CRYPTO_BLKCIPHER
145 select CRYPTO_MANAGER
146 select CRYPTO_WORKQUEUE
148 This is a generic software asynchronous crypto daemon that
149 converts an arbitrary synchronous software crypto algorithm
150 into an asynchronous algorithm that executes in a kernel thread.
152 config CRYPTO_AUTHENC
153 tristate "Authenc support"
155 select CRYPTO_BLKCIPHER
156 select CRYPTO_MANAGER
159 Authenc: Combined mode wrapper for IPsec.
160 This is required for IPSec.
163 tristate "Testing module"
165 select CRYPTO_MANAGER
167 Quick & dirty crypto test module.
169 comment "Authenticated Encryption with Associated Data"
172 tristate "CCM support"
176 Support for Counter with CBC MAC. Required for IPsec.
179 tristate "GCM/GMAC support"
184 Support for Galois/Counter Mode (GCM) and Galois Message
185 Authentication Code (GMAC). Required for IPSec.
188 tristate "Sequence Number IV Generator"
190 select CRYPTO_BLKCIPHER
193 This IV generator generates an IV based on a sequence number by
194 xoring it with a salt. This algorithm is mainly useful for CTR
196 comment "Block modes"
199 tristate "CBC support"
200 select CRYPTO_BLKCIPHER
201 select CRYPTO_MANAGER
203 CBC: Cipher Block Chaining mode
204 This block cipher algorithm is required for IPSec.
207 tristate "CTR support"
208 select CRYPTO_BLKCIPHER
210 select CRYPTO_MANAGER
213 This block cipher algorithm is required for IPSec.
216 tristate "CTS support"
217 select CRYPTO_BLKCIPHER
219 CTS: Cipher Text Stealing
220 This is the Cipher Text Stealing mode as described by
221 Section 8 of rfc2040 and referenced by rfc3962.
222 (rfc3962 includes errata information in its Appendix A)
223 This mode is required for Kerberos gss mechanism support
227 tristate "ECB support"
228 select CRYPTO_BLKCIPHER
229 select CRYPTO_MANAGER
231 ECB: Electronic CodeBook mode
232 This is the simplest block cipher algorithm. It simply encrypts
233 the input block by block.
236 tristate "LRW support (EXPERIMENTAL)"
237 depends on EXPERIMENTAL
238 select CRYPTO_BLKCIPHER
239 select CRYPTO_MANAGER
240 select CRYPTO_GF128MUL
242 LRW: Liskov Rivest Wagner, a tweakable, non malleable, non movable
243 narrow block cipher mode for dm-crypt. Use it with cipher
244 specification string aes-lrw-benbi, the key must be 256, 320 or 384.
245 The first 128, 192 or 256 bits in the key are used for AES and the
246 rest is used to tie each cipher block to its logical position.
249 tristate "PCBC support"
250 select CRYPTO_BLKCIPHER
251 select CRYPTO_MANAGER
253 PCBC: Propagating Cipher Block Chaining mode
254 This block cipher algorithm is required for RxRPC.
257 tristate "XTS support (EXPERIMENTAL)"
258 depends on EXPERIMENTAL
259 select CRYPTO_BLKCIPHER
260 select CRYPTO_MANAGER
261 select CRYPTO_GF128MUL
263 XTS: IEEE1619/D16 narrow block cipher use with aes-xts-plain,
264 key size 256, 384 or 512 bits. This implementation currently
265 can't handle a sectorsize which is not a multiple of 16 bytes.
270 tristate "HMAC support"
272 select CRYPTO_MANAGER
274 HMAC: Keyed-Hashing for Message Authentication (RFC2104).
275 This is required for IPSec.
278 tristate "XCBC support"
279 depends on EXPERIMENTAL
281 select CRYPTO_MANAGER
283 XCBC: Keyed-Hashing with encryption algorithm
284 http://www.ietf.org/rfc/rfc3566.txt
285 http://csrc.nist.gov/encryption/modes/proposedmodes/
286 xcbc-mac/xcbc-mac-spec.pdf
289 tristate "VMAC support"
290 depends on EXPERIMENTAL
292 select CRYPTO_MANAGER
294 VMAC is a message authentication algorithm designed for
295 very high speed on 64-bit architectures.
298 <http://fastcrypto.org/vmac>
303 tristate "CRC32c CRC algorithm"
306 Castagnoli, et al Cyclic Redundancy-Check Algorithm. Used
307 by iSCSI for header and data digests and by others.
308 See Castagnoli93. Module will be crc32c.
310 config CRYPTO_CRC32C_INTEL
311 tristate "CRC32c INTEL hardware acceleration"
315 In Intel processor with SSE4.2 supported, the processor will
316 support CRC32C implementation using hardware accelerated CRC32
317 instruction. This option will create 'crc32c-intel' module,
318 which will enable any routine to use the CRC32 instruction to
319 gain performance compared with software implementation.
320 Module will be crc32c-intel.
323 tristate "GHASH digest algorithm"
325 select CRYPTO_GF128MUL
327 GHASH is message digest algorithm for GCM (Galois/Counter Mode).
330 tristate "MD4 digest algorithm"
333 MD4 message digest algorithm (RFC1320).
336 tristate "MD5 digest algorithm"
339 MD5 message digest algorithm (RFC1321).
341 config CRYPTO_MICHAEL_MIC
342 tristate "Michael MIC keyed digest algorithm"
345 Michael MIC is used for message integrity protection in TKIP
346 (IEEE 802.11i). This algorithm is required for TKIP, but it
347 should not be used for other purposes because of the weakness
351 tristate "RIPEMD-128 digest algorithm"
354 RIPEMD-128 (ISO/IEC 10118-3:2004).
356 RIPEMD-128 is a 128-bit cryptographic hash function. It should only
357 be used as a secure replacement for RIPEMD. For other use cases,
358 RIPEMD-160 should be used.
360 Developed by Hans Dobbertin, Antoon Bosselaers and Bart Preneel.
361 See <http://homes.esat.kuleuven.be/~bosselae/ripemd160.html>
364 tristate "RIPEMD-160 digest algorithm"
367 RIPEMD-160 (ISO/IEC 10118-3:2004).
369 RIPEMD-160 is a 160-bit cryptographic hash function. It is intended
370 to be used as a secure replacement for the 128-bit hash functions
371 MD4, MD5 and it's predecessor RIPEMD
372 (not to be confused with RIPEMD-128).
374 It's speed is comparable to SHA1 and there are no known attacks
377 Developed by Hans Dobbertin, Antoon Bosselaers and Bart Preneel.
378 See <http://homes.esat.kuleuven.be/~bosselae/ripemd160.html>
381 tristate "RIPEMD-256 digest algorithm"
384 RIPEMD-256 is an optional extension of RIPEMD-128 with a
385 256 bit hash. It is intended for applications that require
386 longer hash-results, without needing a larger security level
389 Developed by Hans Dobbertin, Antoon Bosselaers and Bart Preneel.
390 See <http://homes.esat.kuleuven.be/~bosselae/ripemd160.html>
393 tristate "RIPEMD-320 digest algorithm"
396 RIPEMD-320 is an optional extension of RIPEMD-160 with a
397 320 bit hash. It is intended for applications that require
398 longer hash-results, without needing a larger security level
401 Developed by Hans Dobbertin, Antoon Bosselaers and Bart Preneel.
402 See <http://homes.esat.kuleuven.be/~bosselae/ripemd160.html>
405 tristate "SHA1 digest algorithm"
408 SHA-1 secure hash standard (FIPS 180-1/DFIPS 180-2).
411 tristate "SHA224 and SHA256 digest algorithm"
414 SHA256 secure hash standard (DFIPS 180-2).
416 This version of SHA implements a 256 bit hash with 128 bits of
417 security against collision attacks.
419 This code also includes SHA-224, a 224 bit hash with 112 bits
420 of security against collision attacks.
423 tristate "SHA384 and SHA512 digest algorithms"
426 SHA512 secure hash standard (DFIPS 180-2).
428 This version of SHA implements a 512 bit hash with 256 bits of
429 security against collision attacks.
431 This code also includes SHA-384, a 384 bit hash with 192 bits
432 of security against collision attacks.
435 tristate "Tiger digest algorithms"
438 Tiger hash algorithm 192, 160 and 128-bit hashes
440 Tiger is a hash function optimized for 64-bit processors while
441 still having decent performance on 32-bit processors.
442 Tiger was developed by Ross Anderson and Eli Biham.
445 <http://www.cs.technion.ac.il/~biham/Reports/Tiger/>.
448 tristate "Whirlpool digest algorithms"
451 Whirlpool hash algorithm 512, 384 and 256-bit hashes
453 Whirlpool-512 is part of the NESSIE cryptographic primitives.
454 Whirlpool will be part of the ISO/IEC 10118-3:2003(E) standard
457 <http://www.larc.usp.br/~pbarreto/WhirlpoolPage.html>
459 config CRYPTO_GHASH_CLMUL_NI_INTEL
460 tristate "GHASH digest algorithm (CLMUL-NI accelerated)"
461 depends on X86 && 64BIT
465 GHASH is message digest algorithm for GCM (Galois/Counter Mode).
466 The implementation is accelerated by CLMUL-NI of Intel.
471 tristate "AES cipher algorithms"
474 AES cipher algorithms (FIPS-197). AES uses the Rijndael
477 Rijndael appears to be consistently a very good performer in
478 both hardware and software across a wide range of computing
479 environments regardless of its use in feedback or non-feedback
480 modes. Its key setup time is excellent, and its key agility is
481 good. Rijndael's very low memory requirements make it very well
482 suited for restricted-space environments, in which it also
483 demonstrates excellent performance. Rijndael's operations are
484 among the easiest to defend against power and timing attacks.
486 The AES specifies three key sizes: 128, 192 and 256 bits
488 See <http://csrc.nist.gov/CryptoToolkit/aes/> for more information.
490 config CRYPTO_AES_586
491 tristate "AES cipher algorithms (i586)"
492 depends on (X86 || UML_X86) && !64BIT
496 AES cipher algorithms (FIPS-197). AES uses the Rijndael
499 Rijndael appears to be consistently a very good performer in
500 both hardware and software across a wide range of computing
501 environments regardless of its use in feedback or non-feedback
502 modes. Its key setup time is excellent, and its key agility is
503 good. Rijndael's very low memory requirements make it very well
504 suited for restricted-space environments, in which it also
505 demonstrates excellent performance. Rijndael's operations are
506 among the easiest to defend against power and timing attacks.
508 The AES specifies three key sizes: 128, 192 and 256 bits
510 See <http://csrc.nist.gov/encryption/aes/> for more information.
512 config CRYPTO_AES_X86_64
513 tristate "AES cipher algorithms (x86_64)"
514 depends on (X86 || UML_X86) && 64BIT
518 AES cipher algorithms (FIPS-197). AES uses the Rijndael
521 Rijndael appears to be consistently a very good performer in
522 both hardware and software across a wide range of computing
523 environments regardless of its use in feedback or non-feedback
524 modes. Its key setup time is excellent, and its key agility is
525 good. Rijndael's very low memory requirements make it very well
526 suited for restricted-space environments, in which it also
527 demonstrates excellent performance. Rijndael's operations are
528 among the easiest to defend against power and timing attacks.
530 The AES specifies three key sizes: 128, 192 and 256 bits
532 See <http://csrc.nist.gov/encryption/aes/> for more information.
534 config CRYPTO_AES_NI_INTEL
535 tristate "AES cipher algorithms (AES-NI)"
537 select CRYPTO_AES_X86_64 if 64BIT
538 select CRYPTO_AES_586 if !64BIT
542 Use Intel AES-NI instructions for AES algorithm.
544 AES cipher algorithms (FIPS-197). AES uses the Rijndael
547 Rijndael appears to be consistently a very good performer in
548 both hardware and software across a wide range of computing
549 environments regardless of its use in feedback or non-feedback
550 modes. Its key setup time is excellent, and its key agility is
551 good. Rijndael's very low memory requirements make it very well
552 suited for restricted-space environments, in which it also
553 demonstrates excellent performance. Rijndael's operations are
554 among the easiest to defend against power and timing attacks.
556 The AES specifies three key sizes: 128, 192 and 256 bits
558 See <http://csrc.nist.gov/encryption/aes/> for more information.
560 In addition to AES cipher algorithm support, the acceleration
561 for some popular block cipher mode is supported too, including
562 ECB, CBC, LRW, PCBC, XTS. The 64 bit version has additional
563 acceleration for CTR.
566 tristate "Anubis cipher algorithm"
569 Anubis cipher algorithm.
571 Anubis is a variable key length cipher which can use keys from
572 128 bits to 320 bits in length. It was evaluated as a entrant
573 in the NESSIE competition.
576 <https://www.cosic.esat.kuleuven.be/nessie/reports/>
577 <http://www.larc.usp.br/~pbarreto/AnubisPage.html>
580 tristate "ARC4 cipher algorithm"
583 ARC4 cipher algorithm.
585 ARC4 is a stream cipher using keys ranging from 8 bits to 2048
586 bits in length. This algorithm is required for driver-based
587 WEP, but it should not be for other purposes because of the
588 weakness of the algorithm.
590 config CRYPTO_BLOWFISH
591 tristate "Blowfish cipher algorithm"
594 Blowfish cipher algorithm, by Bruce Schneier.
596 This is a variable key length cipher which can use keys from 32
597 bits to 448 bits in length. It's fast, simple and specifically
598 designed for use on "large microprocessors".
601 <http://www.schneier.com/blowfish.html>
603 config CRYPTO_CAMELLIA
604 tristate "Camellia cipher algorithms"
608 Camellia cipher algorithms module.
610 Camellia is a symmetric key block cipher developed jointly
611 at NTT and Mitsubishi Electric Corporation.
613 The Camellia specifies three key sizes: 128, 192 and 256 bits.
616 <https://info.isl.ntt.co.jp/crypt/eng/camellia/index_s.html>
619 tristate "CAST5 (CAST-128) cipher algorithm"
622 The CAST5 encryption algorithm (synonymous with CAST-128) is
623 described in RFC2144.
626 tristate "CAST6 (CAST-256) cipher algorithm"
629 The CAST6 encryption algorithm (synonymous with CAST-256) is
630 described in RFC2612.
633 tristate "DES and Triple DES EDE cipher algorithms"
636 DES cipher algorithm (FIPS 46-2), and Triple DES EDE (FIPS 46-3).
639 tristate "FCrypt cipher algorithm"
641 select CRYPTO_BLKCIPHER
643 FCrypt algorithm used by RxRPC.
646 tristate "Khazad cipher algorithm"
649 Khazad cipher algorithm.
651 Khazad was a finalist in the initial NESSIE competition. It is
652 an algorithm optimized for 64-bit processors with good performance
653 on 32-bit processors. Khazad uses an 128 bit key size.
656 <http://www.larc.usp.br/~pbarreto/KhazadPage.html>
658 config CRYPTO_SALSA20
659 tristate "Salsa20 stream cipher algorithm (EXPERIMENTAL)"
660 depends on EXPERIMENTAL
661 select CRYPTO_BLKCIPHER
663 Salsa20 stream cipher algorithm.
665 Salsa20 is a stream cipher submitted to eSTREAM, the ECRYPT
666 Stream Cipher Project. See <http://www.ecrypt.eu.org/stream/>
668 The Salsa20 stream cipher algorithm is designed by Daniel J.
669 Bernstein <djb@cr.yp.to>. See <http://cr.yp.to/snuffle.html>
671 config CRYPTO_SALSA20_586
672 tristate "Salsa20 stream cipher algorithm (i586) (EXPERIMENTAL)"
673 depends on (X86 || UML_X86) && !64BIT
674 depends on EXPERIMENTAL
675 select CRYPTO_BLKCIPHER
677 Salsa20 stream cipher algorithm.
679 Salsa20 is a stream cipher submitted to eSTREAM, the ECRYPT
680 Stream Cipher Project. See <http://www.ecrypt.eu.org/stream/>
682 The Salsa20 stream cipher algorithm is designed by Daniel J.
683 Bernstein <djb@cr.yp.to>. See <http://cr.yp.to/snuffle.html>
685 config CRYPTO_SALSA20_X86_64
686 tristate "Salsa20 stream cipher algorithm (x86_64) (EXPERIMENTAL)"
687 depends on (X86 || UML_X86) && 64BIT
688 depends on EXPERIMENTAL
689 select CRYPTO_BLKCIPHER
691 Salsa20 stream cipher algorithm.
693 Salsa20 is a stream cipher submitted to eSTREAM, the ECRYPT
694 Stream Cipher Project. See <http://www.ecrypt.eu.org/stream/>
696 The Salsa20 stream cipher algorithm is designed by Daniel J.
697 Bernstein <djb@cr.yp.to>. See <http://cr.yp.to/snuffle.html>
700 tristate "SEED cipher algorithm"
703 SEED cipher algorithm (RFC4269).
705 SEED is a 128-bit symmetric key block cipher that has been
706 developed by KISA (Korea Information Security Agency) as a
707 national standard encryption algorithm of the Republic of Korea.
708 It is a 16 round block cipher with the key size of 128 bit.
711 <http://www.kisa.or.kr/kisa/seed/jsp/seed_eng.jsp>
713 config CRYPTO_SERPENT
714 tristate "Serpent cipher algorithm"
717 Serpent cipher algorithm, by Anderson, Biham & Knudsen.
719 Keys are allowed to be from 0 to 256 bits in length, in steps
720 of 8 bits. Also includes the 'Tnepres' algorithm, a reversed
721 variant of Serpent for compatibility with old kerneli.org code.
724 <http://www.cl.cam.ac.uk/~rja14/serpent.html>
727 tristate "TEA, XTEA and XETA cipher algorithms"
730 TEA cipher algorithm.
732 Tiny Encryption Algorithm is a simple cipher that uses
733 many rounds for security. It is very fast and uses
736 Xtendend Tiny Encryption Algorithm is a modification to
737 the TEA algorithm to address a potential key weakness
738 in the TEA algorithm.
740 Xtendend Encryption Tiny Algorithm is a mis-implementation
741 of the XTEA algorithm for compatibility purposes.
743 config CRYPTO_TWOFISH
744 tristate "Twofish cipher algorithm"
746 select CRYPTO_TWOFISH_COMMON
748 Twofish cipher algorithm.
750 Twofish was submitted as an AES (Advanced Encryption Standard)
751 candidate cipher by researchers at CounterPane Systems. It is a
752 16 round block cipher supporting key sizes of 128, 192, and 256
756 <http://www.schneier.com/twofish.html>
758 config CRYPTO_TWOFISH_COMMON
761 Common parts of the Twofish cipher algorithm shared by the
762 generic c and the assembler implementations.
764 config CRYPTO_TWOFISH_586
765 tristate "Twofish cipher algorithms (i586)"
766 depends on (X86 || UML_X86) && !64BIT
768 select CRYPTO_TWOFISH_COMMON
770 Twofish cipher algorithm.
772 Twofish was submitted as an AES (Advanced Encryption Standard)
773 candidate cipher by researchers at CounterPane Systems. It is a
774 16 round block cipher supporting key sizes of 128, 192, and 256
778 <http://www.schneier.com/twofish.html>
780 config CRYPTO_TWOFISH_X86_64
781 tristate "Twofish cipher algorithm (x86_64)"
782 depends on (X86 || UML_X86) && 64BIT
784 select CRYPTO_TWOFISH_COMMON
786 Twofish cipher algorithm (x86_64).
788 Twofish was submitted as an AES (Advanced Encryption Standard)
789 candidate cipher by researchers at CounterPane Systems. It is a
790 16 round block cipher supporting key sizes of 128, 192, and 256
794 <http://www.schneier.com/twofish.html>
796 comment "Compression"
798 config CRYPTO_DEFLATE
799 tristate "Deflate compression algorithm"
804 This is the Deflate algorithm (RFC1951), specified for use in
805 IPSec with the IPCOMP protocol (RFC3173, RFC2394).
807 You will most probably want this if using IPSec.
810 tristate "Zlib compression algorithm"
816 This is the zlib algorithm.
819 tristate "LZO compression algorithm"
822 select LZO_DECOMPRESS
824 This is the LZO algorithm.
826 comment "Random Number Generation"
828 config CRYPTO_ANSI_CPRNG
829 tristate "Pseudo Random Number Generation for Cryptographic modules"
834 This option enables the generic pseudo random number generator
835 for cryptographic modules. Uses the Algorithm specified in
836 ANSI X9.31 A.2.4. Note that this option must be enabled if
837 CRYPTO_FIPS is selected
839 config CRYPTO_USER_API
842 config CRYPTO_USER_API_HASH
843 tristate "User-space interface for hash algorithms"
846 select CRYPTO_USER_API
848 This option enables the user-spaces interface for hash
851 config CRYPTO_USER_API_SKCIPHER
852 tristate "User-space interface for symmetric key cipher algorithms"
854 select CRYPTO_BLKCIPHER
855 select CRYPTO_USER_API
857 This option enables the user-spaces interface for symmetric
858 key cipher algorithms.
860 source "drivers/crypto/Kconfig"