Kconfig 14 KB

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