Lines Matching full:files
9 transparent encryption of files and directories.
26 at the block device level. This allows it to encrypt different files
27 with different keys and to have unencrypted files on the same
35 UBIFS. This allows encrypted files to be read and written without
38 unencrypted files. Similarly, half as many dentries and inodes are
44 fscrypt does not support encrypting files in-place. Instead, it
46 userspace provides the key, all regular files, directories, and
63 files is not protected.
122 - Per-file keys for in-use files will *not* be removed or wiped.
124 encrypted files and directories before removing a master key, as
156 with another user's encrypted files to which they have read-only
158 used by the other user's accesses to those files, even if the other
240 Since each master key can protect many files, it is necessary to
242 files doesn't map to the same ciphertext, or vice versa. In most
450 before any files can be created in the encrypted directory.
465 files, directories (recursively), and symlinks created in the
473 regular files and directories, including nonempty directories.
611 the filesystem, making all files on the filesystem which were
708 locked/unlocked status of encrypted files (i.e. whether they appear to
712 access encrypted files.
805 try to "lock" all files that had been unlocked with the key. It won't
806 lock files that are still in-use, so this ioctl is expected to be used
807 in cooperation with userspace ensuring that none of the files are
809 later to retry locking any remaining files.
812 (but may still have files remaining to be locked), the user's claim to
813 the key was removed, or the key was already removed but had files
832 files locked; or, the user does not have a claim to the key (but
895 secret has been removed, but some files are still in use; i.e.,
935 With the encryption key, encrypted regular files, directories, and
940 - Unencrypted files, or files encrypted with a different encryption
944 encrypted files can be renamed within an encrypted directory, or
951 all files encrypted from the very beginning. The `shred` program
952 may be used to overwrite the source files but isn't guaranteed to be
955 - Direct I/O is not supported on encrypted files. Attempts to use
956 direct I/O on such files will fall back to buffered I/O.
960 on encrypted files and will fail with EOPNOTSUPP.
962 - Online defragmentation of encrypted files is not supported. The
967 regular files. It will fall back to ordered data mode instead.
969 - DAX (Direct Access) is not supported on encrypted files.
989 files, directories, and symlinks even before their encryption key has
1005 - Files may be deleted. That is, nondirectory files may be deleted
1014 Without the key, regular files cannot be opened or truncated.
1019 Also without the key, files of any type (including directories) cannot
1025 It is not currently possible to backup and restore encrypted files
1033 files, directories, and symbolic links created in that directory
1034 (recursively) will inherit that encryption policy. Special files ---
1038 Except for those special files, it is forbidden to have unencrypted
1039 files, or files encrypted with a different encryption policy, in an
1091 different files to be encrypted differently; see `Per-file keys`_ and
1097 For the read path (->readpage()) of regular files, filesystems can
1102 For the write path (->writepage()) of regular files, filesystems
1176 option. This option causes all new files to be automatically