unmodified pam config, upgraded to pam 1.4.0. mate-screensaver tells me "not permitted to gain access at this time" when i enter an incorrect password. su tells me "permission denied" instead of "su authentication error" when i enter an incorrect password. (whether either or is the better message i'll leave up to the reader) auth.log is full of entries saying it can't open the tally files. the man page for faillog says they should go in a directory in /var/run, except that directory gets wiped on every boot since it's symlinked to /run, and it doesn't get auto-created on boot. Reproducible: Always Steps to Reproduce: 1. upgrade to pam 1.4.0 2. log in and out a bunch of times, or lock an X session 3. read auth.log Actual Results: errors in auth.log Expected Results: no errors in auth.log
s/faillog/faillock
apologies, its not from the pam update, but rather pambase
Is your tmpfiles implementation working?
It wasn't, apparently. Didn't know I needed it. Fixed that and rebooted, unfortunately no change.
(In reply to Chris Henhawke from comment #4) > It wasn't, apparently. Didn't know I needed it. Fixed that and rebooted, > unfortunately no change. Please ensure: 1) It is in your default run level (or enabled with systemd) 2) Started 3) 'dispatch-conf' returns nothing.
I don't use systemd, but rather openrc. gazelle ~ # dispatch-conf gazelle ~ # /etc/init.d/opentmpfiles-dev status * status: started gazelle ~ # /etc/init.d/opentmpfiles-setup status * status: started
Actually scratch that, it fixed the faillock stuff, but didn't fix the error messages changing. Sorry for the bugspam
Should I file another bug for all the error messages changing, or will that be fixed in another update? Thanks
