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
70 This is a generic software asynchronous crypto daemon that
71 converts an arbitrary synchronous software crypto algorithm
72 into an asynchronous algorithm that executes in a kernel thread.
75 tristate "Authenc support"
77 select CRYPTO_BLKCIPHER
81 Authenc: Combined mode wrapper for IPsec.
82 This is required for IPSec.
85 tristate "Testing module"
89 select CRYPTO_BLKCIPHER
91 Quick & dirty crypto test module.
93 comment "Authenticated Encryption with Associated Data"
96 tristate "CCM support"
100 Support for Counter with CBC MAC. Required for IPsec.
103 tristate "GCM/GMAC support"
106 select CRYPTO_GF128MUL
108 Support for Galois/Counter Mode (GCM) and Galois Message
109 Authentication Code (GMAC). Required for IPSec.
112 tristate "Sequence Number IV Generator"
114 select CRYPTO_BLKCIPHER
116 This IV generator generates an IV based on a sequence number by
117 xoring it with a salt. This algorithm is mainly useful for CTR
119 comment "Block modes"
122 tristate "CBC support"
123 select CRYPTO_BLKCIPHER
124 select CRYPTO_MANAGER
126 CBC: Cipher Block Chaining mode
127 This block cipher algorithm is required for IPSec.
130 tristate "CTR support"
131 select CRYPTO_BLKCIPHER
133 select CRYPTO_MANAGER
136 This block cipher algorithm is required for IPSec.
139 tristate "CTS support"
140 select CRYPTO_BLKCIPHER
142 CTS: Cipher Text Stealing
143 This is the Cipher Text Stealing mode as described by
144 Section 8 of rfc2040 and referenced by rfc3962.
145 (rfc3962 includes errata information in its Appendix A)
146 This mode is required for Kerberos gss mechanism support
150 tristate "ECB support"
151 select CRYPTO_BLKCIPHER
152 select CRYPTO_MANAGER
154 ECB: Electronic CodeBook mode
155 This is the simplest block cipher algorithm. It simply encrypts
156 the input block by block.
159 tristate "LRW support (EXPERIMENTAL)"
160 depends on EXPERIMENTAL
161 select CRYPTO_BLKCIPHER
162 select CRYPTO_MANAGER
163 select CRYPTO_GF128MUL
165 LRW: Liskov Rivest Wagner, a tweakable, non malleable, non movable
166 narrow block cipher mode for dm-crypt. Use it with cipher
167 specification string aes-lrw-benbi, the key must be 256, 320 or 384.
168 The first 128, 192 or 256 bits in the key are used for AES and the
169 rest is used to tie each cipher block to its logical position.
172 tristate "PCBC support"
173 select CRYPTO_BLKCIPHER
174 select CRYPTO_MANAGER
176 PCBC: Propagating Cipher Block Chaining mode
177 This block cipher algorithm is required for RxRPC.
180 tristate "XTS support (EXPERIMENTAL)"
181 depends on EXPERIMENTAL
182 select CRYPTO_BLKCIPHER
183 select CRYPTO_MANAGER
184 select CRYPTO_GF128MUL
186 XTS: IEEE1619/D16 narrow block cipher use with aes-xts-plain,
187 key size 256, 384 or 512 bits. This implementation currently
188 can't handle a sectorsize which is not a multiple of 16 bytes.
193 tristate "HMAC support"
195 select CRYPTO_MANAGER
197 HMAC: Keyed-Hashing for Message Authentication (RFC2104).
198 This is required for IPSec.
201 tristate "XCBC support"
202 depends on EXPERIMENTAL
204 select CRYPTO_MANAGER
206 XCBC: Keyed-Hashing with encryption algorithm
207 http://www.ietf.org/rfc/rfc3566.txt
208 http://csrc.nist.gov/encryption/modes/proposedmodes/
209 xcbc-mac/xcbc-mac-spec.pdf
214 tristate "CRC32c CRC algorithm"
218 Castagnoli, et al Cyclic Redundancy-Check Algorithm. Used
219 by iSCSI for header and data digests and by others.
220 See Castagnoli93. This implementation uses lib/libcrc32c.
221 Module will be crc32c.
224 tristate "MD4 digest algorithm"
227 MD4 message digest algorithm (RFC1320).
230 tristate "MD5 digest algorithm"
233 MD5 message digest algorithm (RFC1321).
235 config CRYPTO_MICHAEL_MIC
236 tristate "Michael MIC keyed digest algorithm"
239 Michael MIC is used for message integrity protection in TKIP
240 (IEEE 802.11i). This algorithm is required for TKIP, but it
241 should not be used for other purposes because of the weakness
245 tristate "RIPEMD-128 digest algorithm"
248 RIPEMD-128 (ISO/IEC 10118-3:2004).
250 RIPEMD-128 is a 128-bit cryptographic hash function. It should only
251 to be used as a secure replacement for RIPEMD. For other use cases
252 RIPEMD-160 should be used.
254 Developed by Hans Dobbertin, Antoon Bosselaers and Bart Preneel.
255 See <http://home.esat.kuleuven.be/~bosselae/ripemd160.html>
258 tristate "RIPEMD-160 digest algorithm"
261 RIPEMD-160 (ISO/IEC 10118-3:2004).
263 RIPEMD-160 is a 160-bit cryptographic hash function. It is intended
264 to be used as a secure replacement for the 128-bit hash functions
265 MD4, MD5 and it's predecessor RIPEMD (not to be confused with RIPEMD-128).
267 It's speed is comparable to SHA1 and there are no known attacks against
270 Developed by Hans Dobbertin, Antoon Bosselaers and Bart Preneel.
271 See <http://home.esat.kuleuven.be/~bosselae/ripemd160.html>
274 tristate "RIPEMD-256 digest algorithm"
277 RIPEMD-256 is an optional extension of RIPEMD-128 with a 256 bit hash.
278 It is intended for applications that require longer hash-results, without
279 needing a larger security level (than RIPEMD-128).
281 Developed by Hans Dobbertin, Antoon Bosselaers and Bart Preneel.
282 See <http://home.esat.kuleuven.be/~bosselae/ripemd160.html>
285 tristate "RIPEMD-320 digest algorithm"
288 RIPEMD-320 is an optional extension of RIPEMD-160 with a 320 bit hash.
289 It is intended for applications that require longer hash-results, without
290 needing a larger security level (than RIPEMD-160).
292 Developed by Hans Dobbertin, Antoon Bosselaers and Bart Preneel.
293 See <http://home.esat.kuleuven.be/~bosselae/ripemd160.html>
296 tristate "SHA1 digest algorithm"
299 SHA-1 secure hash standard (FIPS 180-1/DFIPS 180-2).
302 tristate "SHA224 and SHA256 digest algorithm"
305 SHA256 secure hash standard (DFIPS 180-2).
307 This version of SHA implements a 256 bit hash with 128 bits of
308 security against collision attacks.
310 This code also includes SHA-224, a 224 bit hash with 112 bits
311 of security against collision attacks.
314 tristate "SHA384 and SHA512 digest algorithms"
317 SHA512 secure hash standard (DFIPS 180-2).
319 This version of SHA implements a 512 bit hash with 256 bits of
320 security against collision attacks.
322 This code also includes SHA-384, a 384 bit hash with 192 bits
323 of security against collision attacks.
326 tristate "Tiger digest algorithms"
329 Tiger hash algorithm 192, 160 and 128-bit hashes
331 Tiger is a hash function optimized for 64-bit processors while
332 still having decent performance on 32-bit processors.
333 Tiger was developed by Ross Anderson and Eli Biham.
336 <http://www.cs.technion.ac.il/~biham/Reports/Tiger/>.
339 tristate "Whirlpool digest algorithms"
342 Whirlpool hash algorithm 512, 384 and 256-bit hashes
344 Whirlpool-512 is part of the NESSIE cryptographic primitives.
345 Whirlpool will be part of the ISO/IEC 10118-3:2003(E) standard
348 <http://planeta.terra.com.br/informatica/paulobarreto/WhirlpoolPage.html>
353 tristate "AES cipher algorithms"
356 AES cipher algorithms (FIPS-197). AES uses the Rijndael
359 Rijndael appears to be consistently a very good performer in
360 both hardware and software across a wide range of computing
361 environments regardless of its use in feedback or non-feedback
362 modes. Its key setup time is excellent, and its key agility is
363 good. Rijndael's very low memory requirements make it very well
364 suited for restricted-space environments, in which it also
365 demonstrates excellent performance. Rijndael's operations are
366 among the easiest to defend against power and timing attacks.
368 The AES specifies three key sizes: 128, 192 and 256 bits
370 See <http://csrc.nist.gov/CryptoToolkit/aes/> for more information.
372 config CRYPTO_AES_586
373 tristate "AES cipher algorithms (i586)"
374 depends on (X86 || UML_X86) && !64BIT
378 AES cipher algorithms (FIPS-197). AES uses the Rijndael
381 Rijndael appears to be consistently a very good performer in
382 both hardware and software across a wide range of computing
383 environments regardless of its use in feedback or non-feedback
384 modes. Its key setup time is excellent, and its key agility is
385 good. Rijndael's very low memory requirements make it very well
386 suited for restricted-space environments, in which it also
387 demonstrates excellent performance. Rijndael's operations are
388 among the easiest to defend against power and timing attacks.
390 The AES specifies three key sizes: 128, 192 and 256 bits
392 See <http://csrc.nist.gov/encryption/aes/> for more information.
394 config CRYPTO_AES_X86_64
395 tristate "AES cipher algorithms (x86_64)"
396 depends on (X86 || UML_X86) && 64BIT
400 AES cipher algorithms (FIPS-197). AES uses the Rijndael
403 Rijndael appears to be consistently a very good performer in
404 both hardware and software across a wide range of computing
405 environments regardless of its use in feedback or non-feedback
406 modes. Its key setup time is excellent, and its key agility is
407 good. Rijndael's very low memory requirements make it very well
408 suited for restricted-space environments, in which it also
409 demonstrates excellent performance. Rijndael's operations are
410 among the easiest to defend against power and timing attacks.
412 The AES specifies three key sizes: 128, 192 and 256 bits
414 See <http://csrc.nist.gov/encryption/aes/> for more information.
417 tristate "Anubis cipher algorithm"
420 Anubis cipher algorithm.
422 Anubis is a variable key length cipher which can use keys from
423 128 bits to 320 bits in length. It was evaluated as a entrant
424 in the NESSIE competition.
427 <https://www.cosic.esat.kuleuven.ac.be/nessie/reports/>
428 <http://planeta.terra.com.br/informatica/paulobarreto/AnubisPage.html>
431 tristate "ARC4 cipher algorithm"
434 ARC4 cipher algorithm.
436 ARC4 is a stream cipher using keys ranging from 8 bits to 2048
437 bits in length. This algorithm is required for driver-based
438 WEP, but it should not be for other purposes because of the
439 weakness of the algorithm.
441 config CRYPTO_BLOWFISH
442 tristate "Blowfish cipher algorithm"
445 Blowfish cipher algorithm, by Bruce Schneier.
447 This is a variable key length cipher which can use keys from 32
448 bits to 448 bits in length. It's fast, simple and specifically
449 designed for use on "large microprocessors".
452 <http://www.schneier.com/blowfish.html>
454 config CRYPTO_CAMELLIA
455 tristate "Camellia cipher algorithms"
459 Camellia cipher algorithms module.
461 Camellia is a symmetric key block cipher developed jointly
462 at NTT and Mitsubishi Electric Corporation.
464 The Camellia specifies three key sizes: 128, 192 and 256 bits.
467 <https://info.isl.ntt.co.jp/crypt/eng/camellia/index_s.html>
470 tristate "CAST5 (CAST-128) cipher algorithm"
473 The CAST5 encryption algorithm (synonymous with CAST-128) is
474 described in RFC2144.
477 tristate "CAST6 (CAST-256) cipher algorithm"
480 The CAST6 encryption algorithm (synonymous with CAST-256) is
481 described in RFC2612.
484 tristate "DES and Triple DES EDE cipher algorithms"
487 DES cipher algorithm (FIPS 46-2), and Triple DES EDE (FIPS 46-3).
490 tristate "FCrypt cipher algorithm"
492 select CRYPTO_BLKCIPHER
494 FCrypt algorithm used by RxRPC.
497 tristate "Khazad cipher algorithm"
500 Khazad cipher algorithm.
502 Khazad was a finalist in the initial NESSIE competition. It is
503 an algorithm optimized for 64-bit processors with good performance
504 on 32-bit processors. Khazad uses an 128 bit key size.
507 <http://planeta.terra.com.br/informatica/paulobarreto/KhazadPage.html>
509 config CRYPTO_SALSA20
510 tristate "Salsa20 stream cipher algorithm (EXPERIMENTAL)"
511 depends on EXPERIMENTAL
512 select CRYPTO_BLKCIPHER
514 Salsa20 stream cipher algorithm.
516 Salsa20 is a stream cipher submitted to eSTREAM, the ECRYPT
517 Stream Cipher Project. See <http://www.ecrypt.eu.org/stream/>
519 The Salsa20 stream cipher algorithm is designed by Daniel J.
520 Bernstein <djb@cr.yp.to>. See <http://cr.yp.to/snuffle.html>
522 config CRYPTO_SALSA20_586
523 tristate "Salsa20 stream cipher algorithm (i586) (EXPERIMENTAL)"
524 depends on (X86 || UML_X86) && !64BIT
525 depends on EXPERIMENTAL
526 select CRYPTO_BLKCIPHER
528 Salsa20 stream cipher algorithm.
530 Salsa20 is a stream cipher submitted to eSTREAM, the ECRYPT
531 Stream Cipher Project. See <http://www.ecrypt.eu.org/stream/>
533 The Salsa20 stream cipher algorithm is designed by Daniel J.
534 Bernstein <djb@cr.yp.to>. See <http://cr.yp.to/snuffle.html>
536 config CRYPTO_SALSA20_X86_64
537 tristate "Salsa20 stream cipher algorithm (x86_64) (EXPERIMENTAL)"
538 depends on (X86 || UML_X86) && 64BIT
539 depends on EXPERIMENTAL
540 select CRYPTO_BLKCIPHER
542 Salsa20 stream cipher algorithm.
544 Salsa20 is a stream cipher submitted to eSTREAM, the ECRYPT
545 Stream Cipher Project. See <http://www.ecrypt.eu.org/stream/>
547 The Salsa20 stream cipher algorithm is designed by Daniel J.
548 Bernstein <djb@cr.yp.to>. See <http://cr.yp.to/snuffle.html>
551 tristate "SEED cipher algorithm"
554 SEED cipher algorithm (RFC4269).
556 SEED is a 128-bit symmetric key block cipher that has been
557 developed by KISA (Korea Information Security Agency) as a
558 national standard encryption algorithm of the Republic of Korea.
559 It is a 16 round block cipher with the key size of 128 bit.
562 <http://www.kisa.or.kr/kisa/seed/jsp/seed_eng.jsp>
564 config CRYPTO_SERPENT
565 tristate "Serpent cipher algorithm"
568 Serpent cipher algorithm, by Anderson, Biham & Knudsen.
570 Keys are allowed to be from 0 to 256 bits in length, in steps
571 of 8 bits. Also includes the 'Tnepres' algorithm, a reversed
572 variant of Serpent for compatibility with old kerneli.org code.
575 <http://www.cl.cam.ac.uk/~rja14/serpent.html>
578 tristate "TEA, XTEA and XETA cipher algorithms"
581 TEA cipher algorithm.
583 Tiny Encryption Algorithm is a simple cipher that uses
584 many rounds for security. It is very fast and uses
587 Xtendend Tiny Encryption Algorithm is a modification to
588 the TEA algorithm to address a potential key weakness
589 in the TEA algorithm.
591 Xtendend Encryption Tiny Algorithm is a mis-implementation
592 of the XTEA algorithm for compatibility purposes.
594 config CRYPTO_TWOFISH
595 tristate "Twofish cipher algorithm"
597 select CRYPTO_TWOFISH_COMMON
599 Twofish cipher algorithm.
601 Twofish was submitted as an AES (Advanced Encryption Standard)
602 candidate cipher by researchers at CounterPane Systems. It is a
603 16 round block cipher supporting key sizes of 128, 192, and 256
607 <http://www.schneier.com/twofish.html>
609 config CRYPTO_TWOFISH_COMMON
612 Common parts of the Twofish cipher algorithm shared by the
613 generic c and the assembler implementations.
615 config CRYPTO_TWOFISH_586
616 tristate "Twofish cipher algorithms (i586)"
617 depends on (X86 || UML_X86) && !64BIT
619 select CRYPTO_TWOFISH_COMMON
621 Twofish cipher algorithm.
623 Twofish was submitted as an AES (Advanced Encryption Standard)
624 candidate cipher by researchers at CounterPane Systems. It is a
625 16 round block cipher supporting key sizes of 128, 192, and 256
629 <http://www.schneier.com/twofish.html>
631 config CRYPTO_TWOFISH_X86_64
632 tristate "Twofish cipher algorithm (x86_64)"
633 depends on (X86 || UML_X86) && 64BIT
635 select CRYPTO_TWOFISH_COMMON
637 Twofish cipher algorithm (x86_64).
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 comment "Compression"
649 config CRYPTO_DEFLATE
650 tristate "Deflate compression algorithm"
655 This is the Deflate algorithm (RFC1951), specified for use in
656 IPSec with the IPCOMP protocol (RFC3173, RFC2394).
658 You will most probably want this if using IPSec.
661 tristate "LZO compression algorithm"
664 select LZO_DECOMPRESS
666 This is the LZO algorithm.
668 source "drivers/crypto/Kconfig"