Comment 59 for bug 344878

John Johansen (jjohansen) wrote :

Update on the current status
* the on disk format is NOT stable. Changes will likely be made during the upstreaming review cycle.
** If you have data stored using the test kernel, the migration process will be to copy your data out of ecryptfs, update your kernel and then copy your data back in.* the current patch use the xattr storage method
* development on storing long name in file headers isn't stable yet and is eating data (it is not included in the above test kernel)
* the on disk format is not stable. Changes will likely be made during the upstreaming review cycle.
** If you have data stored using the test kernel, the migration process will be to copy your data out of ecryptfs, update your kernel and then copy your data back in.
* the userspace tools have not been updated to make configuring longname support easy has not been done yet
** the test kernels have it enabled by default
** to change it to off requires doing a manual mount (remount won't work) passing the flag -o ecryptfs_no_longname_xattr

A ppa a kernel containing the patch is being set up at
https://launchpad.net/~jjohansen/+archive/ecryptfs-kernel-dev