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
38 HMAC: Keyed-Hashing for Message Authentication (RFC2104).
39 This is required for IPSec.
42 tristate "Null algorithms"
45 These are 'Null' algorithms, used by IPsec, which do nothing.
48 tristate "MD4 digest algorithm"
51 MD4 message digest algorithm (RFC1320).
54 tristate "MD5 digest algorithm"
57 MD5 message digest algorithm (RFC1321).
60 tristate "SHA1 digest algorithm"
63 SHA-1 secure hash standard (FIPS 180-1/DFIPS 180-2).
65 config CRYPTO_SHA1_S390
66 tristate "SHA1 digest algorithm (s390)"
70 This is the s390 hardware accelerated implementation of the
71 SHA-1 secure hash standard (FIPS 180-1/DFIPS 180-2).
74 tristate "SHA256 digest algorithm"
77 SHA256 secure hash standard (DFIPS 180-2).
79 This version of SHA implements a 256 bit hash with 128 bits of
80 security against collision attacks.
82 config CRYPTO_SHA256_S390
83 tristate "SHA256 digest algorithm (s390)"
87 This is the s390 hardware accelerated implementation of the
88 SHA256 secure hash standard (DFIPS 180-2).
90 This version of SHA implements a 256 bit hash with 128 bits of
91 security against collision attacks.
94 tristate "SHA384 and SHA512 digest algorithms"
97 SHA512 secure hash standard (DFIPS 180-2).
99 This version of SHA implements a 512 bit hash with 256 bits of
100 security against collision attacks.
102 This code also includes SHA-384, a 384 bit hash with 192 bits
103 of security against collision attacks.
106 tristate "Whirlpool digest algorithms"
109 Whirlpool hash algorithm 512, 384 and 256-bit hashes
111 Whirlpool-512 is part of the NESSIE cryptographic primitives.
112 Whirlpool will be part of the ISO/IEC 10118-3:2003(E) standard
115 <http://planeta.terra.com.br/informatica/paulobarreto/WhirlpoolPage.html>
118 tristate "Tiger digest algorithms"
121 Tiger hash algorithm 192, 160 and 128-bit hashes
123 Tiger is a hash function optimized for 64-bit processors while
124 still having decent performance on 32-bit processors.
125 Tiger was developed by Ross Anderson and Eli Biham.
128 <http://www.cs.technion.ac.il/~biham/Reports/Tiger/>.
131 tristate "ECB support"
132 select CRYPTO_BLKCIPHER
135 ECB: Electronic CodeBook mode
136 This is the simplest block cipher algorithm. It simply encrypts
137 the input block by block.
140 tristate "CBC support"
141 select CRYPTO_BLKCIPHER
144 CBC: Cipher Block Chaining mode
145 This block cipher algorithm is required for IPSec.
148 tristate "DES and Triple DES EDE cipher algorithms"
151 DES cipher algorithm (FIPS 46-2), and Triple DES EDE (FIPS 46-3).
153 config CRYPTO_DES_S390
154 tristate "DES and Triple DES cipher algorithms (s390)"
157 select CRYPTO_BLKCIPHER
159 DES cipher algorithm (FIPS 46-2), and Triple DES EDE (FIPS 46-3).
161 config CRYPTO_BLOWFISH
162 tristate "Blowfish cipher algorithm"
165 Blowfish cipher algorithm, by Bruce Schneier.
167 This is a variable key length cipher which can use keys from 32
168 bits to 448 bits in length. It's fast, simple and specifically
169 designed for use on "large microprocessors".
172 <http://www.schneier.com/blowfish.html>
174 config CRYPTO_TWOFISH
175 tristate "Twofish cipher algorithm"
177 select CRYPTO_TWOFISH_COMMON
179 Twofish cipher algorithm.
181 Twofish was submitted as an AES (Advanced Encryption Standard)
182 candidate cipher by researchers at CounterPane Systems. It is a
183 16 round block cipher supporting key sizes of 128, 192, and 256
187 <http://www.schneier.com/twofish.html>
189 config CRYPTO_TWOFISH_COMMON
192 Common parts of the Twofish cipher algorithm shared by the
193 generic c and the assembler implementations.
195 config CRYPTO_TWOFISH_586
196 tristate "Twofish cipher algorithms (i586)"
197 depends on (X86 || UML_X86) && !64BIT
199 select CRYPTO_TWOFISH_COMMON
201 Twofish cipher algorithm.
203 Twofish was submitted as an AES (Advanced Encryption Standard)
204 candidate cipher by researchers at CounterPane Systems. It is a
205 16 round block cipher supporting key sizes of 128, 192, and 256
209 <http://www.schneier.com/twofish.html>
211 config CRYPTO_TWOFISH_X86_64
212 tristate "Twofish cipher algorithm (x86_64)"
213 depends on (X86 || UML_X86) && 64BIT
215 select CRYPTO_TWOFISH_COMMON
217 Twofish cipher algorithm (x86_64).
219 Twofish was submitted as an AES (Advanced Encryption Standard)
220 candidate cipher by researchers at CounterPane Systems. It is a
221 16 round block cipher supporting key sizes of 128, 192, and 256
225 <http://www.schneier.com/twofish.html>
227 config CRYPTO_SERPENT
228 tristate "Serpent cipher algorithm"
231 Serpent cipher algorithm, by Anderson, Biham & Knudsen.
233 Keys are allowed to be from 0 to 256 bits in length, in steps
234 of 8 bits. Also includes the 'Tnepres' algorithm, a reversed
235 variant of Serpent for compatibility with old kerneli code.
238 <http://www.cl.cam.ac.uk/~rja14/serpent.html>
241 tristate "AES cipher algorithms"
244 AES cipher algorithms (FIPS-197). AES uses the Rijndael
247 Rijndael appears to be consistently a very good performer in
248 both hardware and software across a wide range of computing
249 environments regardless of its use in feedback or non-feedback
250 modes. Its key setup time is excellent, and its key agility is
251 good. Rijndael's very low memory requirements make it very well
252 suited for restricted-space environments, in which it also
253 demonstrates excellent performance. Rijndael's operations are
254 among the easiest to defend against power and timing attacks.
256 The AES specifies three key sizes: 128, 192 and 256 bits
258 See <http://csrc.nist.gov/CryptoToolkit/aes/> for more information.
260 config CRYPTO_AES_586
261 tristate "AES cipher algorithms (i586)"
262 depends on (X86 || UML_X86) && !64BIT
265 AES cipher algorithms (FIPS-197). AES uses the Rijndael
268 Rijndael appears to be consistently a very good performer in
269 both hardware and software across a wide range of computing
270 environments regardless of its use in feedback or non-feedback
271 modes. Its key setup time is excellent, and its key agility is
272 good. Rijndael's very low memory requirements make it very well
273 suited for restricted-space environments, in which it also
274 demonstrates excellent performance. Rijndael's operations are
275 among the easiest to defend against power and timing attacks.
277 The AES specifies three key sizes: 128, 192 and 256 bits
279 See <http://csrc.nist.gov/encryption/aes/> for more information.
281 config CRYPTO_AES_X86_64
282 tristate "AES cipher algorithms (x86_64)"
283 depends on (X86 || UML_X86) && 64BIT
286 AES cipher algorithms (FIPS-197). AES uses the Rijndael
289 Rijndael appears to be consistently a very good performer in
290 both hardware and software across a wide range of computing
291 environments regardless of its use in feedback or non-feedback
292 modes. Its key setup time is excellent, and its key agility is
293 good. Rijndael's very low memory requirements make it very well
294 suited for restricted-space environments, in which it also
295 demonstrates excellent performance. Rijndael's operations are
296 among the easiest to defend against power and timing attacks.
298 The AES specifies three key sizes: 128, 192 and 256 bits
300 See <http://csrc.nist.gov/encryption/aes/> for more information.
302 config CRYPTO_AES_S390
303 tristate "AES cipher algorithms (s390)"
306 select CRYPTO_BLKCIPHER
308 This is the s390 hardware accelerated implementation of the
309 AES cipher algorithms (FIPS-197). AES uses the Rijndael
312 Rijndael appears to be consistently a very good performer in
313 both hardware and software across a wide range of computing
314 environments regardless of its use in feedback or non-feedback
315 modes. Its key setup time is excellent, and its key agility is
316 good. Rijndael's very low memory requirements make it very well
317 suited for restricted-space environments, in which it also
318 demonstrates excellent performance. Rijndael's operations are
319 among the easiest to defend against power and timing attacks.
321 On s390 the System z9-109 currently only supports the key size
325 tristate "CAST5 (CAST-128) cipher algorithm"
328 The CAST5 encryption algorithm (synonymous with CAST-128) is
329 described in RFC2144.
332 tristate "CAST6 (CAST-256) cipher algorithm"
335 The CAST6 encryption algorithm (synonymous with CAST-256) is
336 described in RFC2612.
339 tristate "TEA, XTEA and XETA cipher algorithms"
342 TEA cipher algorithm.
344 Tiny Encryption Algorithm is a simple cipher that uses
345 many rounds for security. It is very fast and uses
348 Xtendend Tiny Encryption Algorithm is a modification to
349 the TEA algorithm to address a potential key weakness
350 in the TEA algorithm.
352 Xtendend Encryption Tiny Algorithm is a mis-implementation
353 of the XTEA algorithm for compatibility purposes.
356 tristate "ARC4 cipher algorithm"
359 ARC4 cipher algorithm.
361 ARC4 is a stream cipher using keys ranging from 8 bits to 2048
362 bits in length. This algorithm is required for driver-based
363 WEP, but it should not be for other purposes because of the
364 weakness of the algorithm.
367 tristate "Khazad cipher algorithm"
370 Khazad cipher algorithm.
372 Khazad was a finalist in the initial NESSIE competition. It is
373 an algorithm optimized for 64-bit processors with good performance
374 on 32-bit processors. Khazad uses an 128 bit key size.
377 <http://planeta.terra.com.br/informatica/paulobarreto/KhazadPage.html>
380 tristate "Anubis cipher algorithm"
383 Anubis cipher algorithm.
385 Anubis is a variable key length cipher which can use keys from
386 128 bits to 320 bits in length. It was evaluated as a entrant
387 in the NESSIE competition.
390 <https://www.cosic.esat.kuleuven.ac.be/nessie/reports/>
391 <http://planeta.terra.com.br/informatica/paulobarreto/AnubisPage.html>
394 config CRYPTO_DEFLATE
395 tristate "Deflate compression algorithm"
400 This is the Deflate algorithm (RFC1951), specified for use in
401 IPSec with the IPCOMP protocol (RFC3173, RFC2394).
403 You will most probably want this if using IPSec.
405 config CRYPTO_MICHAEL_MIC
406 tristate "Michael MIC keyed digest algorithm"
409 Michael MIC is used for message integrity protection in TKIP
410 (IEEE 802.11i). This algorithm is required for TKIP, but it
411 should not be used for other purposes because of the weakness
415 tristate "CRC32c CRC algorithm"
419 Castagnoli, et al Cyclic Redundancy-Check Algorithm. Used
420 by iSCSI for header and data digests and by others.
421 See Castagnoli93. This implementation uses lib/libcrc32c.
422 Module will be crc32c.
425 tristate "Testing module"
429 Quick & dirty crypto test module.
431 source "drivers/crypto/Kconfig"