Bug 2189458 - oscap should configure sysctl parameters in separate files
Summary: oscap should configure sysctl parameters in separate files
Keywords:
Status: NEW
Alias: None
Product: Red Hat Enterprise Linux 9
Classification: Red Hat
Component: scap-security-guide
Version: 9.1
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Watson Yuuma Sato
QA Contact: BaseOS QE Security Team
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-04-25 10:27 UTC by Marko Myllynen
Modified: 2023-05-29 14:31 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: No Doc Update
Doc Text:
Clone Of:
Environment:
Last Closed:
Type: Bug
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker RHELPLAN-155657 0 None None None 2023-04-25 10:29:01 UTC

Description Marko Myllynen 2023-04-25 10:27:10 UTC
Description of problem:
When remediating a system for CIS, oscap creates separate configuration files e.g. for sshd in /etc/ssh/sshd_config.d and this works as expected by default while still allowing an administrator to override selected parameters if a need arises.

However, when configuring sysctl parameters oscap puts everything in /etc/sysctl.conf instead of separate file(s) in /etc/sysctl.d. This both changes the RPM provided default file /etc/sysctl.conf and makes it impossible to override any parameter local if needed by using separate configuration files in /etc/sysctl.d.

It would be better if oscap would use separate files for sysctl parameters when remediating as is already done with e.g. sshd. Thanks.

Version-Release number of selected component (if applicable):
scap-security-guide-0.1.66-1.el9_1.noarch


Note You need to log in before you can comment on or make changes to this bug.