PAM authrozation

PAM authrozation

Post by ngal » Wed, 08 Oct 2003 23:19:04



Hi,

I am writing a PAM authorization client on solaris (SunOS 5.8 with
uname -rs). However, I am encountering problems getting the PAM
libraries to authenticate users when the program is run at user level.
If the program is run as 'root' then the libraries work fine. Here is
my /etc/pam.conf entry:

progname auth required /usr/lib/security/$ISA/pam_unix.so.1

What is strange is that the same program, with no change in the source
will compile and work with a Linux machine on the same network. The
network uses NIS to manage user accounts and the NIS passwd.byname map
does not disclose the crypted passwords. Instead it uses a private
passwd.adjunct map. The passwords are actually stored in /etc/shadow.

Can anyone help me, or at least direct me to some documentation that
might have an answer. Any help would be greatly appreciated!

Thanks
Natasha

 
 
 

PAM authrozation

Post by Dave Ockwell-Jenne » Thu, 09 Oct 2003 02:22:16



Quote:> I am writing a PAM authorization client on solaris (SunOS 5.8 with
> uname -rs). However, I am encountering problems getting the PAM
> libraries to authenticate users when the program is run at user level.
> If the program is run as 'root' then the libraries work fine. Here is
> my /etc/pam.conf entry:

You need to call the PAM authentication as root, it will not work unless you
are the super-user...

Quote:> progname auth required /usr/lib/security/$ISA/pam_unix.so.1

Consider what is going on.  Solaris uses the /etc/shadow file to specify
related user information (such as password aging, account inactivity, etc.)
The PAM libraries will also need to read /etc/shadow to determine whether
the authentication should succeed.  Furthermore, since /etc/shadow is
readable only by the super-user, then those PAM library calls will need to
be made as root.

Hope that explanation helps!
--
Dave Ockwell-Jenner
Solar Nexus Solutions
http://www.solar-nexus.com/

 
 
 

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. XF86Config for Genoa Phantom 64

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

4. WABI and SLC?

5. ftp chroot jail dir & pam 1.0 /etc/pam.d/ftp file

6. kde upgrade

7. redhat 6.1, PAM, and having to alter /etc/pam.d/kppp

8. linking C++ code to a shared object on AIX

9. PAM and /etc/pam.conf

10. WU-FTP 2.6: PAM can't open pam.conf?! HELP!!!!

11. PAM problem

12. problem with pam and gdm

13. Does pam-0.68 use features that cracklib libs doesnt understand?