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:
We need to have an update made top the 8.1 scap-security-guide.

rsa-sha2-256,rsa-sha2-512

need to be added under PubkeyAcceptedKeyTypes in

/etc/crypto-policies/local.d/opensshserver-ospp.config

to enable more crypto algorithms that we claim.

FTR; for ospp on 8.1, this is done by the "harden_sshd_crypto_policy" rule, which directly remediates the /etc/crypto-policies/local.d/opensshserver-ospp.config file, .. so the change should be as simple as adding the two keytypes to shared.sh and OVAL.

FTR; I've tested this on 8.2 as well and the issue is not present there (FIPS.pmod from crypto-policies correctly adds both KeyTypes).

Steve, is the order of the algorithms in PubkeyAcceptedKeyTypes important? If so, what should it be?

I don't think its order sensitive since its the client making the proposals. But just in case, add these to the beginning.

Fixed upstream: https://github.com/ComplianceAsCode/content/pull/5742

The BZ is Modified, because the pull request has been backported to the 8.1 CC branch.

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-2020:4626