Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 173794 - PAM adding faulty module: /lib64/security/pam_ldap.so
PAM adding faulty module: /lib64/security/pam_ldap.so
Product: Fedora
Classification: Fedora
Component: nss_ldap (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Nalin Dahyabhai
Depends On:
  Show dependency treegraph
Reported: 2005-11-21 04:05 EST by Ola Thoresen
Modified: 2007-11-30 17:11 EST (History)
1 user (show)

See Also:
Fixed In Version: 244-2
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2005-11-21 15:26:34 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Ola Thoresen 2005-11-21 04:05:53 EST
Description of problem:
Unable to log in using pam_ldap on x86_64

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. Configure ldap authentication
2. Try to log in as a normal user from LDAP
3. Cry
Actual results:
Nov 21 10:01:28 ws21 unix_chkpwd[3707]: password check failed for user (olen)
Nov 21 10:01:28 ws21 login(pam_unix)[3608]: authentication failure; logname=
uid=0 euid=0 tty=tty3 ruser= rhost=  user=olen
Nov 21 10:01:30 ws21 login[3608]: FAILED LOGIN 1 FROM (null) FOR olen,
Authentication failure

Expected results:
Should be able to log in

Additional info:
Nov 21 10:01:25 ws21 login: PAM unable to dlopen(/lib64/security/pam_ldap.so)
Nov 21 10:01:25 ws21 login: PAM [dlerror: /usr/lib64/libldap-2.2.so.7: undefined
symbol: SSL_CTX_set_tmp_rsa_callback]
Nov 21 10:01:25 ws21 login: PAM adding faulty module: /lib64/security/pam_ldap.so
Comment 1 Ola Thoresen 2005-11-21 05:48:45 EST
A rebuild of nss_ldap was all that was needed.
Comment 2 Nalin Dahyabhai 2005-11-21 15:26:34 EST
All right then, "fixing" in 244-2.  Thanks!

Note You need to log in before you can comment on or make changes to this bug.