Kconfig 12 KB

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