Home
last modified time | relevance | path

Searched refs:ciphers (Results 1 – 10 of 10) sorted by relevance

/Linux-v4.19/Documentation/crypto/
Dintro.rst7 The kernel crypto API offers a rich set of cryptographic ciphers as well
15 specification, hints to developers of ciphers are provided. Pointers to
21 transformations and handles them the same way as ciphers.
27 - data transformation implementations (typically ciphers) that can be
31 well as for developers implementing ciphers. This API specification,
33 implementations (i.e. implementations of ciphers and other
Darchitecture.rst10 - Symmetric ciphers
12 - AEAD ciphers
23 The kernel crypto API provides implementations of single block ciphers
26 block ciphers and message digests. Templates include all types of block
29 Single block ciphers and message digests can either be directly used by
30 a caller or invoked together with a template to form multi-block ciphers
54 In these examples, "aes" and "sha1" are the ciphers and all others are
119 The list of available ciphers is given in /proc/crypto. However, that
121 ciphers. Each block listed in /proc/crypto may contain the following
134 "kernel" for statically linked ciphers)
[all …]
Dapi-intro.txt8 mode ciphers), this will allow for pages to be encrypted in-place
41 meant to support all ciphers including stream ciphers. The difference
44 subject to block size requirements (i.e., non-stream ciphers can only
88 When using the API for ciphers, performance will be optimal if each
Duserspace-if.rst32 following ciphers are accessible:
36 - Symmetric ciphers
38 - AEAD ciphers
57 calls. This includes the generic vs. unique naming schema for ciphers as
366 - the skcipher cipher type (symmetric ciphers)
375 AEAD ciphers. For a encryption operation, the authentication tag of
Ddevel-algos.rst63 implementations, that being the CIPHER type used for symmetric ciphers.
114 implementations. The multi-block ciphers are used for transformations
/Linux-v4.19/drivers/net/wireless/intel/iwlwifi/mvm/
Dmac80211.c473 BUILD_BUG_ON(ARRAY_SIZE(mvm->ciphers) < ARRAY_SIZE(mvm_ciphers) + 6); in iwl_mvm_mac_setup_register()
474 memcpy(mvm->ciphers, mvm_ciphers, sizeof(mvm_ciphers)); in iwl_mvm_mac_setup_register()
476 hw->wiphy->cipher_suites = mvm->ciphers; in iwl_mvm_mac_setup_register()
479 mvm->ciphers[hw->wiphy->n_cipher_suites] = in iwl_mvm_mac_setup_register()
482 mvm->ciphers[hw->wiphy->n_cipher_suites] = in iwl_mvm_mac_setup_register()
493 mvm->ciphers[hw->wiphy->n_cipher_suites] = in iwl_mvm_mac_setup_register()
497 mvm->ciphers[hw->wiphy->n_cipher_suites] = in iwl_mvm_mac_setup_register()
500 mvm->ciphers[hw->wiphy->n_cipher_suites] = in iwl_mvm_mac_setup_register()
524 mvm->ciphers[hw->wiphy->n_cipher_suites] = cs->cipher; in iwl_mvm_mac_setup_register()
Dmvm.h1088 u32 ciphers[IWL_MVM_NUM_CIPHERS]; member
/Linux-v4.19/drivers/block/
DKconfig250 Say Y here if you want to be able to use the ciphers that are
/Linux-v4.19/drivers/md/
DKconfig287 the ciphers you're going to use in the cryptoapi configuration.
/Linux-v4.19/drivers/crypto/
DKconfig630 The Security System handle AES/DES/3DES ciphers in CBC mode