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.
259 Including the inode number in the IVs was considered.  However, it was
317 per-file keys.  However, it depends on the security of two primitives,
326 to individual filesystems.  However, authenticated encryption (AE)
357 However, each encrypted directory still uses a unique key; or
369 >= 16 bytes; cipher block alignment is not required.  However,
449   FS_IOC_SET_ENCRYPTION_POLICY is executed.  However, it must be added
480 FS_IOC_SET_ENCRYPTION_POLICY is executing.  However, if the new
525 recommended to use when possible.  However, on older kernels only the
580 encryption policy, if any, for a directory or regular file.  However,
655   not need any privileges.  However, the number of keys that can be
669 However, if another user has added the key, it may be desirable to
736 with a filesystem-specific prefix such as "ext4:".  However, the
791 For v2 policy keys, this ioctl is usable by non-root users.  However,
808 still open.  However, if necessary, this ioctl can be executed again
937 after all, the encryption is intended to be transparent.  However,
943   enforcement`_.  Attempts to do so will fail with EXDEV.  However,
1136 However, for very long filenames, base64 encoding would cause the
1168 No tests should fail.  However, tests that use non-default encryption