meant to say 'there' not 'here'. yea, the access.conf works real well on the RH too, I still can't get it to respond on the suse. getting tired of reading docs for something that normally takes 5 minutes to get done... something is not configured normally in there... and all I know is it's real important here... and I should have it there... just wish I knew what it was... beginning to wonder if I actually care... considering the fact that all the software is linux software with all the same vulnerabilities and assest as any linux version... well... it has to be protected and updated the same way... I mean obviously.. when it becomes a problem what is your time worth to deal it just so that yast can work? It's still linux no matter which way you look at it. I don't know. cheers to you also, goodnight. 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