Searched full:cipher (Results 1 – 17 of 17) sorted by relevance
| /Documentation/crypto/ |
| D | architecture.rst | 4 Cipher algorithm types
8 cipher types:
33 A single block cipher may even be called with multiple templates.
34 However, templates cannot be used without a single cipher.
63 When using the synchronous API operation, the caller invokes a cipher
65 That means, the caller waits until the cipher operation completes.
71 implies that the invocation of a cipher operation will complete almost
72 instantly. That invocation triggers the cipher operation but it does not
73 signal its completion. Before invoking a cipher operation, the caller
75 signal the completion of the cipher operation. Furthermore, the caller
[all …]
|
| D | api-skcipher.rst | 1 Block Cipher Algorithm Definitions
5 :doc: Block Cipher Algorithm Definitions
10 Symmetric Key Cipher API
14 :doc: Symmetric Key Cipher API
19 Symmetric Key Cipher Request Handle
23 :doc: Symmetric Key Cipher Request Handle
28 Single Block Cipher API
31 .. kernel-doc:: include/crypto/internal/cipher.h
32 :doc: Single Block Cipher API
34 .. kernel-doc:: include/crypto/internal/cipher.h
|
| D | intro.rst | 19 Therefore, a cipher handle variable usually has the name "tfm". Besides
37 Note: The terms "transformation" and cipher algorithm are used
56 to as a "cipher handle". Such a cipher handle is always subject to the
58 a cipher handle:
60 1. Initialization of a cipher handle.
62 2. Execution of all intended cipher operations applicable for the handle
63 where the cipher handle must be furnished to every API call.
65 3. Destruction of a cipher handle.
67 When using the initialization API calls, a cipher handle is created and
|
| D | userspace-if.rst | 13 consumer and never as a provider of a transformation or cipher
56 A cipher is accessed with the same name as done for the in-kernel API
61 user space application. User space invokes the cipher operation with the
62 send()/write() system call family. The result of the cipher operation is
73 parameter specified below for the different cipher types.
79 particular cipher instance. When invoking send/write or recv/read
83 In-place Cipher operation
87 space interface allows the cipher operation in-place. That means that
90 is of particular interest for symmetric cipher operations where a
101 The message digest type to be used for the cipher operation is selected
[all …]
|
| D | devel-algos.rst | 1 Developing Cipher Algorithms
47 Single-Block Symmetric Ciphers [CIPHER]
53 implementations, that being the CIPHER type used for symmetric ciphers.
54 The CIPHER type is used for transformations which operate on exactly one
60 The registration of [CIPHER] algorithm is specific in that struct
61 crypto_alg field .cra_type is empty. The .cra_u.cipher has to be
66 Cipher Definition With struct cipher_alg
69 Struct cipher_alg defines a single block cipher.
103 This section describes the multi-block cipher transformation
111 The registration of multi-block cipher algorithms is one of the most
[all …]
|
| D | api-akcipher.rst | 1 Asymmetric Cipher Algorithm Definitions
7 Asymmetric Cipher API
16 Asymmetric Cipher Request Handle
|
| D | api-kpp.rst | 1 Key-agreement Protocol Primitives (KPP) Cipher Algorithm Definitions
7 Key-agreement Protocol Primitives (KPP) Cipher API
16 Key-agreement Protocol Primitives (KPP) Cipher Request Handle
|
| D | api-aead.rst | 5 :doc: Authenticated Encryption With Associated Data (AEAD) Cipher API
10 Authenticated Encryption With Associated Data (AEAD) Cipher API
|
| D | index.rst | 9 concepts, details about developing cipher implementations, employment of the API
|
| D | api-intro.rst | 34 [transform ops] (per-type logic glue e.g. cipher.c, compress.c)
95 scatterlist contains data which is a multiple of the cipher's block
119 Cipher Algorithms").
|
| D | api-samples.rst | 4 Code Example For Symmetric Key Cipher Operation
|
| /Documentation/admin-guide/device-mapper/ |
| D | dm-crypt.rst | 13 <cipher> <key> <iv_offset> <device path> \
16 <cipher>
17 Encryption cipher, encryption mode and Initial Vector (IV) generator.
19 The cipher specifications format is::
21 cipher[:keycount]-chainmode-ivmode[:ivopts]
29 Cipher format also supports direct specification with kernel crypt API
34 The crypto API cipher specifications format is::
55 You can only use key sizes that are valid for the selected cipher
205 # Create a crypt device using cryptsetup and LUKS header with default cipher
|
| D | dm-integrity.rst | 150 attacker can't read the journal. You can use a block cipher here
151 (such as "cbc(aes)") or a stream cipher (for example "chacha20"
|
| /Documentation/ABI/testing/ |
| D | debugfs-driver-qat_telemetry | 78 util_wcp<N> utilization of Wireless Cipher slice N [%]
79 exec_wcp<N> execution count of Wireless Cipher slice N
80 util_cph<N> utilization of Cipher slice N [%]
81 exec_cph<N> execution count of Cipher slice N
|
| /Documentation/filesystems/ |
| D | fscrypt.rst | 351 contents encryption uses a block cipher in `XTS mode
355 or a wide-block cipher. Filenames encryption uses a
356 block cipher in `CBC-CTS mode
358 cipher.
365 upgrades the filenames encryption to use a wide-block cipher. (A
366 *wide-block cipher*, also called a tweakable super-pseudorandom
369 cipher is the ideal mode for the problem domain, though CBC-CTS is the
374 of hardware acceleration for AES. Adiantum is a wide-block cipher
530 common prefix at least as long as the cipher block size (16 bytes for AES), the
536 >= 16 bytes; cipher block alignment is not required. However,
|
| /Documentation/devicetree/bindings/riscv/ |
| D | extensions.yaml | 339 The standard Zksed for ShangMi suite: SM4 block cipher instructions
508 The standard Zvkned extension for Vector AES block cipher
544 The standard Zvksed extension for ShangMi suite: SM4 block cipher
|
| /Documentation/arch/x86/ |
| D | sgx.rst | 201 additional changes to prevent cipher text from being returned and SW memory
|