Kconfig 13 KB

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