Closed tas50 closed 5 months ago
hey @tas50 can you please elaborate your issue.
cron.deny and cron.allow are special files that can be placed in /etc/cron.d that allow or deny access to crontab. Their contents are completely different from regular cron.d files and as such can not be serviced by the cron_d resource.
Source: https://docs.oracle.com/cd/E19253-01/817-0403/sysrescron-23/index.html
I noticed that @tas50 is not even processing the file in /etc/cron.d, but in /etc instead, which should not trigger the warning at all imho. I noticed something similar with cron.daily, but will report that in a new issue.
Confirmed bug fixed with #959, but didn't have a regression test, so made one with #972
/etc/cron.deny is matching with the
Chef/Modernize/CronDFileOrTemplate
cop. Example: