Bug 432277

Summary: pam_krb5 does not link against libpam
Product: Red Hat Enterprise Linux 5 Reporter: Sean Dilda <agrajag>
Component: pam_krb5Assignee: Nalin Dahyabhai <nalin>
Status: CLOSED DUPLICATE QA Contact: Brian Brock <bbrock>
Severity: low Docs Contact:
Priority: low    
Version: 5.1CC: mkoci, sghosh, syeghiay
Target Milestone: rc   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2009-06-10 18:31:10 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
Patch to make pam_krb5-2.2.14 link against libpam none

Description Sean Dilda 2008-02-10 21:12:30 UTC 
Description of problem:

pam_krb5 does not link against libpam.   As a result, while trying to use
pam_krb5 in some applications is resulting in an error like this:


Feb 10 15:50:01 jabber-test-01 beam: PAM unable to
dlopen(/lib/security/$ISA/pam_krb5.so)
Feb 10 15:50:01 jabber-test-01 beam: PAM [error:
/lib/security/../../lib/security/pam_krb5.so: undefined symbol: pam_getenv]
Feb 10 15:50:01 jabber-test-01 beam: PAM adding faulty module:
/lib/security/$ISA/pam_krb5.so

Using the same application on RHEL 4, I have no problems.  It appears that RHEL
4 is using a newer version of pam_krb5 that does link against libpam.


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

pam_krb5-2.2.14-1
Comment 1 Sean Dilda 2008-02-10 21:19:46 UTC 
I made a mistake.  The RHEL4 version isn't newer.  However, the RHEL4 version
does not exhibit this problem.
Comment 2 Sean Dilda 2008-02-10 23:57:47 UTC 
Created attachment 294525 [details]
Patch to make pam_krb5-2.2.14 link against libpam

This patch will cause pam_krb5 to link against libpam.

I've confirmed that this patch does fix my problems.
Comment 7 Nalin Dahyabhai 2009-06-10 18:31:10 UTC 
This was included in update 3, where it was tracked as #460998.  Marking this report as the duplicate because the other bug report contains pointers to the advisory.

*** This bug has been marked as a duplicate of bug 460998 ***