Public bug reported: I am trying to use fscrypt in place of ecryptfs to encrypt my home directory, and to automatically unlock/lock it on login and logout. I am using a fresh installation of Ubuntu 18.04 done on 05/01/18. The hardware is a Dell Precision 5520 laptop. The version of the fscrypt and libpam-fscrypt packages is 0.2.2-0ubuntu2.
I began with the instructions in https://github.com/google/fscrypt #setting-up-fscrypt-on-a-directory. I quickly ran into bug #1754270, but after applying the workaround from that bug report I was able to successfully encrypt a directory. With that out of the way, I set up a new encrypted home directory, copied all of my files into it with rsync, then moved it on top of the old home directory. When I logged out and logged back in, I was presented with a blank screen. The cursor was visible and responded to trackpad motion. If I clicked the top right of the screen, I saw the usual drop-down menu containing power settings and the like. I didn't see any other responses to clicks or keypresses. Hitting ctrl-alt-fn-f1 brought me back to the login screen. If I tried to login again, this time the desktop came up normally and everything appeared to be working. All of this suggests some sort of broken interaction here between pam_fscrypt.so and the rest of the desktop startup process. There are some open upstream bugs [1][2] about this, but I don't know enough about PAM and systemd to understand what might be at fault. This is sufficiently inconvenient that I'd consider the "encrypt home directory via fscrypt" workflow to be broken on Ubuntu 18.04 at this time. 1. https://github.com/google/fscrypt/issues/77 2. https://github.com/google/fscrypt/issues/95 ** Affects: fscrypt (Ubuntu) Importance: Undecided Status: New ** Also affects: fscrypt (Ubuntu) Importance: Undecided Status: New ** No longer affects: systemd (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1768340 Title: fscrypt does not work for home directory encryption Status in fscrypt package in Ubuntu: New Bug description: I am trying to use fscrypt in place of ecryptfs to encrypt my home directory, and to automatically unlock/lock it on login and logout. I am using a fresh installation of Ubuntu 18.04 done on 05/01/18. The hardware is a Dell Precision 5520 laptop. The version of the fscrypt and libpam-fscrypt packages is 0.2.2-0ubuntu2. I began with the instructions in https://github.com/google/fscrypt #setting-up-fscrypt-on-a-directory. I quickly ran into bug #1754270, but after applying the workaround from that bug report I was able to successfully encrypt a directory. With that out of the way, I set up a new encrypted home directory, copied all of my files into it with rsync, then moved it on top of the old home directory. When I logged out and logged back in, I was presented with a blank screen. The cursor was visible and responded to trackpad motion. If I clicked the top right of the screen, I saw the usual drop-down menu containing power settings and the like. I didn't see any other responses to clicks or keypresses. Hitting ctrl-alt-fn-f1 brought me back to the login screen. If I tried to login again, this time the desktop came up normally and everything appeared to be working. All of this suggests some sort of broken interaction here between pam_fscrypt.so and the rest of the desktop startup process. There are some open upstream bugs [1][2] about this, but I don't know enough about PAM and systemd to understand what might be at fault. This is sufficiently inconvenient that I'd consider the "encrypt home directory via fscrypt" workflow to be broken on Ubuntu 18.04 at this time. 1. https://github.com/google/fscrypt/issues/77 2. https://github.com/google/fscrypt/issues/95 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fscrypt/+bug/1768340/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
