Package: libpam-modules
Version: 0.79-4
Severity: important
It seems having pam_access in common-account breaks at(3.1.10):
[EMAIL PROTECTED]:/etc/pam.d$ grep '^[^#].*access' *
common-account:account required pam_access.so
[EMAIL PROTECTED]:/etc/pam.d$ grep '^[^#]' /etc/security/access.conf
[EMAIL PROTECTED]:/etc/pam.d$
[EMAIL PROTECTED]:/etc/pam.d$ sudo grep -B1 atd /var/log/auth.log
Oct 11 13:00:00 evi pam_access[18339]: couldn't get the tty name
Oct 11 13:00:00 evi atd[18339]: Critical error - immediate abort
Probably pam_access should treat checks with no tty better than just
freaking out. Maybe at least ALL lines should still match it, and in
this case of an empty access.conf and since the default policy is to
admit a user it should go right through and grant access.
Cron does not appear to have this problem.
Peter
--
| .''`. ** Debian GNU/Linux **
Peter Palfrader | : :' : The universal
http://www.palfrader.org/ | `. `' Operating System
| `- http://www.debian.org/
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
