Cron dislikes pam_access.so

Bug #10635 reported by Scott Dier
6
Affects Status Importance Assigned to Milestone
cron (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

If I add:
account required pam_access.so

to common-account, cron refuses to run its daily cronjobs. There are no entries
in /etc/security/access.conf.

I'm going to fix it here for the time being by changing the cron pam.d file to
exclude common-account and only have the pam_unix.so line.

Revision history for this message
Matt Zimmerman (mdz) wrote :

It sounds like the module is behaving as designed; it seems to deny by default
if the configuration file cannot be read. There should be an error message in
syslog of the form "for service [%s] failed to open accessfile=[%s]"

Please reopen if you still have reason to believe that it is misbehaving.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.