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.
Bug 2021258 - Rule file_permissions_sshd_private_key fails after kickstart installation [rhel-7.9.z]
Summary: Rule file_permissions_sshd_private_key fails after kickstart installation [rh...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: scap-security-guide
Version: 7.9
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Vojtech Polasek
QA Contact: Matus Marhefka
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-11-08 16:58 UTC by Milan Lysonek
Modified: 2022-09-20 09:07 UTC (History)
4 users (show)

Fixed In Version: scap-security-guide-0.1.63-1.el7_9
Doc Type: Known Issue
Doc Text:
Cause: Selecting a security profile containing the rule `xccdf_org.ssgproject.content_rule_file_permissions_sshd_private_key` with identifier CCE-27485-2 during RHEL7 installation. Consequence: The rule `xccdf_org.ssgproject.content_rule_file_permissions_sshd_private_key` with identifier CCE-27485-2 fails to comply with the policy. Workaround (if any): Rerun remediation again for this rule to fix it. Result: The rule `xccdf_org.ssgproject.content_rule_file_permissions_sshd_private_key` with identifier CCE-27485-2 reports passing when a new scan is performed using a security profile that selects it, e.g `xccdf_org.ssgproject.content_profile_stig`. Moreover, this rule expects some files to exist with certain permissions. During installation phase of RHEL, these files don't exist and the compliance assessment reports pass for the rule. But after the first boot, these files are created and they don't comply with the policy, requiring a remediation fix to applied once more.
Clone Of:
Environment:
Last Closed: 2022-09-20 09:07:04 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker RHELPLAN-102008 0 None None None 2021-11-08 17:00:26 UTC

Comment 4 Watson Yuuma Sato 2022-08-01 08:36:19 UTC 
Fixed by https://github.com/ComplianceAsCode/content/pull/9094.

Rule file_permissions_sshd_private_key now accepts private SSH keys with mode 0640 when their group is ssh_keys.
Comment 15 errata-xmlrpc 2022-09-20 09:07:04 UTC 
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:6576
Note You need to log in before you can comment on or make changes to this bug.