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.
Description of problem:
Programs are starting to need openssl3.
If it is at all possible, we, the EPEL community, are asking for openssl 3.x to be put into RHEL 8.
Hi Troy,
unfortunately we don't have any customer request or any specific features from OpenSSL 3.0.0 that we need in RHEL-8.
So we would not be porting it to RHEL-8 and we don't have any plans to do it in the future.
I would be closing this issue for now.
Feel free to reach out to rhel-crypto ML if you need any more details. Thank you
(In reply to Sahana Prasad from comment #2)
> Troy, you could add OpenSSL 3.0.0 in EPEL and ensure the name doesn't
> conflict with 1.1.1
There are plans to figure out, and add openssl3 to epel.
Because it will be a little tricky to do, and then maintain, we wanted to check to see if it was possible to get it into RHEL8. Thus this bug.
I will not be the person putting it in epel8, but there are other people who are working on getting openssl3 in epel8.
I don't have a timeline yet, because it will be tricky.