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
35 This option provides the API for cryptographic algorithms.
41 config CRYPTO_BLKCIPHER
55 tristate "Cryptographic algorithm manager"
58 select CRYPTO_BLKCIPHER
60 Create default cryptographic template instantiations such as
63 config CRYPTO_GF128MUL
64 tristate "GF(2^128) multiplication functions (EXPERIMENTAL)"
65 depends on EXPERIMENTAL
67 Efficient table driven implementation of multiplications in the
68 field GF(2^128). This is needed by some cypher modes. This
69 option will be selected automatically if you select such a
70 cipher mode. Only select this option by hand if you expect to load
71 an external module that requires these functions.
74 tristate "Null algorithms"
76 select CRYPTO_BLKCIPHER
78 These are 'Null' algorithms, used by IPsec, which do nothing.
81 tristate "Software async crypto daemon"
82 select CRYPTO_BLKCIPHER
86 This is a generic software asynchronous crypto daemon that
87 converts an arbitrary synchronous software crypto algorithm
88 into an asynchronous algorithm that executes in a kernel thread.
91 tristate "Authenc support"
93 select CRYPTO_BLKCIPHER
97 Authenc: Combined mode wrapper for IPsec.
98 This is required for IPSec.
101 tristate "Testing module"
103 select CRYPTO_MANAGER
105 Quick & dirty crypto test module.
107 comment "Authenticated Encryption with Associated Data"
110 tristate "CCM support"
114 Support for Counter with CBC MAC. Required for IPsec.
117 tristate "GCM/GMAC support"
120 select CRYPTO_GF128MUL
122 Support for Galois/Counter Mode (GCM) and Galois Message
123 Authentication Code (GMAC). Required for IPSec.
126 tristate "Sequence Number IV Generator"
128 select CRYPTO_BLKCIPHER
131 This IV generator generates an IV based on a sequence number by
132 xoring it with a salt. This algorithm is mainly useful for CTR
134 comment "Block modes"
137 tristate "CBC support"
138 select CRYPTO_BLKCIPHER
139 select CRYPTO_MANAGER
141 CBC: Cipher Block Chaining mode
142 This block cipher algorithm is required for IPSec.
145 tristate "CTR support"
146 select CRYPTO_BLKCIPHER
148 select CRYPTO_MANAGER
151 This block cipher algorithm is required for IPSec.
154 tristate "CTS support"
155 select CRYPTO_BLKCIPHER
157 CTS: Cipher Text Stealing
158 This is the Cipher Text Stealing mode as described by
159 Section 8 of rfc2040 and referenced by rfc3962.
160 (rfc3962 includes errata information in its Appendix A)
161 This mode is required for Kerberos gss mechanism support
165 tristate "ECB support"
166 select CRYPTO_BLKCIPHER
167 select CRYPTO_MANAGER
169 ECB: Electronic CodeBook mode
170 This is the simplest block cipher algorithm. It simply encrypts
171 the input block by block.
174 tristate "LRW support (EXPERIMENTAL)"
175 depends on EXPERIMENTAL
176 select CRYPTO_BLKCIPHER
177 select CRYPTO_MANAGER
178 select CRYPTO_GF128MUL
180 LRW: Liskov Rivest Wagner, a tweakable, non malleable, non movable
181 narrow block cipher mode for dm-crypt. Use it with cipher
182 specification string aes-lrw-benbi, the key must be 256, 320 or 384.
183 The first 128, 192 or 256 bits in the key are used for AES and the
184 rest is used to tie each cipher block to its logical position.
187 tristate "PCBC support"
188 select CRYPTO_BLKCIPHER
189 select CRYPTO_MANAGER
191 PCBC: Propagating Cipher Block Chaining mode
192 This block cipher algorithm is required for RxRPC.
195 tristate "XTS support (EXPERIMENTAL)"
196 depends on EXPERIMENTAL
197 select CRYPTO_BLKCIPHER
198 select CRYPTO_MANAGER
199 select CRYPTO_GF128MUL
201 XTS: IEEE1619/D16 narrow block cipher use with aes-xts-plain,
202 key size 256, 384 or 512 bits. This implementation currently
203 can't handle a sectorsize which is not a multiple of 16 bytes.
208 tristate "HMAC support"
210 select CRYPTO_MANAGER
212 HMAC: Keyed-Hashing for Message Authentication (RFC2104).
213 This is required for IPSec.
216 tristate "XCBC support"
217 depends on EXPERIMENTAL
219 select CRYPTO_MANAGER
221 XCBC: Keyed-Hashing with encryption algorithm
222 http://www.ietf.org/rfc/rfc3566.txt
223 http://csrc.nist.gov/encryption/modes/proposedmodes/
224 xcbc-mac/xcbc-mac-spec.pdf
229 tristate "CRC32c CRC algorithm"
233 Castagnoli, et al Cyclic Redundancy-Check Algorithm. Used
234 by iSCSI for header and data digests and by others.
235 See Castagnoli93. This implementation uses lib/libcrc32c.
236 Module will be crc32c.
238 config CRYPTO_CRC32C_INTEL
239 tristate "CRC32c INTEL hardware acceleration"
243 In Intel processor with SSE4.2 supported, the processor will
244 support CRC32C implementation using hardware accelerated CRC32
245 instruction. This option will create 'crc32c-intel' module,
246 which will enable any routine to use the CRC32 instruction to
247 gain performance compared with software implementation.
248 Module will be crc32c-intel.
251 tristate "MD4 digest algorithm"
254 MD4 message digest algorithm (RFC1320).
257 tristate "MD5 digest algorithm"
260 MD5 message digest algorithm (RFC1321).
262 config CRYPTO_MICHAEL_MIC
263 tristate "Michael MIC keyed digest algorithm"
266 Michael MIC is used for message integrity protection in TKIP
267 (IEEE 802.11i). This algorithm is required for TKIP, but it
268 should not be used for other purposes because of the weakness
272 tristate "RIPEMD-128 digest algorithm"
275 RIPEMD-128 (ISO/IEC 10118-3:2004).
277 RIPEMD-128 is a 128-bit cryptographic hash function. It should only
278 to be used as a secure replacement for RIPEMD. For other use cases
279 RIPEMD-160 should be used.
281 Developed by Hans Dobbertin, Antoon Bosselaers and Bart Preneel.
282 See <http://home.esat.kuleuven.be/~bosselae/ripemd160.html>
285 tristate "RIPEMD-160 digest algorithm"
288 RIPEMD-160 (ISO/IEC 10118-3:2004).
290 RIPEMD-160 is a 160-bit cryptographic hash function. It is intended
291 to be used as a secure replacement for the 128-bit hash functions
292 MD4, MD5 and it's predecessor RIPEMD
293 (not to be confused with RIPEMD-128).
295 It's speed is comparable to SHA1 and there are no known attacks
298 Developed by Hans Dobbertin, Antoon Bosselaers and Bart Preneel.
299 See <http://home.esat.kuleuven.be/~bosselae/ripemd160.html>
302 tristate "RIPEMD-256 digest algorithm"
305 RIPEMD-256 is an optional extension of RIPEMD-128 with a
306 256 bit hash. It is intended for applications that require
307 longer hash-results, without needing a larger security level
310 Developed by Hans Dobbertin, Antoon Bosselaers and Bart Preneel.
311 See <http://home.esat.kuleuven.be/~bosselae/ripemd160.html>
314 tristate "RIPEMD-320 digest algorithm"
317 RIPEMD-320 is an optional extension of RIPEMD-160 with a
318 320 bit hash. It is intended for applications that require
319 longer hash-results, without needing a larger security level
322 Developed by Hans Dobbertin, Antoon Bosselaers and Bart Preneel.
323 See <http://home.esat.kuleuven.be/~bosselae/ripemd160.html>
326 tristate "SHA1 digest algorithm"
329 SHA-1 secure hash standard (FIPS 180-1/DFIPS 180-2).
332 tristate "SHA224 and SHA256 digest algorithm"
335 SHA256 secure hash standard (DFIPS 180-2).
337 This version of SHA implements a 256 bit hash with 128 bits of
338 security against collision attacks.
340 This code also includes SHA-224, a 224 bit hash with 112 bits
341 of security against collision attacks.
344 tristate "SHA384 and SHA512 digest algorithms"
347 SHA512 secure hash standard (DFIPS 180-2).
349 This version of SHA implements a 512 bit hash with 256 bits of
350 security against collision attacks.
352 This code also includes SHA-384, a 384 bit hash with 192 bits
353 of security against collision attacks.
356 tristate "Tiger digest algorithms"
359 Tiger hash algorithm 192, 160 and 128-bit hashes
361 Tiger is a hash function optimized for 64-bit processors while
362 still having decent performance on 32-bit processors.
363 Tiger was developed by Ross Anderson and Eli Biham.
366 <http://www.cs.technion.ac.il/~biham/Reports/Tiger/>.
369 tristate "Whirlpool digest algorithms"
372 Whirlpool hash algorithm 512, 384 and 256-bit hashes
374 Whirlpool-512 is part of the NESSIE cryptographic primitives.
375 Whirlpool will be part of the ISO/IEC 10118-3:2003(E) standard
378 <http://planeta.terra.com.br/informatica/paulobarreto/WhirlpoolPage.html>
383 tristate "AES cipher algorithms"
386 AES cipher algorithms (FIPS-197). AES uses the Rijndael
389 Rijndael appears to be consistently a very good performer in
390 both hardware and software across a wide range of computing
391 environments regardless of its use in feedback or non-feedback
392 modes. Its key setup time is excellent, and its key agility is
393 good. Rijndael's very low memory requirements make it very well
394 suited for restricted-space environments, in which it also
395 demonstrates excellent performance. Rijndael's operations are
396 among the easiest to defend against power and timing attacks.
398 The AES specifies three key sizes: 128, 192 and 256 bits
400 See <http://csrc.nist.gov/CryptoToolkit/aes/> for more information.
402 config CRYPTO_AES_586
403 tristate "AES cipher algorithms (i586)"
404 depends on (X86 || UML_X86) && !64BIT
408 AES cipher algorithms (FIPS-197). AES uses the Rijndael
411 Rijndael appears to be consistently a very good performer in
412 both hardware and software across a wide range of computing
413 environments regardless of its use in feedback or non-feedback
414 modes. Its key setup time is excellent, and its key agility is
415 good. Rijndael's very low memory requirements make it very well
416 suited for restricted-space environments, in which it also
417 demonstrates excellent performance. Rijndael's operations are
418 among the easiest to defend against power and timing attacks.
420 The AES specifies three key sizes: 128, 192 and 256 bits
422 See <http://csrc.nist.gov/encryption/aes/> for more information.
424 config CRYPTO_AES_X86_64
425 tristate "AES cipher algorithms (x86_64)"
426 depends on (X86 || UML_X86) && 64BIT
430 AES cipher algorithms (FIPS-197). AES uses the Rijndael
433 Rijndael appears to be consistently a very good performer in
434 both hardware and software across a wide range of computing
435 environments regardless of its use in feedback or non-feedback
436 modes. Its key setup time is excellent, and its key agility is
437 good. Rijndael's very low memory requirements make it very well
438 suited for restricted-space environments, in which it also
439 demonstrates excellent performance. Rijndael's operations are
440 among the easiest to defend against power and timing attacks.
442 The AES specifies three key sizes: 128, 192 and 256 bits
444 See <http://csrc.nist.gov/encryption/aes/> for more information.
447 tristate "Anubis cipher algorithm"
450 Anubis cipher algorithm.
452 Anubis is a variable key length cipher which can use keys from
453 128 bits to 320 bits in length. It was evaluated as a entrant
454 in the NESSIE competition.
457 <https://www.cosic.esat.kuleuven.ac.be/nessie/reports/>
458 <http://planeta.terra.com.br/informatica/paulobarreto/AnubisPage.html>
461 tristate "ARC4 cipher algorithm"
464 ARC4 cipher algorithm.
466 ARC4 is a stream cipher using keys ranging from 8 bits to 2048
467 bits in length. This algorithm is required for driver-based
468 WEP, but it should not be for other purposes because of the
469 weakness of the algorithm.
471 config CRYPTO_BLOWFISH
472 tristate "Blowfish cipher algorithm"
475 Blowfish cipher algorithm, by Bruce Schneier.
477 This is a variable key length cipher which can use keys from 32
478 bits to 448 bits in length. It's fast, simple and specifically
479 designed for use on "large microprocessors".
482 <http://www.schneier.com/blowfish.html>
484 config CRYPTO_CAMELLIA
485 tristate "Camellia cipher algorithms"
489 Camellia cipher algorithms module.
491 Camellia is a symmetric key block cipher developed jointly
492 at NTT and Mitsubishi Electric Corporation.
494 The Camellia specifies three key sizes: 128, 192 and 256 bits.
497 <https://info.isl.ntt.co.jp/crypt/eng/camellia/index_s.html>
500 tristate "CAST5 (CAST-128) cipher algorithm"
503 The CAST5 encryption algorithm (synonymous with CAST-128) is
504 described in RFC2144.
507 tristate "CAST6 (CAST-256) cipher algorithm"
510 The CAST6 encryption algorithm (synonymous with CAST-256) is
511 described in RFC2612.
514 tristate "DES and Triple DES EDE cipher algorithms"
517 DES cipher algorithm (FIPS 46-2), and Triple DES EDE (FIPS 46-3).
520 tristate "FCrypt cipher algorithm"
522 select CRYPTO_BLKCIPHER
524 FCrypt algorithm used by RxRPC.
527 tristate "Khazad cipher algorithm"
530 Khazad cipher algorithm.
532 Khazad was a finalist in the initial NESSIE competition. It is
533 an algorithm optimized for 64-bit processors with good performance
534 on 32-bit processors. Khazad uses an 128 bit key size.
537 <http://planeta.terra.com.br/informatica/paulobarreto/KhazadPage.html>
539 config CRYPTO_SALSA20
540 tristate "Salsa20 stream cipher algorithm (EXPERIMENTAL)"
541 depends on EXPERIMENTAL
542 select CRYPTO_BLKCIPHER
544 Salsa20 stream cipher algorithm.
546 Salsa20 is a stream cipher submitted to eSTREAM, the ECRYPT
547 Stream Cipher Project. See <http://www.ecrypt.eu.org/stream/>
549 The Salsa20 stream cipher algorithm is designed by Daniel J.
550 Bernstein <djb@cr.yp.to>. See <http://cr.yp.to/snuffle.html>
552 config CRYPTO_SALSA20_586
553 tristate "Salsa20 stream cipher algorithm (i586) (EXPERIMENTAL)"
554 depends on (X86 || UML_X86) && !64BIT
555 depends on EXPERIMENTAL
556 select CRYPTO_BLKCIPHER
558 Salsa20 stream cipher algorithm.
560 Salsa20 is a stream cipher submitted to eSTREAM, the ECRYPT
561 Stream Cipher Project. See <http://www.ecrypt.eu.org/stream/>
563 The Salsa20 stream cipher algorithm is designed by Daniel J.
564 Bernstein <djb@cr.yp.to>. See <http://cr.yp.to/snuffle.html>
566 config CRYPTO_SALSA20_X86_64
567 tristate "Salsa20 stream cipher algorithm (x86_64) (EXPERIMENTAL)"
568 depends on (X86 || UML_X86) && 64BIT
569 depends on EXPERIMENTAL
570 select CRYPTO_BLKCIPHER
572 Salsa20 stream cipher algorithm.
574 Salsa20 is a stream cipher submitted to eSTREAM, the ECRYPT
575 Stream Cipher Project. See <http://www.ecrypt.eu.org/stream/>
577 The Salsa20 stream cipher algorithm is designed by Daniel J.
578 Bernstein <djb@cr.yp.to>. See <http://cr.yp.to/snuffle.html>
581 tristate "SEED cipher algorithm"
584 SEED cipher algorithm (RFC4269).
586 SEED is a 128-bit symmetric key block cipher that has been
587 developed by KISA (Korea Information Security Agency) as a
588 national standard encryption algorithm of the Republic of Korea.
589 It is a 16 round block cipher with the key size of 128 bit.
592 <http://www.kisa.or.kr/kisa/seed/jsp/seed_eng.jsp>
594 config CRYPTO_SERPENT
595 tristate "Serpent cipher algorithm"
598 Serpent cipher algorithm, by Anderson, Biham & Knudsen.
600 Keys are allowed to be from 0 to 256 bits in length, in steps
601 of 8 bits. Also includes the 'Tnepres' algorithm, a reversed
602 variant of Serpent for compatibility with old kerneli.org code.
605 <http://www.cl.cam.ac.uk/~rja14/serpent.html>
608 tristate "TEA, XTEA and XETA cipher algorithms"
611 TEA cipher algorithm.
613 Tiny Encryption Algorithm is a simple cipher that uses
614 many rounds for security. It is very fast and uses
617 Xtendend Tiny Encryption Algorithm is a modification to
618 the TEA algorithm to address a potential key weakness
619 in the TEA algorithm.
621 Xtendend Encryption Tiny Algorithm is a mis-implementation
622 of the XTEA algorithm for compatibility purposes.
624 config CRYPTO_TWOFISH
625 tristate "Twofish cipher algorithm"
627 select CRYPTO_TWOFISH_COMMON
629 Twofish cipher algorithm.
631 Twofish was submitted as an AES (Advanced Encryption Standard)
632 candidate cipher by researchers at CounterPane Systems. It is a
633 16 round block cipher supporting key sizes of 128, 192, and 256
637 <http://www.schneier.com/twofish.html>
639 config CRYPTO_TWOFISH_COMMON
642 Common parts of the Twofish cipher algorithm shared by the
643 generic c and the assembler implementations.
645 config CRYPTO_TWOFISH_586
646 tristate "Twofish cipher algorithms (i586)"
647 depends on (X86 || UML_X86) && !64BIT
649 select CRYPTO_TWOFISH_COMMON
651 Twofish cipher algorithm.
653 Twofish was submitted as an AES (Advanced Encryption Standard)
654 candidate cipher by researchers at CounterPane Systems. It is a
655 16 round block cipher supporting key sizes of 128, 192, and 256
659 <http://www.schneier.com/twofish.html>
661 config CRYPTO_TWOFISH_X86_64
662 tristate "Twofish cipher algorithm (x86_64)"
663 depends on (X86 || UML_X86) && 64BIT
665 select CRYPTO_TWOFISH_COMMON
667 Twofish cipher algorithm (x86_64).
669 Twofish was submitted as an AES (Advanced Encryption Standard)
670 candidate cipher by researchers at CounterPane Systems. It is a
671 16 round block cipher supporting key sizes of 128, 192, and 256
675 <http://www.schneier.com/twofish.html>
677 comment "Compression"
679 config CRYPTO_DEFLATE
680 tristate "Deflate compression algorithm"
685 This is the Deflate algorithm (RFC1951), specified for use in
686 IPSec with the IPCOMP protocol (RFC3173, RFC2394).
688 You will most probably want this if using IPSec.
691 tristate "LZO compression algorithm"
694 select LZO_DECOMPRESS
696 This is the LZO algorithm.
698 comment "Random Number Generation"
700 config CRYPTO_ANSI_CPRNG
701 tristate "Pseudo Random Number Generation for Cryptographic modules"
706 This option enables the generic pseudo random number generator
707 for cryptographic modules. Uses the Algorithm specified in
710 source "drivers/crypto/Kconfig"