-
Notifications
You must be signed in to change notification settings - Fork 741
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
Add exception in sysctl task #240
Conversation
No need apply sysctl in docker and openvz containers. Signed-off-by: Oleg Kupriyanov <[email protected]>
Hey @okupriyanov, thanks for your PR, much appreciated. |
Hey @okupriyanov, I was a little hasty in merging your PR, and needed to revert it, sorry! There are some things that need to be done additionally. For that I created a PR (https://github.com/okupriyanov/ansible-os-hardening/pull/1) against your branch. If you'd merge this we could work continue working on your PR. Sorry for the confusion! |
Added ssh_syslog_facility, ssh_log_level and ssh_strict_modes parameters
Added ssh_syslog_facility, ssh_log_level and ssh_strict_modes parameters
No need apply sysctl in docker and openvz containers. Signed-off-by: Oleg Kupriyanov <[email protected]>
This reverts commit 3e14d45.
No need apply sysctl in docker and openvz containers. I think that it not right. Because not all sysctls are namespaced. Docker does not support changing sysctls inside of a container that also modify the host system. As the kernel evolves we expect to see more sysctls become namespaced.
But when I run test on os-debian9-ansible-latest for example, I got many failed sysctl-* tests. Because only_if don't work for me (https://github.com/dev-sec/linux-baseline/blob/master/controls/sysctl_spec.rb#L23)