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.

There are some work being done towards fixing this problem which will make the rules notapplicable when packages newer than krb5-server-1.17-18.el8.x86_64 and krb5-workstation-1.17-18.el8.x86_64 (that are FIPS compliant) are installed on the system.

These two pull requests should mitigate the situation by using the CPE applicability

https://github.com/ComplianceAsCode/content/pull/8126
https://github.com/ComplianceAsCode/content/pull/9003

Postponing to RHEL-8.8 as the rule_notapplicable_when_ovirt_installed platform in the rule package_krb5-workstation_removed interfere with the platforms which check version of the krb5 packages - this causes that the rule is evaluated as applicable even in cases when it should be notapplicable.

There is a fix upstream: https://github.com/ComplianceAsCode/content/pull/9412

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-2023:2869