Your message dated Thu, 18 Oct 2007 13:24:47 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#446239: pam_access breaks at
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message ---
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/
--- End Message ---
--- Begin Message ---
Version: 0.99.7.1-2
On Thu, Oct 11, 2007 at 01:19:40PM +0200, Peter Palfrader wrote:
> 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.
I believe this bug is fixed in lenny; the current version of pam_access
errors only if it can't find a remote hostname, a tty, /or/ a service name.
--
Steve Langasek Give me a lever long enough and a Free OS
Debian Developer to set it on, and I can move the world.
[EMAIL PROTECTED] http://www.debian.org/
--- End Message ---
