-
-
Notifications
You must be signed in to change notification settings - Fork 41
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Added option to delete the cron.deny file when $manage_users_deny is true. #146
base: master
Are you sure you want to change the base?
Conversation
e5a54f3
to
08da145
Compare
LGTM. Won't approve since I don't use cron anymore :D |
Indeed. Unfortunately, I'm still stuck in the past.... |
@TheMeier , are the tests running properly? I see a bunch of "Could not retrieve fact ipaddress" errors. |
The actual test failures don't appear to be related to that. |
08da145
to
09c0311
Compare
Whoops, I put the management in cron.allow instead of cron.deny. Fixed with this updated branch. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please add spec tests that show what happens when this is set to non-default (absent).
4e9feed
to
29ac9e2
Compare
@ghoneycutt acceptable test? I've very, very little experience writing tests. |
Pull Request (PR) description
Ability to manage the existence of /etc/cron.deny. Some CIS audits recommend/require that if no entries are made to /etc/cron.deny then the file should be deleted.
This Pull Request (PR) fixes the following issues
Allows the deletion of /etc/cron.deny.
Reference #145