Lines Matching refs:encrypted
35 UBIFS. This allows encrypted files to be read and written without
36 caching both the decrypted and encrypted pages in the pagecache,
39 needed. eCryptfs also limits encrypted filenames to 143 bytes,
45 supports marking an empty directory as encrypted. Then, after
48 encrypted.
118 "locked", i.e. in ciphertext or encrypted form.
124 encrypted files and directories before removing a master key, as
126 encrypted directory.
156 with another user's encrypted files to which they have read-only
169 policies on all new encrypted directories.
177 Each encrypted directory tree is protected by a *master key*. Master
185 To "unlock" an encrypted directory tree, userspace must provide the
244 encrypted inode (regular file, directory, or symlink) is created,
272 (contents or filenames) is encrypted, the file's 16-byte nonce is
327 encrypted directories use this style of hashing.
380 For file contents, each filesystem block is encrypted independently.
388 is encrypted with AES-256 where the AES-256 key is the SHA-256 hash
404 encrypted files, e.g. via "collapse range" or "insert range".
409 For filenames, each full filename is encrypted at once. Because of
414 However, each encrypted directory still uses a unique key, or
421 corresponding encrypted filenames will also share a common prefix. This is
428 being encrypted. In addition, to reduce leakage of filename lengths
437 encrypted in the same way as filenames in directory entries, except
483 For new encrypted directories, use v2 policies.
517 before any files can be created in the encrypted directory.
527 If the file is not yet encrypted, then FS_IOC_SET_ENCRYPTION_POLICY
530 encrypted directory. After that, and after providing the
533 directory will be encrypted, inheriting the same encryption policy.
534 The filenames in the directory's entries will be encrypted as well.
536 Alternatively, if the file is already encrypted, then
548 encrypted directory does not need to be accessed immediately, then the
552 encrypted, even if it is empty. Users who want to encrypt an entire
560 - ``EEXIST``: the file is already encrypted with an encryption policy
581 - ``EPERM``: this directory may not be encrypted, e.g. because it is
627 - ``EINVAL``: the file is encrypted, but it uses an unrecognized
629 - ``ENODATA``: the file is not encrypted
636 - ``EOVERFLOW``: the file is encrypted and uses a recognized
640 Note: if you only need to know whether a file is encrypted or not, on
658 encrypted using a newer encryption policy version.
676 On encrypted files and directories it gets the inode's 16-byte nonce.
691 encrypted using that key appear "unlocked", i.e. in plaintext form.
815 locked/unlocked status of encrypted files (i.e. whether they appear to
819 access encrypted files.
1025 for determining whether the key for a given encrypted directory needs
1042 With the encryption key, encrypted regular files, directories, and
1047 - Unencrypted files, or files encrypted with a different encryption
1049 linked into an encrypted directory; see `Encryption policy
1051 encrypted files can be renamed within an encrypted directory, or
1054 Note: "moving" an unencrypted file into an encrypted directory, e.g.
1058 all files encrypted from the very beginning. The `shred` program
1062 - Direct I/O is supported on encrypted files only under some
1066 FALLOC_FL_INSERT_RANGE are not supported on encrypted files and will
1069 - Online defragmentation of encrypted files is not supported. The
1073 - The ext4 filesystem does not support data journaling with encrypted
1076 - DAX (Direct Access) is not supported on encrypted files.
1078 - The maximum length of an encrypted symlink is 2 bytes shorter than
1081 to 4095 bytes long, while encrypted symlinks can only be up to 4093
1085 for an encrypted file contains the plaintext, not the ciphertext.
1090 Some filesystem operations may be performed on encrypted regular
1105 present and are not encrypted or encoded.
1113 in encrypted form, similar to filenames in directories. Hence, they
1122 be created or linked into an encrypted directory, nor can a name in an
1123 encrypted directory be the source or target of a rename, nor can an
1124 O_TMPFILE temporary file be created in an encrypted directory. All
1127 It is not currently possible to backup and restore encrypted files
1138 not be encrypted.
1141 files, or files encrypted with a different encryption policy, in an
1142 encrypted directory tree. Attempts to link or rename such a file into
1143 an encrypted directory will fail with EXDEV. This is also enforced
1167 (I/O requests) to specify how the data will be encrypted or decrypted
1197 For direct I/O on an encrypted file to work, the following conditions
1213 encrypted file will fall back to buffered I/O.
1258 different files to be encrypted differently; see `Per-file encryption
1297 impossible for the filesystem's fsck tool to optimize encrypted
1323 ``rm -r`` work as expected on encrypted directories.
1354 encrypted with a dummy key, without having to make any API calls.
1355 This tests the encrypted I/O paths more thoroughly. To do this with