Bug#870126: ecryptfs-mount-private: mount: No such file or directory

2020-01-09 Thread Vladimir K
So linkage of user and session keyrings is apparently done by pam_keyinit module. There is a line: sessionoptional pam_keyinit.so force revoke in /etc/pam.d/login, but not in /etc/pam.d/lightdm.

Bug#870126: ecryptfs-mount-private: mount: No such file or directory

2019-09-02 Thread Vladimir K
keyctl link workaround works for me. I'm using lightdm and slimmed down LXQt session. What system component should link keyrings by design? DM, session lead, PAM, basic login scripts? I feel that this bug should be redirected accordingly.

Bug#870126: ecryptfs-mount-private: mount: No such file or directory

2017-07-29 Thread Craig Small
Package: ecryptfs-utils Version: 111-4 Severity: important I have setup the standard home ~/Private directory. It looks like it is confused about which key to use. For the last few months or so, I get this (key IDs changed but consistent in report): $ ecryptfs-mount-private Enter your login pa