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 bool "Cryptographic API"
18 This option provides the core Cryptographic API.
25 This option provides the API for cryptographic algorithms.
31 config CRYPTO_BLKCIPHER
36 tristate "Sequence Number IV Generator"
38 select CRYPTO_BLKCIPHER
40 This IV generator generates an IV based on a sequence number by
41 xoring it with a salt. This algorithm is mainly useful for CTR
49 tristate "Cryptographic algorithm manager"
52 Create default cryptographic template instantiations such as
56 tristate "HMAC support"
60 HMAC: Keyed-Hashing for Message Authentication (RFC2104).
61 This is required for IPSec.
64 tristate "XCBC support"
65 depends on EXPERIMENTAL
69 XCBC: Keyed-Hashing with encryption algorithm
70 http://www.ietf.org/rfc/rfc3566.txt
71 http://csrc.nist.gov/encryption/modes/proposedmodes/
72 xcbc-mac/xcbc-mac-spec.pdf
75 tristate "Null algorithms"
78 These are 'Null' algorithms, used by IPsec, which do nothing.
81 tristate "MD4 digest algorithm"
84 MD4 message digest algorithm (RFC1320).
87 tristate "MD5 digest algorithm"
90 MD5 message digest algorithm (RFC1321).
93 tristate "SHA1 digest algorithm"
96 SHA-1 secure hash standard (FIPS 180-1/DFIPS 180-2).
99 tristate "SHA224 and SHA256 digest algorithm"
102 SHA256 secure hash standard (DFIPS 180-2).
104 This version of SHA implements a 256 bit hash with 128 bits of
105 security against collision attacks.
107 This code also includes SHA-224, a 224 bit hash with 112 bits
108 of security against collision attacks.
111 tristate "SHA384 and SHA512 digest algorithms"
114 SHA512 secure hash standard (DFIPS 180-2).
116 This version of SHA implements a 512 bit hash with 256 bits of
117 security against collision attacks.
119 This code also includes SHA-384, a 384 bit hash with 192 bits
120 of security against collision attacks.
123 tristate "Whirlpool digest algorithms"
126 Whirlpool hash algorithm 512, 384 and 256-bit hashes
128 Whirlpool-512 is part of the NESSIE cryptographic primitives.
129 Whirlpool will be part of the ISO/IEC 10118-3:2003(E) standard
132 <http://planeta.terra.com.br/informatica/paulobarreto/WhirlpoolPage.html>
135 tristate "Tiger digest algorithms"
138 Tiger hash algorithm 192, 160 and 128-bit hashes
140 Tiger is a hash function optimized for 64-bit processors while
141 still having decent performance on 32-bit processors.
142 Tiger was developed by Ross Anderson and Eli Biham.
145 <http://www.cs.technion.ac.il/~biham/Reports/Tiger/>.
147 config CRYPTO_GF128MUL
148 tristate "GF(2^128) multiplication functions (EXPERIMENTAL)"
149 depends on EXPERIMENTAL
151 Efficient table driven implementation of multiplications in the
152 field GF(2^128). This is needed by some cypher modes. This
153 option will be selected automatically if you select such a
154 cipher mode. Only select this option by hand if you expect to load
155 an external module that requires these functions.
158 tristate "ECB support"
159 select CRYPTO_BLKCIPHER
160 select CRYPTO_MANAGER
162 ECB: Electronic CodeBook mode
163 This is the simplest block cipher algorithm. It simply encrypts
164 the input block by block.
167 tristate "CBC support"
168 select CRYPTO_BLKCIPHER
169 select CRYPTO_MANAGER
171 CBC: Cipher Block Chaining mode
172 This block cipher algorithm is required for IPSec.
175 tristate "PCBC support"
176 select CRYPTO_BLKCIPHER
177 select CRYPTO_MANAGER
179 PCBC: Propagating Cipher Block Chaining mode
180 This block cipher algorithm is required for RxRPC.
183 tristate "LRW support (EXPERIMENTAL)"
184 depends on EXPERIMENTAL
185 select CRYPTO_BLKCIPHER
186 select CRYPTO_MANAGER
187 select CRYPTO_GF128MUL
189 LRW: Liskov Rivest Wagner, a tweakable, non malleable, non movable
190 narrow block cipher mode for dm-crypt. Use it with cipher
191 specification string aes-lrw-benbi, the key must be 256, 320 or 384.
192 The first 128, 192 or 256 bits in the key are used for AES and the
193 rest is used to tie each cipher block to its logical position.
196 tristate "XTS support (EXPERIMENTAL)"
197 depends on EXPERIMENTAL
198 select CRYPTO_BLKCIPHER
199 select CRYPTO_MANAGER
200 select CRYPTO_GF128MUL
202 XTS: IEEE1619/D16 narrow block cipher use with aes-xts-plain,
203 key size 256, 384 or 512 bits. This implementation currently
204 can't handle a sectorsize which is not a multiple of 16 bytes.
207 tristate "CTR support"
208 select CRYPTO_BLKCIPHER
210 select CRYPTO_MANAGER
213 This block cipher algorithm is required for IPSec.
216 tristate "GCM/GMAC support"
219 select CRYPTO_GF128MUL
221 Support for Galois/Counter Mode (GCM) and Galois Message
222 Authentication Code (GMAC). Required for IPSec.
225 tristate "CCM support"
229 Support for Counter with CBC MAC. Required for IPsec.
232 tristate "Software async crypto daemon"
233 select CRYPTO_BLKCIPHER
234 select CRYPTO_MANAGER
236 This is a generic software asynchronous crypto daemon that
237 converts an arbitrary synchronous software crypto algorithm
238 into an asynchronous algorithm that executes in a kernel thread.
241 tristate "DES and Triple DES EDE cipher algorithms"
244 DES cipher algorithm (FIPS 46-2), and Triple DES EDE (FIPS 46-3).
247 tristate "FCrypt cipher algorithm"
249 select CRYPTO_BLKCIPHER
251 FCrypt algorithm used by RxRPC.
253 config CRYPTO_BLOWFISH
254 tristate "Blowfish cipher algorithm"
257 Blowfish cipher algorithm, by Bruce Schneier.
259 This is a variable key length cipher which can use keys from 32
260 bits to 448 bits in length. It's fast, simple and specifically
261 designed for use on "large microprocessors".
264 <http://www.schneier.com/blowfish.html>
266 config CRYPTO_TWOFISH
267 tristate "Twofish cipher algorithm"
269 select CRYPTO_TWOFISH_COMMON
271 Twofish cipher algorithm.
273 Twofish was submitted as an AES (Advanced Encryption Standard)
274 candidate cipher by researchers at CounterPane Systems. It is a
275 16 round block cipher supporting key sizes of 128, 192, and 256
279 <http://www.schneier.com/twofish.html>
281 config CRYPTO_TWOFISH_COMMON
284 Common parts of the Twofish cipher algorithm shared by the
285 generic c and the assembler implementations.
287 config CRYPTO_TWOFISH_586
288 tristate "Twofish cipher algorithms (i586)"
289 depends on (X86 || UML_X86) && !64BIT
291 select CRYPTO_TWOFISH_COMMON
293 Twofish cipher algorithm.
295 Twofish was submitted as an AES (Advanced Encryption Standard)
296 candidate cipher by researchers at CounterPane Systems. It is a
297 16 round block cipher supporting key sizes of 128, 192, and 256
301 <http://www.schneier.com/twofish.html>
303 config CRYPTO_TWOFISH_X86_64
304 tristate "Twofish cipher algorithm (x86_64)"
305 depends on (X86 || UML_X86) && 64BIT
307 select CRYPTO_TWOFISH_COMMON
309 Twofish cipher algorithm (x86_64).
311 Twofish was submitted as an AES (Advanced Encryption Standard)
312 candidate cipher by researchers at CounterPane Systems. It is a
313 16 round block cipher supporting key sizes of 128, 192, and 256
317 <http://www.schneier.com/twofish.html>
319 config CRYPTO_SERPENT
320 tristate "Serpent cipher algorithm"
323 Serpent cipher algorithm, by Anderson, Biham & Knudsen.
325 Keys are allowed to be from 0 to 256 bits in length, in steps
326 of 8 bits. Also includes the 'Tnepres' algorithm, a reversed
327 variant of Serpent for compatibility with old kerneli.org code.
330 <http://www.cl.cam.ac.uk/~rja14/serpent.html>
333 tristate "AES cipher algorithms"
336 AES cipher algorithms (FIPS-197). AES uses the Rijndael
339 Rijndael appears to be consistently a very good performer in
340 both hardware and software across a wide range of computing
341 environments regardless of its use in feedback or non-feedback
342 modes. Its key setup time is excellent, and its key agility is
343 good. Rijndael's very low memory requirements make it very well
344 suited for restricted-space environments, in which it also
345 demonstrates excellent performance. Rijndael's operations are
346 among the easiest to defend against power and timing attacks.
348 The AES specifies three key sizes: 128, 192 and 256 bits
350 See <http://csrc.nist.gov/CryptoToolkit/aes/> for more information.
352 config CRYPTO_AES_586
353 tristate "AES cipher algorithms (i586)"
354 depends on (X86 || UML_X86) && !64BIT
358 AES cipher algorithms (FIPS-197). AES uses the Rijndael
361 Rijndael appears to be consistently a very good performer in
362 both hardware and software across a wide range of computing
363 environments regardless of its use in feedback or non-feedback
364 modes. Its key setup time is excellent, and its key agility is
365 good. Rijndael's very low memory requirements make it very well
366 suited for restricted-space environments, in which it also
367 demonstrates excellent performance. Rijndael's operations are
368 among the easiest to defend against power and timing attacks.
370 The AES specifies three key sizes: 128, 192 and 256 bits
372 See <http://csrc.nist.gov/encryption/aes/> for more information.
374 config CRYPTO_AES_X86_64
375 tristate "AES cipher algorithms (x86_64)"
376 depends on (X86 || UML_X86) && 64BIT
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/encryption/aes/> for more information.
397 tristate "CAST5 (CAST-128) cipher algorithm"
400 The CAST5 encryption algorithm (synonymous with CAST-128) is
401 described in RFC2144.
404 tristate "CAST6 (CAST-256) cipher algorithm"
407 The CAST6 encryption algorithm (synonymous with CAST-256) is
408 described in RFC2612.
411 tristate "TEA, XTEA and XETA cipher algorithms"
414 TEA cipher algorithm.
416 Tiny Encryption Algorithm is a simple cipher that uses
417 many rounds for security. It is very fast and uses
420 Xtendend Tiny Encryption Algorithm is a modification to
421 the TEA algorithm to address a potential key weakness
422 in the TEA algorithm.
424 Xtendend Encryption Tiny Algorithm is a mis-implementation
425 of the XTEA algorithm for compatibility purposes.
428 tristate "ARC4 cipher algorithm"
431 ARC4 cipher algorithm.
433 ARC4 is a stream cipher using keys ranging from 8 bits to 2048
434 bits in length. This algorithm is required for driver-based
435 WEP, but it should not be for other purposes because of the
436 weakness of the algorithm.
439 tristate "Khazad cipher algorithm"
442 Khazad cipher algorithm.
444 Khazad was a finalist in the initial NESSIE competition. It is
445 an algorithm optimized for 64-bit processors with good performance
446 on 32-bit processors. Khazad uses an 128 bit key size.
449 <http://planeta.terra.com.br/informatica/paulobarreto/KhazadPage.html>
452 tristate "Anubis cipher algorithm"
455 Anubis cipher algorithm.
457 Anubis is a variable key length cipher which can use keys from
458 128 bits to 320 bits in length. It was evaluated as a entrant
459 in the NESSIE competition.
462 <https://www.cosic.esat.kuleuven.ac.be/nessie/reports/>
463 <http://planeta.terra.com.br/informatica/paulobarreto/AnubisPage.html>
466 tristate "SEED cipher algorithm"
469 SEED cipher algorithm (RFC4269).
471 SEED is a 128-bit symmetric key block cipher that has been
472 developed by KISA (Korea Information Security Agency) as a
473 national standard encryption algorithm of the Republic of Korea.
474 It is a 16 round block cipher with the key size of 128 bit.
477 <http://www.kisa.or.kr/kisa/seed/jsp/seed_eng.jsp>
479 config CRYPTO_SALSA20
480 tristate "Salsa20 stream cipher algorithm (EXPERIMENTAL)"
481 depends on EXPERIMENTAL
482 select CRYPTO_BLKCIPHER
484 Salsa20 stream cipher algorithm.
486 Salsa20 is a stream cipher submitted to eSTREAM, the ECRYPT
487 Stream Cipher Project. See <http://www.ecrypt.eu.org/stream/>
489 The Salsa20 stream cipher algorithm is designed by Daniel J.
490 Bernstein <djb@cr.yp.to>. See <http://cr.yp.to/snuffle.html>
492 config CRYPTO_SALSA20_586
493 tristate "Salsa20 stream cipher algorithm (i586) (EXPERIMENTAL)"
494 depends on (X86 || UML_X86) && !64BIT
495 depends on EXPERIMENTAL
496 select CRYPTO_BLKCIPHER
498 Salsa20 stream cipher algorithm.
500 Salsa20 is a stream cipher submitted to eSTREAM, the ECRYPT
501 Stream Cipher Project. See <http://www.ecrypt.eu.org/stream/>
503 The Salsa20 stream cipher algorithm is designed by Daniel J.
504 Bernstein <djb@cr.yp.to>. See <http://cr.yp.to/snuffle.html>
506 config CRYPTO_SALSA20_X86_64
507 tristate "Salsa20 stream cipher algorithm (x86_64) (EXPERIMENTAL)"
508 depends on (X86 || UML_X86) && 64BIT
509 depends on EXPERIMENTAL
510 select CRYPTO_BLKCIPHER
512 Salsa20 stream cipher algorithm.
514 Salsa20 is a stream cipher submitted to eSTREAM, the ECRYPT
515 Stream Cipher Project. See <http://www.ecrypt.eu.org/stream/>
517 The Salsa20 stream cipher algorithm is designed by Daniel J.
518 Bernstein <djb@cr.yp.to>. See <http://cr.yp.to/snuffle.html>
520 config CRYPTO_DEFLATE
521 tristate "Deflate compression algorithm"
526 This is the Deflate algorithm (RFC1951), specified for use in
527 IPSec with the IPCOMP protocol (RFC3173, RFC2394).
529 You will most probably want this if using IPSec.
531 config CRYPTO_MICHAEL_MIC
532 tristate "Michael MIC keyed digest algorithm"
535 Michael MIC is used for message integrity protection in TKIP
536 (IEEE 802.11i). This algorithm is required for TKIP, but it
537 should not be used for other purposes because of the weakness
541 tristate "CRC32c CRC algorithm"
545 Castagnoli, et al Cyclic Redundancy-Check Algorithm. Used
546 by iSCSI for header and data digests and by others.
547 See Castagnoli93. This implementation uses lib/libcrc32c.
548 Module will be crc32c.
550 config CRYPTO_CAMELLIA
551 tristate "Camellia cipher algorithms"
555 Camellia cipher algorithms module.
557 Camellia is a symmetric key block cipher developed jointly
558 at NTT and Mitsubishi Electric Corporation.
560 The Camellia specifies three key sizes: 128, 192 and 256 bits.
563 <https://info.isl.ntt.co.jp/crypt/eng/camellia/index_s.html>
566 tristate "Testing module"
571 Quick & dirty crypto test module.
573 config CRYPTO_AUTHENC
574 tristate "Authenc support"
576 select CRYPTO_MANAGER
579 Authenc: Combined mode wrapper for IPsec.
580 This is required for IPSec.
583 tristate "LZO compression algorithm"
586 select LZO_DECOMPRESS
588 This is the LZO algorithm.
590 source "drivers/crypto/Kconfig"