ecryptfs-utils does not work with Ubuntu 14.04, neither with 16.04

I'm using 14.04.1 for amd64 plain version and it behaves the same way :(

It fails with a new 14.04.1 installation and with several other 14.04.1 upgraded installations.

Greets.

Partial workaround: install a 12.04 system, create user(s) with encrypted home directory, upgrade to 14.04.

Status changed to 'Confirmed' because the bug affects multiple users.

I've figured out the cause for this bug. It happens when pam_keyinit is used. This happened with ssh based logins in this openssh upload:

  https://launchpad.net/ubuntu/+source/openssh/1:6.5p1-1

The use of pam_keyinit and the way that it creates a session keyring when logging in over ssh is keeping the eCryptfs kernel code from being able to find the mount key. ecryptfs-setup-private is ran as the root user. It executes ecryptfs-add-passphrase. which adds the user's mount key to root's user keyring. However, the root's user keyring is masked by the session keyring that was created earlier so the kernel cannot find the mount key when ecryptfs-setup-private executes the mount program.

WORKAROUND:

$ sudo keyctl link @u @s
$ sudo adduser --encrypt-home foo
$ sudo keyctl unlink @u @s

I'm not sure about the appropriate fix at this time.

Still a bug over 1 year later in 14.04.2

sudo adduser --home /home/colin --ingroup adm --encrypt-home colin
Adding user `colin' ...
Adding new user `colin' (1001) with group `adm' ...
Creating home directory `/home/colin' ...
Setting up encryption ...

************************************************************************
YOU SHOULD RECORD YOUR MOUNT PASSPHRASE AND STORE IT IN A SAFE LOCATION.
  ecryptfs-unwrap-passphrase ~/.ecryptfs/wrapped-passphrase
THIS WILL BE REQUIRED IF YOU NEED TO RECOVER YOUR DATA AT A LATER TIME.
************************************************************************

lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 14.04.2 LTS
Release: 14.04
Codename: trusty

Done configuring.

mount: No such file or directory
ERROR: Could not mount
adduser: `/usr/bin/ecryptfs-setup-private -b -u colin' returned error code 1. Exiting.

Agree Colin, very disappointing that an easy to reproduce bug, have no attention at all.

It is a shame, specially for an LTS release!

However, the workaround that Tyler posted on #5 works for me.

Cheers!

Adding 'sddm' to the affected list after finding this issue when switching from lightdm to sddm (the Kubuntu display manager) on 15.10, and mounting an ecryptfs file-system on external storage using ecryptfs-recover-private.

I've verified that the pam config files shipped with sddm call out to pam_keyinit.so with the 'force' option. This causes a new session keyring to be created for each login process.

I hope it gets fixed for 16.04... :-/

Still a bug in 15.10.

This is still a BUG on Xenial!

---
root@xenial-1:~# apt install ecryptfs-utils

root@xenial-1:~# adduser --encrypt-home cofre1
Adding user `cofre1' ...
Adding new group `cofre1' (1001) ...
Adding new user `cofre1' (1001) with group `cofre1' ...
Creating home directory `/home/cofre1' ...
Setting up encryption ...

************************************************************************
YOU SHOULD RECORD YOUR MOUNT PASSPHRASE AND STORE IT IN A SAFE LOCATION.
  ecryptfs-unwrap-passphrase ~/.ecryptfs/wrapped-passphrase
THIS WILL BE REQUIRED IF YOU NEED TO RECOVER YOUR DATA AT A LATER TIME.
************************************************************************

Done configuring.

mount: mount(2) failed: No such file or directory
ERROR: Could not mount
adduser: `/usr/bin/ecryptfs-setup-private -b -u cofre1' returned error code 1. Exiting.

root@xenial-1:~# lsb_release -ra
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu Xenial Xerus (development branch)
Release: 16.04
Codename: xenial
---

This bug was fixed in the package ecryptfs-utils - 111-0ubuntu1

---------------
ecryptfs-utils (111-0ubuntu1) xenial; urgency=medium

  * src/utils/ecryptfs-setup-private: LP: #1328689
    - fix a long standing bug, where setting up an encrypted private,
      encrypted home, or migrating to an encrypted home did not work
      correctly over ssh sessions
    - the root cause of the bug is some complexity in the handling of
      user keyrings and session keyrings
    - the long term solution would be to correctly use session keyrings
    - the short term solution is to continue linking user and session
      keyrings
  * xenial

 -- Dustin Kirkland <email address hidden> Fri, 26 Feb 2016 17:58:16 -0600

Wheeeee!!! It is working! Thank you Dustin! :-D

Xenial is going to be great! YAY!

Not fixed on 14.04.5