/linux-6.12.1/crypto/ |
D | testmgr.h | 40 const char *plaintext; member 4556 .plaintext = "", 4560 .plaintext = "a", 4565 .plaintext = "abc", 4570 .plaintext = "message digest", 4575 .plaintext = "abcdefghijklmnopqrstuvwxyz", 4580 .plaintext = "ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz0123456789", 4585 .plaintext = "123456789012345678901234567890123456789012345678901234567890123" 4595 .plaintext = "", 4601 .plaintext = "a", [all …]
|
D | khazad.c | 803 u8 *ciphertext, const u8 *plaintext) in khazad_crypt() argument 805 const __be64 *src = (const __be64 *)plaintext; in khazad_crypt()
|
D | anubis.c | 573 u8 *ciphertext, const u8 *plaintext, const int R) in anubis_crypt() argument 575 const __be32 *src = (const __be32 *)plaintext; in anubis_crypt()
|
D | testmgr.c | 1257 kv.iov_base = (void *)vec->plaintext; in build_hash_sglist() 1723 generate_random_bytes(rng, (u8 *)vec->plaintext, vec->psize); in generate_random_hash_testvec() 1745 vec->digest_error = crypto_shash_digest(desc, vec->plaintext, in generate_random_hash_testvec() 1845 vec.plaintext = kmalloc(maxdatasize, GFP_KERNEL); in test_hash_vs_generic_impl() 1847 if (!vec.key || !vec.plaintext || !vec.digest) { in test_hash_vs_generic_impl() 1869 kfree(vec.plaintext); in test_hash_vs_generic_impl()
|
/linux-6.12.1/net/sunrpc/auth_gss/ |
D | gss_krb5_test.c | 30 const struct xdr_netobj *plaintext; member 76 .head[0].iov_len = param->plaintext->len, in checksum_case() 77 .len = param->plaintext->len, in checksum_case() 103 memcpy(buf.head[0].iov_base, param->plaintext->data, buf.head[0].iov_len); in checksum_case() 235 .plaintext = &nfold_test1_plaintext, 241 .plaintext = &nfold_test2_plaintext, 247 .plaintext = &nfold_test3_plaintext, 253 .plaintext = &nfold_test4_plaintext, 259 .plaintext = &nfold_test5_plaintext, 265 .plaintext = &nfold_test6_plaintext, [all …]
|
/linux-6.12.1/tools/verification/models/ |
D | wwnr.dot | 2 {node [shape = plaintext, style=invis, label=""] "__init_not_running"}; 4 {node [shape = plaintext] "not_running"}; 5 {node [shape = plaintext] "running"};
|
D | wip.dot | 3 {node [shape = plaintext, style=invis, label=""] "__init_preemptive"};
|
/linux-6.12.1/Documentation/admin-guide/blockdev/drbd/ |
D | drbd-connection-state-overview.dot | 6 node [shape=plaintext]
|
/linux-6.12.1/Documentation/crypto/ |
D | userspace-if.rst | 93 If a consumer on the other hand wants to maintain the plaintext and the 237 with the plaintext / ciphertext. See below for the memory structure. 263 - plaintext or ciphertext 277 - AEAD encryption input: AAD \|\| plaintext 286 - AEAD decryption output: plaintext
|
D | devel-algos.rst | 132 contains the plaintext and will contain the ciphertext. Please refer
|
/linux-6.12.1/drivers/virt/coco/sev-guest/ |
D | sev-guest.c | 267 void *plaintext, size_t len) in __enc_payload() argument 275 return enc_dec_message(crypto, msg, plaintext, msg->payload, len, true); in __enc_payload() 279 void *plaintext, size_t len) in dec_payload() argument 288 return enc_dec_message(crypto, msg, msg->payload, plaintext, len, false); in dec_payload()
|
/linux-6.12.1/Documentation/block/ |
D | inline-encryption.rst | 283 its integrity information is calculated (using the plaintext data, since 287 must not store the integrity info that it received with the plaintext data 288 since that might reveal information about the plaintext data. As such, it must 290 instead. Another issue with storing the integrity info of the plaintext data is 294 ciphertext, not that of the plaintext).
|
/linux-6.12.1/Documentation/security/keys/ |
D | ecryptfs.rst | 28 In order to avoid known-plaintext attacks, the datablob obtained through
|
/linux-6.12.1/Documentation/virt/kvm/s390/ |
D | s390-pv-boot.rst | 15 On IPL (boot) a small plaintext bootloader is started, which provides
|
/linux-6.12.1/Documentation/filesystems/ |
D | fscrypt.rst | 90 plaintext file contents or filenames from other users on the same 241 "tweak" the encryption of each file so that the same plaintext in two 323 plaintext filenames, the KDF is also used to derive a 128-bit 527 With CBC-CTS, the IV reuse means that when the plaintext filenames share a 533 All supported filenames encryption modes accept any plaintext length 830 encrypted using that key appear "unlocked", i.e. in plaintext form. 955 be in plaintext form or in ciphertext form) is global. This mismatch 1224 for an encrypted file contains the plaintext, not the ciphertext. 1418 plaintext must be preserved. Instead, filesystems must encrypt into a 1435 plaintext filenames, since the plaintext filenames are unavailable [all …]
|
D | fsverity.rst | 595 fs-verity. In this case, the plaintext data is verified rather than 608 when the file is, since it contains hashes of the plaintext data. 892 file contents are, because it stores hashes of the plaintext
|
/linux-6.12.1/Documentation/trace/rv/ |
D | deterministic_automata.rst | 117 {node [shape = plaintext, style=invis, label=""] "__init_preemptive"};
|
/linux-6.12.1/Documentation/virt/kvm/x86/ |
D | hypercalls.rst | 185 * bit 4 - plaintext = 0, encrypted = 1
|
/linux-6.12.1/Documentation/power/ |
D | swsusp.rst | 329 your sensitive data are then stored in plaintext on disk. This means
|
/linux-6.12.1/Documentation/admin-guide/cifs/ |
D | usage.rst | 644 does not work with lanman or plaintext authentication.
|
/linux-6.12.1/Documentation/virt/kvm/ |
D | api.rst | 4787 engine uses a tweak such that two identical plaintext pages, each at 4789 moving ciphertext of those pages will not result in plaintext being
|