Kconfig 22 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251252253254255256257258259260261262263264265266267268269270271272273274275276277278279280281282283284285286287288289290291292293294295296297298299300301302303304305306307308309310311312313314315316317318319320321322323324325326327328329330331332333334335336337338339340341342343344345346347348349350351352353354355356357358359360361362363364365366367368369370371372373374375376377378379380381382383384385386387388389390391392393394395396397398399400401402403404405406407408409410411412413414415416417418419420421422423424425426427428429430431432433434435436437438439440441442443444445446447448449450451452453454455456457458459460461462463464465466467468469470471472473474475476477478479480481482483484485486487488489490491492493494495496497498499500501502503504505506507508509510511512513514515516517518519520521522523524525526527528529530531532533534535536537538539540541542543544545546547548549550551552553554555556557558559560561562563564565566567568569570571572573574575576577578579580581582583584585586587588589590591592593594595596597598599600601602603604605606607608609610611612613614615616617618619620621622623624625626627628629630631632633634635636637638639640641642643644645646647648649650651652653654655656657658659660661662663664665666667668669670671672673674675676677678679680681682683684685686687688689690691692693694695696697698699700701702703704705706707708709710711712713714715716717718719720721722723724725726727728729730731732733734735736737738739740741742743744745746747748749750751752753754755756757758759760761762763764765766767768769770771772773774775776777778779780781782783
  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. tristate "Cryptographic API"
  15. help
  16. This option provides the core Cryptographic API.
  17. if CRYPTO
  18. comment "Crypto core or helper"
  19. config CRYPTO_FIPS
  20. bool "FIPS 200 compliance"
  21. help
  22. This options enables the fips boot option which is
  23. required if you want to system to operate in a FIPS 200
  24. certification. You should say no unless you know what
  25. this is.
  26. config CRYPTO_ALGAPI
  27. tristate
  28. select CRYPTO_ALGAPI2
  29. help
  30. This option provides the API for cryptographic algorithms.
  31. config CRYPTO_ALGAPI2
  32. tristate
  33. config CRYPTO_AEAD
  34. tristate
  35. select CRYPTO_AEAD2
  36. select CRYPTO_ALGAPI
  37. config CRYPTO_AEAD2
  38. tristate
  39. select CRYPTO_ALGAPI2
  40. config CRYPTO_BLKCIPHER
  41. tristate
  42. select CRYPTO_BLKCIPHER2
  43. select CRYPTO_ALGAPI
  44. config CRYPTO_BLKCIPHER2
  45. tristate
  46. select CRYPTO_ALGAPI2
  47. select CRYPTO_RNG2
  48. select CRYPTO_WORKQUEUE
  49. config CRYPTO_HASH
  50. tristate
  51. select CRYPTO_HASH2
  52. select CRYPTO_ALGAPI
  53. config CRYPTO_HASH2
  54. tristate
  55. select CRYPTO_ALGAPI2
  56. config CRYPTO_RNG
  57. tristate
  58. select CRYPTO_RNG2
  59. select CRYPTO_ALGAPI
  60. config CRYPTO_RNG2
  61. tristate
  62. select CRYPTO_ALGAPI2
  63. config CRYPTO_PCOMP
  64. tristate
  65. select CRYPTO_ALGAPI2
  66. config CRYPTO_MANAGER
  67. tristate "Cryptographic algorithm manager"
  68. select CRYPTO_MANAGER2
  69. help
  70. Create default cryptographic template instantiations such as
  71. cbc(aes).
  72. config CRYPTO_MANAGER2
  73. def_tristate CRYPTO_MANAGER || (CRYPTO_MANAGER!=n && CRYPTO_ALGAPI=y)
  74. select CRYPTO_AEAD2
  75. select CRYPTO_HASH2
  76. select CRYPTO_BLKCIPHER2
  77. select CRYPTO_PCOMP
  78. config CRYPTO_GF128MUL
  79. tristate "GF(2^128) multiplication functions (EXPERIMENTAL)"
  80. depends on EXPERIMENTAL
  81. help
  82. Efficient table driven implementation of multiplications in the
  83. field GF(2^128). This is needed by some cypher modes. This
  84. option will be selected automatically if you select such a
  85. cipher mode. Only select this option by hand if you expect to load
  86. an external module that requires these functions.
  87. config CRYPTO_NULL
  88. tristate "Null algorithms"
  89. select CRYPTO_ALGAPI
  90. select CRYPTO_BLKCIPHER
  91. select CRYPTO_HASH
  92. help
  93. These are 'Null' algorithms, used by IPsec, which do nothing.
  94. config CRYPTO_WORKQUEUE
  95. tristate
  96. config CRYPTO_CRYPTD
  97. tristate "Software async crypto daemon"
  98. select CRYPTO_BLKCIPHER
  99. select CRYPTO_HASH
  100. select CRYPTO_MANAGER
  101. select CRYPTO_WORKQUEUE
  102. help
  103. This is a generic software asynchronous crypto daemon that
  104. converts an arbitrary synchronous software crypto algorithm
  105. into an asynchronous algorithm that executes in a kernel thread.
  106. config CRYPTO_AUTHENC
  107. tristate "Authenc support"
  108. select CRYPTO_AEAD
  109. select CRYPTO_BLKCIPHER
  110. select CRYPTO_MANAGER
  111. select CRYPTO_HASH
  112. help
  113. Authenc: Combined mode wrapper for IPsec.
  114. This is required for IPSec.
  115. config CRYPTO_TEST
  116. tristate "Testing module"
  117. depends on m
  118. select CRYPTO_MANAGER
  119. help
  120. Quick & dirty crypto test module.
  121. comment "Authenticated Encryption with Associated Data"
  122. config CRYPTO_CCM
  123. tristate "CCM support"
  124. select CRYPTO_CTR
  125. select CRYPTO_AEAD
  126. help
  127. Support for Counter with CBC MAC. Required for IPsec.
  128. config CRYPTO_GCM
  129. tristate "GCM/GMAC support"
  130. select CRYPTO_CTR
  131. select CRYPTO_AEAD
  132. select CRYPTO_GF128MUL
  133. help
  134. Support for Galois/Counter Mode (GCM) and Galois Message
  135. Authentication Code (GMAC). Required for IPSec.
  136. config CRYPTO_SEQIV
  137. tristate "Sequence Number IV Generator"
  138. select CRYPTO_AEAD
  139. select CRYPTO_BLKCIPHER
  140. select CRYPTO_RNG
  141. help
  142. This IV generator generates an IV based on a sequence number by
  143. xoring it with a salt. This algorithm is mainly useful for CTR
  144. comment "Block modes"
  145. config CRYPTO_CBC
  146. tristate "CBC support"
  147. select CRYPTO_BLKCIPHER
  148. select CRYPTO_MANAGER
  149. help
  150. CBC: Cipher Block Chaining mode
  151. This block cipher algorithm is required for IPSec.
  152. config CRYPTO_CTR
  153. tristate "CTR support"
  154. select CRYPTO_BLKCIPHER
  155. select CRYPTO_SEQIV
  156. select CRYPTO_MANAGER
  157. help
  158. CTR: Counter mode
  159. This block cipher algorithm is required for IPSec.
  160. config CRYPTO_CTS
  161. tristate "CTS support"
  162. select CRYPTO_BLKCIPHER
  163. help
  164. CTS: Cipher Text Stealing
  165. This is the Cipher Text Stealing mode as described by
  166. Section 8 of rfc2040 and referenced by rfc3962.
  167. (rfc3962 includes errata information in its Appendix A)
  168. This mode is required for Kerberos gss mechanism support
  169. for AES encryption.
  170. config CRYPTO_ECB
  171. tristate "ECB support"
  172. select CRYPTO_BLKCIPHER
  173. select CRYPTO_MANAGER
  174. help
  175. ECB: Electronic CodeBook mode
  176. This is the simplest block cipher algorithm. It simply encrypts
  177. the input block by block.
  178. config CRYPTO_LRW
  179. tristate "LRW support (EXPERIMENTAL)"
  180. depends on EXPERIMENTAL
  181. select CRYPTO_BLKCIPHER
  182. select CRYPTO_MANAGER
  183. select CRYPTO_GF128MUL
  184. help
  185. LRW: Liskov Rivest Wagner, a tweakable, non malleable, non movable
  186. narrow block cipher mode for dm-crypt. Use it with cipher
  187. specification string aes-lrw-benbi, the key must be 256, 320 or 384.
  188. The first 128, 192 or 256 bits in the key are used for AES and the
  189. rest is used to tie each cipher block to its logical position.
  190. config CRYPTO_PCBC
  191. tristate "PCBC support"
  192. select CRYPTO_BLKCIPHER
  193. select CRYPTO_MANAGER
  194. help
  195. PCBC: Propagating Cipher Block Chaining mode
  196. This block cipher algorithm is required for RxRPC.
  197. config CRYPTO_XTS
  198. tristate "XTS support (EXPERIMENTAL)"
  199. depends on EXPERIMENTAL
  200. select CRYPTO_BLKCIPHER
  201. select CRYPTO_MANAGER
  202. select CRYPTO_GF128MUL
  203. help
  204. XTS: IEEE1619/D16 narrow block cipher use with aes-xts-plain,
  205. key size 256, 384 or 512 bits. This implementation currently
  206. can't handle a sectorsize which is not a multiple of 16 bytes.
  207. comment "Hash modes"
  208. config CRYPTO_HMAC
  209. tristate "HMAC support"
  210. select CRYPTO_HASH
  211. select CRYPTO_MANAGER
  212. help
  213. HMAC: Keyed-Hashing for Message Authentication (RFC2104).
  214. This is required for IPSec.
  215. config CRYPTO_XCBC
  216. tristate "XCBC support"
  217. depends on EXPERIMENTAL
  218. select CRYPTO_HASH
  219. select CRYPTO_MANAGER
  220. help
  221. XCBC: Keyed-Hashing with encryption algorithm
  222. http://www.ietf.org/rfc/rfc3566.txt
  223. http://csrc.nist.gov/encryption/modes/proposedmodes/
  224. xcbc-mac/xcbc-mac-spec.pdf
  225. comment "Digest"
  226. config CRYPTO_CRC32C
  227. tristate "CRC32c CRC algorithm"
  228. select CRYPTO_HASH
  229. help
  230. Castagnoli, et al Cyclic Redundancy-Check Algorithm. Used
  231. by iSCSI for header and data digests and by others.
  232. See Castagnoli93. Module will be crc32c.
  233. config CRYPTO_CRC32C_INTEL
  234. tristate "CRC32c INTEL hardware acceleration"
  235. depends on X86
  236. select CRYPTO_HASH
  237. help
  238. In Intel processor with SSE4.2 supported, the processor will
  239. support CRC32C implementation using hardware accelerated CRC32
  240. instruction. This option will create 'crc32c-intel' module,
  241. which will enable any routine to use the CRC32 instruction to
  242. gain performance compared with software implementation.
  243. Module will be crc32c-intel.
  244. config CRYPTO_MD4
  245. tristate "MD4 digest algorithm"
  246. select CRYPTO_HASH
  247. help
  248. MD4 message digest algorithm (RFC1320).
  249. config CRYPTO_MD5
  250. tristate "MD5 digest algorithm"
  251. select CRYPTO_HASH
  252. help
  253. MD5 message digest algorithm (RFC1321).
  254. config CRYPTO_MICHAEL_MIC
  255. tristate "Michael MIC keyed digest algorithm"
  256. select CRYPTO_HASH
  257. help
  258. Michael MIC is used for message integrity protection in TKIP
  259. (IEEE 802.11i). This algorithm is required for TKIP, but it
  260. should not be used for other purposes because of the weakness
  261. of the algorithm.
  262. config CRYPTO_RMD128
  263. tristate "RIPEMD-128 digest algorithm"
  264. select CRYPTO_HASH
  265. help
  266. RIPEMD-128 (ISO/IEC 10118-3:2004).
  267. RIPEMD-128 is a 128-bit cryptographic hash function. It should only
  268. to be used as a secure replacement for RIPEMD. For other use cases
  269. RIPEMD-160 should be used.
  270. Developed by Hans Dobbertin, Antoon Bosselaers and Bart Preneel.
  271. See <http://home.esat.kuleuven.be/~bosselae/ripemd160.html>
  272. config CRYPTO_RMD160
  273. tristate "RIPEMD-160 digest algorithm"
  274. select CRYPTO_HASH
  275. help
  276. RIPEMD-160 (ISO/IEC 10118-3:2004).
  277. RIPEMD-160 is a 160-bit cryptographic hash function. It is intended
  278. to be used as a secure replacement for the 128-bit hash functions
  279. MD4, MD5 and it's predecessor RIPEMD
  280. (not to be confused with RIPEMD-128).
  281. It's speed is comparable to SHA1 and there are no known attacks
  282. against RIPEMD-160.
  283. Developed by Hans Dobbertin, Antoon Bosselaers and Bart Preneel.
  284. See <http://home.esat.kuleuven.be/~bosselae/ripemd160.html>
  285. config CRYPTO_RMD256
  286. tristate "RIPEMD-256 digest algorithm"
  287. select CRYPTO_HASH
  288. help
  289. RIPEMD-256 is an optional extension of RIPEMD-128 with a
  290. 256 bit hash. It is intended for applications that require
  291. longer hash-results, without needing a larger security level
  292. (than RIPEMD-128).
  293. Developed by Hans Dobbertin, Antoon Bosselaers and Bart Preneel.
  294. See <http://home.esat.kuleuven.be/~bosselae/ripemd160.html>
  295. config CRYPTO_RMD320
  296. tristate "RIPEMD-320 digest algorithm"
  297. select CRYPTO_HASH
  298. help
  299. RIPEMD-320 is an optional extension of RIPEMD-160 with a
  300. 320 bit hash. It is intended for applications that require
  301. longer hash-results, without needing a larger security level
  302. (than RIPEMD-160).
  303. Developed by Hans Dobbertin, Antoon Bosselaers and Bart Preneel.
  304. See <http://home.esat.kuleuven.be/~bosselae/ripemd160.html>
  305. config CRYPTO_SHA1
  306. tristate "SHA1 digest algorithm"
  307. select CRYPTO_HASH
  308. help
  309. SHA-1 secure hash standard (FIPS 180-1/DFIPS 180-2).
  310. config CRYPTO_SHA256
  311. tristate "SHA224 and SHA256 digest algorithm"
  312. select CRYPTO_HASH
  313. help
  314. SHA256 secure hash standard (DFIPS 180-2).
  315. This version of SHA implements a 256 bit hash with 128 bits of
  316. security against collision attacks.
  317. This code also includes SHA-224, a 224 bit hash with 112 bits
  318. of security against collision attacks.
  319. config CRYPTO_SHA512
  320. tristate "SHA384 and SHA512 digest algorithms"
  321. select CRYPTO_HASH
  322. help
  323. SHA512 secure hash standard (DFIPS 180-2).
  324. This version of SHA implements a 512 bit hash with 256 bits of
  325. security against collision attacks.
  326. This code also includes SHA-384, a 384 bit hash with 192 bits
  327. of security against collision attacks.
  328. config CRYPTO_TGR192
  329. tristate "Tiger digest algorithms"
  330. select CRYPTO_HASH
  331. help
  332. Tiger hash algorithm 192, 160 and 128-bit hashes
  333. Tiger is a hash function optimized for 64-bit processors while
  334. still having decent performance on 32-bit processors.
  335. Tiger was developed by Ross Anderson and Eli Biham.
  336. See also:
  337. <http://www.cs.technion.ac.il/~biham/Reports/Tiger/>.
  338. config CRYPTO_WP512
  339. tristate "Whirlpool digest algorithms"
  340. select CRYPTO_HASH
  341. help
  342. Whirlpool hash algorithm 512, 384 and 256-bit hashes
  343. Whirlpool-512 is part of the NESSIE cryptographic primitives.
  344. Whirlpool will be part of the ISO/IEC 10118-3:2003(E) standard
  345. See also:
  346. <http://planeta.terra.com.br/informatica/paulobarreto/WhirlpoolPage.html>
  347. comment "Ciphers"
  348. config CRYPTO_AES
  349. tristate "AES cipher algorithms"
  350. select CRYPTO_ALGAPI
  351. help
  352. AES cipher algorithms (FIPS-197). AES uses the Rijndael
  353. algorithm.
  354. Rijndael appears to be consistently a very good performer in
  355. both hardware and software across a wide range of computing
  356. environments regardless of its use in feedback or non-feedback
  357. modes. Its key setup time is excellent, and its key agility is
  358. good. Rijndael's very low memory requirements make it very well
  359. suited for restricted-space environments, in which it also
  360. demonstrates excellent performance. Rijndael's operations are
  361. among the easiest to defend against power and timing attacks.
  362. The AES specifies three key sizes: 128, 192 and 256 bits
  363. See <http://csrc.nist.gov/CryptoToolkit/aes/> for more information.
  364. config CRYPTO_AES_586
  365. tristate "AES cipher algorithms (i586)"
  366. depends on (X86 || UML_X86) && !64BIT
  367. select CRYPTO_ALGAPI
  368. select CRYPTO_AES
  369. help
  370. AES cipher algorithms (FIPS-197). AES uses the Rijndael
  371. algorithm.
  372. Rijndael appears to be consistently a very good performer in
  373. both hardware and software across a wide range of computing
  374. environments regardless of its use in feedback or non-feedback
  375. modes. Its key setup time is excellent, and its key agility is
  376. good. Rijndael's very low memory requirements make it very well
  377. suited for restricted-space environments, in which it also
  378. demonstrates excellent performance. Rijndael's operations are
  379. among the easiest to defend against power and timing attacks.
  380. The AES specifies three key sizes: 128, 192 and 256 bits
  381. See <http://csrc.nist.gov/encryption/aes/> for more information.
  382. config CRYPTO_AES_X86_64
  383. tristate "AES cipher algorithms (x86_64)"
  384. depends on (X86 || UML_X86) && 64BIT
  385. select CRYPTO_ALGAPI
  386. select CRYPTO_AES
  387. help
  388. AES cipher algorithms (FIPS-197). AES uses the Rijndael
  389. algorithm.
  390. Rijndael appears to be consistently a very good performer in
  391. both hardware and software across a wide range of computing
  392. environments regardless of its use in feedback or non-feedback
  393. modes. Its key setup time is excellent, and its key agility is
  394. good. Rijndael's very low memory requirements make it very well
  395. suited for restricted-space environments, in which it also
  396. demonstrates excellent performance. Rijndael's operations are
  397. among the easiest to defend against power and timing attacks.
  398. The AES specifies three key sizes: 128, 192 and 256 bits
  399. See <http://csrc.nist.gov/encryption/aes/> for more information.
  400. config CRYPTO_AES_NI_INTEL
  401. tristate "AES cipher algorithms (AES-NI)"
  402. depends on (X86 || UML_X86) && 64BIT
  403. select CRYPTO_AES_X86_64
  404. select CRYPTO_CRYPTD
  405. select CRYPTO_ALGAPI
  406. help
  407. Use Intel AES-NI instructions for AES algorithm.
  408. AES cipher algorithms (FIPS-197). AES uses the Rijndael
  409. algorithm.
  410. Rijndael appears to be consistently a very good performer in
  411. both hardware and software across a wide range of computing
  412. environments regardless of its use in feedback or non-feedback
  413. modes. Its key setup time is excellent, and its key agility is
  414. good. Rijndael's very low memory requirements make it very well
  415. suited for restricted-space environments, in which it also
  416. demonstrates excellent performance. Rijndael's operations are
  417. among the easiest to defend against power and timing attacks.
  418. The AES specifies three key sizes: 128, 192 and 256 bits
  419. See <http://csrc.nist.gov/encryption/aes/> for more information.
  420. config CRYPTO_ANUBIS
  421. tristate "Anubis cipher algorithm"
  422. select CRYPTO_ALGAPI
  423. help
  424. Anubis cipher algorithm.
  425. Anubis is a variable key length cipher which can use keys from
  426. 128 bits to 320 bits in length. It was evaluated as a entrant
  427. in the NESSIE competition.
  428. See also:
  429. <https://www.cosic.esat.kuleuven.ac.be/nessie/reports/>
  430. <http://planeta.terra.com.br/informatica/paulobarreto/AnubisPage.html>
  431. config CRYPTO_ARC4
  432. tristate "ARC4 cipher algorithm"
  433. select CRYPTO_ALGAPI
  434. help
  435. ARC4 cipher algorithm.
  436. ARC4 is a stream cipher using keys ranging from 8 bits to 2048
  437. bits in length. This algorithm is required for driver-based
  438. WEP, but it should not be for other purposes because of the
  439. weakness of the algorithm.
  440. config CRYPTO_BLOWFISH
  441. tristate "Blowfish cipher algorithm"
  442. select CRYPTO_ALGAPI
  443. help
  444. Blowfish cipher algorithm, by Bruce Schneier.
  445. This is a variable key length cipher which can use keys from 32
  446. bits to 448 bits in length. It's fast, simple and specifically
  447. designed for use on "large microprocessors".
  448. See also:
  449. <http://www.schneier.com/blowfish.html>
  450. config CRYPTO_CAMELLIA
  451. tristate "Camellia cipher algorithms"
  452. depends on CRYPTO
  453. select CRYPTO_ALGAPI
  454. help
  455. Camellia cipher algorithms module.
  456. Camellia is a symmetric key block cipher developed jointly
  457. at NTT and Mitsubishi Electric Corporation.
  458. The Camellia specifies three key sizes: 128, 192 and 256 bits.
  459. See also:
  460. <https://info.isl.ntt.co.jp/crypt/eng/camellia/index_s.html>
  461. config CRYPTO_CAST5
  462. tristate "CAST5 (CAST-128) cipher algorithm"
  463. select CRYPTO_ALGAPI
  464. help
  465. The CAST5 encryption algorithm (synonymous with CAST-128) is
  466. described in RFC2144.
  467. config CRYPTO_CAST6
  468. tristate "CAST6 (CAST-256) cipher algorithm"
  469. select CRYPTO_ALGAPI
  470. help
  471. The CAST6 encryption algorithm (synonymous with CAST-256) is
  472. described in RFC2612.
  473. config CRYPTO_DES
  474. tristate "DES and Triple DES EDE cipher algorithms"
  475. select CRYPTO_ALGAPI
  476. help
  477. DES cipher algorithm (FIPS 46-2), and Triple DES EDE (FIPS 46-3).
  478. config CRYPTO_FCRYPT
  479. tristate "FCrypt cipher algorithm"
  480. select CRYPTO_ALGAPI
  481. select CRYPTO_BLKCIPHER
  482. help
  483. FCrypt algorithm used by RxRPC.
  484. config CRYPTO_KHAZAD
  485. tristate "Khazad cipher algorithm"
  486. select CRYPTO_ALGAPI
  487. help
  488. Khazad cipher algorithm.
  489. Khazad was a finalist in the initial NESSIE competition. It is
  490. an algorithm optimized for 64-bit processors with good performance
  491. on 32-bit processors. Khazad uses an 128 bit key size.
  492. See also:
  493. <http://planeta.terra.com.br/informatica/paulobarreto/KhazadPage.html>
  494. config CRYPTO_SALSA20
  495. tristate "Salsa20 stream cipher algorithm (EXPERIMENTAL)"
  496. depends on EXPERIMENTAL
  497. select CRYPTO_BLKCIPHER
  498. help
  499. Salsa20 stream cipher algorithm.
  500. Salsa20 is a stream cipher submitted to eSTREAM, the ECRYPT
  501. Stream Cipher Project. See <http://www.ecrypt.eu.org/stream/>
  502. The Salsa20 stream cipher algorithm is designed by Daniel J.
  503. Bernstein <djb@cr.yp.to>. See <http://cr.yp.to/snuffle.html>
  504. config CRYPTO_SALSA20_586
  505. tristate "Salsa20 stream cipher algorithm (i586) (EXPERIMENTAL)"
  506. depends on (X86 || UML_X86) && !64BIT
  507. depends on EXPERIMENTAL
  508. select CRYPTO_BLKCIPHER
  509. help
  510. Salsa20 stream cipher algorithm.
  511. Salsa20 is a stream cipher submitted to eSTREAM, the ECRYPT
  512. Stream Cipher Project. See <http://www.ecrypt.eu.org/stream/>
  513. The Salsa20 stream cipher algorithm is designed by Daniel J.
  514. Bernstein <djb@cr.yp.to>. See <http://cr.yp.to/snuffle.html>
  515. config CRYPTO_SALSA20_X86_64
  516. tristate "Salsa20 stream cipher algorithm (x86_64) (EXPERIMENTAL)"
  517. depends on (X86 || UML_X86) && 64BIT
  518. depends on EXPERIMENTAL
  519. select CRYPTO_BLKCIPHER
  520. help
  521. Salsa20 stream cipher algorithm.
  522. Salsa20 is a stream cipher submitted to eSTREAM, the ECRYPT
  523. Stream Cipher Project. See <http://www.ecrypt.eu.org/stream/>
  524. The Salsa20 stream cipher algorithm is designed by Daniel J.
  525. Bernstein <djb@cr.yp.to>. See <http://cr.yp.to/snuffle.html>
  526. config CRYPTO_SEED
  527. tristate "SEED cipher algorithm"
  528. select CRYPTO_ALGAPI
  529. help
  530. SEED cipher algorithm (RFC4269).
  531. SEED is a 128-bit symmetric key block cipher that has been
  532. developed by KISA (Korea Information Security Agency) as a
  533. national standard encryption algorithm of the Republic of Korea.
  534. It is a 16 round block cipher with the key size of 128 bit.
  535. See also:
  536. <http://www.kisa.or.kr/kisa/seed/jsp/seed_eng.jsp>
  537. config CRYPTO_SERPENT
  538. tristate "Serpent cipher algorithm"
  539. select CRYPTO_ALGAPI
  540. help
  541. Serpent cipher algorithm, by Anderson, Biham & Knudsen.
  542. Keys are allowed to be from 0 to 256 bits in length, in steps
  543. of 8 bits. Also includes the 'Tnepres' algorithm, a reversed
  544. variant of Serpent for compatibility with old kerneli.org code.
  545. See also:
  546. <http://www.cl.cam.ac.uk/~rja14/serpent.html>
  547. config CRYPTO_TEA
  548. tristate "TEA, XTEA and XETA cipher algorithms"
  549. select CRYPTO_ALGAPI
  550. help
  551. TEA cipher algorithm.
  552. Tiny Encryption Algorithm is a simple cipher that uses
  553. many rounds for security. It is very fast and uses
  554. little memory.
  555. Xtendend Tiny Encryption Algorithm is a modification to
  556. the TEA algorithm to address a potential key weakness
  557. in the TEA algorithm.
  558. Xtendend Encryption Tiny Algorithm is a mis-implementation
  559. of the XTEA algorithm for compatibility purposes.
  560. config CRYPTO_TWOFISH
  561. tristate "Twofish cipher algorithm"
  562. select CRYPTO_ALGAPI
  563. select CRYPTO_TWOFISH_COMMON
  564. help
  565. Twofish cipher algorithm.
  566. Twofish was submitted as an AES (Advanced Encryption Standard)
  567. candidate cipher by researchers at CounterPane Systems. It is a
  568. 16 round block cipher supporting key sizes of 128, 192, and 256
  569. bits.
  570. See also:
  571. <http://www.schneier.com/twofish.html>
  572. config CRYPTO_TWOFISH_COMMON
  573. tristate
  574. help
  575. Common parts of the Twofish cipher algorithm shared by the
  576. generic c and the assembler implementations.
  577. config CRYPTO_TWOFISH_586
  578. tristate "Twofish cipher algorithms (i586)"
  579. depends on (X86 || UML_X86) && !64BIT
  580. select CRYPTO_ALGAPI
  581. select CRYPTO_TWOFISH_COMMON
  582. help
  583. Twofish cipher algorithm.
  584. Twofish was submitted as an AES (Advanced Encryption Standard)
  585. candidate cipher by researchers at CounterPane Systems. It is a
  586. 16 round block cipher supporting key sizes of 128, 192, and 256
  587. bits.
  588. See also:
  589. <http://www.schneier.com/twofish.html>
  590. config CRYPTO_TWOFISH_X86_64
  591. tristate "Twofish cipher algorithm (x86_64)"
  592. depends on (X86 || UML_X86) && 64BIT
  593. select CRYPTO_ALGAPI
  594. select CRYPTO_TWOFISH_COMMON
  595. help
  596. Twofish cipher algorithm (x86_64).
  597. Twofish was submitted as an AES (Advanced Encryption Standard)
  598. candidate cipher by researchers at CounterPane Systems. It is a
  599. 16 round block cipher supporting key sizes of 128, 192, and 256
  600. bits.
  601. See also:
  602. <http://www.schneier.com/twofish.html>
  603. comment "Compression"
  604. config CRYPTO_DEFLATE
  605. tristate "Deflate compression algorithm"
  606. select CRYPTO_ALGAPI
  607. select ZLIB_INFLATE
  608. select ZLIB_DEFLATE
  609. help
  610. This is the Deflate algorithm (RFC1951), specified for use in
  611. IPSec with the IPCOMP protocol (RFC3173, RFC2394).
  612. You will most probably want this if using IPSec.
  613. config CRYPTO_ZLIB
  614. tristate "Zlib compression algorithm"
  615. select CRYPTO_PCOMP
  616. select ZLIB_INFLATE
  617. select ZLIB_DEFLATE
  618. select NLATTR
  619. help
  620. This is the zlib algorithm.
  621. config CRYPTO_LZO
  622. tristate "LZO compression algorithm"
  623. select CRYPTO_ALGAPI
  624. select LZO_COMPRESS
  625. select LZO_DECOMPRESS
  626. help
  627. This is the LZO algorithm.
  628. comment "Random Number Generation"
  629. config CRYPTO_ANSI_CPRNG
  630. tristate "Pseudo Random Number Generation for Cryptographic modules"
  631. select CRYPTO_AES
  632. select CRYPTO_RNG
  633. select CRYPTO_FIPS
  634. help
  635. This option enables the generic pseudo random number generator
  636. for cryptographic modules. Uses the Algorithm specified in
  637. ANSI X9.31 A.2.4
  638. source "drivers/crypto/Kconfig"
  639. endif # if CRYPTO