PAM [error: /lib/security/pam_smbpass.so

Bug #218110 reported by yamo
8
Affects Status Importance Assigned to Milestone
pam (Ubuntu)
New
Undecided
Unassigned

Bug Description

Hi,

Since I've updated from gutsy to hardy heron I have manay many messages in /var/log/auth.log :

Apr 16 11:08:31 mostro gdm[5675]: pam_unix(gdm:auth): authentication failure; logname= uid=0 euid=0 tty=:0 ruser= rhost=
Apr 16 11:08:33 mostro gdm[5675]: PAM unable to dlopen(/lib/security/pam_smbpass.so)
Apr 16 11:08:33 mostro gdm[5675]: PAM [error: /lib/security/pam_smbpass.so: Ne peut ouvrir le fichier d'objet partagé: Aucun fichier ou dossier de ce type]
Apr 16 11:08:33 mostro gdm[5675]: PAM adding faulty module: /lib/security/pam_smbpass.so
Apr 16 11:08:33 mostro gdm[5675]: pam_unix(gdm:auth): check pass; user unknown
Apr 16 11:08:33 mostro gdm[5675]: pam_unix(gdm:auth): authentication failure; logname= uid=0 euid=0 tty=:0 ruser= rhost=
Apr 16 11:08:34 mostro gdm[5675]: PAM unable to dlopen(/lib/security/pam_smbpass.so)
Apr 16 11:08:34 mostro gdm[5675]: PAM [error: /lib/security/pam_smbpass.so: Ne peut ouvrir le fichier d'objet partagé: Aucun fichier ou dossier de ce type]
Apr 16 11:08:34 mostro gdm[5675]: PAM adding faulty module: /lib/security/pam_smbpass.so
Apr 16 11:08:34 mostro gdm[5675]: pam_unix(gdm:auth): check pass; user unknown
Apr 16 11:08:34 mostro gdm[5675]: pam_unix(gdm:auth): authentication failure; logname= uid=0 euid=0 tty=:0 ruser= rhost=

 uname -a
Linux mostro 2.6.24-16-generic #1 SMP Thu Apr 10 13:23:42 UTC 2008 i686 GNU/Linux

 gnome-about --version
GNOME gnome-about 2.22.1

$ cat /etc/lsb-release
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=8.04
DISTRIB_CODENAME=hardy
DISTRIB_DESCRIPTION="Ubuntu 8.04"

Revision history for this message
yamo (stephane-gregoire) wrote :
Revision history for this message
yamo (stephane-gregoire) wrote :

In /var/log/syslog
 I have this :

Apr 16 11:28:01 mostro gdm[5675]: WARNING: Impossible d'identifier l'utilisateur

$ gdm --version
GDM 2.20.5

Revision history for this message
Kees Cook (kees) wrote :

Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find.

Revision history for this message
Jamie Strandboge (jdstrand) wrote :

Reassigning to samba: pam_smbpass.so is in the libpam-smbpass package which is part of samba source package.

Revision history for this message
Jamie Strandboge (jdstrand) wrote :

Erm, my mistake-- this really is a pam problem as it defines the optional pam_smbpass module. Putting it back to pam.

Revision history for this message
Steve Langasek (vorlon) wrote :

This is a duplicate of bug #216990. We will work on cleaning up this logging information for hardy; please note however that these log messages are entirely advisory and in the case of pam_smbpass don't indicate a problem with your system.

Revision history for this message
yamo (stephane-gregoire) wrote :

Thanks a lot!

Revision history for this message
NoOp (glgxg) wrote :

While this may be considered a duplicate of 216990 and even https://bugs.launchpad.net/ubuntu/+bug/222003, I found that I could no longer VNC into a recently upgraded Gutsty to Hardy. I would receive a password prompt, but continue to get authentication errors. It was only after looking at the auth.log and seeing the same messages as yamo that I finally found the problem:

libpam-smbpass was not installed during the upgrade.

Installing libpam-smbpass (sudo apt-get install libpam-smbpass) immediately fixed the problem.

Revision history for this message
Krishna E. Bera (keb) wrote :

i didnt want any samba support,
so instead i commented out all the lines in the files in /etc/pam.d containing pam_smbpass .
the lines were all 'optional' but maybe there is a bug in the new pam that ignores it.

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

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.