Kconfig 12 KB

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