[Bug 216990] Re: error in auth.log when switch user -- pam_smbpass.so

[Steve Langasek]

Anyone seeing such issues in releases later than Ubuntu intrepid most
likely has a locally-broken PAM config, not an Ubuntu bug.  Please see
the Ubuntu forums, askubuntu.com, or another support forum for
assistance.

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to pam in Ubuntu.
https://bugs.launchpad.net/bugs/216990

Title:
  error in auth.log when switch user -- pam_smbpass.so

Status in “pam” package in Ubuntu:
  Fix Released
Status in “pam” source package in Hardy:
  Fix Released
Status in “pam” source package in Intrepid:
  Fix Released

Bug description:
  I am working on a kubuntu hardy (8.04) beta installed from scratch.
  Everything work well but  when I switch user (su) I see this
   error in /var/log/auth.log file:

    : PAM unable to dlopen(/lib/security/pam_smbpass.so)
    : PAM [error: /lib/security/pam_smbpass.so: cannot open shared object file:
          No such file or directory]
    : PAM adding faulty module: /lib/security/pam_smbpass.so

  The user switch is successfully done .

  The file pam_smbpass.so is not present on my systema and i  have solved the
   problem installing the package: libpam-smbpass.

  Maybe a missed package ?

  Best Regards

  TEST CASE:
  monitor /var/log/auth.log.  With hardy version of libpam-runtime and libpam0g installed, and libpam-smbpass not installed, run 'sudo -k' followed by 'sudo ls'.  Observe that three log messages are written about libpam-smbpass.  Upgrade to hardy-proposed versions of libpam-runtime and libpam0g.  Run 'sudo -k', then 'sudo ls' again.  Observe that there are no log messages about libpam-smbpass.

  Regression potential: minimal.  No modules are known to use a
  'missingok' option today, so there is minimal practical risk of
  overlapping semantics.  In particular, the smbpass module ignores this
  as an unknown option, so this will not negatively impact users who do
  have pam_smbpass installed.  The maximum potential impact is that
  users who use 'missingok' in their PAM configs for other modules, for
  whatever reason, will find it more difficult to debug failures caused
  by the named module being missing from the system.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pam/+bug/216990/+subscriptions