Home
last modified time | relevance | path

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

/linux/arch/arm64/crypto/
H A DKconfig165 - XTS (XOR Encrypt XOR with ciphertext stealing) mode (NIST SP800-38E
182 - XTS (XOR Encrypt XOR with ciphertext stealing) mode (NIST SP800-38E
214 - XTS (XOR Encrypt XOR with ciphertext stealing) mode (NIST SP800-38E
244 - XTS (XOR Encrypt XOR with ciphertext stealing) mode (NIST SP800-38E
/linux/arch/arm/crypto/
H A DKconfig179 - XTS (XOR Encrypt XOR with ciphertext stealing) mode (NIST SP800-38E
192 ciphertext stealing when the message isn't a multiple of 16 bytes, and
208 - XTS (XOR Encrypt XOR with ciphertext stealing) mode (NIST SP800-38E
/linux/fs/smb/server/
H A Dntlmssp.h165 unsigned char ciphertext[CIFS_CPHTXT_SIZE]; member
/linux/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/Documentation/filesystems/
H A Dfscrypt.rst118 "locked", i.e. in ciphertext or encrypted form.
221 resulting ciphertext is used as the derived key. If the ciphertext is
242 files doesn't map to the same ciphertext, or vice versa. In most
351 the difficulty of dealing with ciphertext expansion. Therefore,
955 be in plaintext form or in ciphertext form) is global. This mismatch
1224 for an encrypted file contains the plaintext, not the ciphertext.
1236 listed in an encoded form derived from their ciphertext. The
1329 Inline encryption doesn't affect the ciphertext or other aspects of
1412 read the ciphertext into the page cache and decrypt it in-place. The
1438 directories.) Instead, filesystems hash the ciphertext filenames,
[all …]
/linux/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).
/linux/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/Documentation/admin-guide/device-mapper/
H A Ddm-crypt.rst107 the leak of information about the ciphertext device (filesystem type,
/linux/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.c1213 memcpy(tmp, ses->ntlmssp->ciphertext, CIFS_CPHTXT_SIZE); in build_ntlmssp_auth_blob()
/linux/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/Documentation/virt/kvm/
H A Dapi.rst4795 moving ciphertext of those pages will not result in plaintext being
4800 swap or migrate (move) ciphertext pages. Hence, for now we pin the guest