Home
last modified time | relevance | path

Searched refs:ciphertext (Results 1 – 16 of 16) sorted by relevance

/linux-6.15/arch/arm64/crypto/
H A DKconfig166 - XTS (XOR Encrypt XOR with ciphertext stealing) mode (NIST SP800-38E
183 - XTS (XOR Encrypt XOR with ciphertext stealing) mode (NIST SP800-38E
216 - XTS (XOR Encrypt XOR with ciphertext stealing) mode (NIST SP800-38E
246 - XTS (XOR Encrypt XOR with ciphertext stealing) mode (NIST SP800-38E
/linux-6.15/arch/arm/crypto/
H A DKconfig182 - XTS (XOR Encrypt XOR with ciphertext stealing) mode (NIST SP800-38E
195 ciphertext stealing when the message isn't a multiple of 16 bytes, and
211 - XTS (XOR Encrypt XOR with ciphertext stealing) mode (NIST SP800-38E
/linux-6.15/fs/smb/server/
H A Dntlmssp.h165 unsigned char ciphertext[CIFS_CPHTXT_SIZE]; member
/linux-6.15/Documentation/crypto/
H A Duserspace-if.rst94 ciphertext in different memory locations, all a consumer needs to do is
237 with the plaintext / ciphertext. See below for the memory structure.
263 - plaintext or ciphertext
279 - AEAD decryption input: AAD \|\| ciphertext \|\| authentication tag
284 - AEAD encryption output: ciphertext \|\| authentication tag
397 provided ciphertext is assumed to contain an authentication tag of
H A Ddevel-algos.rst132 contains the plaintext and will contain the ciphertext. Please refer
/linux-6.15/Documentation/filesystems/
H A Dfscrypt.rst118 "locked", i.e. in ciphertext or encrypted form.
220 resulting ciphertext is used as the derived key. If the ciphertext is
241 files doesn't map to the same ciphertext, or vice versa. In most
350 the difficulty of dealing with ciphertext expansion. Therefore,
1220 for an encrypted file contains the plaintext, not the ciphertext.
1232 listed in an encoded form derived from their ciphertext. The
1325 Inline encryption doesn't affect the ciphertext or other aspects of
1434 directories.) Instead, filesystems hash the ciphertext filenames,
1437 the user-supplied name to get the ciphertext.
1444 back to the raw ciphertext.
[all …]
H A Dfsverity.rst602 the ciphertext. This is necessary in order to make the fs-verity file
/linux-6.15/Documentation/block/
H A Dinline-encryption.rst33 verify the correctness of the resulting ciphertext. Inline encryption hardware
177 blk-crypto-fallback is used, the ciphertext written to disk (and hence the
289 re-generate the integrity info from the ciphertext data and store that on disk
294 ciphertext, not that of the plaintext).
537 reproduced in software in order to verify the ciphertext that is written to disk
547 For an example of a test that verifies the ciphertext written to disk in the
/linux-6.15/drivers/staging/rtl8723bs/core/
H A Drtw_security.c668 static void aes128k128d(u8 *key, u8 *data, u8 *ciphertext);
676 static void aes128k128d(u8 *key, u8 *data, u8 *ciphertext) in aes128k128d() argument
681 aes_encrypt(&ctx, ciphertext, data); in aes128k128d()
/linux-6.15/fs/smb/client/
H A Dcifsencrypt.c686 cifs_arc4_crypt(ctx_arc4, ses->ntlmssp->ciphertext, sec_key, in calc_seckey()
H A Dcifsglob.h238 unsigned char ciphertext[CIFS_CPHTXT_SIZE]; /* sent to server */ member
H A Dsess.c1241 memcpy(tmp, ses->ntlmssp->ciphertext, CIFS_CPHTXT_SIZE); in build_ntlmssp_auth_blob()
/linux-6.15/Documentation/admin-guide/device-mapper/
H A Ddm-crypt.rst107 the leak of information about the ciphertext device (filesystem type,
/linux-6.15/crypto/
H A DKconfig746 tristate "XTS (XOR Encrypt XOR with ciphertext stealing)"
751 XTS (XOR Encrypt XOR with ciphertext stealing) mode (NIST SP800-38E
/linux-6.15/Documentation/virt/kvm/x86/
H A Damd-memory-encryption.rst239 … SEV_STATE_SECRET, /* guest is being launched and ready to accept the ciphertext data */
/linux-6.15/Documentation/virt/kvm/
H A Dapi.rst4799 moving ciphertext of those pages will not result in plaintext being
4804 swap or migrate (move) ciphertext pages. Hence, for now we pin the guest