Re: Shadow PAM troubles

[XenWryla LeFae <xela grex org>]

Thanks so much for your response and the patch!

Funny thing.  I applied the patch and recompiled PAM,
then I recompiled shadow, but it still failed unable to
find "-lpam".  I looked at libpam*.so and they were all
symlinks to nonexistant libpam*.so.0, so I remade the
symlinks to libpam*.so.0.75 .  Then shadow compiled
just fine and reported the proper libraries with "ldd
/bin/login".

However, then login is broken and fails with "login:
PAM Failure, aborting: Critical error - immediate
abort".  Well at least I know its going through PAM
now.  Passwd and su work just fine.

Any further help anyone can give this poor helpless
leech is greatly appreciated.

My /etc/pam.d/shadow file is the default that comes
with shadow:

auth		sufficient	pam_rootok.so
account		required	pam_permit.so
password	required	pam_make.so /var/db

The only clue I have is that /var/db doesn't exist.
What is it?

On Tue, 15 May 2001, Andrew Morgan wrote:

> There is a sorry bug in the Linux-PAM configure setup with 0.75, and it
> relates to the naming of shared libraries. The fix for it is committed
> to the CVS repository, and corresponds to:
> 
>  cvs diff -u -r1.13 -r1.14 configure.in
> 
> For information about the CVS repository as a whole, take a look at:
> pam.sourceforge.net .
> 
> I'm attaching the patch (be sure to remove the version number change
> when applying it).
> 
> Cheers
> 
> Andrew
> 
> Sergey Ostrovsky wrote:
> > <--- snip
> > > ... I'm sure I am just missing some
> > > vital element.
> > <--- snip