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.
225 tristate "MD4 digest algorithm"
228 MD4 message digest algorithm (RFC1320).
231 tristate "MD5 digest algorithm"
234 MD5 message digest algorithm (RFC1321).
236 config CRYPTO_MICHAEL_MIC
237 tristate "Michael MIC keyed digest algorithm"
240 Michael MIC is used for message integrity protection in TKIP
241 (IEEE 802.11i). This algorithm is required for TKIP, but it
242 should not be used for other purposes because of the weakness
246 tristate "RIPEMD-128 digest algorithm"
249 RIPEMD-128 (ISO/IEC 10118-3:2004).
251 RIPEMD-128 is a 128-bit cryptographic hash function. It should only
252 to be used as a secure replacement for RIPEMD. For other use cases
253 RIPEMD-160 should be used.
255 Developed by Hans Dobbertin, Antoon Bosselaers and Bart Preneel.
256 See <http://home.esat.kuleuven.be/~bosselae/ripemd160.html>
259 tristate "RIPEMD-160 digest algorithm"
262 RIPEMD-160 (ISO/IEC 10118-3:2004).
264 RIPEMD-160 is a 160-bit cryptographic hash function. It is intended
265 to be used as a secure replacement for the 128-bit hash functions
266 MD4, MD5 and it's predecessor RIPEMD (not to be confused with RIPEMD-128).
268 It's speed is comparable to SHA1 and there are no known attacks against
271 Developed by Hans Dobbertin, Antoon Bosselaers and Bart Preneel.
272 See <http://home.esat.kuleuven.be/~bosselae/ripemd160.html>
275 tristate "RIPEMD-256 digest algorithm"
278 RIPEMD-256 is an optional extension of RIPEMD-128 with a 256 bit hash.
279 It is intended for applications that require longer hash-results, without
280 needing a larger security level (than RIPEMD-128).
282 Developed by Hans Dobbertin, Antoon Bosselaers and Bart Preneel.
283 See <http://home.esat.kuleuven.be/~bosselae/ripemd160.html>
286 tristate "RIPEMD-320 digest algorithm"
289 RIPEMD-320 is an optional extension of RIPEMD-160 with a 320 bit hash.
290 It is intended for applications that require longer hash-results, without
291 needing a larger security level (than RIPEMD-160).
293 Developed by Hans Dobbertin, Antoon Bosselaers and Bart Preneel.
294 See <http://home.esat.kuleuven.be/~bosselae/ripemd160.html>
297 tristate "SHA1 digest algorithm"
300 SHA-1 secure hash standard (FIPS 180-1/DFIPS 180-2).
303 tristate "SHA224 and SHA256 digest algorithm"
306 SHA256 secure hash standard (DFIPS 180-2).
308 This version of SHA implements a 256 bit hash with 128 bits of
309 security against collision attacks.
311 This code also includes SHA-224, a 224 bit hash with 112 bits
312 of security against collision attacks.
315 tristate "SHA384 and SHA512 digest algorithms"
318 SHA512 secure hash standard (DFIPS 180-2).
320 This version of SHA implements a 512 bit hash with 256 bits of
321 security against collision attacks.
323 This code also includes SHA-384, a 384 bit hash with 192 bits
324 of security against collision attacks.
327 tristate "Tiger digest algorithms"
330 Tiger hash algorithm 192, 160 and 128-bit hashes
332 Tiger is a hash function optimized for 64-bit processors while
333 still having decent performance on 32-bit processors.
334 Tiger was developed by Ross Anderson and Eli Biham.
337 <http://www.cs.technion.ac.il/~biham/Reports/Tiger/>.
340 tristate "Whirlpool digest algorithms"
343 Whirlpool hash algorithm 512, 384 and 256-bit hashes
345 Whirlpool-512 is part of the NESSIE cryptographic primitives.
346 Whirlpool will be part of the ISO/IEC 10118-3:2003(E) standard
349 <http://planeta.terra.com.br/informatica/paulobarreto/WhirlpoolPage.html>
354 tristate "AES cipher algorithms"
357 AES cipher algorithms (FIPS-197). AES uses the Rijndael
360 Rijndael appears to be consistently a very good performer in
361 both hardware and software across a wide range of computing
362 environments regardless of its use in feedback or non-feedback
363 modes. Its key setup time is excellent, and its key agility is
364 good. Rijndael's very low memory requirements make it very well
365 suited for restricted-space environments, in which it also
366 demonstrates excellent performance. Rijndael's operations are
367 among the easiest to defend against power and timing attacks.
369 The AES specifies three key sizes: 128, 192 and 256 bits
371 See <http://csrc.nist.gov/CryptoToolkit/aes/> for more information.
373 config CRYPTO_AES_586
374 tristate "AES cipher algorithms (i586)"
375 depends on (X86 || UML_X86) && !64BIT
379 AES cipher algorithms (FIPS-197). AES uses the Rijndael
382 Rijndael appears to be consistently a very good performer in
383 both hardware and software across a wide range of computing
384 environments regardless of its use in feedback or non-feedback
385 modes. Its key setup time is excellent, and its key agility is
386 good. Rijndael's very low memory requirements make it very well
387 suited for restricted-space environments, in which it also
388 demonstrates excellent performance. Rijndael's operations are
389 among the easiest to defend against power and timing attacks.
391 The AES specifies three key sizes: 128, 192 and 256 bits
393 See <http://csrc.nist.gov/encryption/aes/> for more information.
395 config CRYPTO_AES_X86_64
396 tristate "AES cipher algorithms (x86_64)"
397 depends on (X86 || UML_X86) && 64BIT
401 AES cipher algorithms (FIPS-197). AES uses the Rijndael
404 Rijndael appears to be consistently a very good performer in
405 both hardware and software across a wide range of computing
406 environments regardless of its use in feedback or non-feedback
407 modes. Its key setup time is excellent, and its key agility is
408 good. Rijndael's very low memory requirements make it very well
409 suited for restricted-space environments, in which it also
410 demonstrates excellent performance. Rijndael's operations are
411 among the easiest to defend against power and timing attacks.
413 The AES specifies three key sizes: 128, 192 and 256 bits
415 See <http://csrc.nist.gov/encryption/aes/> for more information.
418 tristate "Anubis cipher algorithm"
421 Anubis cipher algorithm.
423 Anubis is a variable key length cipher which can use keys from
424 128 bits to 320 bits in length. It was evaluated as a entrant
425 in the NESSIE competition.
428 <https://www.cosic.esat.kuleuven.ac.be/nessie/reports/>
429 <http://planeta.terra.com.br/informatica/paulobarreto/AnubisPage.html>
432 tristate "ARC4 cipher algorithm"
435 ARC4 cipher algorithm.
437 ARC4 is a stream cipher using keys ranging from 8 bits to 2048
438 bits in length. This algorithm is required for driver-based
439 WEP, but it should not be for other purposes because of the
440 weakness of the algorithm.
442 config CRYPTO_BLOWFISH
443 tristate "Blowfish cipher algorithm"
446 Blowfish cipher algorithm, by Bruce Schneier.
448 This is a variable key length cipher which can use keys from 32
449 bits to 448 bits in length. It's fast, simple and specifically
450 designed for use on "large microprocessors".
453 <http://www.schneier.com/blowfish.html>
455 config CRYPTO_CAMELLIA
456 tristate "Camellia cipher algorithms"
460 Camellia cipher algorithms module.
462 Camellia is a symmetric key block cipher developed jointly
463 at NTT and Mitsubishi Electric Corporation.
465 The Camellia specifies three key sizes: 128, 192 and 256 bits.
468 <https://info.isl.ntt.co.jp/crypt/eng/camellia/index_s.html>
471 tristate "CAST5 (CAST-128) cipher algorithm"
474 The CAST5 encryption algorithm (synonymous with CAST-128) is
475 described in RFC2144.
478 tristate "CAST6 (CAST-256) cipher algorithm"
481 The CAST6 encryption algorithm (synonymous with CAST-256) is
482 described in RFC2612.
485 tristate "DES and Triple DES EDE cipher algorithms"
488 DES cipher algorithm (FIPS 46-2), and Triple DES EDE (FIPS 46-3).
491 tristate "FCrypt cipher algorithm"
493 select CRYPTO_BLKCIPHER
495 FCrypt algorithm used by RxRPC.
498 tristate "Khazad cipher algorithm"
501 Khazad cipher algorithm.
503 Khazad was a finalist in the initial NESSIE competition. It is
504 an algorithm optimized for 64-bit processors with good performance
505 on 32-bit processors. Khazad uses an 128 bit key size.
508 <http://planeta.terra.com.br/informatica/paulobarreto/KhazadPage.html>
510 config CRYPTO_SALSA20
511 tristate "Salsa20 stream cipher algorithm (EXPERIMENTAL)"
512 depends on EXPERIMENTAL
513 select CRYPTO_BLKCIPHER
515 Salsa20 stream cipher algorithm.
517 Salsa20 is a stream cipher submitted to eSTREAM, the ECRYPT
518 Stream Cipher Project. See <http://www.ecrypt.eu.org/stream/>
520 The Salsa20 stream cipher algorithm is designed by Daniel J.
521 Bernstein <djb@cr.yp.to>. See <http://cr.yp.to/snuffle.html>
523 config CRYPTO_SALSA20_586
524 tristate "Salsa20 stream cipher algorithm (i586) (EXPERIMENTAL)"
525 depends on (X86 || UML_X86) && !64BIT
526 depends on EXPERIMENTAL
527 select CRYPTO_BLKCIPHER
529 Salsa20 stream cipher algorithm.
531 Salsa20 is a stream cipher submitted to eSTREAM, the ECRYPT
532 Stream Cipher Project. See <http://www.ecrypt.eu.org/stream/>
534 The Salsa20 stream cipher algorithm is designed by Daniel J.
535 Bernstein <djb@cr.yp.to>. See <http://cr.yp.to/snuffle.html>
537 config CRYPTO_SALSA20_X86_64
538 tristate "Salsa20 stream cipher algorithm (x86_64) (EXPERIMENTAL)"
539 depends on (X86 || UML_X86) && 64BIT
540 depends on EXPERIMENTAL
541 select CRYPTO_BLKCIPHER
543 Salsa20 stream cipher algorithm.
545 Salsa20 is a stream cipher submitted to eSTREAM, the ECRYPT
546 Stream Cipher Project. See <http://www.ecrypt.eu.org/stream/>
548 The Salsa20 stream cipher algorithm is designed by Daniel J.
549 Bernstein <djb@cr.yp.to>. See <http://cr.yp.to/snuffle.html>
552 tristate "SEED cipher algorithm"
555 SEED cipher algorithm (RFC4269).
557 SEED is a 128-bit symmetric key block cipher that has been
558 developed by KISA (Korea Information Security Agency) as a
559 national standard encryption algorithm of the Republic of Korea.
560 It is a 16 round block cipher with the key size of 128 bit.
563 <http://www.kisa.or.kr/kisa/seed/jsp/seed_eng.jsp>
565 config CRYPTO_SERPENT
566 tristate "Serpent cipher algorithm"
569 Serpent cipher algorithm, by Anderson, Biham & Knudsen.
571 Keys are allowed to be from 0 to 256 bits in length, in steps
572 of 8 bits. Also includes the 'Tnepres' algorithm, a reversed
573 variant of Serpent for compatibility with old kerneli.org code.
576 <http://www.cl.cam.ac.uk/~rja14/serpent.html>
579 tristate "TEA, XTEA and XETA cipher algorithms"
582 TEA cipher algorithm.
584 Tiny Encryption Algorithm is a simple cipher that uses
585 many rounds for security. It is very fast and uses
588 Xtendend Tiny Encryption Algorithm is a modification to
589 the TEA algorithm to address a potential key weakness
590 in the TEA algorithm.
592 Xtendend Encryption Tiny Algorithm is a mis-implementation
593 of the XTEA algorithm for compatibility purposes.
595 config CRYPTO_TWOFISH
596 tristate "Twofish cipher algorithm"
598 select CRYPTO_TWOFISH_COMMON
600 Twofish cipher algorithm.
602 Twofish was submitted as an AES (Advanced Encryption Standard)
603 candidate cipher by researchers at CounterPane Systems. It is a
604 16 round block cipher supporting key sizes of 128, 192, and 256
608 <http://www.schneier.com/twofish.html>
610 config CRYPTO_TWOFISH_COMMON
613 Common parts of the Twofish cipher algorithm shared by the
614 generic c and the assembler implementations.
616 config CRYPTO_TWOFISH_586
617 tristate "Twofish cipher algorithms (i586)"
618 depends on (X86 || UML_X86) && !64BIT
620 select CRYPTO_TWOFISH_COMMON
622 Twofish cipher algorithm.
624 Twofish was submitted as an AES (Advanced Encryption Standard)
625 candidate cipher by researchers at CounterPane Systems. It is a
626 16 round block cipher supporting key sizes of 128, 192, and 256
630 <http://www.schneier.com/twofish.html>
632 config CRYPTO_TWOFISH_X86_64
633 tristate "Twofish cipher algorithm (x86_64)"
634 depends on (X86 || UML_X86) && 64BIT
636 select CRYPTO_TWOFISH_COMMON
638 Twofish cipher algorithm (x86_64).
640 Twofish was submitted as an AES (Advanced Encryption Standard)
641 candidate cipher by researchers at CounterPane Systems. It is a
642 16 round block cipher supporting key sizes of 128, 192, and 256
646 <http://www.schneier.com/twofish.html>
648 comment "Compression"
650 config CRYPTO_DEFLATE
651 tristate "Deflate compression algorithm"
656 This is the Deflate algorithm (RFC1951), specified for use in
657 IPSec with the IPCOMP protocol (RFC3173, RFC2394).
659 You will most probably want this if using IPSec.
662 tristate "LZO compression algorithm"
665 select LZO_DECOMPRESS
667 This is the LZO algorithm.
669 source "drivers/crypto/Kconfig"