| fscrypt.rst (23d19ba06b9c5614d6457f5fed349ec8f6d4dac9) | fscrypt.rst (643fa9612bf1a29153eee46fd398117632f93cbe) |
|---|---|
| 1===================================== 2Filesystem-level encryption (fscrypt) 3===================================== 4 5Introduction 6============ 7 8fscrypt is a library which filesystems can hook into to support --- 329 unchanged lines hidden (view full) --- 338 different from the one specified 339- ``EINVAL``: an invalid encryption policy was specified (invalid 340 version, mode(s), or flags) 341- ``ENOTDIR``: the file is unencrypted and is a regular file, not a 342 directory 343- ``ENOTEMPTY``: the file is unencrypted and is a nonempty directory 344- ``ENOTTY``: this type of filesystem does not implement encryption 345- ``EOPNOTSUPP``: the kernel was not configured with encryption | 1===================================== 2Filesystem-level encryption (fscrypt) 3===================================== 4 5Introduction 6============ 7 8fscrypt is a library which filesystems can hook into to support --- 329 unchanged lines hidden (view full) --- 338 different from the one specified 339- ``EINVAL``: an invalid encryption policy was specified (invalid 340 version, mode(s), or flags) 341- ``ENOTDIR``: the file is unencrypted and is a regular file, not a 342 directory 343- ``ENOTEMPTY``: the file is unencrypted and is a nonempty directory 344- ``ENOTTY``: this type of filesystem does not implement encryption 345- ``EOPNOTSUPP``: the kernel was not configured with encryption |
| 346 support for this filesystem, or the filesystem superblock has not | 346 support for filesystems, or the filesystem superblock has not |
| 347 had encryption enabled on it. (For example, to use encryption on an | 347 had encryption enabled on it. (For example, to use encryption on an |
| 348 ext4 filesystem, CONFIG_EXT4_ENCRYPTION must be enabled in the | 348 ext4 filesystem, CONFIG_FS_ENCRYPTION must be enabled in the |
| 349 kernel config, and the superblock must have had the "encrypt" 350 feature flag enabled using ``tune2fs -O encrypt`` or ``mkfs.ext4 -O 351 encrypt``.) 352- ``EPERM``: this directory may not be encrypted, e.g. because it is 353 the root directory of an ext4 filesystem 354- ``EROFS``: the filesystem is readonly 355 356Getting an encryption policy --- 285 unchanged lines hidden --- | 349 kernel config, and the superblock must have had the "encrypt" 350 feature flag enabled using ``tune2fs -O encrypt`` or ``mkfs.ext4 -O 351 encrypt``.) 352- ``EPERM``: this directory may not be encrypted, e.g. because it is 353 the root directory of an ext4 filesystem 354- ``EROFS``: the filesystem is readonly 355 356Getting an encryption policy --- 285 unchanged lines hidden --- |