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.
368 For file contents, each filesystem block is encrypted independently.
376 is encrypted with AES-256 where the AES-256 key is the SHA-256 hash
392 encrypted files, e.g. via "collapse range" or "insert range".
397 For filenames, each full filename is encrypted at once. Because of
402 However, each encrypted directory still uses a unique key, or
409 bytes for AES), the corresponding encrypted filenames will also share
416 being encrypted. In addition, to reduce leakage of filename lengths
425 encrypted in the same way as filenames in directory entries, except
471 For new encrypted directories, use v2 policies.
505 before any files can be created in the encrypted directory.
515 If the file is not yet encrypted, then FS_IOC_SET_ENCRYPTION_POLICY
518 encrypted directory. After that, and after providing the
521 directory will be encrypted, inheriting the same encryption policy.
522 The filenames in the directory's entries will be encrypted as well.
524 Alternatively, if the file is already encrypted, then
536 encrypted directory does not need to be accessed immediately, then the
540 encrypted, even if it is empty. Users who want to encrypt an entire
548 - ``EEXIST``: the file is already encrypted with an encryption policy
569 - ``EPERM``: this directory may not be encrypted, e.g. because it is
615 - ``EINVAL``: the file is encrypted, but it uses an unrecognized
617 - ``ENODATA``: the file is not encrypted
624 - ``EOVERFLOW``: the file is encrypted and uses a recognized
628 Note: if you only need to know whether a file is encrypted or not, on
646 encrypted using a newer encryption policy version.
664 On encrypted files and directories it gets the inode's 16-byte nonce.
679 encrypted using that key appear "unlocked", i.e. in plaintext form.
803 locked/unlocked status of encrypted files (i.e. whether they appear to
807 access encrypted files.
1013 for determining whether the key for a given encrypted directory needs
1030 With the encryption key, encrypted regular files, directories, and
1035 - Unencrypted files, or files encrypted with a different encryption
1037 linked into an encrypted directory; see `Encryption policy
1039 encrypted files can be renamed within an encrypted directory, or
1042 Note: "moving" an unencrypted file into an encrypted directory, e.g.
1046 all files encrypted from the very beginning. The `shred` program
1050 - Direct I/O is not supported on encrypted files. Attempts to use
1054 FALLOC_FL_INSERT_RANGE are not supported on encrypted files and will
1057 - Online defragmentation of encrypted files is not supported. The
1061 - The ext4 filesystem does not support data journaling with encrypted
1064 - DAX (Direct Access) is not supported on encrypted files.
1066 - The st_size of an encrypted symlink will not necessarily give the
1071 - The maximum length of an encrypted symlink is 2 bytes shorter than
1074 to 4095 bytes long, while encrypted symlinks can only be up to 4093
1078 for an encrypted file contains the plaintext, not the ciphertext.
1083 Some filesystem operations may be performed on encrypted regular
1098 present and are not encrypted or encoded.
1106 in encrypted form, similar to filenames in directories. Hence, they
1115 be created or linked into an encrypted directory, nor can a name in an
1116 encrypted directory be the source or target of a rename, nor can an
1117 O_TMPFILE temporary file be created in an encrypted directory. All
1120 It is not currently possible to backup and restore encrypted files
1131 not be encrypted.
1134 files, or files encrypted with a different encryption policy, in an
1135 encrypted directory tree. Attempts to link or rename such a file into
1136 an encrypted directory will fail with EXDEV. This is also enforced
1186 different files to be encrypted differently; see `Per-file encryption
1230 impossible for the filesystem's fsck tool to optimize encrypted
1256 ``rm -r`` work as expected on encrypted directories.
1287 encrypted with a dummy key, without having to make any API calls.
1288 This tests the encrypted I/O paths more thoroughly. To do this with