Lines Matching full:however

30 However, except for filenames, fscrypt does not encrypt filesystem
110 However, fscrypt allows encryption keys to be removed from the kernel,
120 However, these ioctls have some limitations:
142   to your kernel command line.  However, this has a performance cost.
328 per-file keys.  However, it depends on the security of two primitives,
337 to individual filesystems.  However, authenticated encryption (AE)
374 However, each encrypted directory still uses a unique key, or
386 >= 16 bytes; cipher block alignment is not required.  However,
469   FS_IOC_SET_ENCRYPTION_POLICY is executed.  However, it must be added
500 FS_IOC_SET_ENCRYPTION_POLICY is executing.  However, if the new
545 recommended to use when possible.  However, on older kernels only the
600 encryption policy, if any, for a directory or regular file.  However,
675   not need any privileges.  However, the number of keys that can be
689 However, if another user has added the key, it may be desirable to
756 with a filesystem-specific prefix such as "ext4:".  However, the
811 For v2 policy keys, this ioctl is usable by non-root users.  However,
828 still open.  However, if necessary, this ioctl can be executed again
957 after all, the encryption is intended to be transparent.  However,
963   enforcement`_.  Attempts to do so will fail with EXDEV.  However,
1156 However, for very long filenames, base64 encoding would cause the
1188 No tests should fail.  However, tests that use non-default encryption