Lines Matching full: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
394 Filenames encryption
397 For filenames, each full filename is encrypted at once.  Because of
399 filenames of up to 255 bytes, the same IV is used for every filename
407 With CTS-CBC, the IV reuse means that when the plaintext filenames
409 bytes for AES), the corresponding encrypted filenames will also share
413 All supported filenames encryption modes accept any plaintext length
415 filenames shorter than 16 bytes are NUL-padded to 16 bytes before
417 via their ciphertexts, all filenames are NUL-padded to the next 4, 8,
421 not otherwise a valid character in filenames, the padding will never
425 encrypted in the same way as filenames in directory entries, except
482     encrypting filenames.  If unsure, use FSCRYPT_POLICY_FLAGS_PAD_32
522 The filenames in the directory's entries will be encrypted as well.
1089 - Directories may be listed, in which case the filenames will be
1093   guaranteed that the presented filenames will be no longer than
1106   in encrypted form, similar to filenames in directories.  Hence, they
1228 plaintext filenames, since the plaintext filenames are unavailable
1229 without the key.  (Hashing the plaintext filenames would also make it
1231 directories.)  Instead, filesystems hash the ciphertext filenames,
1238 filenames.  Therefore, readdir() must base64-encode the ciphertext for
1239 presentation.  For most filenames, this works fine; on ->lookup(), the
1243 However, for very long filenames, base64 encoding would cause the
1245 actually presents long filenames in an abbreviated form which encodes
1253 Note that the precise way that filenames are presented to userspace
1255 as a way to temporarily present valid filenames so that commands like