feat(cron): set permissions on cron scripts/jobs to splunk#174
feat(cron): set permissions on cron scripts/jobs to splunk#174zyphermonkey wants to merge 1 commit intosplunk:masterfrom
Conversation
Following the "least privilege" model we should only be running things as root when absolutely necessary.
|
Since this changes the location of the cron configuration do we want to add cleanup tasks for the crontab entries? I couldn't find any other references for cleanup for any other changes so I assume the idea is that this just needs to work on a fresh system. I can add the cleanup tasks though if requested, just being cautious of adding tasks that will go unused almost all the time. |
There are a lot of things that need to be done with securing this playbook, and making it more safe. This is a good idea to implement.
Agreed, it makes it a lot cleaner.
This is the only problem with moving it to If we keep the old cron job which runs as root, and change the owner to |
On second thought, we can change the mode to |
Following the "least privilege" model we should only be running things as root when absolutely necessary.
Also migrate from crontab to cron.d to isolate jobs into separate files for more granular management.