Comment 26 for bug 1756840

Any news or progress on this? I've been fighting with installing ecryptfs now for days (first time using it) after installing Ubuntu 18 by following these instructions: https://www.howtogeek.com/116032/how-to-encrypt-your-home-folder-after-installing-ubuntu/amp/.

These instructions fail with rsync errors, but the usable encrypted home dir does get created, and when testing recovering an encrypted home from a live USB I ran into problem after problem (these instructions fail badly: https://www.howtogeek.com/116297/how-to-recover-an-encrypted-home-directory-on-ubuntu/amp/), but using the "Recovering Your Data Manually" instructions here (https://help.ubuntu.com/community/EncryptedPrivateDirectory#Recovering_Your_Data_Manually) does indeed work, so I feel somewhat better about using ecryptfs now.

My final solution may be to use the encrypted home I've got now, that is in fact recoverable from a live USB, but I need to go back and manually use rsync to copy from old home to new home again, fixing copy errors as I go which occur because some file names are too long since ecryptfs reduces max usable file name length since part of the name stores encryption info.

Am I on the right track to a good and viable solution? Or should I wait for Ubuntu 18 to fix this confusing mess and then reinstall using an official installer? Will fscrypt, which is supposed to be much faster and better than ecryptfs, ever be fully supported? When?

Is an encrypted home using ecryptfs known to be buggy or unusable in the long term even though it boots and appears to work now?

What should I do?