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 && ARCH_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 && ARCH_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 && ARCH_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"
135 Twofish cipher algorithm.
137 Twofish was submitted as an AES (Advanced Encryption Standard)
138 candidate cipher by researchers at CounterPane Systems. It is a
139 16 round block cipher supporting key sizes of 128, 192, and 256
143 <http://www.schneier.com/twofish.html>
145 config CRYPTO_SERPENT
146 tristate "Serpent cipher algorithm"
149 Serpent cipher algorithm, by Anderson, Biham & Knudsen.
151 Keys are allowed to be from 0 to 256 bits in length, in steps
152 of 8 bits. Also includes the 'Tnepres' algorithm, a reversed
153 variant of Serpent for compatibility with old kerneli code.
156 <http://www.cl.cam.ac.uk/~rja14/serpent.html>
159 tristate "AES cipher algorithms"
160 depends on CRYPTO && !(X86 || UML_X86)
162 AES cipher algorithms (FIPS-197). AES uses the Rijndael
165 Rijndael appears to be consistently a very good performer in
166 both hardware and software across a wide range of computing
167 environments regardless of its use in feedback or non-feedback
168 modes. Its key setup time is excellent, and its key agility is
169 good. Rijndael's very low memory requirements make it very well
170 suited for restricted-space environments, in which it also
171 demonstrates excellent performance. Rijndael's operations are
172 among the easiest to defend against power and timing attacks.
174 The AES specifies three key sizes: 128, 192 and 256 bits
176 See <http://csrc.nist.gov/CryptoToolkit/aes/> for more information.
178 config CRYPTO_AES_586
179 tristate "AES cipher algorithms (i586)"
180 depends on CRYPTO && ((X86 || UML_X86) && !64BIT)
182 AES cipher algorithms (FIPS-197). AES uses the Rijndael
185 Rijndael appears to be consistently a very good performer in
186 both hardware and software across a wide range of computing
187 environments regardless of its use in feedback or non-feedback
188 modes. Its key setup time is excellent, and its key agility is
189 good. Rijndael's very low memory requirements make it very well
190 suited for restricted-space environments, in which it also
191 demonstrates excellent performance. Rijndael's operations are
192 among the easiest to defend against power and timing attacks.
194 The AES specifies three key sizes: 128, 192 and 256 bits
196 See <http://csrc.nist.gov/encryption/aes/> for more information.
198 config CRYPTO_AES_X86_64
199 tristate "AES cipher algorithms (x86_64)"
200 depends on CRYPTO && ((X86 || UML_X86) && 64BIT)
202 AES cipher algorithms (FIPS-197). AES uses the Rijndael
205 Rijndael appears to be consistently a very good performer in
206 both hardware and software across a wide range of computing
207 environments regardless of its use in feedback or non-feedback
208 modes. Its key setup time is excellent, and its key agility is
209 good. Rijndael's very low memory requirements make it very well
210 suited for restricted-space environments, in which it also
211 demonstrates excellent performance. Rijndael's operations are
212 among the easiest to defend against power and timing attacks.
214 The AES specifies three key sizes: 128, 192 and 256 bits
216 See <http://csrc.nist.gov/encryption/aes/> for more information.
219 tristate "CAST5 (CAST-128) cipher algorithm"
222 The CAST5 encryption algorithm (synonymous with CAST-128) is
223 described in RFC2144.
226 tristate "CAST6 (CAST-256) cipher algorithm"
229 The CAST6 encryption algorithm (synonymous with CAST-256) is
230 described in RFC2612.
233 tristate "TEA, XTEA and XETA cipher algorithms"
236 TEA cipher algorithm.
238 Tiny Encryption Algorithm is a simple cipher that uses
239 many rounds for security. It is very fast and uses
242 Xtendend Tiny Encryption Algorithm is a modification to
243 the TEA algorithm to address a potential key weakness
244 in the TEA algorithm.
246 Xtendend Encryption Tiny Algorithm is a mis-implementation
247 of the XTEA algorithm for compatibility purposes.
250 tristate "ARC4 cipher algorithm"
253 ARC4 cipher algorithm.
255 ARC4 is a stream cipher using keys ranging from 8 bits to 2048
256 bits in length. This algorithm is required for driver-based
257 WEP, but it should not be for other purposes because of the
258 weakness of the algorithm.
261 tristate "Khazad cipher algorithm"
264 Khazad cipher algorithm.
266 Khazad was a finalist in the initial NESSIE competition. It is
267 an algorithm optimized for 64-bit processors with good performance
268 on 32-bit processors. Khazad uses an 128 bit key size.
271 <http://planeta.terra.com.br/informatica/paulobarreto/KhazadPage.html>
274 tristate "Anubis cipher algorithm"
277 Anubis cipher algorithm.
279 Anubis is a variable key length cipher which can use keys from
280 128 bits to 320 bits in length. It was evaluated as a entrant
281 in the NESSIE competition.
284 <https://www.cosic.esat.kuleuven.ac.be/nessie/reports/>
285 <http://planeta.terra.com.br/informatica/paulobarreto/AnubisPage.html>
288 config CRYPTO_DEFLATE
289 tristate "Deflate compression algorithm"
294 This is the Deflate algorithm (RFC1951), specified for use in
295 IPSec with the IPCOMP protocol (RFC3173, RFC2394).
297 You will most probably want this if using IPSec.
299 config CRYPTO_MICHAEL_MIC
300 tristate "Michael MIC keyed digest algorithm"
303 Michael MIC is used for message integrity protection in TKIP
304 (IEEE 802.11i). This algorithm is required for TKIP, but it
305 should not be used for other purposes because of the weakness
309 tristate "CRC32c CRC algorithm"
313 Castagnoli, et al Cyclic Redundancy-Check Algorithm. Used
314 by iSCSI for header and data digests and by others.
315 See Castagnoli93. This implementation uses lib/libcrc32c.
316 Module will be crc32c.
319 tristate "Testing module"
322 Quick & dirty crypto test module.
324 source "drivers/crypto/Kconfig"