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