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"
27 This option provides the API for cryptographic algorithms.
33 config CRYPTO_BLKCIPHER
42 tristate "Cryptographic algorithm manager"
45 Create default cryptographic template instantiations such as
48 config CRYPTO_GF128MUL
49 tristate "GF(2^128) multiplication functions (EXPERIMENTAL)"
50 depends on EXPERIMENTAL
52 Efficient table driven implementation of multiplications in the
53 field GF(2^128). This is needed by some cypher modes. This
54 option will be selected automatically if you select such a
55 cipher mode. Only select this option by hand if you expect to load
56 an external module that requires these functions.
59 tristate "Null algorithms"
61 select CRYPTO_BLKCIPHER
63 These are 'Null' algorithms, used by IPsec, which do nothing.
66 tristate "Software async crypto daemon"
67 select CRYPTO_BLKCIPHER
71 This is a generic software asynchronous crypto daemon that
72 converts an arbitrary synchronous software crypto algorithm
73 into an asynchronous algorithm that executes in a kernel thread.
76 tristate "Authenc support"
78 select CRYPTO_BLKCIPHER
82 Authenc: Combined mode wrapper for IPsec.
83 This is required for IPSec.
86 tristate "Testing module"
90 select CRYPTO_BLKCIPHER
92 Quick & dirty crypto test module.
94 comment "Authenticated Encryption with Associated Data"
97 tristate "CCM support"
101 Support for Counter with CBC MAC. Required for IPsec.
104 tristate "GCM/GMAC support"
107 select CRYPTO_GF128MUL
109 Support for Galois/Counter Mode (GCM) and Galois Message
110 Authentication Code (GMAC). Required for IPSec.
113 tristate "Sequence Number IV Generator"
115 select CRYPTO_BLKCIPHER
117 This IV generator generates an IV based on a sequence number by
118 xoring it with a salt. This algorithm is mainly useful for CTR
120 comment "Block modes"
123 tristate "CBC support"
124 select CRYPTO_BLKCIPHER
125 select CRYPTO_MANAGER
127 CBC: Cipher Block Chaining mode
128 This block cipher algorithm is required for IPSec.
131 tristate "CTR support"
132 select CRYPTO_BLKCIPHER
134 select CRYPTO_MANAGER
137 This block cipher algorithm is required for IPSec.
140 tristate "CTS support"
141 select CRYPTO_BLKCIPHER
143 CTS: Cipher Text Stealing
144 This is the Cipher Text Stealing mode as described by
145 Section 8 of rfc2040 and referenced by rfc3962.
146 (rfc3962 includes errata information in its Appendix A)
147 This mode is required for Kerberos gss mechanism support
151 tristate "ECB support"
152 select CRYPTO_BLKCIPHER
153 select CRYPTO_MANAGER
155 ECB: Electronic CodeBook mode
156 This is the simplest block cipher algorithm. It simply encrypts
157 the input block by block.
160 tristate "LRW support (EXPERIMENTAL)"
161 depends on EXPERIMENTAL
162 select CRYPTO_BLKCIPHER
163 select CRYPTO_MANAGER
164 select CRYPTO_GF128MUL
166 LRW: Liskov Rivest Wagner, a tweakable, non malleable, non movable
167 narrow block cipher mode for dm-crypt. Use it with cipher
168 specification string aes-lrw-benbi, the key must be 256, 320 or 384.
169 The first 128, 192 or 256 bits in the key are used for AES and the
170 rest is used to tie each cipher block to its logical position.
173 tristate "PCBC support"
174 select CRYPTO_BLKCIPHER
175 select CRYPTO_MANAGER
177 PCBC: Propagating Cipher Block Chaining mode
178 This block cipher algorithm is required for RxRPC.
181 tristate "XTS support (EXPERIMENTAL)"
182 depends on EXPERIMENTAL
183 select CRYPTO_BLKCIPHER
184 select CRYPTO_MANAGER
185 select CRYPTO_GF128MUL
187 XTS: IEEE1619/D16 narrow block cipher use with aes-xts-plain,
188 key size 256, 384 or 512 bits. This implementation currently
189 can't handle a sectorsize which is not a multiple of 16 bytes.
194 tristate "HMAC support"
196 select CRYPTO_MANAGER
198 HMAC: Keyed-Hashing for Message Authentication (RFC2104).
199 This is required for IPSec.
202 tristate "XCBC support"
203 depends on EXPERIMENTAL
205 select CRYPTO_MANAGER
207 XCBC: Keyed-Hashing with encryption algorithm
208 http://www.ietf.org/rfc/rfc3566.txt
209 http://csrc.nist.gov/encryption/modes/proposedmodes/
210 xcbc-mac/xcbc-mac-spec.pdf
215 tristate "CRC32c CRC algorithm"
219 Castagnoli, et al Cyclic Redundancy-Check Algorithm. Used
220 by iSCSI for header and data digests and by others.
221 See Castagnoli93. This implementation uses lib/libcrc32c.
222 Module will be crc32c.
224 config CRYPTO_CRC32C_INTEL
225 tristate "CRC32c INTEL hardware acceleration"
229 In Intel processor with SSE4.2 supported, the processor will
230 support CRC32C implementation using hardware accelerated CRC32
231 instruction. This option will create 'crc32c-intel' module,
232 which will enable any routine to use the CRC32 instruction to
233 gain performance compared with software implementation.
234 Module will be crc32c-intel.
237 tristate "MD4 digest algorithm"
240 MD4 message digest algorithm (RFC1320).
243 tristate "MD5 digest algorithm"
246 MD5 message digest algorithm (RFC1321).
248 config CRYPTO_MICHAEL_MIC
249 tristate "Michael MIC keyed digest algorithm"
252 Michael MIC is used for message integrity protection in TKIP
253 (IEEE 802.11i). This algorithm is required for TKIP, but it
254 should not be used for other purposes because of the weakness
258 tristate "RIPEMD-128 digest algorithm"
261 RIPEMD-128 (ISO/IEC 10118-3:2004).
263 RIPEMD-128 is a 128-bit cryptographic hash function. It should only
264 to be used as a secure replacement for RIPEMD. For other use cases
265 RIPEMD-160 should be used.
267 Developed by Hans Dobbertin, Antoon Bosselaers and Bart Preneel.
268 See <http://home.esat.kuleuven.be/~bosselae/ripemd160.html>
271 tristate "RIPEMD-160 digest algorithm"
274 RIPEMD-160 (ISO/IEC 10118-3:2004).
276 RIPEMD-160 is a 160-bit cryptographic hash function. It is intended
277 to be used as a secure replacement for the 128-bit hash functions
278 MD4, MD5 and it's predecessor RIPEMD
279 (not to be confused with RIPEMD-128).
281 It's speed is comparable to SHA1 and there are no known attacks
284 Developed by Hans Dobbertin, Antoon Bosselaers and Bart Preneel.
285 See <http://home.esat.kuleuven.be/~bosselae/ripemd160.html>
288 tristate "RIPEMD-256 digest algorithm"
291 RIPEMD-256 is an optional extension of RIPEMD-128 with a
292 256 bit hash. It is intended for applications that require
293 longer hash-results, without needing a larger security level
296 Developed by Hans Dobbertin, Antoon Bosselaers and Bart Preneel.
297 See <http://home.esat.kuleuven.be/~bosselae/ripemd160.html>
300 tristate "RIPEMD-320 digest algorithm"
303 RIPEMD-320 is an optional extension of RIPEMD-160 with a
304 320 bit hash. It is intended for applications that require
305 longer hash-results, without needing a larger security level
308 Developed by Hans Dobbertin, Antoon Bosselaers and Bart Preneel.
309 See <http://home.esat.kuleuven.be/~bosselae/ripemd160.html>
312 tristate "SHA1 digest algorithm"
315 SHA-1 secure hash standard (FIPS 180-1/DFIPS 180-2).
318 tristate "SHA224 and SHA256 digest algorithm"
321 SHA256 secure hash standard (DFIPS 180-2).
323 This version of SHA implements a 256 bit hash with 128 bits of
324 security against collision attacks.
326 This code also includes SHA-224, a 224 bit hash with 112 bits
327 of security against collision attacks.
330 tristate "SHA384 and SHA512 digest algorithms"
333 SHA512 secure hash standard (DFIPS 180-2).
335 This version of SHA implements a 512 bit hash with 256 bits of
336 security against collision attacks.
338 This code also includes SHA-384, a 384 bit hash with 192 bits
339 of security against collision attacks.
342 tristate "Tiger digest algorithms"
345 Tiger hash algorithm 192, 160 and 128-bit hashes
347 Tiger is a hash function optimized for 64-bit processors while
348 still having decent performance on 32-bit processors.
349 Tiger was developed by Ross Anderson and Eli Biham.
352 <http://www.cs.technion.ac.il/~biham/Reports/Tiger/>.
355 tristate "Whirlpool digest algorithms"
358 Whirlpool hash algorithm 512, 384 and 256-bit hashes
360 Whirlpool-512 is part of the NESSIE cryptographic primitives.
361 Whirlpool will be part of the ISO/IEC 10118-3:2003(E) standard
364 <http://planeta.terra.com.br/informatica/paulobarreto/WhirlpoolPage.html>
369 tristate "AES cipher algorithms"
372 AES cipher algorithms (FIPS-197). AES uses the Rijndael
375 Rijndael appears to be consistently a very good performer in
376 both hardware and software across a wide range of computing
377 environments regardless of its use in feedback or non-feedback
378 modes. Its key setup time is excellent, and its key agility is
379 good. Rijndael's very low memory requirements make it very well
380 suited for restricted-space environments, in which it also
381 demonstrates excellent performance. Rijndael's operations are
382 among the easiest to defend against power and timing attacks.
384 The AES specifies three key sizes: 128, 192 and 256 bits
386 See <http://csrc.nist.gov/CryptoToolkit/aes/> for more information.
388 config CRYPTO_AES_586
389 tristate "AES cipher algorithms (i586)"
390 depends on (X86 || UML_X86) && !64BIT
394 AES cipher algorithms (FIPS-197). AES uses the Rijndael
397 Rijndael appears to be consistently a very good performer in
398 both hardware and software across a wide range of computing
399 environments regardless of its use in feedback or non-feedback
400 modes. Its key setup time is excellent, and its key agility is
401 good. Rijndael's very low memory requirements make it very well
402 suited for restricted-space environments, in which it also
403 demonstrates excellent performance. Rijndael's operations are
404 among the easiest to defend against power and timing attacks.
406 The AES specifies three key sizes: 128, 192 and 256 bits
408 See <http://csrc.nist.gov/encryption/aes/> for more information.
410 config CRYPTO_AES_X86_64
411 tristate "AES cipher algorithms (x86_64)"
412 depends on (X86 || UML_X86) && 64BIT
416 AES cipher algorithms (FIPS-197). AES uses the Rijndael
419 Rijndael appears to be consistently a very good performer in
420 both hardware and software across a wide range of computing
421 environments regardless of its use in feedback or non-feedback
422 modes. Its key setup time is excellent, and its key agility is
423 good. Rijndael's very low memory requirements make it very well
424 suited for restricted-space environments, in which it also
425 demonstrates excellent performance. Rijndael's operations are
426 among the easiest to defend against power and timing attacks.
428 The AES specifies three key sizes: 128, 192 and 256 bits
430 See <http://csrc.nist.gov/encryption/aes/> for more information.
433 tristate "Anubis cipher algorithm"
436 Anubis cipher algorithm.
438 Anubis is a variable key length cipher which can use keys from
439 128 bits to 320 bits in length. It was evaluated as a entrant
440 in the NESSIE competition.
443 <https://www.cosic.esat.kuleuven.ac.be/nessie/reports/>
444 <http://planeta.terra.com.br/informatica/paulobarreto/AnubisPage.html>
447 tristate "ARC4 cipher algorithm"
450 ARC4 cipher algorithm.
452 ARC4 is a stream cipher using keys ranging from 8 bits to 2048
453 bits in length. This algorithm is required for driver-based
454 WEP, but it should not be for other purposes because of the
455 weakness of the algorithm.
457 config CRYPTO_BLOWFISH
458 tristate "Blowfish cipher algorithm"
461 Blowfish cipher algorithm, by Bruce Schneier.
463 This is a variable key length cipher which can use keys from 32
464 bits to 448 bits in length. It's fast, simple and specifically
465 designed for use on "large microprocessors".
468 <http://www.schneier.com/blowfish.html>
470 config CRYPTO_CAMELLIA
471 tristate "Camellia cipher algorithms"
475 Camellia cipher algorithms module.
477 Camellia is a symmetric key block cipher developed jointly
478 at NTT and Mitsubishi Electric Corporation.
480 The Camellia specifies three key sizes: 128, 192 and 256 bits.
483 <https://info.isl.ntt.co.jp/crypt/eng/camellia/index_s.html>
486 tristate "CAST5 (CAST-128) cipher algorithm"
489 The CAST5 encryption algorithm (synonymous with CAST-128) is
490 described in RFC2144.
493 tristate "CAST6 (CAST-256) cipher algorithm"
496 The CAST6 encryption algorithm (synonymous with CAST-256) is
497 described in RFC2612.
500 tristate "DES and Triple DES EDE cipher algorithms"
503 DES cipher algorithm (FIPS 46-2), and Triple DES EDE (FIPS 46-3).
506 tristate "FCrypt cipher algorithm"
508 select CRYPTO_BLKCIPHER
510 FCrypt algorithm used by RxRPC.
513 tristate "Khazad cipher algorithm"
516 Khazad cipher algorithm.
518 Khazad was a finalist in the initial NESSIE competition. It is
519 an algorithm optimized for 64-bit processors with good performance
520 on 32-bit processors. Khazad uses an 128 bit key size.
523 <http://planeta.terra.com.br/informatica/paulobarreto/KhazadPage.html>
525 config CRYPTO_SALSA20
526 tristate "Salsa20 stream cipher algorithm (EXPERIMENTAL)"
527 depends on EXPERIMENTAL
528 select CRYPTO_BLKCIPHER
530 Salsa20 stream cipher algorithm.
532 Salsa20 is a stream cipher submitted to eSTREAM, the ECRYPT
533 Stream Cipher Project. See <http://www.ecrypt.eu.org/stream/>
535 The Salsa20 stream cipher algorithm is designed by Daniel J.
536 Bernstein <djb@cr.yp.to>. See <http://cr.yp.to/snuffle.html>
538 config CRYPTO_SALSA20_586
539 tristate "Salsa20 stream cipher algorithm (i586) (EXPERIMENTAL)"
540 depends on (X86 || UML_X86) && !64BIT
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_X86_64
553 tristate "Salsa20 stream cipher algorithm (x86_64) (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>
567 tristate "SEED cipher algorithm"
570 SEED cipher algorithm (RFC4269).
572 SEED is a 128-bit symmetric key block cipher that has been
573 developed by KISA (Korea Information Security Agency) as a
574 national standard encryption algorithm of the Republic of Korea.
575 It is a 16 round block cipher with the key size of 128 bit.
578 <http://www.kisa.or.kr/kisa/seed/jsp/seed_eng.jsp>
580 config CRYPTO_SERPENT
581 tristate "Serpent cipher algorithm"
584 Serpent cipher algorithm, by Anderson, Biham & Knudsen.
586 Keys are allowed to be from 0 to 256 bits in length, in steps
587 of 8 bits. Also includes the 'Tnepres' algorithm, a reversed
588 variant of Serpent for compatibility with old kerneli.org code.
591 <http://www.cl.cam.ac.uk/~rja14/serpent.html>
594 tristate "TEA, XTEA and XETA cipher algorithms"
597 TEA cipher algorithm.
599 Tiny Encryption Algorithm is a simple cipher that uses
600 many rounds for security. It is very fast and uses
603 Xtendend Tiny Encryption Algorithm is a modification to
604 the TEA algorithm to address a potential key weakness
605 in the TEA algorithm.
607 Xtendend Encryption Tiny Algorithm is a mis-implementation
608 of the XTEA algorithm for compatibility purposes.
610 config CRYPTO_TWOFISH
611 tristate "Twofish cipher algorithm"
613 select CRYPTO_TWOFISH_COMMON
615 Twofish cipher algorithm.
617 Twofish was submitted as an AES (Advanced Encryption Standard)
618 candidate cipher by researchers at CounterPane Systems. It is a
619 16 round block cipher supporting key sizes of 128, 192, and 256
623 <http://www.schneier.com/twofish.html>
625 config CRYPTO_TWOFISH_COMMON
628 Common parts of the Twofish cipher algorithm shared by the
629 generic c and the assembler implementations.
631 config CRYPTO_TWOFISH_586
632 tristate "Twofish cipher algorithms (i586)"
633 depends on (X86 || UML_X86) && !64BIT
635 select CRYPTO_TWOFISH_COMMON
637 Twofish cipher algorithm.
639 Twofish was submitted as an AES (Advanced Encryption Standard)
640 candidate cipher by researchers at CounterPane Systems. It is a
641 16 round block cipher supporting key sizes of 128, 192, and 256
645 <http://www.schneier.com/twofish.html>
647 config CRYPTO_TWOFISH_X86_64
648 tristate "Twofish cipher algorithm (x86_64)"
649 depends on (X86 || UML_X86) && 64BIT
651 select CRYPTO_TWOFISH_COMMON
653 Twofish cipher algorithm (x86_64).
655 Twofish was submitted as an AES (Advanced Encryption Standard)
656 candidate cipher by researchers at CounterPane Systems. It is a
657 16 round block cipher supporting key sizes of 128, 192, and 256
661 <http://www.schneier.com/twofish.html>
663 comment "Compression"
665 config CRYPTO_DEFLATE
666 tristate "Deflate compression algorithm"
671 This is the Deflate algorithm (RFC1951), specified for use in
672 IPSec with the IPCOMP protocol (RFC3173, RFC2394).
674 You will most probably want this if using IPSec.
677 tristate "LZO compression algorithm"
680 select LZO_DECOMPRESS
682 This is the LZO algorithm.
684 source "drivers/crypto/Kconfig"