On Sun, Sep 29, 2002 at 08:17:03PM -0400, Susan Buczak wrote:
Just out of curiousity, maybe you guys know, but on my redhat system the current /etc/pam.d/login looks like this:
#%PAM-1.0 auth required /lib/security/pam_securetty.so auth required /lib/security/pam_stack.so service=system-auth auth required /lib/security/pam_nologin.so account required /lib/security/pam_stack.so service=system-auth password required /lib/security/pam_stack.so service=system-auth session required /lib/security/pam_stack.so service=system-auth session optional /lib/security/pam_console.so account required /lib/security/pam_access.so ^^^^^^^^^^^^^
So obviously I am missing access.conf here which should be easy enough to throw in, but any ideas about the differences between using mxauth and not using it, as suse appears to be doing, what's suse's equivalent of the auth file?
pam_access.so is in use on your RH system
and nullOk is that safe or does it just apply to mail and stuff?
nullok means an empty password is acceptable. If you are using accounts with no password then it is ok. But I would rather not allow it (I mean passwordless accounts) Regards, -Kastus