Package: cron Version: 3.0pl1-100 Severity: wishlist I believe that a cron job is fundamentally different to a user login session. The existence of the files /etc/cron.allow and /etc/cron.deny shows that for a long time there has been a demand for the ability to control who can use cron jobs.
It seems to me that the ideal way of managing this is via PAM. Among other things this would allow authenticating users by password at the time that they change cron jobs (as they will be authenticated when they run chsh and similar commands). -- System Information: Debian Release: 4.0 APT prefers stable APT policy: (500, 'stable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.18-6-686 Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=ANSI_X3.4-1968) (ignored: LC_ALL set to C) Versions of packages cron depends on: ii adduser 3.102 Add and remove users and groups ii debianutils 2.17 Miscellaneous utilities specific t ii libc6 2.3.6.ds1-13etch5 GNU C Library: Shared libraries ii libpam0g 0.79-5 Pluggable Authentication Modules l ii libselinux1 2.0.15-2.etch1 SELinux shared libraries ii lsb-base 3.1-23.2etch1 Linux Standard Base 3.1 init scrip Versions of packages cron recommends: ii postfix [mail-transport-agent 2.3.8-2+b1 A high-performance mail transport -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
