ecryptfs decrypts home AFTER systemd user daemon is loaded. trouble ensues…

Bug #1734290 reported by nemoinis on 2017-11-24
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
eCryptfs
Undecided
Unassigned

Bug Description

(I discovered and filed this bug on Debian, but checked with Ubuntu and it's there too. Since Debian ecryptfs bug reports seem to be completely ignored, I'm refiling here):

Dear Maintainer,

After having created some systemd user units (and timers), as I have
done on several other machines without issue, I noticed that the units
were not started upon login on this particular machine. In fact
systemctl showed no knowledge of them at all - until I reloaded the
systemd user daemon and timers; after that all was fine.

The difference between this machine and the other working setups: my
home is encrypted via ecryptfs on this laptop.

So I wondered if maybe the systemd user daemon was started upon login
BEFORE my home was decrypted (thus it'd know nothing of my setup).

Sure enough, in /etc/pam.d/common-session, pam_ecryptfs.so unwrap was
invoked AFTER pam_systemd.so.

Reversing the order fixed the problem. I don't know too much about pam but
I think ecryptfs should specify a higher priority in the common-session stack.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers