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
50 tristate "Cryptographic algorithm manager"
53 select CRYPTO_BLKCIPHER
55 Create default cryptographic template instantiations such as
58 config CRYPTO_GF128MUL
59 tristate "GF(2^128) multiplication functions (EXPERIMENTAL)"
60 depends on EXPERIMENTAL
62 Efficient table driven implementation of multiplications in the
63 field GF(2^128). This is needed by some cypher modes. This
64 option will be selected automatically if you select such a
65 cipher mode. Only select this option by hand if you expect to load
66 an external module that requires these functions.
69 tristate "Null algorithms"
71 select CRYPTO_BLKCIPHER
73 These are 'Null' algorithms, used by IPsec, which do nothing.
76 tristate "Software async crypto daemon"
77 select CRYPTO_BLKCIPHER
81 This is a generic software asynchronous crypto daemon that
82 converts an arbitrary synchronous software crypto algorithm
83 into an asynchronous algorithm that executes in a kernel thread.
86 tristate "Authenc support"
88 select CRYPTO_BLKCIPHER
92 Authenc: Combined mode wrapper for IPsec.
93 This is required for IPSec.
96 tristate "Testing module"
100 Quick & dirty crypto test module.
102 comment "Authenticated Encryption with Associated Data"
105 tristate "CCM support"
109 Support for Counter with CBC MAC. Required for IPsec.
112 tristate "GCM/GMAC support"
115 select CRYPTO_GF128MUL
117 Support for Galois/Counter Mode (GCM) and Galois Message
118 Authentication Code (GMAC). Required for IPSec.
121 tristate "Sequence Number IV Generator"
123 select CRYPTO_BLKCIPHER
125 This IV generator generates an IV based on a sequence number by
126 xoring it with a salt. This algorithm is mainly useful for CTR
128 comment "Block modes"
131 tristate "CBC support"
132 select CRYPTO_BLKCIPHER
133 select CRYPTO_MANAGER
135 CBC: Cipher Block Chaining mode
136 This block cipher algorithm is required for IPSec.
139 tristate "CTR support"
140 select CRYPTO_BLKCIPHER
142 select CRYPTO_MANAGER
145 This block cipher algorithm is required for IPSec.
148 tristate "CTS support"
149 select CRYPTO_BLKCIPHER
151 CTS: Cipher Text Stealing
152 This is the Cipher Text Stealing mode as described by
153 Section 8 of rfc2040 and referenced by rfc3962.
154 (rfc3962 includes errata information in its Appendix A)
155 This mode is required for Kerberos gss mechanism support
159 tristate "ECB support"
160 select CRYPTO_BLKCIPHER
161 select CRYPTO_MANAGER
163 ECB: Electronic CodeBook mode
164 This is the simplest block cipher algorithm. It simply encrypts
165 the input block by block.
168 tristate "LRW support (EXPERIMENTAL)"
169 depends on EXPERIMENTAL
170 select CRYPTO_BLKCIPHER
171 select CRYPTO_MANAGER
172 select CRYPTO_GF128MUL
174 LRW: Liskov Rivest Wagner, a tweakable, non malleable, non movable
175 narrow block cipher mode for dm-crypt. Use it with cipher
176 specification string aes-lrw-benbi, the key must be 256, 320 or 384.
177 The first 128, 192 or 256 bits in the key are used for AES and the
178 rest is used to tie each cipher block to its logical position.
181 tristate "PCBC support"
182 select CRYPTO_BLKCIPHER
183 select CRYPTO_MANAGER
185 PCBC: Propagating Cipher Block Chaining mode
186 This block cipher algorithm is required for RxRPC.
189 tristate "XTS support (EXPERIMENTAL)"
190 depends on EXPERIMENTAL
191 select CRYPTO_BLKCIPHER
192 select CRYPTO_MANAGER
193 select CRYPTO_GF128MUL
195 XTS: IEEE1619/D16 narrow block cipher use with aes-xts-plain,
196 key size 256, 384 or 512 bits. This implementation currently
197 can't handle a sectorsize which is not a multiple of 16 bytes.
202 tristate "HMAC support"
204 select CRYPTO_MANAGER
206 HMAC: Keyed-Hashing for Message Authentication (RFC2104).
207 This is required for IPSec.
210 tristate "XCBC support"
211 depends on EXPERIMENTAL
213 select CRYPTO_MANAGER
215 XCBC: Keyed-Hashing with encryption algorithm
216 http://www.ietf.org/rfc/rfc3566.txt
217 http://csrc.nist.gov/encryption/modes/proposedmodes/
218 xcbc-mac/xcbc-mac-spec.pdf
223 tristate "CRC32c CRC algorithm"
227 Castagnoli, et al Cyclic Redundancy-Check Algorithm. Used
228 by iSCSI for header and data digests and by others.
229 See Castagnoli93. This implementation uses lib/libcrc32c.
230 Module will be crc32c.
232 config CRYPTO_CRC32C_INTEL
233 tristate "CRC32c INTEL hardware acceleration"
237 In Intel processor with SSE4.2 supported, the processor will
238 support CRC32C implementation using hardware accelerated CRC32
239 instruction. This option will create 'crc32c-intel' module,
240 which will enable any routine to use the CRC32 instruction to
241 gain performance compared with software implementation.
242 Module will be crc32c-intel.
245 tristate "MD4 digest algorithm"
248 MD4 message digest algorithm (RFC1320).
251 tristate "MD5 digest algorithm"
254 MD5 message digest algorithm (RFC1321).
256 config CRYPTO_MICHAEL_MIC
257 tristate "Michael MIC keyed digest algorithm"
260 Michael MIC is used for message integrity protection in TKIP
261 (IEEE 802.11i). This algorithm is required for TKIP, but it
262 should not be used for other purposes because of the weakness
266 tristate "RIPEMD-128 digest algorithm"
269 RIPEMD-128 (ISO/IEC 10118-3:2004).
271 RIPEMD-128 is a 128-bit cryptographic hash function. It should only
272 to be used as a secure replacement for RIPEMD. For other use cases
273 RIPEMD-160 should be used.
275 Developed by Hans Dobbertin, Antoon Bosselaers and Bart Preneel.
276 See <http://home.esat.kuleuven.be/~bosselae/ripemd160.html>
279 tristate "RIPEMD-160 digest algorithm"
282 RIPEMD-160 (ISO/IEC 10118-3:2004).
284 RIPEMD-160 is a 160-bit cryptographic hash function. It is intended
285 to be used as a secure replacement for the 128-bit hash functions
286 MD4, MD5 and it's predecessor RIPEMD
287 (not to be confused with RIPEMD-128).
289 It's speed is comparable to SHA1 and there are no known attacks
292 Developed by Hans Dobbertin, Antoon Bosselaers and Bart Preneel.
293 See <http://home.esat.kuleuven.be/~bosselae/ripemd160.html>
296 tristate "RIPEMD-256 digest algorithm"
299 RIPEMD-256 is an optional extension of RIPEMD-128 with a
300 256 bit hash. It is intended for applications that require
301 longer hash-results, without needing a larger security level
304 Developed by Hans Dobbertin, Antoon Bosselaers and Bart Preneel.
305 See <http://home.esat.kuleuven.be/~bosselae/ripemd160.html>
308 tristate "RIPEMD-320 digest algorithm"
311 RIPEMD-320 is an optional extension of RIPEMD-160 with a
312 320 bit hash. It is intended for applications that require
313 longer hash-results, without needing a larger security level
316 Developed by Hans Dobbertin, Antoon Bosselaers and Bart Preneel.
317 See <http://home.esat.kuleuven.be/~bosselae/ripemd160.html>
320 tristate "SHA1 digest algorithm"
323 SHA-1 secure hash standard (FIPS 180-1/DFIPS 180-2).
326 tristate "SHA224 and SHA256 digest algorithm"
329 SHA256 secure hash standard (DFIPS 180-2).
331 This version of SHA implements a 256 bit hash with 128 bits of
332 security against collision attacks.
334 This code also includes SHA-224, a 224 bit hash with 112 bits
335 of security against collision attacks.
338 tristate "SHA384 and SHA512 digest algorithms"
341 SHA512 secure hash standard (DFIPS 180-2).
343 This version of SHA implements a 512 bit hash with 256 bits of
344 security against collision attacks.
346 This code also includes SHA-384, a 384 bit hash with 192 bits
347 of security against collision attacks.
350 tristate "Tiger digest algorithms"
353 Tiger hash algorithm 192, 160 and 128-bit hashes
355 Tiger is a hash function optimized for 64-bit processors while
356 still having decent performance on 32-bit processors.
357 Tiger was developed by Ross Anderson and Eli Biham.
360 <http://www.cs.technion.ac.il/~biham/Reports/Tiger/>.
363 tristate "Whirlpool digest algorithms"
366 Whirlpool hash algorithm 512, 384 and 256-bit hashes
368 Whirlpool-512 is part of the NESSIE cryptographic primitives.
369 Whirlpool will be part of the ISO/IEC 10118-3:2003(E) standard
372 <http://planeta.terra.com.br/informatica/paulobarreto/WhirlpoolPage.html>
377 tristate "AES cipher algorithms"
380 AES cipher algorithms (FIPS-197). AES uses the Rijndael
383 Rijndael appears to be consistently a very good performer in
384 both hardware and software across a wide range of computing
385 environments regardless of its use in feedback or non-feedback
386 modes. Its key setup time is excellent, and its key agility is
387 good. Rijndael's very low memory requirements make it very well
388 suited for restricted-space environments, in which it also
389 demonstrates excellent performance. Rijndael's operations are
390 among the easiest to defend against power and timing attacks.
392 The AES specifies three key sizes: 128, 192 and 256 bits
394 See <http://csrc.nist.gov/CryptoToolkit/aes/> for more information.
396 config CRYPTO_AES_586
397 tristate "AES cipher algorithms (i586)"
398 depends on (X86 || UML_X86) && !64BIT
402 AES cipher algorithms (FIPS-197). AES uses the Rijndael
405 Rijndael appears to be consistently a very good performer in
406 both hardware and software across a wide range of computing
407 environments regardless of its use in feedback or non-feedback
408 modes. Its key setup time is excellent, and its key agility is
409 good. Rijndael's very low memory requirements make it very well
410 suited for restricted-space environments, in which it also
411 demonstrates excellent performance. Rijndael's operations are
412 among the easiest to defend against power and timing attacks.
414 The AES specifies three key sizes: 128, 192 and 256 bits
416 See <http://csrc.nist.gov/encryption/aes/> for more information.
418 config CRYPTO_AES_X86_64
419 tristate "AES cipher algorithms (x86_64)"
420 depends on (X86 || UML_X86) && 64BIT
424 AES cipher algorithms (FIPS-197). AES uses the Rijndael
427 Rijndael appears to be consistently a very good performer in
428 both hardware and software across a wide range of computing
429 environments regardless of its use in feedback or non-feedback
430 modes. Its key setup time is excellent, and its key agility is
431 good. Rijndael's very low memory requirements make it very well
432 suited for restricted-space environments, in which it also
433 demonstrates excellent performance. Rijndael's operations are
434 among the easiest to defend against power and timing attacks.
436 The AES specifies three key sizes: 128, 192 and 256 bits
438 See <http://csrc.nist.gov/encryption/aes/> for more information.
441 tristate "Anubis cipher algorithm"
444 Anubis cipher algorithm.
446 Anubis is a variable key length cipher which can use keys from
447 128 bits to 320 bits in length. It was evaluated as a entrant
448 in the NESSIE competition.
451 <https://www.cosic.esat.kuleuven.ac.be/nessie/reports/>
452 <http://planeta.terra.com.br/informatica/paulobarreto/AnubisPage.html>
455 tristate "ARC4 cipher algorithm"
458 ARC4 cipher algorithm.
460 ARC4 is a stream cipher using keys ranging from 8 bits to 2048
461 bits in length. This algorithm is required for driver-based
462 WEP, but it should not be for other purposes because of the
463 weakness of the algorithm.
465 config CRYPTO_BLOWFISH
466 tristate "Blowfish cipher algorithm"
469 Blowfish cipher algorithm, by Bruce Schneier.
471 This is a variable key length cipher which can use keys from 32
472 bits to 448 bits in length. It's fast, simple and specifically
473 designed for use on "large microprocessors".
476 <http://www.schneier.com/blowfish.html>
478 config CRYPTO_CAMELLIA
479 tristate "Camellia cipher algorithms"
483 Camellia cipher algorithms module.
485 Camellia is a symmetric key block cipher developed jointly
486 at NTT and Mitsubishi Electric Corporation.
488 The Camellia specifies three key sizes: 128, 192 and 256 bits.
491 <https://info.isl.ntt.co.jp/crypt/eng/camellia/index_s.html>
494 tristate "CAST5 (CAST-128) cipher algorithm"
497 The CAST5 encryption algorithm (synonymous with CAST-128) is
498 described in RFC2144.
501 tristate "CAST6 (CAST-256) cipher algorithm"
504 The CAST6 encryption algorithm (synonymous with CAST-256) is
505 described in RFC2612.
508 tristate "DES and Triple DES EDE cipher algorithms"
511 DES cipher algorithm (FIPS 46-2), and Triple DES EDE (FIPS 46-3).
514 tristate "FCrypt cipher algorithm"
516 select CRYPTO_BLKCIPHER
518 FCrypt algorithm used by RxRPC.
521 tristate "Khazad cipher algorithm"
524 Khazad cipher algorithm.
526 Khazad was a finalist in the initial NESSIE competition. It is
527 an algorithm optimized for 64-bit processors with good performance
528 on 32-bit processors. Khazad uses an 128 bit key size.
531 <http://planeta.terra.com.br/informatica/paulobarreto/KhazadPage.html>
533 config CRYPTO_SALSA20
534 tristate "Salsa20 stream cipher algorithm (EXPERIMENTAL)"
535 depends on EXPERIMENTAL
536 select CRYPTO_BLKCIPHER
538 Salsa20 stream cipher algorithm.
540 Salsa20 is a stream cipher submitted to eSTREAM, the ECRYPT
541 Stream Cipher Project. See <http://www.ecrypt.eu.org/stream/>
543 The Salsa20 stream cipher algorithm is designed by Daniel J.
544 Bernstein <djb@cr.yp.to>. See <http://cr.yp.to/snuffle.html>
546 config CRYPTO_SALSA20_586
547 tristate "Salsa20 stream cipher algorithm (i586) (EXPERIMENTAL)"
548 depends on (X86 || UML_X86) && !64BIT
549 depends on EXPERIMENTAL
550 select CRYPTO_BLKCIPHER
552 Salsa20 stream cipher algorithm.
554 Salsa20 is a stream cipher submitted to eSTREAM, the ECRYPT
555 Stream Cipher Project. See <http://www.ecrypt.eu.org/stream/>
557 The Salsa20 stream cipher algorithm is designed by Daniel J.
558 Bernstein <djb@cr.yp.to>. See <http://cr.yp.to/snuffle.html>
560 config CRYPTO_SALSA20_X86_64
561 tristate "Salsa20 stream cipher algorithm (x86_64) (EXPERIMENTAL)"
562 depends on (X86 || UML_X86) && 64BIT
563 depends on EXPERIMENTAL
564 select CRYPTO_BLKCIPHER
566 Salsa20 stream cipher algorithm.
568 Salsa20 is a stream cipher submitted to eSTREAM, the ECRYPT
569 Stream Cipher Project. See <http://www.ecrypt.eu.org/stream/>
571 The Salsa20 stream cipher algorithm is designed by Daniel J.
572 Bernstein <djb@cr.yp.to>. See <http://cr.yp.to/snuffle.html>
575 tristate "SEED cipher algorithm"
578 SEED cipher algorithm (RFC4269).
580 SEED is a 128-bit symmetric key block cipher that has been
581 developed by KISA (Korea Information Security Agency) as a
582 national standard encryption algorithm of the Republic of Korea.
583 It is a 16 round block cipher with the key size of 128 bit.
586 <http://www.kisa.or.kr/kisa/seed/jsp/seed_eng.jsp>
588 config CRYPTO_SERPENT
589 tristate "Serpent cipher algorithm"
592 Serpent cipher algorithm, by Anderson, Biham & Knudsen.
594 Keys are allowed to be from 0 to 256 bits in length, in steps
595 of 8 bits. Also includes the 'Tnepres' algorithm, a reversed
596 variant of Serpent for compatibility with old kerneli.org code.
599 <http://www.cl.cam.ac.uk/~rja14/serpent.html>
602 tristate "TEA, XTEA and XETA cipher algorithms"
605 TEA cipher algorithm.
607 Tiny Encryption Algorithm is a simple cipher that uses
608 many rounds for security. It is very fast and uses
611 Xtendend Tiny Encryption Algorithm is a modification to
612 the TEA algorithm to address a potential key weakness
613 in the TEA algorithm.
615 Xtendend Encryption Tiny Algorithm is a mis-implementation
616 of the XTEA algorithm for compatibility purposes.
618 config CRYPTO_TWOFISH
619 tristate "Twofish cipher algorithm"
621 select CRYPTO_TWOFISH_COMMON
623 Twofish cipher algorithm.
625 Twofish was submitted as an AES (Advanced Encryption Standard)
626 candidate cipher by researchers at CounterPane Systems. It is a
627 16 round block cipher supporting key sizes of 128, 192, and 256
631 <http://www.schneier.com/twofish.html>
633 config CRYPTO_TWOFISH_COMMON
636 Common parts of the Twofish cipher algorithm shared by the
637 generic c and the assembler implementations.
639 config CRYPTO_TWOFISH_586
640 tristate "Twofish cipher algorithms (i586)"
641 depends on (X86 || UML_X86) && !64BIT
643 select CRYPTO_TWOFISH_COMMON
645 Twofish cipher algorithm.
647 Twofish was submitted as an AES (Advanced Encryption Standard)
648 candidate cipher by researchers at CounterPane Systems. It is a
649 16 round block cipher supporting key sizes of 128, 192, and 256
653 <http://www.schneier.com/twofish.html>
655 config CRYPTO_TWOFISH_X86_64
656 tristate "Twofish cipher algorithm (x86_64)"
657 depends on (X86 || UML_X86) && 64BIT
659 select CRYPTO_TWOFISH_COMMON
661 Twofish cipher algorithm (x86_64).
663 Twofish was submitted as an AES (Advanced Encryption Standard)
664 candidate cipher by researchers at CounterPane Systems. It is a
665 16 round block cipher supporting key sizes of 128, 192, and 256
669 <http://www.schneier.com/twofish.html>
671 comment "Compression"
673 config CRYPTO_DEFLATE
674 tristate "Deflate compression algorithm"
679 This is the Deflate algorithm (RFC1951), specified for use in
680 IPSec with the IPCOMP protocol (RFC3173, RFC2394).
682 You will most probably want this if using IPSec.
685 tristate "LZO compression algorithm"
688 select LZO_DECOMPRESS
690 This is the LZO algorithm.
692 source "drivers/crypto/Kconfig"