Searched full:digest (Results 1 – 22 of 22) sorted by relevance
| /Documentation/crypto/ |
| D | api-digest.rst | 1 Message Digest Algorithm Definitions
5 :doc: Message Digest Algorithm Definitions
10 Asynchronous Message Digest API
14 :doc: Asynchronous Message Digest API
28 Synchronous Message Digest API
32 :doc: Synchronous Message Digest API
|
| D | userspace-if.rst | 34 - Message digest including keyed message digest (HMAC, CMAC)
98 Message Digest API
101 The message digest type to be used for the cipher operation is selected
116 digests. Though, a keyed message digest is referenced by the appropriate
118 how the key can be set for a keyed message digest.
121 should be processed with the message digest. The send system call allows
125 message digest update function where the final hash is not yet
127 the final message digest immediately.
129 With the recv() system call, the application can read the message digest
131 digest, the flag MSG_TRUNC is set by the kernel.
[all …]
|
| D | api-samples.rst | 119 unsigned char *digest)
130 ret = crypto_shash_digest(&sdesc->shash, data, datalen, digest);
136 unsigned char *digest)
147 ret = calc_hash(alg, data, datalen, digest);
|
| D | architecture.rst | 14 - Message digest, including keyed message digest
150 - shash for synchronous message digest
152 - ahash for asynchronous message digest
171 - digestsize: output size of the message digest
207 - CRYPTO_ALG_TYPE_HASH Raw message digest
371 Generic Keyed Message Digest Structure
374 Keyed message digest implementations again follow the same concept as
414 handle to calculate the message digest.
|
| D | api.rst | 10 api-digest
|
| D | devel-algos.rst | 194 .digest() ! The entire process is handled
195 | by the .digest() call.
|
| D | asymmetric-keys.rst | 97 digest algorithms used by those::
133 u8 *digest;
148 hash must be pointed to by sig->digest and the size of the hash be placed in
|
| /Documentation/security/ |
| D | IMA-templates.rst | 65 - 'd': the digest of the event (i.e. the digest of a measured file),
68 - 'd-ng': the digest of the event, calculated with an arbitrary hash
69 algorithm (field format: <hash algo>:digest);
70 - 'd-ngv2': same as d-ng, but prefixed with the "ima" or "verity" digest type
71 (field format: <digest type>:<hash algo>:digest);
72 - 'd-modsig': the digest of the event without the appended modsig;
74 - 'sig': the file signature, based on either the file's/fsverity's digest[1],
|
| /Documentation/filesystems/ |
| D | fsverity.rst | 30 the "fs-verity file digest", which is a hash that includes the Merkle
79 retrieving its fs-verity digest using `FS_IOC_MEASURE_VERITY`_, then
94 files by their verity digest, and ``fsverity_signature`` to authorize
205 The FS_IOC_MEASURE_VERITY ioctl retrieves the digest of a verity file.
206 The fs-verity file digest is a cryptographic digest that identifies
208 a Merkle tree and is different from a traditional full-file digest.
215 __u8 digest[];
220 ``digest`` field.
226 digest. It will match ``fsverity_enable_arg::hash_algorithm``.
227 - ``digest_size`` will be the size of the digest in bytes, e.g. 32
[all …]
|
| D | overlayfs.rst | 448 digest of the lower file is added to the "trusted.overlay.metacopy"
458 digest check, or from a later read due to fs-verity) and a detailed
477 The metacopy digest is never generated or used. This is the
480 Whenever a metacopy files specifies an expected digest, the
481 corresponding data file must match the specified digest. When
482 generating a metacopy file the verity digest will be set in it
486 digest (or EIO is returned on open). This means metadata copy up
|
| /Documentation/scsi/ |
| D | cxgb3i.rst | 16 - iSCSI PDU digest generation and verification
19 Data digest into the PDUs.
21 Data digest of the PDUs.
|
| /Documentation/admin-guide/device-mapper/ |
| D | verity.rst | 6 block devices using a cryptographic digest provided by the kernel crypto API.
17 <algorithm> <digest> <salt>
28 The salt is prepended when hashing and each digest is
44 Each block corresponds to one digest on the hash device.
62 <digest>
188 selected cryptographic digest algorithm. The hashes are linearly-ordered in
|
| D | dm-crypt.rst | 165 of the digest size of the used HMAC algorithm.
|
| D | dm-ima.rst | 61 TEMPLATE_DATA_DIGEST := Template data digest of the IMA record.
68 ALG := Algorithm to compute event digest
69 EVENT_DIGEST := Digest of the event data
|
| /Documentation/ABI/testing/ |
| D | ima_policy | 56 limited to fsverity digest based signatures
64 Require fs-verity's file digest instead of the
166 with indication of type of digest in the measurement list.
175 which includes the indication of type of digest and the file
|
| /Documentation/devicetree/bindings/crypto/ |
| D | fsl-sec2.txt | 23 bit 3 = set if SEC has the message digest EU (MDEU/MDEU-A)
29 bit 11 = set if SEC has the message digest EU extended alg set (MDEU-B)
|
| D | aspeed,ast2500-hace.yaml | 14 of hash data digest, encryption, and decryption. Basically, HACE can be
|
| /Documentation/virt/kvm/x86/ |
| D | amd-memory-encryption.rst | 312 report containing the SHA-256 digest of the guest memory and VMSA passed through the KVM_SEV_LAUNCH
313 commands and signed with the PEK. The digest returned by the command should match the digest
|
| /Documentation/admin-guide/LSM/ |
| D | ipe.rst | 52 signature, assessing the digest of a fs-verity protected file, or
115 authorized reference value (digest, signature, etc) as per the defined
387 along with the version and the hash digest of the two policies.
787 restrictions on the digest algorithm itself;
792 restrictions on the digest algorithm itself;
|
| /Documentation/gpu/ |
| D | drm-vm-bind-async.rst | 31 understanding of dma-fences is required to digest this
|
| /Documentation/security/keys/ |
| D | trusted-encrypted.rst | 227 policydigest= digest for the authorization policy. must be calculated
|
| D | core.rst | 1730 digest algorithm - the name of which should be supplied in hash_algo.
1738 will be validated. Depending on the encoding, the digest algorithm used
|