| /Linux-v5.10/crypto/ |
| D | testmgr.h | 39 const char *plaintext; member
2401 .plaintext = "",
2405 .plaintext = "a",
2410 .plaintext = "abc",
2415 .plaintext = "message digest",
2420 .plaintext = "abcdefghijklmnopqrstuvwxyz",
2425 .plaintext = "ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz0123456789",
2430 .plaintext = "123456789012345678901234567890123456789012345678901234567890123"
2440 .plaintext = "",
2446 .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 | 1131 kv.iov_base = (void *)vec->plaintext; in build_hash_sglist()
1603 generate_random_bytes((u8 *)vec->plaintext, vec->psize); in generate_random_hash_testvec()
1625 vec->digest_error = crypto_shash_digest(desc, vec->plaintext, in generate_random_hash_testvec()
1722 vec.plaintext = kmalloc(maxdatasize, GFP_KERNEL); in test_hash_vs_generic_impl()
1724 if (!vec.key || !vec.plaintext || !vec.digest) { in test_hash_vs_generic_impl()
1745 kfree(vec.plaintext); in test_hash_vs_generic_impl()
|
| D | Kconfig | 437 with the plaintext blocks to get the ciphertext. Flipping a bit in the
438 ciphertext produces a flipped bit in the plaintext at the same
|
| /Linux-v5.10/Documentation/admin-guide/blockdev/drbd/ |
| D | drbd-connection-state-overview.dot | 6 node [shape=plaintext]
|
| /Linux-v5.10/Documentation/block/ |
| D | inline-encryption.rst | 243 its integrity information is calculated (using the plaintext data, since
247 must not store the integrity info that it received with the plaintext data
248 since that might reveal information about the plaintext data. As such, it must
250 instead. Another issue with storing the integrity info of the plaintext data is
254 ciphertext, not that of the plaintext).
|
| /Linux-v5.10/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-v5.10/Documentation/security/keys/ |
| D | ecryptfs.rst | 28 In order to avoid known-plaintext attacks, the datablob obtained through
|
| /Linux-v5.10/net/bluetooth/ |
| D | amp.c | 128 static int hmac_sha256(u8 *key, u8 ksize, char *plaintext, u8 psize, u8 *output) in hmac_sha256() argument
158 ret = crypto_shash_digest(shash, plaintext, psize, output); in hmac_sha256()
|
| /Linux-v5.10/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
407 With CTS-CBC, the IV reuse means that when the plaintext filenames
413 All supported filenames encryption modes accept any plaintext length
679 encrypted using that key appear "unlocked", i.e. in plaintext form.
804 be in plaintext form or in ciphertext form) is global. This mismatch
1069 than the plaintext due to NUL-padding and an extra 2-byte overhead.
1078 for an encrypted file contains the plaintext, not the ciphertext.
1199 plaintext must be preserved. Instead, filesystems must encrypt into a
[all …]
|
| D | fsverity.rst | 423 fs-verity. In this case, the plaintext data is verified rather than
436 when the file is, since it contains hashes of the plaintext data.
719 file contents are, because it stores hashes of the plaintext
|
| /Linux-v5.10/Documentation/virt/kvm/ |
| D | s390-pv-boot.rst | 15 On IPL (boot) a small plaintext bootloader is started, which provides
|
| D | api.rst | 4240 engine uses a tweak such that two identical plaintext pages, each at
4242 moving ciphertext of those pages will not result in plaintext being
|
| /Linux-v5.10/arch/x86/crypto/ |
| D | aesni-intel_asm.S | 374 # (r13 is the number of bytes in plaintext mod 16)
666 # r16-r13 is the number of bytes in plaintext mod 16)
837 # write back plaintext/ciphertext for num_initial_blocks
845 # prepare plaintext/ciphertext for GHASH computation
1331 movdqu \XMM1, (%arg3,%r11,1) # Write to plaintext buffer
1335 movdqu \XMM2, 16(%arg3,%r11,1) # Write to plaintext buffer
1339 movdqu \XMM3, 32(%arg3,%r11,1) # Write to plaintext buffer
1343 movdqu \XMM4, 48(%arg3,%r11,1) # Write to plaintext buffer
|
| D | aesni-intel_avx-x86_64.S | 309 mov arg5, %r13 # save the number of bytes of plaintext/ciphertext
451 # number of bytes in plaintext mod 16)
467 # (r13 is the number of bytes in plaintext mod 16)
775 # r16-r13 is the number of bytes in plaintext mod 16)
994 ## if a = number of total plaintext bytes
1942 ## if a = number of total plaintext bytes
|
| /Linux-v5.10/Documentation/admin-guide/cifs/ |
| D | usage.rst | 644 does not work with lanman or plaintext authentication.
734 plaintext, ntlm, ntlmv2, signing allowed). Some
736 options to be enabled (lanman and plaintext require
738 plaintext authentication currently requires also
756 may use plaintext passwords 0x00020
757 must use plaintext passwords 0x20020
|
| /Linux-v5.10/Documentation/power/ |
| D | swsusp.rst | 329 your sensitive data are then stored in plaintext on disk. This means
|
