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_SERPENT
154 tristate "Serpent cipher algorithm"
157 Serpent cipher algorithm, by Anderson, Biham & Knudsen.
159 Keys are allowed to be from 0 to 256 bits in length, in steps
160 of 8 bits. Also includes the 'Tnepres' algorithm, a reversed
161 variant of Serpent for compatibility with old kerneli code.
164 <http://www.cl.cam.ac.uk/~rja14/serpent.html>
167 tristate "AES cipher algorithms"
170 AES cipher algorithms (FIPS-197). AES uses the Rijndael
173 Rijndael appears to be consistently a very good performer in
174 both hardware and software across a wide range of computing
175 environments regardless of its use in feedback or non-feedback
176 modes. Its key setup time is excellent, and its key agility is
177 good. Rijndael's very low memory requirements make it very well
178 suited for restricted-space environments, in which it also
179 demonstrates excellent performance. Rijndael's operations are
180 among the easiest to defend against power and timing attacks.
182 The AES specifies three key sizes: 128, 192 and 256 bits
184 See <http://csrc.nist.gov/CryptoToolkit/aes/> for more information.
186 config CRYPTO_AES_586
187 tristate "AES cipher algorithms (i586)"
188 depends on CRYPTO && ((X86 || UML_X86) && !64BIT)
190 AES cipher algorithms (FIPS-197). AES uses the Rijndael
193 Rijndael appears to be consistently a very good performer in
194 both hardware and software across a wide range of computing
195 environments regardless of its use in feedback or non-feedback
196 modes. Its key setup time is excellent, and its key agility is
197 good. Rijndael's very low memory requirements make it very well
198 suited for restricted-space environments, in which it also
199 demonstrates excellent performance. Rijndael's operations are
200 among the easiest to defend against power and timing attacks.
202 The AES specifies three key sizes: 128, 192 and 256 bits
204 See <http://csrc.nist.gov/encryption/aes/> for more information.
206 config CRYPTO_AES_X86_64
207 tristate "AES cipher algorithms (x86_64)"
208 depends on CRYPTO && ((X86 || UML_X86) && 64BIT)
210 AES cipher algorithms (FIPS-197). AES uses the Rijndael
213 Rijndael appears to be consistently a very good performer in
214 both hardware and software across a wide range of computing
215 environments regardless of its use in feedback or non-feedback
216 modes. Its key setup time is excellent, and its key agility is
217 good. Rijndael's very low memory requirements make it very well
218 suited for restricted-space environments, in which it also
219 demonstrates excellent performance. Rijndael's operations are
220 among the easiest to defend against power and timing attacks.
222 The AES specifies three key sizes: 128, 192 and 256 bits
224 See <http://csrc.nist.gov/encryption/aes/> for more information.
226 config CRYPTO_AES_S390
227 tristate "AES cipher algorithms (s390)"
228 depends on CRYPTO && S390
230 This is the s390 hardware accelerated implementation of the
231 AES cipher algorithms (FIPS-197). AES uses the Rijndael
234 Rijndael appears to be consistently a very good performer in
235 both hardware and software across a wide range of computing
236 environments regardless of its use in feedback or non-feedback
237 modes. Its key setup time is excellent, and its key agility is
238 good. Rijndael's very low memory requirements make it very well
239 suited for restricted-space environments, in which it also
240 demonstrates excellent performance. Rijndael's operations are
241 among the easiest to defend against power and timing attacks.
243 On s390 the System z9-109 currently only supports the key size
247 tristate "CAST5 (CAST-128) cipher algorithm"
250 The CAST5 encryption algorithm (synonymous with CAST-128) is
251 described in RFC2144.
254 tristate "CAST6 (CAST-256) cipher algorithm"
257 The CAST6 encryption algorithm (synonymous with CAST-256) is
258 described in RFC2612.
261 tristate "TEA, XTEA and XETA cipher algorithms"
264 TEA cipher algorithm.
266 Tiny Encryption Algorithm is a simple cipher that uses
267 many rounds for security. It is very fast and uses
270 Xtendend Tiny Encryption Algorithm is a modification to
271 the TEA algorithm to address a potential key weakness
272 in the TEA algorithm.
274 Xtendend Encryption Tiny Algorithm is a mis-implementation
275 of the XTEA algorithm for compatibility purposes.
278 tristate "ARC4 cipher algorithm"
281 ARC4 cipher algorithm.
283 ARC4 is a stream cipher using keys ranging from 8 bits to 2048
284 bits in length. This algorithm is required for driver-based
285 WEP, but it should not be for other purposes because of the
286 weakness of the algorithm.
289 tristate "Khazad cipher algorithm"
292 Khazad cipher algorithm.
294 Khazad was a finalist in the initial NESSIE competition. It is
295 an algorithm optimized for 64-bit processors with good performance
296 on 32-bit processors. Khazad uses an 128 bit key size.
299 <http://planeta.terra.com.br/informatica/paulobarreto/KhazadPage.html>
302 tristate "Anubis cipher algorithm"
305 Anubis cipher algorithm.
307 Anubis is a variable key length cipher which can use keys from
308 128 bits to 320 bits in length. It was evaluated as a entrant
309 in the NESSIE competition.
312 <https://www.cosic.esat.kuleuven.ac.be/nessie/reports/>
313 <http://planeta.terra.com.br/informatica/paulobarreto/AnubisPage.html>
316 config CRYPTO_DEFLATE
317 tristate "Deflate compression algorithm"
322 This is the Deflate algorithm (RFC1951), specified for use in
323 IPSec with the IPCOMP protocol (RFC3173, RFC2394).
325 You will most probably want this if using IPSec.
327 config CRYPTO_MICHAEL_MIC
328 tristate "Michael MIC keyed digest algorithm"
331 Michael MIC is used for message integrity protection in TKIP
332 (IEEE 802.11i). This algorithm is required for TKIP, but it
333 should not be used for other purposes because of the weakness
337 tristate "CRC32c CRC algorithm"
341 Castagnoli, et al Cyclic Redundancy-Check Algorithm. Used
342 by iSCSI for header and data digests and by others.
343 See Castagnoli93. This implementation uses lib/libcrc32c.
344 Module will be crc32c.
347 tristate "Testing module"
348 depends on CRYPTO && m
350 Quick & dirty crypto test module.
352 source "drivers/crypto/Kconfig"