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.

OpenSSL 3.0.0 in RHEL-9 does not support SHA-1 for signature creation and verification by default (SHA-1 KDFs and HMACs are still supported). However, to support backwards compatibility with RHEL-8 systems that still use SHA-1 for signatures, a new configuration option - ‘rh-allow-sha1-signatures’ is introduced in RHEL-9. This config option, if enabled in the ‘alg_section’ of openssl.cnf, additionally permits the creation and verification of SHA-1 signatures.

We would like this option would be automatically set if the LEGACY policy is set via crypto-policies. 

Exact name of the config option - rh-allow-sha1-signatures could vary. It will be implemented as part of https://bugzilla.redhat.com/show_bug.cgi?id=2031742

Can we get https://kojihub.stream.centos.org/koji/buildinfo?buildID=16754 pushed to mirrors? The package is not available yet there and it will simplify setting openssl for supporting COPR and CentOS SIGs rpms installation

(In reply to Sandro Bonazzola from comment #7)
> Can we get https://kojihub.stream.centos.org/koji/buildinfo?buildID=16754
> pushed to mirrors? The package is not available yet there and it will
> simplify setting openssl for supporting COPR and CentOS SIGs rpms
> installation

There's other work that needs to land before this can be made available.  It will be tagged in as soon as possible.

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 (new packages: crypto-policies), 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:3953

The needinfo request[s] on this closed bug have been removed as they have been unresolved for 365 days