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
84 hide the plaintext file contents or filenames from other users on the
115 greater of the key length needed by the contents and filenames
142   contents encryption and as a CTS-CBC key for filenames encryption
151 - Per-file keys strengthen the encryption of filenames, where IVs are
188 and one encryption mode to be specified for filenames.  Different
192 - AES-256-XTS for contents and AES-256-CTS-CBC for filenames
193 - AES-128-CBC for contents and AES-128-CTS-CBC for filenames
194 - Speck128/256-XTS for contents and Speck128/256-CTS-CBC for filenames
223 For filenames, the full filename is encrypted at once.  Because of the
225 filenames of up to 255 bytes, a constant initialization vector (IV) is
229 filenames share a common prefix at least as long as the cipher block
230 size (16 bytes for AES), the corresponding encrypted filenames will
236 Since filenames are encrypted with the CTS-CBC mode of operation, the
237 plaintext and ciphertext filenames need not be multiples of the AES
239 encrypted is 16 bytes, so shorter filenames are NUL-padded to 16 bytes
241 lengths via their ciphertexts, all filenames are NUL-padded to the
245 (``\0``) is not otherwise a valid character in filenames, the padding
249 encrypted in the same way as filenames in directory entries.  Each
287   filenames.  If unsure, use FS_POLICY_FLAGS_PAD_32 (0x3).
305 The filenames in the directory's entries will be encrypted as well.
482 - Directories may be listed, in which case the filenames will be
486   guaranteed that the presented filenames will be no longer than
499   in encrypted form, similar to filenames in directories.  Hence, they
598 plaintext filenames, since the plaintext filenames are unavailable
599 without the key.  (Hashing the plaintext filenames would also make it
601 directories.)  Instead, filesystems hash the ciphertext filenames,
608 filenames.  Therefore, readdir() must base64-encode the ciphertext for
609 presentation.  For most filenames, this works fine; on ->lookup(), the
613 However, for very long filenames, base64 encoding would cause the
615 actually presents long filenames in an abbreviated form which encodes
623 Note that the precise way that filenames are presented to userspace
625 as a way to temporarily present valid filenames so that commands like