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 2192893 - ".include =" in rhel8-playbook-stig.yml causing STIG to flag it.
Summary: ".include =" in rhel8-playbook-stig.yml causing STIG to flag it.
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: scap-security-guide
Version: 8.8
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: rc
: ---
Assignee: Vojtech Polasek
QA Contact: Milan Lysonek
Mirek Jahoda
URL:
Whiteboard:
Depends On: 2164995
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-05-03 12:39 UTC by Vojtech Polasek
Modified: 2023-11-14 17:08 UTC (History)
13 users (show)

Fixed In Version: scap-security-guide-0.1.69-1.el8
Doc Type: Bug Fix
Doc Text:
.SSG remediations are now aligned with `configure_openssl_cryptopolicy` Previously, the SCAP Security Guide (SSG) remediation added the `=` character to the `opensslcnf.config` file. This syntax dit not match the description of the `configure_openssl_cryptopolicy` rule. Consequently, compliance checks might fail after remediations that inserted `.include =` instead of `.include` to `opensslcnf.config`. With this release, the remediation scripts are aligned with the rule description, and SSG remediations that use `configure_openssl_cryptopolicy` no longer fail due to additional `=`.
Clone Of: 2164995
Environment:
Last Closed: 2023-11-14 15:36:38 UTC
Type: Bug
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker RHELPLAN-156301 0 None None None 2023-05-03 12:39:55 UTC
Red Hat Product Errata RHBA-2023:7056 0 None None None 2023-11-14 15:37:30 UTC

Comment 1 Jan Černý 2023-07-27 13:41:45 UTC 
Patch for this rule is merged in Upstream: https://github.com/ComplianceAsCode/content/pull/10828
Comment 14 errata-xmlrpc 2023-11-14 15:36:38 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 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-2023:7056
Note You need to log in before you can comment on or make changes to this bug.