On 11.02.20 17:32, Francois Marier wrote: > I see the following in my logs: > > Feb 11 07:39:22 hostname systemd: PAM unable to dlopen(pam_cap.so): > /lib/security/pam_cap.so: cannot open shared object file: No such file or > directory > Feb 11 07:39:22 hostname systemd: PAM adding faulty module: pam_cap.so > Feb 11 07:39:54 hostname systemd: PAM unable to dlopen(pam_cap.so): > /lib/security/pam_cap.so: cannot open shared object file: No such file or > directory > Feb 11 07:39:54 hostname systemd: PAM adding faulty module: pam_cap.so > > Not sure why because the file is installed: > > $ ls -lh /lib/x86_64-linux-gnu/security/pam_cap.so > -rw-r--r-- 1 root root 14K Feb 9 05:52 > /lib/x86_64-linux-gnu/security/pam_cap.so
I'm afraid that at this point, I don't know why you are seeing this. I can reproduce the log message trivially (with sshd, didn't try systemd) by moving pam_cap.so out of the way. I would suspect an issue with the recent update form 2.27 to 2.31. However, I just created a test entry in /etc/security/capability.conf, and verified the results with capsh(1), and 2.31 worked as intended.
