On that note, I found a similar problem with pam_cracklib. I had the same
syslog error but it was complaining about crypt.

Feb 7 14:26:36 hosvrlog passwd: PAM unable to
dlopen(/lib/security/pam_cracklib.so)
Feb 7 14:26:36 hosvrlog passwd: PAM [dlerror: undefined symbol: crypt]
Feb 7 14:26:36 hosvrlog passwd: PAM adding faulty module:
/lib/security/pam_cracklib.so

So I changed the Makefile for pam_cracklib to the following:

from
MODULE_SIMPLE_EXTRALIBS=-lcrack
to
MODULE_SIMPLE_EXTRALIBS=-lcrack -lcrypt

and it seems to work fine now.

John Delisle
Corporate Technology
Ceridian Canada Ltd
204-975-5909

                                                                                                                 
                    Michael Tokarev
                    <mjttls.msk.ru To: pam-listredhat.com
> cc:
                    Sent by: Subject: BUG: pam_lastlog: -lutil?
                    pam-list-admin
                    redhat.com
                                                                                                                 
                                                                                                                 
                    2001/02/08
                    10:00 AM
                    Please respond
                    to pam-list
                                                                                                                 
                                                                                                                 

Found in syslog after adding pam_lastlog module to pam.d:

 PAM unable to dlopen(/lib/security/pam_lastlog.so)
 PAM [dlerror: /lib/security/pam_lastlog.so: undefined symbol: logwtmp]
 PAM adding faulty module: /lib/security/pam_lastlog.so

As it seems to be, pam_lastlog depends on libutil.so (where logwtmp
leaves), but not linked with it. It's trivial to add -lutil to
link command of pam_lastlog, but for now, with new autoconf stuff,
this should be in configure.in (as not all platforms have -lutil
and/or logwtmp in it, and some (?) ever does not have logwtmp),
so I'm not shure how to correct this Right Way... And this is
a more general question than just about this pam_lastlog issue.

This was/is on all pam releases since 0.71!.. Does anyone uses
pam_lastlog at all? :)

Regards,
 Michael.

_______________________________________________
Pam-list mailing list
Pam-listredhat.com
https://listman.redhat.com/mailman/listinfo/pam-list

_______________________________________________
Pam-list mailing list
Pam-listredhat.com
https://listman.redhat.com/mailman/listinfo/pam-list

• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]