-
-
Notifications
You must be signed in to change notification settings - Fork 244
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
Basis for selinux set to disabled #242
Comments
+1 |
But why is this cookbook managing SELinux? I'm confused as to why it is in this purview at all. |
I agree with @agperson. As a security professional, having no documentation of this change and adding it to the run list could dramatically impact my security. SELinux should be managed be a separate wrapper cookbook. |
@mdavis7771 It is a long story, but ultimately it is a relic from an incorrect generation of this cookbook about a year ago. I do not have a problem removing this cookbook touching SELinux at all. |
I'll accept a PR here if either @mdavis7771 or @agperson is willing to do so. We'll need to increment the minor release. |
@johnbellone, Understood, I'll do a PR later this week. |
#256 should fulfill this. |
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
What is the basis for setting selinux to disabled in this cookbook? I see it changed from permissive sometime between version 1.2.0 and 1.3.0.
We have some compliance restrictions that require selinux and was surprised to see it outright disabled here.
Thanks!
The text was updated successfully, but these errors were encountered: