Jamie Wilkinson wrote:
> This one time, at band camp, Luke McKee said:
> >Before PAM decides to load in any modules it decides to peruse
> >/etc/passwd to see if a user is in there.
> >Does anyone have a idea why PAM would do this?
>
> Because it was told to? What's the relevant files in /etc/pam.d/ look
> like? I'll place money on a spurious pam_unix.so lying around where you
> least expect it.
>
> --
> jamesw
>
> <Jaq> what's wrong with the default? :)
> <jdub> It is poopie.
>
> --
> SLUG - Sydney Linux User Group Mailing List - http://slug.org.au/
> More Info: http://lists.slug.org.au/listinfo/slug
I've been doing a stack trace on the process. It is reading the correct
configuration file when a user exists in NSS.
When a user doesn't exist it doesn't read any conf files (in my case
/etc/pam.d/qmail-pop3) or load any pam modules.
I find that this is a bit strange.
My /etc/pam.d/qmail-pop3 file looks like this:
auth required /lib/security/pam_smb_auth.so debug nolocal
session required /lib/security/pam_permit.so
account required /lib/security/pam_permit.so
password required /lib/security/pam_permit.so
This configuration file has no pam_unix or no pam_pwdb entries.
Thanks for the tip though. I really do try to read the FAQ and try for at
least a day before posting to the SLUG list.
I nearly got PAM - Samba-TNG\Winbind working but it just kept saying an
account didn't exist.
Luke
--
SLUG - Sydney Linux User Group Mailing List - http://slug.org.au/
More Info: http://lists.slug.org.au/listinfo/slug
