Details
-
New Feature
-
Resolution: Fixed
-
Minor
-
None
-
9223372036854775807
Description
This ticket is a place-holder to describe work to be done for client-side file name encryption. This is a follow-up of LU-12275, so all principles and concepts detailed there are still valid.
In particular, filename encryption principles are explained in this document:
https://jira.whamcloud.com/secure/attachment/32657/lustre_encryption_modes_usage.txt
Further details will be added as the feature design makes progress.
Attachments
Issue Links
- is related to
-
LU-15027 sanity-sec: crash in __list_add_valid() during sanity-sec test_47
- Resolved
-
LU-15406 Using the native fscrypt for Ubuntu20 5.4 kernel fails several migration test
- Resolved
-
LU-15407 fscrypt does not work on Ubuntu 5.8 kernel
- Resolved
-
LU-15810 Migrated encrypted directory lacks on-disk encryption flag and context
- Resolved
-
LU-15922 Interop: sanity-sec test_46: File name too long
- Resolved
-
LU-15848 ldiskfs: escape encrypted file names
- Resolved
-
LU-15827 BUG: KASAN: slab-out-of-bounds in osd_ldiskfs_filldir+0x16c2/0x1860 [osd_ldiskfs]
- Resolved
-
LU-16085 Ubuntu 22.04 sanityn test_106c: supported stx_attributes: got '2030', expected '30'
- Resolved
- is related to
-
LU-15928 pass key length as part of index API
- Open
-
LU-15787 clients built without encryption support can corrupt encrypted directories
- Resolved
-
LU-15855 Return -ENOKEY to encrypt-unaware clients if filename is missing
- Resolved
-
LU-15911 Make enable_filename_encryption tunable only available with embedded llcrypt
- Resolved
-
LU-12275 Client-side file data encryption
- Resolved
-
LU-14677 lfs migrate/mirror of encrypted files
- Resolved