You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I was wondering if the crontab that is installed under the (root) user is somewhat obsolete since a cron script is also installed by the Debian package in /etc/cron.daily/aide ?
By default /etc/aide/aide.conf (used by the command in the crontab entry) does not contain any (restrictive) selection lines, so it really does nothing.
The text was updated successfully, but these errors were encountered:
Based on the command it does run grep for the regex in /etc/cron.* as well, so if the role was already adding to /etc/cron.daily/aide, and the above audit command returns a cron job to you in response; then you are good with not adding to root's crontab.
To disable that specific task, you can just set ubuntu_2004_cis_section1_rule_1_3_2 to false in your playbook (example):
---
- name: Example Playbook to apply cis_ubuntu_2004 role with ipv6.hosts: localhost # or any grouping of hostsconnection: local # or 'ssh'become: yesgather_facts: trueroles:
- cis_ubuntu_2004vars:
ansible_python_interpreter: /usr/bin/python3ubuntu_2004_cis_section1_rule_1_3_2: false
I was wondering if the crontab that is installed under the (root) user is somewhat obsolete since a cron script is also installed by the Debian package in /etc/cron.daily/aide ?
I am refering to this crontab:
https://github.com/darkwizard242/cis_ubuntu_2004/blob/master/defaults/main/section_01.yml#L208-L218
By default /etc/aide/aide.conf (used by the command in the crontab entry) does not contain any (restrictive) selection lines, so it really does nothing.
The text was updated successfully, but these errors were encountered: