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.

Created attachment 1784008 [details]
Proposed patch

Well, this is doable, of course.

The downside is that, by tying SHA-1 to SECLEVEL, we'll lose the ability to go lower than what SECLEVEL=1 offers, even with custom policies.

See the proposed patch, do you have any better suggestions?

Infinite customisability to pick and choose supported signature algorithms and key sizes is not something upstream supports, so this is rather unavoidable. For people that have no choice but to go lower there's opting out of crypto-policies and SECLEVEL=0.

We have decided to no longer modify the SECLEVELS in OpenSSL. Instead we will implement a new config option that allows SHA-1 signatures.
Therefore this change in CP is not required.