In a Cronie-compatible system, /etc/cron.allow exists but does not list alice.
alice is listed in /etc/cron.deny.
Can alice use crontab?
When cron.allow exists, only users listed there may use crontab; cron.allow takes precedence over cron.deny.
Detailed explanation
Incorrect. Being in cron.deny never grants permission.
Incorrect. Being in cron.deny never grants permission.
Incorrect. The allow list controls access when it exists.
Incorrect. The allow list controls access when it exists.
Correct. alice is not in cron.allow, so access is denied.
Correct. alice is not in cron.allow, so access is denied.
Incorrect. The daemon uses these files for access control.
Incorrect. The daemon uses these files for access control.
Try it yourself
An example you can run in a temporary verification environment.
printf '%s\n' 'cron.allow exists -> only listed users are allowed'Expected result
allow存在時の判定規則Key points
- allow list has priority
- deny is used when allow is absent
- Check implementation docs
Notes
- Environment: Cronie互換アクセス制御の概念確認
- Command output formatting can vary slightly by distribution or tool version.
- Run the example in a temporary directory or process when possible.
Foundation review
Read the scope first
Check whether the command acts on the current shell, a new process, an existing process, or a file.
Verify the observable result
Use the supplied command and compare the output with the expected result.