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:

I have noticed that for "compat-openssl11" package in RHEL9 and CentOS Stream there is no devel sub-package provided: devel files are stripped during the package build.

The devel files are needed to build some packages for which there is still no OpenSSL 3.0+ compatibility added, e.g. "opensmtpd" (see BZ#2132827).

Please provide "compat-openssl11-devel" sub-package, to have a possibility to build packages components against OpenSSL 1.1.1 natively.

Dear Denis,

Unfortunately we don't plan to add the compat-openssl11-devel package. We intentionally removed it in RHEL9 to prevent appearing the new packages depending on OpenSSL 1.1.1 in the distribution.

Just a reminder, with very limited exceptions you can just temporary ignore the deprecated warnings and rebuild your package against OpenSSL 3.0

Please feel free to ask us if any migration help is needed.

Dmitry, thank you for your answer.
We have a compatibility issue in opensmtpd, which is described in https://github.com/OpenSMTPD/OpenSMTPD/issues/1171
I understand that we need more traction with the upstream to fix it in a native way. But realistically, it won't be really soon.

If you can provide a minimal enough example and the real reason is that openssl considers legacy key to be a provided one, it shouldn't be too hard to fix.

We can reproduce faulty behavior as described in the ticket above. Currently, I know only this case.