Not sure if this should be a new bug, opening a zesty task for now until we are sure.
Summary: pam_winbind.so fails to open
Related: bug 1584485
Repro:
$ apt-get install samba winbind libnss-winbind libpam-winbind
$ sed -i -e 's/^passwd: compat/passwd: winbind compat/' /etc/nsswitch.conf
$ systemctl restart smbd nmbd winbind
$ tail -n 5 /var/log/auth.log
May 5 06:31:43 zesty-test groupadd[19598]: group added to /etc/group: name=sambashare, GID=118
May 5 06:31:43 zesty-test groupadd[19598]: group added to /etc/gshadow: name=sambashare
May 5 06:31:43 zesty-test groupadd[19598]: new group: name=sambashare, GID=118
May 5 06:32:08 zesty-test sudo: PAM unable to dlopen(pam_winbind.so): /lib/security/pam_winbind.so: cannot open shared object file: No such file or directory
May 5 06:32:08 zesty-test sudo: PAM adding faulty module: pam_winbind.so
Also the path is different as outlined before:
dpkg -S pam_winbind.so
libpam-winbind:amd64: /lib/x86_64-linux-gnu/security/pam_winbind.so
Confirmed at least on zesty for now, but I'm no windbind/pam expert so I struggle to see what is going on without diving much deeper - this might even be just the wrong way to set it up ... ? :-/
Not sure if this should be a new bug, opening a zesty task for now until we are sure. pam_winbind. so): /lib/security/ pam_winbind. so: cannot open shared object file: No such file or directory
Summary: pam_winbind.so fails to open
Related: bug 1584485
Repro:
$ apt-get install samba winbind libnss-winbind libpam-winbind
$ sed -i -e 's/^passwd: compat/passwd: winbind compat/' /etc/nsswitch.conf
$ systemctl restart smbd nmbd winbind
$ tail -n 5 /var/log/auth.log
May 5 06:31:43 zesty-test groupadd[19598]: group added to /etc/group: name=sambashare, GID=118
May 5 06:31:43 zesty-test groupadd[19598]: group added to /etc/gshadow: name=sambashare
May 5 06:31:43 zesty-test groupadd[19598]: new group: name=sambashare, GID=118
May 5 06:32:08 zesty-test sudo: PAM unable to dlopen(
May 5 06:32:08 zesty-test sudo: PAM adding faulty module: pam_winbind.so
Also the path is different as outlined before: winbind: amd64: /lib/x86_ 64-linux- gnu/security/ pam_winbind. so
dpkg -S pam_winbind.so
libpam-
Confirmed at least on zesty for now, but I'm no windbind/pam expert so I struggle to see what is going on without diving much deeper - this might even be just the wrong way to set it up ... ? :-/