2 # Cryptographic API Configuration
5 menu "Cryptographic options"
8 bool "Cryptographic API"
10 This option provides the core Cryptographic API.
17 This option provides the API for cryptographic algorithms.
19 config CRYPTO_BLKCIPHER
28 tristate "Cryptographic algorithm manager"
32 Create default cryptographic template instantiations such as
36 tristate "HMAC support"
39 HMAC: Keyed-Hashing for Message Authentication (RFC2104).
40 This is required for IPSec.
43 tristate "Null algorithms"
46 These are 'Null' algorithms, used by IPsec, which do nothing.
49 tristate "MD4 digest algorithm"
52 MD4 message digest algorithm (RFC1320).
55 tristate "MD5 digest algorithm"
58 MD5 message digest algorithm (RFC1321).
61 tristate "SHA1 digest algorithm"
64 SHA-1 secure hash standard (FIPS 180-1/DFIPS 180-2).
66 config CRYPTO_SHA1_S390
67 tristate "SHA1 digest algorithm (s390)"
71 This is the s390 hardware accelerated implementation of the
72 SHA-1 secure hash standard (FIPS 180-1/DFIPS 180-2).
75 tristate "SHA256 digest algorithm"
78 SHA256 secure hash standard (DFIPS 180-2).
80 This version of SHA implements a 256 bit hash with 128 bits of
81 security against collision attacks.
83 config CRYPTO_SHA256_S390
84 tristate "SHA256 digest algorithm (s390)"
88 This is the s390 hardware accelerated implementation of the
89 SHA256 secure hash standard (DFIPS 180-2).
91 This version of SHA implements a 256 bit hash with 128 bits of
92 security against collision attacks.
95 tristate "SHA384 and SHA512 digest algorithms"
98 SHA512 secure hash standard (DFIPS 180-2).
100 This version of SHA implements a 512 bit hash with 256 bits of
101 security against collision attacks.
103 This code also includes SHA-384, a 384 bit hash with 192 bits
104 of security against collision attacks.
107 tristate "Whirlpool digest algorithms"
110 Whirlpool hash algorithm 512, 384 and 256-bit hashes
112 Whirlpool-512 is part of the NESSIE cryptographic primitives.
113 Whirlpool will be part of the ISO/IEC 10118-3:2003(E) standard
116 <http://planeta.terra.com.br/informatica/paulobarreto/WhirlpoolPage.html>
119 tristate "Tiger digest algorithms"
122 Tiger hash algorithm 192, 160 and 128-bit hashes
124 Tiger is a hash function optimized for 64-bit processors while
125 still having decent performance on 32-bit processors.
126 Tiger was developed by Ross Anderson and Eli Biham.
129 <http://www.cs.technion.ac.il/~biham/Reports/Tiger/>.
132 tristate "ECB support"
133 select CRYPTO_BLKCIPHER
136 ECB: Electronic CodeBook mode
137 This is the simplest block cipher algorithm. It simply encrypts
138 the input block by block.
141 tristate "CBC support"
142 select CRYPTO_BLKCIPHER
145 CBC: Cipher Block Chaining mode
146 This block cipher algorithm is required for IPSec.
149 tristate "DES and Triple DES EDE cipher algorithms"
152 DES cipher algorithm (FIPS 46-2), and Triple DES EDE (FIPS 46-3).
154 config CRYPTO_DES_S390
155 tristate "DES and Triple DES cipher algorithms (s390)"
158 select CRYPTO_BLKCIPHER
160 DES cipher algorithm (FIPS 46-2), and Triple DES EDE (FIPS 46-3).
162 config CRYPTO_BLOWFISH
163 tristate "Blowfish cipher algorithm"
166 Blowfish cipher algorithm, by Bruce Schneier.
168 This is a variable key length cipher which can use keys from 32
169 bits to 448 bits in length. It's fast, simple and specifically
170 designed for use on "large microprocessors".
173 <http://www.schneier.com/blowfish.html>
175 config CRYPTO_TWOFISH
176 tristate "Twofish cipher algorithm"
178 select CRYPTO_TWOFISH_COMMON
180 Twofish cipher algorithm.
182 Twofish was submitted as an AES (Advanced Encryption Standard)
183 candidate cipher by researchers at CounterPane Systems. It is a
184 16 round block cipher supporting key sizes of 128, 192, and 256
188 <http://www.schneier.com/twofish.html>
190 config CRYPTO_TWOFISH_COMMON
193 Common parts of the Twofish cipher algorithm shared by the
194 generic c and the assembler implementations.
196 config CRYPTO_TWOFISH_586
197 tristate "Twofish cipher algorithms (i586)"
198 depends on (X86 || UML_X86) && !64BIT
200 select CRYPTO_TWOFISH_COMMON
202 Twofish cipher algorithm.
204 Twofish was submitted as an AES (Advanced Encryption Standard)
205 candidate cipher by researchers at CounterPane Systems. It is a
206 16 round block cipher supporting key sizes of 128, 192, and 256
210 <http://www.schneier.com/twofish.html>
212 config CRYPTO_TWOFISH_X86_64
213 tristate "Twofish cipher algorithm (x86_64)"
214 depends on (X86 || UML_X86) && 64BIT
216 select CRYPTO_TWOFISH_COMMON
218 Twofish cipher algorithm (x86_64).
220 Twofish was submitted as an AES (Advanced Encryption Standard)
221 candidate cipher by researchers at CounterPane Systems. It is a
222 16 round block cipher supporting key sizes of 128, 192, and 256
226 <http://www.schneier.com/twofish.html>
228 config CRYPTO_SERPENT
229 tristate "Serpent cipher algorithm"
232 Serpent cipher algorithm, by Anderson, Biham & Knudsen.
234 Keys are allowed to be from 0 to 256 bits in length, in steps
235 of 8 bits. Also includes the 'Tnepres' algorithm, a reversed
236 variant of Serpent for compatibility with old kerneli code.
239 <http://www.cl.cam.ac.uk/~rja14/serpent.html>
242 tristate "AES cipher algorithms"
245 AES cipher algorithms (FIPS-197). AES uses the Rijndael
248 Rijndael appears to be consistently a very good performer in
249 both hardware and software across a wide range of computing
250 environments regardless of its use in feedback or non-feedback
251 modes. Its key setup time is excellent, and its key agility is
252 good. Rijndael's very low memory requirements make it very well
253 suited for restricted-space environments, in which it also
254 demonstrates excellent performance. Rijndael's operations are
255 among the easiest to defend against power and timing attacks.
257 The AES specifies three key sizes: 128, 192 and 256 bits
259 See <http://csrc.nist.gov/CryptoToolkit/aes/> for more information.
261 config CRYPTO_AES_586
262 tristate "AES cipher algorithms (i586)"
263 depends on (X86 || UML_X86) && !64BIT
266 AES cipher algorithms (FIPS-197). AES uses the Rijndael
269 Rijndael appears to be consistently a very good performer in
270 both hardware and software across a wide range of computing
271 environments regardless of its use in feedback or non-feedback
272 modes. Its key setup time is excellent, and its key agility is
273 good. Rijndael's very low memory requirements make it very well
274 suited for restricted-space environments, in which it also
275 demonstrates excellent performance. Rijndael's operations are
276 among the easiest to defend against power and timing attacks.
278 The AES specifies three key sizes: 128, 192 and 256 bits
280 See <http://csrc.nist.gov/encryption/aes/> for more information.
282 config CRYPTO_AES_X86_64
283 tristate "AES cipher algorithms (x86_64)"
284 depends on (X86 || UML_X86) && 64BIT
287 AES cipher algorithms (FIPS-197). AES uses the Rijndael
290 Rijndael appears to be consistently a very good performer in
291 both hardware and software across a wide range of computing
292 environments regardless of its use in feedback or non-feedback
293 modes. Its key setup time is excellent, and its key agility is
294 good. Rijndael's very low memory requirements make it very well
295 suited for restricted-space environments, in which it also
296 demonstrates excellent performance. Rijndael's operations are
297 among the easiest to defend against power and timing attacks.
299 The AES specifies three key sizes: 128, 192 and 256 bits
301 See <http://csrc.nist.gov/encryption/aes/> for more information.
303 config CRYPTO_AES_S390
304 tristate "AES cipher algorithms (s390)"
307 select CRYPTO_BLKCIPHER
309 This is the s390 hardware accelerated implementation of the
310 AES cipher algorithms (FIPS-197). AES uses the Rijndael
313 Rijndael appears to be consistently a very good performer in
314 both hardware and software across a wide range of computing
315 environments regardless of its use in feedback or non-feedback
316 modes. Its key setup time is excellent, and its key agility is
317 good. Rijndael's very low memory requirements make it very well
318 suited for restricted-space environments, in which it also
319 demonstrates excellent performance. Rijndael's operations are
320 among the easiest to defend against power and timing attacks.
322 On s390 the System z9-109 currently only supports the key size
326 tristate "CAST5 (CAST-128) cipher algorithm"
329 The CAST5 encryption algorithm (synonymous with CAST-128) is
330 described in RFC2144.
333 tristate "CAST6 (CAST-256) cipher algorithm"
336 The CAST6 encryption algorithm (synonymous with CAST-256) is
337 described in RFC2612.
340 tristate "TEA, XTEA and XETA cipher algorithms"
343 TEA cipher algorithm.
345 Tiny Encryption Algorithm is a simple cipher that uses
346 many rounds for security. It is very fast and uses
349 Xtendend Tiny Encryption Algorithm is a modification to
350 the TEA algorithm to address a potential key weakness
351 in the TEA algorithm.
353 Xtendend Encryption Tiny Algorithm is a mis-implementation
354 of the XTEA algorithm for compatibility purposes.
357 tristate "ARC4 cipher algorithm"
360 ARC4 cipher algorithm.
362 ARC4 is a stream cipher using keys ranging from 8 bits to 2048
363 bits in length. This algorithm is required for driver-based
364 WEP, but it should not be for other purposes because of the
365 weakness of the algorithm.
368 tristate "Khazad cipher algorithm"
371 Khazad cipher algorithm.
373 Khazad was a finalist in the initial NESSIE competition. It is
374 an algorithm optimized for 64-bit processors with good performance
375 on 32-bit processors. Khazad uses an 128 bit key size.
378 <http://planeta.terra.com.br/informatica/paulobarreto/KhazadPage.html>
381 tristate "Anubis cipher algorithm"
384 Anubis cipher algorithm.
386 Anubis is a variable key length cipher which can use keys from
387 128 bits to 320 bits in length. It was evaluated as a entrant
388 in the NESSIE competition.
391 <https://www.cosic.esat.kuleuven.ac.be/nessie/reports/>
392 <http://planeta.terra.com.br/informatica/paulobarreto/AnubisPage.html>
395 config CRYPTO_DEFLATE
396 tristate "Deflate compression algorithm"
401 This is the Deflate algorithm (RFC1951), specified for use in
402 IPSec with the IPCOMP protocol (RFC3173, RFC2394).
404 You will most probably want this if using IPSec.
406 config CRYPTO_MICHAEL_MIC
407 tristate "Michael MIC keyed digest algorithm"
410 Michael MIC is used for message integrity protection in TKIP
411 (IEEE 802.11i). This algorithm is required for TKIP, but it
412 should not be used for other purposes because of the weakness
416 tristate "CRC32c CRC algorithm"
420 Castagnoli, et al Cyclic Redundancy-Check Algorithm. Used
421 by iSCSI for header and data digests and by others.
422 See Castagnoli93. This implementation uses lib/libcrc32c.
423 Module will be crc32c.
426 tristate "Testing module"
430 Quick & dirty crypto test module.
432 source "drivers/crypto/Kconfig"