Kconfig 14 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251252253254255256257258259260261262263264265266267268269270271272273274275276277278279280281282283284285286287288289290291292293294295296297298299300301302303304305306307308309310311312313314315316317318319320321322323324325326327328329330331332333334335336337338339340341342343344345346347348349350351352353354355356357358359360361362363364365366367368369370371372373374375376377378379380381382383384385386387388389390391392393394395396397398399400401402403404405406407408409410411412413414415416417418419420421422423424425426427428429430431432433434435436437438439440441442443444445446447448449450451452453454455456457458459460461462463464465466467468469470471472
  1. #
  2. # Cryptographic API Configuration
  3. #
  4. menu "Cryptographic options"
  5. config CRYPTO
  6. bool "Cryptographic API"
  7. help
  8. This option provides the core Cryptographic API.
  9. if CRYPTO
  10. config CRYPTO_ALGAPI
  11. tristate
  12. help
  13. This option provides the API for cryptographic algorithms.
  14. config CRYPTO_BLKCIPHER
  15. tristate
  16. select CRYPTO_ALGAPI
  17. config CRYPTO_HASH
  18. tristate
  19. select CRYPTO_ALGAPI
  20. config CRYPTO_MANAGER
  21. tristate "Cryptographic algorithm manager"
  22. select CRYPTO_ALGAPI
  23. help
  24. Create default cryptographic template instantiations such as
  25. cbc(aes).
  26. config CRYPTO_HMAC
  27. tristate "HMAC support"
  28. select CRYPTO_HASH
  29. select CRYPTO_MANAGER
  30. help
  31. HMAC: Keyed-Hashing for Message Authentication (RFC2104).
  32. This is required for IPSec.
  33. config CRYPTO_XCBC
  34. tristate "XCBC support"
  35. depends on EXPERIMENTAL
  36. select CRYPTO_HASH
  37. select CRYPTO_MANAGER
  38. help
  39. XCBC: Keyed-Hashing with encryption algorithm
  40. http://www.ietf.org/rfc/rfc3566.txt
  41. http://csrc.nist.gov/encryption/modes/proposedmodes/
  42. xcbc-mac/xcbc-mac-spec.pdf
  43. config CRYPTO_NULL
  44. tristate "Null algorithms"
  45. select CRYPTO_ALGAPI
  46. help
  47. These are 'Null' algorithms, used by IPsec, which do nothing.
  48. config CRYPTO_MD4
  49. tristate "MD4 digest algorithm"
  50. select CRYPTO_ALGAPI
  51. help
  52. MD4 message digest algorithm (RFC1320).
  53. config CRYPTO_MD5
  54. tristate "MD5 digest algorithm"
  55. select CRYPTO_ALGAPI
  56. help
  57. MD5 message digest algorithm (RFC1321).
  58. config CRYPTO_SHA1
  59. tristate "SHA1 digest algorithm"
  60. select CRYPTO_ALGAPI
  61. help
  62. SHA-1 secure hash standard (FIPS 180-1/DFIPS 180-2).
  63. config CRYPTO_SHA1_S390
  64. tristate "SHA1 digest algorithm (s390)"
  65. depends on S390
  66. select CRYPTO_ALGAPI
  67. help
  68. This is the s390 hardware accelerated implementation of the
  69. SHA-1 secure hash standard (FIPS 180-1/DFIPS 180-2).
  70. config CRYPTO_SHA256
  71. tristate "SHA256 digest algorithm"
  72. select CRYPTO_ALGAPI
  73. help
  74. SHA256 secure hash standard (DFIPS 180-2).
  75. This version of SHA implements a 256 bit hash with 128 bits of
  76. security against collision attacks.
  77. config CRYPTO_SHA256_S390
  78. tristate "SHA256 digest algorithm (s390)"
  79. depends on S390
  80. select CRYPTO_ALGAPI
  81. help
  82. This is the s390 hardware accelerated implementation of the
  83. SHA256 secure hash standard (DFIPS 180-2).
  84. This version of SHA implements a 256 bit hash with 128 bits of
  85. security against collision attacks.
  86. config CRYPTO_SHA512
  87. tristate "SHA384 and SHA512 digest algorithms"
  88. select CRYPTO_ALGAPI
  89. help
  90. SHA512 secure hash standard (DFIPS 180-2).
  91. This version of SHA implements a 512 bit hash with 256 bits of
  92. security against collision attacks.
  93. This code also includes SHA-384, a 384 bit hash with 192 bits
  94. of security against collision attacks.
  95. config CRYPTO_WP512
  96. tristate "Whirlpool digest algorithms"
  97. select CRYPTO_ALGAPI
  98. help
  99. Whirlpool hash algorithm 512, 384 and 256-bit hashes
  100. Whirlpool-512 is part of the NESSIE cryptographic primitives.
  101. Whirlpool will be part of the ISO/IEC 10118-3:2003(E) standard
  102. See also:
  103. <http://planeta.terra.com.br/informatica/paulobarreto/WhirlpoolPage.html>
  104. config CRYPTO_TGR192
  105. tristate "Tiger digest algorithms"
  106. select CRYPTO_ALGAPI
  107. help
  108. Tiger hash algorithm 192, 160 and 128-bit hashes
  109. Tiger is a hash function optimized for 64-bit processors while
  110. still having decent performance on 32-bit processors.
  111. Tiger was developed by Ross Anderson and Eli Biham.
  112. See also:
  113. <http://www.cs.technion.ac.il/~biham/Reports/Tiger/>.
  114. config CRYPTO_GF128MUL
  115. tristate "GF(2^128) multiplication functions (EXPERIMENTAL)"
  116. depends on EXPERIMENTAL
  117. help
  118. Efficient table driven implementation of multiplications in the
  119. field GF(2^128). This is needed by some cypher modes. This
  120. option will be selected automatically if you select such a
  121. cipher mode. Only select this option by hand if you expect to load
  122. an external module that requires these functions.
  123. config CRYPTO_ECB
  124. tristate "ECB support"
  125. select CRYPTO_BLKCIPHER
  126. select CRYPTO_MANAGER
  127. default m
  128. help
  129. ECB: Electronic CodeBook mode
  130. This is the simplest block cipher algorithm. It simply encrypts
  131. the input block by block.
  132. config CRYPTO_CBC
  133. tristate "CBC support"
  134. select CRYPTO_BLKCIPHER
  135. select CRYPTO_MANAGER
  136. default m
  137. help
  138. CBC: Cipher Block Chaining mode
  139. This block cipher algorithm is required for IPSec.
  140. config CRYPTO_LRW
  141. tristate "LRW support (EXPERIMENTAL)"
  142. depends on EXPERIMENTAL
  143. select CRYPTO_BLKCIPHER
  144. select CRYPTO_MANAGER
  145. select CRYPTO_GF128MUL
  146. help
  147. LRW: Liskov Rivest Wagner, a tweakable, non malleable, non movable
  148. narrow block cipher mode for dm-crypt. Use it with cipher
  149. specification string aes-lrw-benbi, the key must be 256, 320 or 384.
  150. The first 128, 192 or 256 bits in the key are used for AES and the
  151. rest is used to tie each cipher block to its logical position.
  152. config CRYPTO_DES
  153. tristate "DES and Triple DES EDE cipher algorithms"
  154. select CRYPTO_ALGAPI
  155. help
  156. DES cipher algorithm (FIPS 46-2), and Triple DES EDE (FIPS 46-3).
  157. config CRYPTO_DES_S390
  158. tristate "DES and Triple DES cipher algorithms (s390)"
  159. depends on S390
  160. select CRYPTO_ALGAPI
  161. select CRYPTO_BLKCIPHER
  162. help
  163. DES cipher algorithm (FIPS 46-2), and Triple DES EDE (FIPS 46-3).
  164. config CRYPTO_BLOWFISH
  165. tristate "Blowfish cipher algorithm"
  166. select CRYPTO_ALGAPI
  167. help
  168. Blowfish cipher algorithm, by Bruce Schneier.
  169. This is a variable key length cipher which can use keys from 32
  170. bits to 448 bits in length. It's fast, simple and specifically
  171. designed for use on "large microprocessors".
  172. See also:
  173. <http://www.schneier.com/blowfish.html>
  174. config CRYPTO_TWOFISH
  175. tristate "Twofish cipher algorithm"
  176. select CRYPTO_ALGAPI
  177. select CRYPTO_TWOFISH_COMMON
  178. help
  179. Twofish cipher algorithm.
  180. Twofish was submitted as an AES (Advanced Encryption Standard)
  181. candidate cipher by researchers at CounterPane Systems. It is a
  182. 16 round block cipher supporting key sizes of 128, 192, and 256
  183. bits.
  184. See also:
  185. <http://www.schneier.com/twofish.html>
  186. config CRYPTO_TWOFISH_COMMON
  187. tristate
  188. help
  189. Common parts of the Twofish cipher algorithm shared by the
  190. generic c and the assembler implementations.
  191. config CRYPTO_TWOFISH_586
  192. tristate "Twofish cipher algorithms (i586)"
  193. depends on (X86 || UML_X86) && !64BIT
  194. select CRYPTO_ALGAPI
  195. select CRYPTO_TWOFISH_COMMON
  196. help
  197. Twofish cipher algorithm.
  198. Twofish was submitted as an AES (Advanced Encryption Standard)
  199. candidate cipher by researchers at CounterPane Systems. It is a
  200. 16 round block cipher supporting key sizes of 128, 192, and 256
  201. bits.
  202. See also:
  203. <http://www.schneier.com/twofish.html>
  204. config CRYPTO_TWOFISH_X86_64
  205. tristate "Twofish cipher algorithm (x86_64)"
  206. depends on (X86 || UML_X86) && 64BIT
  207. select CRYPTO_ALGAPI
  208. select CRYPTO_TWOFISH_COMMON
  209. help
  210. Twofish cipher algorithm (x86_64).
  211. Twofish was submitted as an AES (Advanced Encryption Standard)
  212. candidate cipher by researchers at CounterPane Systems. It is a
  213. 16 round block cipher supporting key sizes of 128, 192, and 256
  214. bits.
  215. See also:
  216. <http://www.schneier.com/twofish.html>
  217. config CRYPTO_SERPENT
  218. tristate "Serpent cipher algorithm"
  219. select CRYPTO_ALGAPI
  220. help
  221. Serpent cipher algorithm, by Anderson, Biham & Knudsen.
  222. Keys are allowed to be from 0 to 256 bits in length, in steps
  223. of 8 bits. Also includes the 'Tnepres' algorithm, a reversed
  224. variant of Serpent for compatibility with old kerneli code.
  225. See also:
  226. <http://www.cl.cam.ac.uk/~rja14/serpent.html>
  227. config CRYPTO_AES
  228. tristate "AES cipher algorithms"
  229. select CRYPTO_ALGAPI
  230. help
  231. AES cipher algorithms (FIPS-197). AES uses the Rijndael
  232. algorithm.
  233. Rijndael appears to be consistently a very good performer in
  234. both hardware and software across a wide range of computing
  235. environments regardless of its use in feedback or non-feedback
  236. modes. Its key setup time is excellent, and its key agility is
  237. good. Rijndael's very low memory requirements make it very well
  238. suited for restricted-space environments, in which it also
  239. demonstrates excellent performance. Rijndael's operations are
  240. among the easiest to defend against power and timing attacks.
  241. The AES specifies three key sizes: 128, 192 and 256 bits
  242. See <http://csrc.nist.gov/CryptoToolkit/aes/> for more information.
  243. config CRYPTO_AES_586
  244. tristate "AES cipher algorithms (i586)"
  245. depends on (X86 || UML_X86) && !64BIT
  246. select CRYPTO_ALGAPI
  247. help
  248. AES cipher algorithms (FIPS-197). AES uses the Rijndael
  249. algorithm.
  250. Rijndael appears to be consistently a very good performer in
  251. both hardware and software across a wide range of computing
  252. environments regardless of its use in feedback or non-feedback
  253. modes. Its key setup time is excellent, and its key agility is
  254. good. Rijndael's very low memory requirements make it very well
  255. suited for restricted-space environments, in which it also
  256. demonstrates excellent performance. Rijndael's operations are
  257. among the easiest to defend against power and timing attacks.
  258. The AES specifies three key sizes: 128, 192 and 256 bits
  259. See <http://csrc.nist.gov/encryption/aes/> for more information.
  260. config CRYPTO_AES_X86_64
  261. tristate "AES cipher algorithms (x86_64)"
  262. depends on (X86 || UML_X86) && 64BIT
  263. select CRYPTO_ALGAPI
  264. help
  265. AES cipher algorithms (FIPS-197). AES uses the Rijndael
  266. algorithm.
  267. Rijndael appears to be consistently a very good performer in
  268. both hardware and software across a wide range of computing
  269. environments regardless of its use in feedback or non-feedback
  270. modes. Its key setup time is excellent, and its key agility is
  271. good. Rijndael's very low memory requirements make it very well
  272. suited for restricted-space environments, in which it also
  273. demonstrates excellent performance. Rijndael's operations are
  274. among the easiest to defend against power and timing attacks.
  275. The AES specifies three key sizes: 128, 192 and 256 bits
  276. See <http://csrc.nist.gov/encryption/aes/> for more information.
  277. config CRYPTO_AES_S390
  278. tristate "AES cipher algorithms (s390)"
  279. depends on S390
  280. select CRYPTO_ALGAPI
  281. select CRYPTO_BLKCIPHER
  282. help
  283. This is the s390 hardware accelerated implementation of the
  284. AES cipher algorithms (FIPS-197). AES uses the Rijndael
  285. algorithm.
  286. Rijndael appears to be consistently a very good performer in
  287. both hardware and software across a wide range of computing
  288. environments regardless of its use in feedback or non-feedback
  289. modes. Its key setup time is excellent, and its key agility is
  290. good. Rijndael's very low memory requirements make it very well
  291. suited for restricted-space environments, in which it also
  292. demonstrates excellent performance. Rijndael's operations are
  293. among the easiest to defend against power and timing attacks.
  294. On s390 the System z9-109 currently only supports the key size
  295. of 128 bit.
  296. config CRYPTO_CAST5
  297. tristate "CAST5 (CAST-128) cipher algorithm"
  298. select CRYPTO_ALGAPI
  299. help
  300. The CAST5 encryption algorithm (synonymous with CAST-128) is
  301. described in RFC2144.
  302. config CRYPTO_CAST6
  303. tristate "CAST6 (CAST-256) cipher algorithm"
  304. select CRYPTO_ALGAPI
  305. help
  306. The CAST6 encryption algorithm (synonymous with CAST-256) is
  307. described in RFC2612.
  308. config CRYPTO_TEA
  309. tristate "TEA, XTEA and XETA cipher algorithms"
  310. select CRYPTO_ALGAPI
  311. help
  312. TEA cipher algorithm.
  313. Tiny Encryption Algorithm is a simple cipher that uses
  314. many rounds for security. It is very fast and uses
  315. little memory.
  316. Xtendend Tiny Encryption Algorithm is a modification to
  317. the TEA algorithm to address a potential key weakness
  318. in the TEA algorithm.
  319. Xtendend Encryption Tiny Algorithm is a mis-implementation
  320. of the XTEA algorithm for compatibility purposes.
  321. config CRYPTO_ARC4
  322. tristate "ARC4 cipher algorithm"
  323. select CRYPTO_ALGAPI
  324. help
  325. ARC4 cipher algorithm.
  326. ARC4 is a stream cipher using keys ranging from 8 bits to 2048
  327. bits in length. This algorithm is required for driver-based
  328. WEP, but it should not be for other purposes because of the
  329. weakness of the algorithm.
  330. config CRYPTO_KHAZAD
  331. tristate "Khazad cipher algorithm"
  332. select CRYPTO_ALGAPI
  333. help
  334. Khazad cipher algorithm.
  335. Khazad was a finalist in the initial NESSIE competition. It is
  336. an algorithm optimized for 64-bit processors with good performance
  337. on 32-bit processors. Khazad uses an 128 bit key size.
  338. See also:
  339. <http://planeta.terra.com.br/informatica/paulobarreto/KhazadPage.html>
  340. config CRYPTO_ANUBIS
  341. tristate "Anubis cipher algorithm"
  342. select CRYPTO_ALGAPI
  343. help
  344. Anubis cipher algorithm.
  345. Anubis is a variable key length cipher which can use keys from
  346. 128 bits to 320 bits in length. It was evaluated as a entrant
  347. in the NESSIE competition.
  348. See also:
  349. <https://www.cosic.esat.kuleuven.ac.be/nessie/reports/>
  350. <http://planeta.terra.com.br/informatica/paulobarreto/AnubisPage.html>
  351. config CRYPTO_DEFLATE
  352. tristate "Deflate compression algorithm"
  353. select CRYPTO_ALGAPI
  354. select ZLIB_INFLATE
  355. select ZLIB_DEFLATE
  356. help
  357. This is the Deflate algorithm (RFC1951), specified for use in
  358. IPSec with the IPCOMP protocol (RFC3173, RFC2394).
  359. You will most probably want this if using IPSec.
  360. config CRYPTO_MICHAEL_MIC
  361. tristate "Michael MIC keyed digest algorithm"
  362. select CRYPTO_ALGAPI
  363. help
  364. Michael MIC is used for message integrity protection in TKIP
  365. (IEEE 802.11i). This algorithm is required for TKIP, but it
  366. should not be used for other purposes because of the weakness
  367. of the algorithm.
  368. config CRYPTO_CRC32C
  369. tristate "CRC32c CRC algorithm"
  370. select CRYPTO_ALGAPI
  371. select LIBCRC32C
  372. help
  373. Castagnoli, et al Cyclic Redundancy-Check Algorithm. Used
  374. by iSCSI for header and data digests and by others.
  375. See Castagnoli93. This implementation uses lib/libcrc32c.
  376. Module will be crc32c.
  377. config CRYPTO_TEST
  378. tristate "Testing module"
  379. depends on m
  380. select CRYPTO_ALGAPI
  381. help
  382. Quick & dirty crypto test module.
  383. source "drivers/crypto/Kconfig"
  384. endif # if CRYPTO
  385. endmenu