Kconfig 13 KB

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