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, /etc/pki/tls/openssl.cnf contains:
[ crypto_policy ]
.include /etc/crypto-policies/back-ends/opensslcnf.config
.include = /etc/crypto-policies/back-ends/opensslcnf.config
This is presumably caused by OVAL not checking for a line variant with = and without it. It doesn't cause openssl errors because the config file supports both syntax styles:
A file can include other files using the include syntax:
.include [=] pathname
However, SCAP content should
1) check for both variants and PASS if either is present
2) if none is present, remediate the variant with =, since it seems to be
more standard/common
Version-Release number of selected component (if applicable):
scap-security-guide-0.1.60-6.el9_0.noarch (scratch build by wsato)
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:8131
Description of problem: After remediating, /etc/pki/tls/openssl.cnf contains: [ crypto_policy ] .include /etc/crypto-policies/back-ends/opensslcnf.config .include = /etc/crypto-policies/back-ends/opensslcnf.config This is presumably caused by OVAL not checking for a line variant with = and without it. It doesn't cause openssl errors because the config file supports both syntax styles: A file can include other files using the include syntax: .include [=] pathname However, SCAP content should 1) check for both variants and PASS if either is present 2) if none is present, remediate the variant with =, since it seems to be more standard/common Version-Release number of selected component (if applicable): scap-security-guide-0.1.60-6.el9_0.noarch (scratch build by wsato)