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.
1. Proposed title of this feature request
RHEL6 update for Net:SSL or perl-Crypt-SSLeay.x86_64
2. What is the nature and description of the request?
Application upgrade requirement
3. Why do you need this - specific/brief business justification ?
Our client needs to update their application before December. The application vendor requires Net:SSL version 2.85 or higher.
4. Is there already an existing RFE upstream or in Red Hat Bugzilla?
Unknown - not found.
5. Do you have any specific timeline dependencies and which release would they like to target (i.e. RHEL5, RHEL6)?
12/1/2016 for RHEL6
6. Is the sales team involved in this request and do they have any additional input?
No
7. List any affected packages or components.
Net:SSL which is integrated within perl-Crypt-SSLeay.x86_64
8. Will you be assist in testing this functionality if implemented?
We have a test environment. Once we have Net:SSL version 2.85 on our Satellite, we will provide it for our client's test servers and they can upgrade the application in Dev/Test and begin verification.
Could you explain what specific feature the custom is missing in the Net::SSL module?
I have problem with this request for upgrade for these reasons:
(1) RHEL does not upgrade packages just only because of "old version".
(2) RHEL-6 reached a life-cycle phase in which no new features are allowed.
The Net:SSL 2.85 first appear in Crypt-SSLeay-0.58. There are many changes between current RHEL's Crypt-SSLeay-0.57 and the requested 0.58 <http://cpansearch.perl.org/src/NANIS/Crypt-SSLeay-0.72/Changes>. Could you please quote what's the desired item by the customer?
The change log contains mostly bug fixes and build script refactoring. So upgrading could be safe. But still I would prefer back-porting a fix.
I'm sorry, RHEL-6 is now in production phase 2 where no new features are added into the product <https://access.redhat.com/support/policy/updates/errata/>.
If you want new features, you can migrate to RHEL-7 where you can find perl-Crypt-SSLeay-0.64-5.el7 that provides Net::SSL 2.85.
1. Proposed title of this feature request RHEL6 update for Net:SSL or perl-Crypt-SSLeay.x86_64 2. What is the nature and description of the request? Application upgrade requirement 3. Why do you need this - specific/brief business justification ? Our client needs to update their application before December. The application vendor requires Net:SSL version 2.85 or higher. 4. Is there already an existing RFE upstream or in Red Hat Bugzilla? Unknown - not found. 5. Do you have any specific timeline dependencies and which release would they like to target (i.e. RHEL5, RHEL6)? 12/1/2016 for RHEL6 6. Is the sales team involved in this request and do they have any additional input? No 7. List any affected packages or components. Net:SSL which is integrated within perl-Crypt-SSLeay.x86_64 8. Will you be assist in testing this functionality if implemented? We have a test environment. Once we have Net:SSL version 2.85 on our Satellite, we will provide it for our client's test servers and they can upgrade the application in Dev/Test and begin verification.