Kconfig 16 KB

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