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)"
113 depends on EXPERIMENTAL
115 Efficient table driven implementation of multiplications in the
116 field GF(2^128). This is needed by some cypher modes. This
117 option will be selected automatically if you select such a
118 cipher mode. Only select this option by hand if you expect to load
119 an external module that requires these functions.
122 tristate "Null algorithms"
124 select CRYPTO_BLKCIPHER
127 These are 'Null' algorithms, used by IPsec, which do nothing.
130 tristate "Parallel crypto engine (EXPERIMENTAL)"
131 depends on SMP && EXPERIMENTAL
133 select CRYPTO_MANAGER
136 This converts an arbitrary crypto algorithm into a parallel
137 algorithm that executes in kernel threads.
139 config CRYPTO_WORKQUEUE
143 tristate "Software async crypto daemon"
144 select CRYPTO_BLKCIPHER
146 select CRYPTO_MANAGER
147 select CRYPTO_WORKQUEUE
149 This is a generic software asynchronous crypto daemon that
150 converts an arbitrary synchronous software crypto algorithm
151 into an asynchronous algorithm that executes in a kernel thread.
153 config CRYPTO_AUTHENC
154 tristate "Authenc support"
156 select CRYPTO_BLKCIPHER
157 select CRYPTO_MANAGER
160 Authenc: Combined mode wrapper for IPsec.
161 This is required for IPSec.
164 tristate "Testing module"
166 select CRYPTO_MANAGER
168 Quick & dirty crypto test module.
170 comment "Authenticated Encryption with Associated Data"
173 tristate "CCM support"
177 Support for Counter with CBC MAC. Required for IPsec.
180 tristate "GCM/GMAC support"
185 Support for Galois/Counter Mode (GCM) and Galois Message
186 Authentication Code (GMAC). Required for IPSec.
189 tristate "Sequence Number IV Generator"
191 select CRYPTO_BLKCIPHER
194 This IV generator generates an IV based on a sequence number by
195 xoring it with a salt. This algorithm is mainly useful for CTR
197 comment "Block modes"
200 tristate "CBC support"
201 select CRYPTO_BLKCIPHER
202 select CRYPTO_MANAGER
204 CBC: Cipher Block Chaining mode
205 This block cipher algorithm is required for IPSec.
208 tristate "CTR support"
209 select CRYPTO_BLKCIPHER
211 select CRYPTO_MANAGER
214 This block cipher algorithm is required for IPSec.
217 tristate "CTS support"
218 select CRYPTO_BLKCIPHER
220 CTS: Cipher Text Stealing
221 This is the Cipher Text Stealing mode as described by
222 Section 8 of rfc2040 and referenced by rfc3962.
223 (rfc3962 includes errata information in its Appendix A)
224 This mode is required for Kerberos gss mechanism support
228 tristate "ECB support"
229 select CRYPTO_BLKCIPHER
230 select CRYPTO_MANAGER
232 ECB: Electronic CodeBook mode
233 This is the simplest block cipher algorithm. It simply encrypts
234 the input block by block.
237 tristate "LRW support (EXPERIMENTAL)"
238 depends on EXPERIMENTAL
239 select CRYPTO_BLKCIPHER
240 select CRYPTO_MANAGER
241 select CRYPTO_GF128MUL
243 LRW: Liskov Rivest Wagner, a tweakable, non malleable, non movable
244 narrow block cipher mode for dm-crypt. Use it with cipher
245 specification string aes-lrw-benbi, the key must be 256, 320 or 384.
246 The first 128, 192 or 256 bits in the key are used for AES and the
247 rest is used to tie each cipher block to its logical position.
250 tristate "PCBC support"
251 select CRYPTO_BLKCIPHER
252 select CRYPTO_MANAGER
254 PCBC: Propagating Cipher Block Chaining mode
255 This block cipher algorithm is required for RxRPC.
258 tristate "XTS support (EXPERIMENTAL)"
259 depends on EXPERIMENTAL
260 select CRYPTO_BLKCIPHER
261 select CRYPTO_MANAGER
262 select CRYPTO_GF128MUL
264 XTS: IEEE1619/D16 narrow block cipher use with aes-xts-plain,
265 key size 256, 384 or 512 bits. This implementation currently
266 can't handle a sectorsize which is not a multiple of 16 bytes.
270 select CRYPTO_BLKCIPHER
271 select CRYPTO_MANAGER
276 tristate "HMAC support"
278 select CRYPTO_MANAGER
280 HMAC: Keyed-Hashing for Message Authentication (RFC2104).
281 This is required for IPSec.
284 tristate "XCBC support"
285 depends on EXPERIMENTAL
287 select CRYPTO_MANAGER
289 XCBC: Keyed-Hashing with encryption algorithm
290 http://www.ietf.org/rfc/rfc3566.txt
291 http://csrc.nist.gov/encryption/modes/proposedmodes/
292 xcbc-mac/xcbc-mac-spec.pdf
295 tristate "VMAC support"
296 depends on EXPERIMENTAL
298 select CRYPTO_MANAGER
300 VMAC is a message authentication algorithm designed for
301 very high speed on 64-bit architectures.
304 <http://fastcrypto.org/vmac>
309 tristate "CRC32c CRC algorithm"
312 Castagnoli, et al Cyclic Redundancy-Check Algorithm. Used
313 by iSCSI for header and data digests and by others.
314 See Castagnoli93. Module will be crc32c.
316 config CRYPTO_CRC32C_INTEL
317 tristate "CRC32c INTEL hardware acceleration"
321 In Intel processor with SSE4.2 supported, the processor will
322 support CRC32C implementation using hardware accelerated CRC32
323 instruction. This option will create 'crc32c-intel' module,
324 which will enable any routine to use the CRC32 instruction to
325 gain performance compared with software implementation.
326 Module will be crc32c-intel.
329 tristate "GHASH digest algorithm"
331 select CRYPTO_GF128MUL
333 GHASH is message digest algorithm for GCM (Galois/Counter Mode).
336 tristate "MD4 digest algorithm"
339 MD4 message digest algorithm (RFC1320).
342 tristate "MD5 digest algorithm"
345 MD5 message digest algorithm (RFC1321).
347 config CRYPTO_MICHAEL_MIC
348 tristate "Michael MIC keyed digest algorithm"
351 Michael MIC is used for message integrity protection in TKIP
352 (IEEE 802.11i). This algorithm is required for TKIP, but it
353 should not be used for other purposes because of the weakness
357 tristate "RIPEMD-128 digest algorithm"
360 RIPEMD-128 (ISO/IEC 10118-3:2004).
362 RIPEMD-128 is a 128-bit cryptographic hash function. It should only
363 to be used as a secure replacement for RIPEMD. For other use cases
364 RIPEMD-160 should be used.
366 Developed by Hans Dobbertin, Antoon Bosselaers and Bart Preneel.
367 See <http://homes.esat.kuleuven.be/~bosselae/ripemd160.html>
370 tristate "RIPEMD-160 digest algorithm"
373 RIPEMD-160 (ISO/IEC 10118-3:2004).
375 RIPEMD-160 is a 160-bit cryptographic hash function. It is intended
376 to be used as a secure replacement for the 128-bit hash functions
377 MD4, MD5 and it's predecessor RIPEMD
378 (not to be confused with RIPEMD-128).
380 It's speed is comparable to SHA1 and there are no known attacks
383 Developed by Hans Dobbertin, Antoon Bosselaers and Bart Preneel.
384 See <http://homes.esat.kuleuven.be/~bosselae/ripemd160.html>
387 tristate "RIPEMD-256 digest algorithm"
390 RIPEMD-256 is an optional extension of RIPEMD-128 with a
391 256 bit hash. It is intended for applications that require
392 longer hash-results, without needing a larger security level
395 Developed by Hans Dobbertin, Antoon Bosselaers and Bart Preneel.
396 See <http://homes.esat.kuleuven.be/~bosselae/ripemd160.html>
399 tristate "RIPEMD-320 digest algorithm"
402 RIPEMD-320 is an optional extension of RIPEMD-160 with a
403 320 bit hash. It is intended for applications that require
404 longer hash-results, without needing a larger security level
407 Developed by Hans Dobbertin, Antoon Bosselaers and Bart Preneel.
408 See <http://homes.esat.kuleuven.be/~bosselae/ripemd160.html>
411 tristate "SHA1 digest algorithm"
414 SHA-1 secure hash standard (FIPS 180-1/DFIPS 180-2).
417 tristate "SHA224 and SHA256 digest algorithm"
420 SHA256 secure hash standard (DFIPS 180-2).
422 This version of SHA implements a 256 bit hash with 128 bits of
423 security against collision attacks.
425 This code also includes SHA-224, a 224 bit hash with 112 bits
426 of security against collision attacks.
429 tristate "SHA384 and SHA512 digest algorithms"
432 SHA512 secure hash standard (DFIPS 180-2).
434 This version of SHA implements a 512 bit hash with 256 bits of
435 security against collision attacks.
437 This code also includes SHA-384, a 384 bit hash with 192 bits
438 of security against collision attacks.
441 tristate "Tiger digest algorithms"
444 Tiger hash algorithm 192, 160 and 128-bit hashes
446 Tiger is a hash function optimized for 64-bit processors while
447 still having decent performance on 32-bit processors.
448 Tiger was developed by Ross Anderson and Eli Biham.
451 <http://www.cs.technion.ac.il/~biham/Reports/Tiger/>.
454 tristate "Whirlpool digest algorithms"
457 Whirlpool hash algorithm 512, 384 and 256-bit hashes
459 Whirlpool-512 is part of the NESSIE cryptographic primitives.
460 Whirlpool will be part of the ISO/IEC 10118-3:2003(E) standard
463 <http://www.larc.usp.br/~pbarreto/WhirlpoolPage.html>
465 config CRYPTO_GHASH_CLMUL_NI_INTEL
466 tristate "GHASH digest algorithm (CLMUL-NI accelerated)"
467 depends on (X86 || UML_X86) && 64BIT
471 GHASH is message digest algorithm for GCM (Galois/Counter Mode).
472 The implementation is accelerated by CLMUL-NI of Intel.
477 tristate "AES cipher algorithms"
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/CryptoToolkit/aes/> for more information.
496 config CRYPTO_AES_586
497 tristate "AES cipher algorithms (i586)"
498 depends on (X86 || UML_X86) && !64BIT
502 AES cipher algorithms (FIPS-197). AES uses the Rijndael
505 Rijndael appears to be consistently a very good performer in
506 both hardware and software across a wide range of computing
507 environments regardless of its use in feedback or non-feedback
508 modes. Its key setup time is excellent, and its key agility is
509 good. Rijndael's very low memory requirements make it very well
510 suited for restricted-space environments, in which it also
511 demonstrates excellent performance. Rijndael's operations are
512 among the easiest to defend against power and timing attacks.
514 The AES specifies three key sizes: 128, 192 and 256 bits
516 See <http://csrc.nist.gov/encryption/aes/> for more information.
518 config CRYPTO_AES_X86_64
519 tristate "AES cipher algorithms (x86_64)"
520 depends on (X86 || UML_X86) && 64BIT
524 AES cipher algorithms (FIPS-197). AES uses the Rijndael
527 Rijndael appears to be consistently a very good performer in
528 both hardware and software across a wide range of computing
529 environments regardless of its use in feedback or non-feedback
530 modes. Its key setup time is excellent, and its key agility is
531 good. Rijndael's very low memory requirements make it very well
532 suited for restricted-space environments, in which it also
533 demonstrates excellent performance. Rijndael's operations are
534 among the easiest to defend against power and timing attacks.
536 The AES specifies three key sizes: 128, 192 and 256 bits
538 See <http://csrc.nist.gov/encryption/aes/> for more information.
540 config CRYPTO_AES_NI_INTEL
541 tristate "AES cipher algorithms (AES-NI)"
542 depends on (X86 || UML_X86) && 64BIT
543 select CRYPTO_AES_X86_64
548 Use Intel AES-NI instructions for AES algorithm.
550 AES cipher algorithms (FIPS-197). AES uses the Rijndael
553 Rijndael appears to be consistently a very good performer in
554 both hardware and software across a wide range of computing
555 environments regardless of its use in feedback or non-feedback
556 modes. Its key setup time is excellent, and its key agility is
557 good. Rijndael's very low memory requirements make it very well
558 suited for restricted-space environments, in which it also
559 demonstrates excellent performance. Rijndael's operations are
560 among the easiest to defend against power and timing attacks.
562 The AES specifies three key sizes: 128, 192 and 256 bits
564 See <http://csrc.nist.gov/encryption/aes/> for more information.
566 In addition to AES cipher algorithm support, the
567 acceleration for some popular block cipher mode is supported
568 too, including ECB, CBC, CTR, LRW, PCBC, XTS.
571 tristate "Anubis cipher algorithm"
574 Anubis cipher algorithm.
576 Anubis is a variable key length cipher which can use keys from
577 128 bits to 320 bits in length. It was evaluated as a entrant
578 in the NESSIE competition.
581 <https://www.cosic.esat.kuleuven.be/nessie/reports/>
582 <http://www.larc.usp.br/~pbarreto/AnubisPage.html>
585 tristate "ARC4 cipher algorithm"
588 ARC4 cipher algorithm.
590 ARC4 is a stream cipher using keys ranging from 8 bits to 2048
591 bits in length. This algorithm is required for driver-based
592 WEP, but it should not be for other purposes because of the
593 weakness of the algorithm.
595 config CRYPTO_BLOWFISH
596 tristate "Blowfish cipher algorithm"
599 Blowfish cipher algorithm, by Bruce Schneier.
601 This is a variable key length cipher which can use keys from 32
602 bits to 448 bits in length. It's fast, simple and specifically
603 designed for use on "large microprocessors".
606 <http://www.schneier.com/blowfish.html>
608 config CRYPTO_CAMELLIA
609 tristate "Camellia cipher algorithms"
613 Camellia cipher algorithms module.
615 Camellia is a symmetric key block cipher developed jointly
616 at NTT and Mitsubishi Electric Corporation.
618 The Camellia specifies three key sizes: 128, 192 and 256 bits.
621 <https://info.isl.ntt.co.jp/crypt/eng/camellia/index_s.html>
624 tristate "CAST5 (CAST-128) cipher algorithm"
627 The CAST5 encryption algorithm (synonymous with CAST-128) is
628 described in RFC2144.
631 tristate "CAST6 (CAST-256) cipher algorithm"
634 The CAST6 encryption algorithm (synonymous with CAST-256) is
635 described in RFC2612.
638 tristate "DES and Triple DES EDE cipher algorithms"
641 DES cipher algorithm (FIPS 46-2), and Triple DES EDE (FIPS 46-3).
644 tristate "FCrypt cipher algorithm"
646 select CRYPTO_BLKCIPHER
648 FCrypt algorithm used by RxRPC.
651 tristate "Khazad cipher algorithm"
654 Khazad cipher algorithm.
656 Khazad was a finalist in the initial NESSIE competition. It is
657 an algorithm optimized for 64-bit processors with good performance
658 on 32-bit processors. Khazad uses an 128 bit key size.
661 <http://www.larc.usp.br/~pbarreto/KhazadPage.html>
663 config CRYPTO_SALSA20
664 tristate "Salsa20 stream cipher algorithm (EXPERIMENTAL)"
665 depends on EXPERIMENTAL
666 select CRYPTO_BLKCIPHER
668 Salsa20 stream cipher algorithm.
670 Salsa20 is a stream cipher submitted to eSTREAM, the ECRYPT
671 Stream Cipher Project. See <http://www.ecrypt.eu.org/stream/>
673 The Salsa20 stream cipher algorithm is designed by Daniel J.
674 Bernstein <djb@cr.yp.to>. See <http://cr.yp.to/snuffle.html>
676 config CRYPTO_SALSA20_586
677 tristate "Salsa20 stream cipher algorithm (i586) (EXPERIMENTAL)"
678 depends on (X86 || UML_X86) && !64BIT
679 depends on EXPERIMENTAL
680 select CRYPTO_BLKCIPHER
682 Salsa20 stream cipher algorithm.
684 Salsa20 is a stream cipher submitted to eSTREAM, the ECRYPT
685 Stream Cipher Project. See <http://www.ecrypt.eu.org/stream/>
687 The Salsa20 stream cipher algorithm is designed by Daniel J.
688 Bernstein <djb@cr.yp.to>. See <http://cr.yp.to/snuffle.html>
690 config CRYPTO_SALSA20_X86_64
691 tristate "Salsa20 stream cipher algorithm (x86_64) (EXPERIMENTAL)"
692 depends on (X86 || UML_X86) && 64BIT
693 depends on EXPERIMENTAL
694 select CRYPTO_BLKCIPHER
696 Salsa20 stream cipher algorithm.
698 Salsa20 is a stream cipher submitted to eSTREAM, the ECRYPT
699 Stream Cipher Project. See <http://www.ecrypt.eu.org/stream/>
701 The Salsa20 stream cipher algorithm is designed by Daniel J.
702 Bernstein <djb@cr.yp.to>. See <http://cr.yp.to/snuffle.html>
705 tristate "SEED cipher algorithm"
708 SEED cipher algorithm (RFC4269).
710 SEED is a 128-bit symmetric key block cipher that has been
711 developed by KISA (Korea Information Security Agency) as a
712 national standard encryption algorithm of the Republic of Korea.
713 It is a 16 round block cipher with the key size of 128 bit.
716 <http://www.kisa.or.kr/kisa/seed/jsp/seed_eng.jsp>
718 config CRYPTO_SERPENT
719 tristate "Serpent cipher algorithm"
722 Serpent cipher algorithm, by Anderson, Biham & Knudsen.
724 Keys are allowed to be from 0 to 256 bits in length, in steps
725 of 8 bits. Also includes the 'Tnepres' algorithm, a reversed
726 variant of Serpent for compatibility with old kerneli.org code.
729 <http://www.cl.cam.ac.uk/~rja14/serpent.html>
732 tristate "TEA, XTEA and XETA cipher algorithms"
735 TEA cipher algorithm.
737 Tiny Encryption Algorithm is a simple cipher that uses
738 many rounds for security. It is very fast and uses
741 Xtendend Tiny Encryption Algorithm is a modification to
742 the TEA algorithm to address a potential key weakness
743 in the TEA algorithm.
745 Xtendend Encryption Tiny Algorithm is a mis-implementation
746 of the XTEA algorithm for compatibility purposes.
748 config CRYPTO_TWOFISH
749 tristate "Twofish cipher algorithm"
751 select CRYPTO_TWOFISH_COMMON
753 Twofish cipher algorithm.
755 Twofish was submitted as an AES (Advanced Encryption Standard)
756 candidate cipher by researchers at CounterPane Systems. It is a
757 16 round block cipher supporting key sizes of 128, 192, and 256
761 <http://www.schneier.com/twofish.html>
763 config CRYPTO_TWOFISH_COMMON
766 Common parts of the Twofish cipher algorithm shared by the
767 generic c and the assembler implementations.
769 config CRYPTO_TWOFISH_586
770 tristate "Twofish cipher algorithms (i586)"
771 depends on (X86 || UML_X86) && !64BIT
773 select CRYPTO_TWOFISH_COMMON
775 Twofish cipher algorithm.
777 Twofish was submitted as an AES (Advanced Encryption Standard)
778 candidate cipher by researchers at CounterPane Systems. It is a
779 16 round block cipher supporting key sizes of 128, 192, and 256
783 <http://www.schneier.com/twofish.html>
785 config CRYPTO_TWOFISH_X86_64
786 tristate "Twofish cipher algorithm (x86_64)"
787 depends on (X86 || UML_X86) && 64BIT
789 select CRYPTO_TWOFISH_COMMON
791 Twofish cipher algorithm (x86_64).
793 Twofish was submitted as an AES (Advanced Encryption Standard)
794 candidate cipher by researchers at CounterPane Systems. It is a
795 16 round block cipher supporting key sizes of 128, 192, and 256
799 <http://www.schneier.com/twofish.html>
801 comment "Compression"
803 config CRYPTO_DEFLATE
804 tristate "Deflate compression algorithm"
809 This is the Deflate algorithm (RFC1951), specified for use in
810 IPSec with the IPCOMP protocol (RFC3173, RFC2394).
812 You will most probably want this if using IPSec.
815 tristate "Zlib compression algorithm"
821 This is the zlib algorithm.
824 tristate "LZO compression algorithm"
827 select LZO_DECOMPRESS
829 This is the LZO algorithm.
831 comment "Random Number Generation"
833 config CRYPTO_ANSI_CPRNG
834 tristate "Pseudo Random Number Generation for Cryptographic modules"
839 This option enables the generic pseudo random number generator
840 for cryptographic modules. Uses the Algorithm specified in
841 ANSI X9.31 A.2.4. Note that this option must be enabled if
842 CRYPTO_FIPS is selected
844 config CRYPTO_USER_API
847 source "drivers/crypto/Kconfig"