RHEL 9 STIG: make sysctl_user_max_user_namespaces not scored and informational #12824
+8
−4
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
vojtapolasek
added
bugfix
|
Start a new ephemeral environment with changes proposed in this pull request: Fedora Environment Oracle Linux 8 Environment |
|
@vojtapolasek please rebase to fix the required CI tests. |
…nformational The rule can conflict with some services which use Systemd PrivateUsers feature, such as irqbalance. Therefore, we do not enforce the rule and it is kept there as informational only.
vojtapolasek
force-pushed
the
stig_make_user_namespaces_not_scored
branch
from
8bcd3d4 to
21ef5b3
Compare
|
@Mab879 done. |
|
Code Climate has analyzed commit 21ef5b3 and detected 0 issues on this pull request. The test coverage on the diff in this pull request is 100.0% (50% is the threshold). This pull request will bring the total coverage in the repository to 61.8% (0.0% change). View more on Code Climate. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description:
Rationale:
I think is is a ballanced approach. DISA allows exceptions to the rule, if operationally required and documented. At the same time, users can make the rule scored and enforced with proper tailoring.
Review Hints: