Skip to content
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

Handle immutability of config #36

Open
james-stocks opened this issue Jul 10, 2018 · 1 comment
Open

Handle immutability of config #36

james-stocks opened this issue Jul 10, 2018 · 1 comment

Comments

@james-stocks
Copy link

This cookbook (at least if you set the cis rules) will include -e 2 config, making the auditd config immutable.

This means that if the cookbook is run repeatedly in Chef runs; the notified restart of the auditd service will have no effect on the current config.
When auditd is configured to be immutable; a restart of the host is needed.

This cookbook should possibly do something to address this.
Maybe a warning/failure if this happens. Maybe control over the immutability through attributes.
I think we can notify the host to reboot if needed; but this should definitely be attribute controlled and disabled by default!

@jblaine
Copy link
Contributor

jblaine commented Dec 11, 2019

Agreed. We had to duplicate the service 'auditd' resource and add an ignore_failure to it in a wrapper cookbook as a workaround.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants