2.6 /etc/pam.conf question

2.6 /etc/pam.conf question

Post by Mark Hedg » Sun, 24 May 1998 04:00:00



So, we upgraded to Solaris 2.6 (sparc) and installed the recommended
patches, etc.

in.ftpd (running out of inetd) continuously complains about
/etc/pam.conf.

If /etc/pam.conf is not writable by group (but readable by just root, or
root and group or everybody, or writable by root but not group,
whatever) then it spits out this message when someone quits:

May 23 14:28:57 rigel ftpd[26204]: open_pam_conf: stat(/etc/pam.conf)
failed: No such file or directory

And if /etc/pam.conf is mode 660 or 664 (writable by group) it sees
something different and spits out this message when someone logs in:

May 23 14:30:40 rigel ftpd[26320]: open_pam_conf: /etc/pam.conf writable
by group

but no message when someone quits.

Could someone share their experience with pam? Everything seems to work,
but these messages are annoying. Thanks. Best regards.

Mark Hedges

 
 
 

2.6 /etc/pam.conf question

Post by Matt Kirsc » Wed, 27 May 1998 04:00:00


 > So, we upgraded to Solaris 2.6 (sparc) and installed the recommended
 > patches, etc.

 > in.ftpd (running out of inetd) continuously complains about
 > /etc/pam.conf.

 > If /etc/pam.conf is not writable by group (but readable by just root,
or
 > root and group or everybody, or writable by root but not group,
 > whatever) then it spits out this message when someone quits:

According to my research on just-installed Solaris 2.6 systems, the
permissions on /etc/pam.conf should be 644.

 > Could someone share their experience with pam? Everything seems to
work,
 > but these messages are annoying. Thanks. Best regards.

I don't understand pam or what its purpose is. My first experiences with
it were from RedHat Linux, where it suddenly appeared after an upgrade.
At the time, there was no documentation for it, period. I couldn't find
any on the system, on the CDROM, or even on the Web. Even with the
sparse documentation I've found now, I don't know what purpose it
serves.

 
 
 

2.6 /etc/pam.conf question

Post by Steve Bellen » Wed, 27 May 1998 04:00:00



Quote:>I don't understand pam or what its purpose is. My first experiences with
>it were from RedHat Linux, where it suddenly appeared after an upgrade.
>At the time, there was no documentation for it, period. I couldn't find
>any on the system, on the CDROM, or even on the Web. Even with the
>sparse documentation I've found now, I don't know what purpose it
>serves.

man pam(3) yields PAM = Pluggable Authentication Module. It is way
of giving the administrator more control over the login/authentication
process. PAM is fairly new but has been around is someform or another
since 2.4 (2.3?).
--

 
 
 

2.6 /etc/pam.conf question

Post by Frank Peter » Wed, 27 May 1998 04:00:00



> I don't understand pam or what its purpose is. My first experiences with
> it were from RedHat Linux, where it suddenly appeared after an upgrade.
> At the time, there was no documentation for it, period. I couldn't find
> any on the system, on the CDROM, or even on the Web. Even with the
> sparse documentation I've found now, I don't know what purpose it
> serves.

In the good old days, if you wanted to do a new authentication scheme
such as kerberos, you would need to replace all of the programs
(login, rlogind, su or whatever) that do authentication with versions
that had the different authentication scheme coded into them.  This
often lead to confusion.  For example, the login that you installed
with kerberos might not support the same feature set as the login
that shipped with the OS.  Or an OS security patch might replace your
modified login with a new one that used the standard authentication
scheme.

PAM is the pluggable authentication module and it attempts to resolve
this by allowing you to create dynamically loadable authentication
modules that implement your authentication scheme.

Now to do kerberos you can just create a PAM module that implements
kerberos and list it in the appropriate place in /etc/pam.conf to
arrange for programs to start using it without modifying the programs
themselves.

--
-- Frank Peters    Mississippi State University    Systems and Networks
-- fwp at net.msstate.edu    +1 (601) 325-0741   FAX: +1 (601) 325-8921

 
 
 

2.6 /etc/pam.conf question

Post by Vadim Kolonts » Thu, 28 May 1998 04:00:00



>I don't understand pam or what its purpose is. My first experiences with
>it were from RedHat Linux, where it suddenly appeared after an upgrade.
>At the time, there was no documentation for it, period. I couldn't find
>any on the system, on the CDROM, or even on the Web.

  PAM stands for Pluggable Authentication Modules.

  http://hoth.stsci.edu/public/pam/ - pointer to Solaris PAM docs.

Regards,
V.
--
Vadim Kolontsov
Tver Internet Center NOC

 
 
 

1. PAM (/etc/pam.conf).....Is It Needed?

I do not have much experience with PAM, but in conversations with
others relating to our Solaris servers (versions 2.6 thru 9), I'm under
the impression that we are not using it.

In a recent audit of some of our files, we were cited with having some
servers "less secure" than others simply by virtue of the entries
within /etc/pam.conf.  They do seem to differ, especially when
comparing the 2.6 servers with more current versions (7 thru 9).

My questions become: "IF we are not using PAM, I would presume that we
do not have a need to access the /etc/pam.conf file.  That being said,
do we even need it (i.e. can it be removed without serious
ramifications)?  How would one go about determining IF it is "actually"
being used?

Thanks.

2. Ascii-fying a text file...

3. PAM and /etc/pam.conf

4. finding DETAILED cgi error info

5. in.ftpd: open_pam_conf: stat(/etc/pam.conf) failed

6. how to setup Sun Workstation as a web server?

7. Any doc on /etc/pam.conf and /lib/security/* anywhere????

8. Download MP3 files via Lynx.

9. Looking for sample /etc/named.conf and etc/resolv.conf and /etc/hosts

10. /etc/inetd.conf, /etc/xinetd.conf

11. /etc/inetd.conf and /etc/xinetd.conf

12. /etc/host.conf and /etc/nsswitch.conf

13. PAM/RedHat: pop3 /etc/pam.d config