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.
Description of problem:
After remediating require_singleuser_auth via the ospp profile, we can see that rpm -V shows:
# rpm -V systemd | grep -v -e ' c /' -e ' g /'
S.5....T. /usr/lib/systemd/system/rescue.service
and, indeed, reinstalling systemd removes the remediated change, because rpm considers the file to be invalid.
A better way to remediate this would be to first copy the file to /etc/systemd/system, modify it there, and call systemctl daemon-reload.
Since most of /etc/systemd/system/* is not owned by any package, this would fix the problem.
Version-Release number of selected component (if applicable):
scap-security-guide-0.1.57-5.el9
Comment 3Jan Pazdziora (Red Hat)
2021-10-19 12:35:57 UTC
Shouldn't this be doable with a drop-in snippet as well, using ExecStart= with empty value to clear the default, and another one to set the new value?
(In reply to Vojtech Polasek from comment #4)
> Isn't this actually a duplicate of this one?
> https://bugzilla.redhat.com/show_bug.cgi?id=1999576
It is possible - I did search for the rule name in BZ and didn't find bug 1999576, however if the rule has no additional profile-specific configuration, then this might be a duplicate.