Kconfig 10 KB

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