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 key length needed by the contents and filenames
268 suitable for both contents and filenames encryption, and it accepts
277 filenames) is encrypted, the file's 16-byte nonce is included in the
299 and one encryption mode to be specified for filenames.  Different
303 - AES-256-XTS for contents and AES-256-CTS-CBC for filenames
304 - AES-128-CBC for contents and AES-128-CTS-CBC for filenames
305 - Adiantum for both contents and filenames
352 For filenames, each full filename is encrypted at once.  Because of
354 filenames of up to 255 bytes, the same IV is used for every filename
362 With CTS-CBC, the IV reuse means that when the plaintext filenames
364 bytes for AES), the corresponding encrypted filenames will also share
368 All supported filenames encryption modes accept any plaintext length
370 filenames shorter than 16 bytes are NUL-padded to 16 bytes before
372 via their ciphertexts, all filenames are NUL-padded to the next 4, 8,
376 not otherwise a valid character in filenames, the padding will never
380 encrypted in the same way as filenames in directory entries, except
436   filenames.  If unsure, use FSCRYPT_POLICY_FLAGS_PAD_32 (0x3).
467 The filenames in the directory's entries will be encrypted as well.
994 - Directories may be listed, in which case the filenames will be
998   guaranteed that the presented filenames will be no longer than
1011   in encrypted form, similar to filenames in directories.  Hence, they
1121 plaintext filenames, since the plaintext filenames are unavailable
1122 without the key.  (Hashing the plaintext filenames would also make it
1124 directories.)  Instead, filesystems hash the ciphertext filenames,
1131 filenames.  Therefore, readdir() must base64-encode the ciphertext for
1132 presentation.  For most filenames, this works fine; on ->lookup(), the
1136 However, for very long filenames, base64 encoding would cause the
1138 actually presents long filenames in an abbreviated form which encodes
1146 Note that the precise way that filenames are presented to userspace
1148 as a way to temporarily present valid filenames so that commands like