2 # Cryptographic API Configuration
5 menu "Cryptographic options"
8 bool "Cryptographic API"
10 This option provides the core Cryptographic API.
16 HMAC: Keyed-Hashing for Message Authentication (RFC2104).
17 This is required for IPSec.
20 tristate "Null algorithms"
23 These are 'Null' algorithms, used by IPsec, which do nothing.
26 tristate "MD4 digest algorithm"
29 MD4 message digest algorithm (RFC1320).
32 tristate "MD5 digest algorithm"
35 MD5 message digest algorithm (RFC1321).
38 tristate "SHA1 digest algorithm"
41 SHA-1 secure hash standard (FIPS 180-1/DFIPS 180-2).
43 config CRYPTO_SHA1_S390
44 tristate "SHA1 digest algorithm (s390)"
45 depends on CRYPTO && S390
47 This is the s390 hardware accelerated implementation of the
48 SHA-1 secure hash standard (FIPS 180-1/DFIPS 180-2).
51 tristate "SHA256 digest algorithm"
54 SHA256 secure hash standard (DFIPS 180-2).
56 This version of SHA implements a 256 bit hash with 128 bits of
57 security against collision attacks.
59 config CRYPTO_SHA256_S390
60 tristate "SHA256 digest algorithm (s390)"
61 depends on CRYPTO && S390
63 This is the s390 hardware accelerated implementation of the
64 SHA256 secure hash standard (DFIPS 180-2).
66 This version of SHA implements a 256 bit hash with 128 bits of
67 security against collision attacks.
70 tristate "SHA384 and SHA512 digest algorithms"
73 SHA512 secure hash standard (DFIPS 180-2).
75 This version of SHA implements a 512 bit hash with 256 bits of
76 security against collision attacks.
78 This code also includes SHA-384, a 384 bit hash with 192 bits
79 of security against collision attacks.
82 tristate "Whirlpool digest algorithms"
85 Whirlpool hash algorithm 512, 384 and 256-bit hashes
87 Whirlpool-512 is part of the NESSIE cryptographic primitives.
88 Whirlpool will be part of the ISO/IEC 10118-3:2003(E) standard
91 <http://planeta.terra.com.br/informatica/paulobarreto/WhirlpoolPage.html>
94 tristate "Tiger digest algorithms"
97 Tiger hash algorithm 192, 160 and 128-bit hashes
99 Tiger is a hash function optimized for 64-bit processors while
100 still having decent performance on 32-bit processors.
101 Tiger was developed by Ross Anderson and Eli Biham.
104 <http://www.cs.technion.ac.il/~biham/Reports/Tiger/>.
107 tristate "DES and Triple DES EDE cipher algorithms"
110 DES cipher algorithm (FIPS 46-2), and Triple DES EDE (FIPS 46-3).
112 config CRYPTO_DES_S390
113 tristate "DES and Triple DES cipher algorithms (s390)"
114 depends on CRYPTO && S390
116 DES cipher algorithm (FIPS 46-2), and Triple DES EDE (FIPS 46-3).
118 config CRYPTO_BLOWFISH
119 tristate "Blowfish cipher algorithm"
122 Blowfish cipher algorithm, by Bruce Schneier.
124 This is a variable key length cipher which can use keys from 32
125 bits to 448 bits in length. It's fast, simple and specifically
126 designed for use on "large microprocessors".
129 <http://www.schneier.com/blowfish.html>
131 config CRYPTO_TWOFISH
132 tristate "Twofish cipher algorithm"
134 select CRYPTO_TWOFISH_COMMON
136 Twofish cipher algorithm.
138 Twofish was submitted as an AES (Advanced Encryption Standard)
139 candidate cipher by researchers at CounterPane Systems. It is a
140 16 round block cipher supporting key sizes of 128, 192, and 256
144 <http://www.schneier.com/twofish.html>
146 config CRYPTO_TWOFISH_COMMON
150 Common parts of the Twofish cipher algorithm shared by the
151 generic c and the assembler implementations.
153 config CRYPTO_TWOFISH_586
154 tristate "Twofish cipher algorithms (i586)"
155 depends on CRYPTO && ((X86 || UML_X86) && !64BIT)
156 select CRYPTO_TWOFISH_COMMON
158 Twofish cipher algorithm.
160 Twofish was submitted as an AES (Advanced Encryption Standard)
161 candidate cipher by researchers at CounterPane Systems. It is a
162 16 round block cipher supporting key sizes of 128, 192, and 256
166 <http://www.schneier.com/twofish.html>
168 config CRYPTO_SERPENT
169 tristate "Serpent cipher algorithm"
172 Serpent cipher algorithm, by Anderson, Biham & Knudsen.
174 Keys are allowed to be from 0 to 256 bits in length, in steps
175 of 8 bits. Also includes the 'Tnepres' algorithm, a reversed
176 variant of Serpent for compatibility with old kerneli code.
179 <http://www.cl.cam.ac.uk/~rja14/serpent.html>
182 tristate "AES cipher algorithms"
185 AES cipher algorithms (FIPS-197). AES uses the Rijndael
188 Rijndael appears to be consistently a very good performer in
189 both hardware and software across a wide range of computing
190 environments regardless of its use in feedback or non-feedback
191 modes. Its key setup time is excellent, and its key agility is
192 good. Rijndael's very low memory requirements make it very well
193 suited for restricted-space environments, in which it also
194 demonstrates excellent performance. Rijndael's operations are
195 among the easiest to defend against power and timing attacks.
197 The AES specifies three key sizes: 128, 192 and 256 bits
199 See <http://csrc.nist.gov/CryptoToolkit/aes/> for more information.
201 config CRYPTO_AES_586
202 tristate "AES cipher algorithms (i586)"
203 depends on CRYPTO && ((X86 || UML_X86) && !64BIT)
205 AES cipher algorithms (FIPS-197). AES uses the Rijndael
208 Rijndael appears to be consistently a very good performer in
209 both hardware and software across a wide range of computing
210 environments regardless of its use in feedback or non-feedback
211 modes. Its key setup time is excellent, and its key agility is
212 good. Rijndael's very low memory requirements make it very well
213 suited for restricted-space environments, in which it also
214 demonstrates excellent performance. Rijndael's operations are
215 among the easiest to defend against power and timing attacks.
217 The AES specifies three key sizes: 128, 192 and 256 bits
219 See <http://csrc.nist.gov/encryption/aes/> for more information.
221 config CRYPTO_AES_X86_64
222 tristate "AES cipher algorithms (x86_64)"
223 depends on CRYPTO && ((X86 || UML_X86) && 64BIT)
225 AES cipher algorithms (FIPS-197). AES uses the Rijndael
228 Rijndael appears to be consistently a very good performer in
229 both hardware and software across a wide range of computing
230 environments regardless of its use in feedback or non-feedback
231 modes. Its key setup time is excellent, and its key agility is
232 good. Rijndael's very low memory requirements make it very well
233 suited for restricted-space environments, in which it also
234 demonstrates excellent performance. Rijndael's operations are
235 among the easiest to defend against power and timing attacks.
237 The AES specifies three key sizes: 128, 192 and 256 bits
239 See <http://csrc.nist.gov/encryption/aes/> for more information.
241 config CRYPTO_AES_S390
242 tristate "AES cipher algorithms (s390)"
243 depends on CRYPTO && S390
245 This is the s390 hardware accelerated implementation of the
246 AES cipher algorithms (FIPS-197). AES uses the Rijndael
249 Rijndael appears to be consistently a very good performer in
250 both hardware and software across a wide range of computing
251 environments regardless of its use in feedback or non-feedback
252 modes. Its key setup time is excellent, and its key agility is
253 good. Rijndael's very low memory requirements make it very well
254 suited for restricted-space environments, in which it also
255 demonstrates excellent performance. Rijndael's operations are
256 among the easiest to defend against power and timing attacks.
258 On s390 the System z9-109 currently only supports the key size
262 tristate "CAST5 (CAST-128) cipher algorithm"
265 The CAST5 encryption algorithm (synonymous with CAST-128) is
266 described in RFC2144.
269 tristate "CAST6 (CAST-256) cipher algorithm"
272 The CAST6 encryption algorithm (synonymous with CAST-256) is
273 described in RFC2612.
276 tristate "TEA, XTEA and XETA cipher algorithms"
279 TEA cipher algorithm.
281 Tiny Encryption Algorithm is a simple cipher that uses
282 many rounds for security. It is very fast and uses
285 Xtendend Tiny Encryption Algorithm is a modification to
286 the TEA algorithm to address a potential key weakness
287 in the TEA algorithm.
289 Xtendend Encryption Tiny Algorithm is a mis-implementation
290 of the XTEA algorithm for compatibility purposes.
293 tristate "ARC4 cipher algorithm"
296 ARC4 cipher algorithm.
298 ARC4 is a stream cipher using keys ranging from 8 bits to 2048
299 bits in length. This algorithm is required for driver-based
300 WEP, but it should not be for other purposes because of the
301 weakness of the algorithm.
304 tristate "Khazad cipher algorithm"
307 Khazad cipher algorithm.
309 Khazad was a finalist in the initial NESSIE competition. It is
310 an algorithm optimized for 64-bit processors with good performance
311 on 32-bit processors. Khazad uses an 128 bit key size.
314 <http://planeta.terra.com.br/informatica/paulobarreto/KhazadPage.html>
317 tristate "Anubis cipher algorithm"
320 Anubis cipher algorithm.
322 Anubis is a variable key length cipher which can use keys from
323 128 bits to 320 bits in length. It was evaluated as a entrant
324 in the NESSIE competition.
327 <https://www.cosic.esat.kuleuven.ac.be/nessie/reports/>
328 <http://planeta.terra.com.br/informatica/paulobarreto/AnubisPage.html>
331 config CRYPTO_DEFLATE
332 tristate "Deflate compression algorithm"
337 This is the Deflate algorithm (RFC1951), specified for use in
338 IPSec with the IPCOMP protocol (RFC3173, RFC2394).
340 You will most probably want this if using IPSec.
342 config CRYPTO_MICHAEL_MIC
343 tristate "Michael MIC keyed digest algorithm"
346 Michael MIC is used for message integrity protection in TKIP
347 (IEEE 802.11i). This algorithm is required for TKIP, but it
348 should not be used for other purposes because of the weakness
352 tristate "CRC32c CRC algorithm"
356 Castagnoli, et al Cyclic Redundancy-Check Algorithm. Used
357 by iSCSI for header and data digests and by others.
358 See Castagnoli93. This implementation uses lib/libcrc32c.
359 Module will be crc32c.
362 tristate "Testing module"
363 depends on CRYPTO && m
365 Quick & dirty crypto test module.
367 source "drivers/crypto/Kconfig"