[NTLUG:Discuss] WHAT PAM FILES!!!

[ntlug@rain4us.net]

> I don't want to discourage you,
> but if your distro isn't PAM enabled,
> you're going to have a lot of work in front of you.
>

Oh it's not discouragement.   I'm not trying to pam enable every %@$#%
thing..  I just want to provide PAM for the ONE app that needs it.  I've
done this once before on slackware...where I installed pam and created a
vmware-authd  file that contained

----
#%PAM-1.0
auth       required     /lib/security/pam_unix_auth.so shadow nullok
account    required     /lib/security/pam_unix_acct.so
----

Only, I know not which files exist in a standard /etc/pam.d direcotry, nor
do I know their contents.  I know not which file winbindd will be
using...etc.

It is my understanding that if SSH is not configured to use pam..then it
won't matter WHAT is in its ssh config file. In other words, only those
applications that are looking for PAM will find and use it....which is
fine by me!

Hey! if anyone out there would like to tar up their /etc/pam.d directory
and send it over...I think I'll be able to push my way through this. :) 
It will be a next step anyway.

BTW:  When upgrading from Samba 2.2.8a to Samba 3.0.9 (3.0.10 was released
today btw) on Slackware,  and IF you've compiled and installed them via
the source tarballs,  be careful to make sure that you are using the
correct path to your binaries.   2.2.8a uses /usr/local/samba/bin and
3.0.9 uses  /usr/local/samba/sbin.   It's amazing how ONE little character
can bite you in the butt.

-- 
Richard the unpamful Slacker.