Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
DescriptionJan Pazdziora (Red Hat)
2022-05-10 15:06:42 UTC
Description of problem:
The sysctl_user_max_user_namespaces SCAP rule is defined in the OSPP profile with
- sysctl_user_max_user_namespaces.role=unscored
- sysctl_user_max_user_namespaces.severity=info
That means that the rule is not evaluated and not enforced.
For RHEL 9, we'd like those properties not to be manipulated in the profile, so that the rule actually disables user namespaces.
Version-Release number of selected component (if applicable):
scap-security-guide-0.1.60-6.el9_0
How reproducible:
Deterministic.
Steps to Reproduce:
1. oscap xccdf eval --profile xccdf_org.ssgproject.content_profile_ospp /usr/share/xml/scap/ssg/content/ssg-rhel9-ds.xml | grep -A3 sysctl_user_max_user_namespaces | grep Result
Actual results:
Result informational
Expected results:
Result pass
Additional info:
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory (scap-security-guide bug fix and enhancement update), and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://access.redhat.com/errata/RHBA-2022:8131
Description of problem: The sysctl_user_max_user_namespaces SCAP rule is defined in the OSPP profile with - sysctl_user_max_user_namespaces.role=unscored - sysctl_user_max_user_namespaces.severity=info That means that the rule is not evaluated and not enforced. For RHEL 9, we'd like those properties not to be manipulated in the profile, so that the rule actually disables user namespaces. Version-Release number of selected component (if applicable): scap-security-guide-0.1.60-6.el9_0 How reproducible: Deterministic. Steps to Reproduce: 1. oscap xccdf eval --profile xccdf_org.ssgproject.content_profile_ospp /usr/share/xml/scap/ssg/content/ssg-rhel9-ds.xml | grep -A3 sysctl_user_max_user_namespaces | grep Result Actual results: Result informational Expected results: Result pass Additional info: