Right now I have pam-0.75-33mdk and some files in /etc/pam.d: xscreensaver: #%PAM-1.0
# Red Hat says this is right for them, as of 7.3: auth required /lib/security/pam_stack.so service=system-auth # This is what we were using before: # auth required /lib/security/pam_pwdb.so shadow nullok xlock: #%PAM-1.0 auth required /lib/security/pam_stack.so service=system-auth kscreensaver3: #%PAM-1.0 #auth sufficient /lib/security/pam_linux_afs.so ignore_root #auth sufficient /lib/security/pam_linux_afs.so no_unlog ignore_root #auth required /lib/security/pam_pwdb.so shadow nullok auth required /lib/security/pam_stack.so service=system-auth Also there doesn't appear to be anything in auth.log from when I couldn't login in xlock. Oliver Lemke wrote: > On Tue, 22 Jul 2003 17:51:18 +0200, Buchan Milne wrote: >> >> /etc/pam.d/xscreensaver most likely. But you may want to see if there >> are any interesting errors in /var/log/auth.log. >> > > *cough* Quite obvious, should've looked by myself before asking. ;-) > > I tried to use the alternative line in pam.d/xscreensaver: > > # Red Hat says this is right for them, as of 7.3: > -auth required /lib/security/pam_stack.so service=system-auth > +#auth required /lib/security/pam_stack.so service=system-auth > > # This is what we were using before: > -# auth required /lib/security/pam_pwdb.so shadow nullok > +auth required /lib/security/pam_pwdb.so shadow nullok > > To no avail. Also, auth.log doesn't provide any info. No log entry at all > about the authentication request from the screensaver. :-( >
