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"
31 Create default cryptographic template instantiations such as
35 tristate "HMAC support"
39 HMAC: Keyed-Hashing for Message Authentication (RFC2104).
40 This is required for IPSec.
43 tristate "XCBC support"
44 depends on EXPERIMENTAL
48 XCBC: Keyed-Hashing with encryption algorithm
49 http://www.ietf.org/rfc/rfc3566.txt
50 http://csrc.nist.gov/encryption/modes/proposedmodes/
51 xcbc-mac/xcbc-mac-spec.pdf
54 tristate "Null algorithms"
57 These are 'Null' algorithms, used by IPsec, which do nothing.
60 tristate "MD4 digest algorithm"
63 MD4 message digest algorithm (RFC1320).
66 tristate "MD5 digest algorithm"
69 MD5 message digest algorithm (RFC1321).
72 tristate "SHA1 digest algorithm"
75 SHA-1 secure hash standard (FIPS 180-1/DFIPS 180-2).
78 tristate "SHA256 digest algorithm"
81 SHA256 secure hash standard (DFIPS 180-2).
83 This version of SHA implements a 256 bit hash with 128 bits of
84 security against collision attacks.
87 tristate "SHA384 and SHA512 digest algorithms"
90 SHA512 secure hash standard (DFIPS 180-2).
92 This version of SHA implements a 512 bit hash with 256 bits of
93 security against collision attacks.
95 This code also includes SHA-384, a 384 bit hash with 192 bits
96 of security against collision attacks.
99 tristate "Whirlpool digest algorithms"
102 Whirlpool hash algorithm 512, 384 and 256-bit hashes
104 Whirlpool-512 is part of the NESSIE cryptographic primitives.
105 Whirlpool will be part of the ISO/IEC 10118-3:2003(E) standard
108 <http://planeta.terra.com.br/informatica/paulobarreto/WhirlpoolPage.html>
111 tristate "Tiger digest algorithms"
114 Tiger hash algorithm 192, 160 and 128-bit hashes
116 Tiger is a hash function optimized for 64-bit processors while
117 still having decent performance on 32-bit processors.
118 Tiger was developed by Ross Anderson and Eli Biham.
121 <http://www.cs.technion.ac.il/~biham/Reports/Tiger/>.
123 config CRYPTO_GF128MUL
124 tristate "GF(2^128) multiplication functions (EXPERIMENTAL)"
125 depends on EXPERIMENTAL
127 Efficient table driven implementation of multiplications in the
128 field GF(2^128). This is needed by some cypher modes. This
129 option will be selected automatically if you select such a
130 cipher mode. Only select this option by hand if you expect to load
131 an external module that requires these functions.
134 tristate "ECB support"
135 select CRYPTO_BLKCIPHER
136 select CRYPTO_MANAGER
139 ECB: Electronic CodeBook mode
140 This is the simplest block cipher algorithm. It simply encrypts
141 the input block by block.
144 tristate "CBC support"
145 select CRYPTO_BLKCIPHER
146 select CRYPTO_MANAGER
149 CBC: Cipher Block Chaining mode
150 This block cipher algorithm is required for IPSec.
153 tristate "LRW support (EXPERIMENTAL)"
154 depends on EXPERIMENTAL
155 select CRYPTO_BLKCIPHER
156 select CRYPTO_MANAGER
157 select CRYPTO_GF128MUL
159 LRW: Liskov Rivest Wagner, a tweakable, non malleable, non movable
160 narrow block cipher mode for dm-crypt. Use it with cipher
161 specification string aes-lrw-benbi, the key must be 256, 320 or 384.
162 The first 128, 192 or 256 bits in the key are used for AES and the
163 rest is used to tie each cipher block to its logical position.
166 tristate "DES and Triple DES EDE cipher algorithms"
169 DES cipher algorithm (FIPS 46-2), and Triple DES EDE (FIPS 46-3).
171 config CRYPTO_BLOWFISH
172 tristate "Blowfish cipher algorithm"
175 Blowfish cipher algorithm, by Bruce Schneier.
177 This is a variable key length cipher which can use keys from 32
178 bits to 448 bits in length. It's fast, simple and specifically
179 designed for use on "large microprocessors".
182 <http://www.schneier.com/blowfish.html>
184 config CRYPTO_TWOFISH
185 tristate "Twofish cipher algorithm"
187 select CRYPTO_TWOFISH_COMMON
189 Twofish cipher algorithm.
191 Twofish was submitted as an AES (Advanced Encryption Standard)
192 candidate cipher by researchers at CounterPane Systems. It is a
193 16 round block cipher supporting key sizes of 128, 192, and 256
197 <http://www.schneier.com/twofish.html>
199 config CRYPTO_TWOFISH_COMMON
202 Common parts of the Twofish cipher algorithm shared by the
203 generic c and the assembler implementations.
205 config CRYPTO_TWOFISH_586
206 tristate "Twofish cipher algorithms (i586)"
207 depends on (X86 || UML_X86) && !64BIT
209 select CRYPTO_TWOFISH_COMMON
211 Twofish cipher algorithm.
213 Twofish was submitted as an AES (Advanced Encryption Standard)
214 candidate cipher by researchers at CounterPane Systems. It is a
215 16 round block cipher supporting key sizes of 128, 192, and 256
219 <http://www.schneier.com/twofish.html>
221 config CRYPTO_TWOFISH_X86_64
222 tristate "Twofish cipher algorithm (x86_64)"
223 depends on (X86 || UML_X86) && 64BIT
225 select CRYPTO_TWOFISH_COMMON
227 Twofish cipher algorithm (x86_64).
229 Twofish was submitted as an AES (Advanced Encryption Standard)
230 candidate cipher by researchers at CounterPane Systems. It is a
231 16 round block cipher supporting key sizes of 128, 192, and 256
235 <http://www.schneier.com/twofish.html>
237 config CRYPTO_SERPENT
238 tristate "Serpent cipher algorithm"
241 Serpent cipher algorithm, by Anderson, Biham & Knudsen.
243 Keys are allowed to be from 0 to 256 bits in length, in steps
244 of 8 bits. Also includes the 'Tnepres' algorithm, a reversed
245 variant of Serpent for compatibility with old kerneli code.
248 <http://www.cl.cam.ac.uk/~rja14/serpent.html>
251 tristate "AES cipher algorithms"
254 AES cipher algorithms (FIPS-197). AES uses the Rijndael
257 Rijndael appears to be consistently a very good performer in
258 both hardware and software across a wide range of computing
259 environments regardless of its use in feedback or non-feedback
260 modes. Its key setup time is excellent, and its key agility is
261 good. Rijndael's very low memory requirements make it very well
262 suited for restricted-space environments, in which it also
263 demonstrates excellent performance. Rijndael's operations are
264 among the easiest to defend against power and timing attacks.
266 The AES specifies three key sizes: 128, 192 and 256 bits
268 See <http://csrc.nist.gov/CryptoToolkit/aes/> for more information.
270 config CRYPTO_AES_586
271 tristate "AES cipher algorithms (i586)"
272 depends on (X86 || UML_X86) && !64BIT
275 AES cipher algorithms (FIPS-197). AES uses the Rijndael
278 Rijndael appears to be consistently a very good performer in
279 both hardware and software across a wide range of computing
280 environments regardless of its use in feedback or non-feedback
281 modes. Its key setup time is excellent, and its key agility is
282 good. Rijndael's very low memory requirements make it very well
283 suited for restricted-space environments, in which it also
284 demonstrates excellent performance. Rijndael's operations are
285 among the easiest to defend against power and timing attacks.
287 The AES specifies three key sizes: 128, 192 and 256 bits
289 See <http://csrc.nist.gov/encryption/aes/> for more information.
291 config CRYPTO_AES_X86_64
292 tristate "AES cipher algorithms (x86_64)"
293 depends on (X86 || UML_X86) && 64BIT
296 AES cipher algorithms (FIPS-197). AES uses the Rijndael
299 Rijndael appears to be consistently a very good performer in
300 both hardware and software across a wide range of computing
301 environments regardless of its use in feedback or non-feedback
302 modes. Its key setup time is excellent, and its key agility is
303 good. Rijndael's very low memory requirements make it very well
304 suited for restricted-space environments, in which it also
305 demonstrates excellent performance. Rijndael's operations are
306 among the easiest to defend against power and timing attacks.
308 The AES specifies three key sizes: 128, 192 and 256 bits
310 See <http://csrc.nist.gov/encryption/aes/> for more information.
313 tristate "CAST5 (CAST-128) cipher algorithm"
316 The CAST5 encryption algorithm (synonymous with CAST-128) is
317 described in RFC2144.
320 tristate "CAST6 (CAST-256) cipher algorithm"
323 The CAST6 encryption algorithm (synonymous with CAST-256) is
324 described in RFC2612.
327 tristate "TEA, XTEA and XETA cipher algorithms"
330 TEA cipher algorithm.
332 Tiny Encryption Algorithm is a simple cipher that uses
333 many rounds for security. It is very fast and uses
336 Xtendend Tiny Encryption Algorithm is a modification to
337 the TEA algorithm to address a potential key weakness
338 in the TEA algorithm.
340 Xtendend Encryption Tiny Algorithm is a mis-implementation
341 of the XTEA algorithm for compatibility purposes.
344 tristate "ARC4 cipher algorithm"
347 ARC4 cipher algorithm.
349 ARC4 is a stream cipher using keys ranging from 8 bits to 2048
350 bits in length. This algorithm is required for driver-based
351 WEP, but it should not be for other purposes because of the
352 weakness of the algorithm.
355 tristate "Khazad cipher algorithm"
358 Khazad cipher algorithm.
360 Khazad was a finalist in the initial NESSIE competition. It is
361 an algorithm optimized for 64-bit processors with good performance
362 on 32-bit processors. Khazad uses an 128 bit key size.
365 <http://planeta.terra.com.br/informatica/paulobarreto/KhazadPage.html>
368 tristate "Anubis cipher algorithm"
371 Anubis cipher algorithm.
373 Anubis is a variable key length cipher which can use keys from
374 128 bits to 320 bits in length. It was evaluated as a entrant
375 in the NESSIE competition.
378 <https://www.cosic.esat.kuleuven.ac.be/nessie/reports/>
379 <http://planeta.terra.com.br/informatica/paulobarreto/AnubisPage.html>
382 config CRYPTO_DEFLATE
383 tristate "Deflate compression algorithm"
388 This is the Deflate algorithm (RFC1951), specified for use in
389 IPSec with the IPCOMP protocol (RFC3173, RFC2394).
391 You will most probably want this if using IPSec.
393 config CRYPTO_MICHAEL_MIC
394 tristate "Michael MIC keyed digest algorithm"
397 Michael MIC is used for message integrity protection in TKIP
398 (IEEE 802.11i). This algorithm is required for TKIP, but it
399 should not be used for other purposes because of the weakness
403 tristate "CRC32c CRC algorithm"
407 Castagnoli, et al Cyclic Redundancy-Check Algorithm. Used
408 by iSCSI for header and data digests and by others.
409 See Castagnoli93. This implementation uses lib/libcrc32c.
410 Module will be crc32c.
413 tristate "Testing module"
417 Quick & dirty crypto test module.
419 source "drivers/crypto/Kconfig"