Kconfig 8.4 KB

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