| /linux/crypto/ |
| A D | khazad.c | 803 u8 *ciphertext, const u8 *plaintext) in khazad_crypt() argument
806 __be64 *dst = (__be64 *)ciphertext; in khazad_crypt()
|
| A D | anubis.c | 573 u8 *ciphertext, const u8 *plaintext, const int R) in anubis_crypt() argument
576 __be32 *dst = (__be32 *)ciphertext; in anubis_crypt()
|
| A D | Kconfig | 733 tristate "XTS (XOR Encrypt XOR with ciphertext stealing)"
738 XTS (XOR Encrypt XOR with ciphertext stealing) mode (NIST SP800-38E
|
| /linux/arch/arm64/crypto/ |
| A D | Kconfig | 165 - 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/fs/smb/server/ |
| A D | ntlmssp.h | 165 unsigned char ciphertext[CIFS_CPHTXT_SIZE]; member
|
| /linux/arch/arm/crypto/ |
| A D | Kconfig | 179 - 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/Documentation/crypto/ |
| A D | userspace-if.rst | 94 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
|
| A D | devel-algos.rst | 132 contains the plaintext and will contain the ciphertext. Please refer
|
| /linux/drivers/staging/rtl8712/ |
| A D | rtl871x_security.c | 858 static void aes128k128d(u8 *key, u8 *data, u8 *ciphertext) in aes128k128d() argument
870 xor_128(round_key, data, ciphertext); in aes128k128d()
873 byte_sub(ciphertext, intermediatea); in aes128k128d()
875 xor_128(intermediateb, round_key, ciphertext); in aes128k128d()
877 byte_sub(ciphertext, intermediatea); in aes128k128d()
883 xor_128(intermediatea, round_key, ciphertext); in aes128k128d()
|
| /linux/Documentation/filesystems/ |
| A D | fscrypt.rst | 118 "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,
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
1438 directories.) Instead, filesystems hash the ciphertext filenames,
1441 the user-supplied name to get the ciphertext.
1448 back to the raw ciphertext.
[all …]
|
| A D | fsverity.rst | 596 the ciphertext. This is necessary in order to make the fs-verity file
|
| /linux/Documentation/block/ |
| A D | inline-encryption.rst | 33 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/ |
| A D | rtw_security.c | 668 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/fs/smb/client/ |
| A D | cifsencrypt.c | 684 cifs_arc4_crypt(ctx_arc4, ses->ntlmssp->ciphertext, sec_key, in calc_seckey()
|
| A D | cifsglob.h | 195 unsigned char ciphertext[CIFS_CPHTXT_SIZE]; /* sent to server */ member
|
| A D | sess.c | 1241 memcpy(tmp, ses->ntlmssp->ciphertext, CIFS_CPHTXT_SIZE); in build_ntlmssp_auth_blob()
|
| /linux/Documentation/admin-guide/device-mapper/ |
| A D | dm-crypt.rst | 107 the leak of information about the ciphertext device (filesystem type,
|
| /linux/Documentation/virt/kvm/x86/ |
| A D | amd-memory-encryption.rst | 239 … SEV_STATE_SECRET, /* guest is being launched and ready to accept the ciphertext data */
|
| /linux/Documentation/virt/kvm/ |
| A D | api.rst | 4789 moving ciphertext of those pages will not result in plaintext being
4794 swap or migrate (move) ciphertext pages. Hence, for now we pin the guest
|