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:

The SCAP security guide remediation for add .include for opensslcnf.config to crypto_policy section in RHEL 8 and RHEL 9 adds a line beginning with ".include =". The STIG check expects it to just be ".include" without the = (equals) symbol. Documentation suggests that the use of = here is for backward-compatibility with older versions so that it is harmlessly discarded if not supported. However, we do not want silent disabling of this include, and RHEL 8/9 include the necessary support anyway. Please amend to remove the = (equals) symbol. 

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
Step 1. Install a RHEL 9.1 VM/system.
Step 2. Install the scap-security-guide package.
Step 3. Bring up /usr/share/scap-security-guide/ansible/rhel9-playbook-stig.yml in your favorite editor.
Step 4. Search for a line containing ".include =".

Actual results:

scap adds ".include =" to opensslcnf.config 

Expected results:

scap should add ".inlcude " to opensslcnf.config 

Additional info:

Patch for this rule is merged in Upstream: https://github.com/ComplianceAsCode/content/pull/10828

con