Lines Matching refs:filenames

30 However, except for filenames, fscrypt does not encrypt filesystem
39 needed.  eCryptfs also limits encrypted filenames to 143 bytes,
57 protects the confidentiality of file contents and filenames in the
90 plaintext file contents or filenames from other users on the same
137 - In general, decrypted contents and filenames in the kernel VFS
179 greater of the security strength of the contents and filenames
263 suitable for both contents and filenames encryption, and it accepts
272 (contents or filenames) is encrypted, the file's 16-byte nonce is
290 key and a single filenames encryption key.  To still encrypt different
323 plaintext filenames, the KDF is also used to derive a 128-bit
324 SipHash-2-4 key per directory in order to hash filenames.  This works
333 and one encryption mode to be specified for filenames.  Different
337 - AES-256-XTS for contents and AES-256-CTS-CBC for filenames
338 - AES-128-CBC for contents and AES-128-CTS-CBC for filenames
339 - Adiantum for both contents and filenames
340 - AES-256-XTS for contents and AES-256-HCTR2 for filenames (v2 policies only)
409 For filenames, each full filename is encrypted at once.  Because of
411 filenames of up to 255 bytes, the same IV is used for every filename
419 With CTS-CBC, the IV reuse means that when the plaintext filenames share a
421 corresponding encrypted filenames will also share a common prefix.  This is
425 All supported filenames encryption modes accept any plaintext length
427 filenames shorter than 16 bytes are NUL-padded to 16 bytes before
429 via their ciphertexts, all filenames are NUL-padded to the next 4, 8,
433 not otherwise a valid character in filenames, the padding will never
437 encrypted in the same way as filenames in directory entries, except
494     encrypting filenames.  If unsure, use FSCRYPT_POLICY_FLAGS_PAD_32
534 The filenames in the directory's entries will be encrypted as well.
1096 - Directories may be listed, in which case the filenames will be
1100   guaranteed that the presented filenames will be no longer than
1113   in encrypted form, similar to filenames in directories.  Hence, they
1295 plaintext filenames, since the plaintext filenames are unavailable
1296 without the key.  (Hashing the plaintext filenames would also make it
1298 directories.)  Instead, filesystems hash the ciphertext filenames,
1305 filenames.  Therefore, readdir() must base64url-encode the ciphertext
1306 for presentation.  For most filenames, this works fine; on ->lookup(),
1310 However, for very long filenames, base64url encoding would cause the
1312 actually presents long filenames in an abbreviated form which encodes
1320 Note that the precise way that filenames are presented to userspace
1322 as a way to temporarily present valid filenames so that commands like