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.
Bug 1365490 - RHEA-2016:0817-1 broke usage of $ENV{HTTPS_CERT_FILE} and $ENV{HTTPS_KEY_FILE}
Summary: RHEA-2016:0817-1 broke usage of $ENV{HTTPS_CERT_FILE} and $ENV{HTTPS_KEY_FILE}
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: perl-libwww-perl
Version: 6.8
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Petr Pisar
QA Contact: Martin Kyral
URL:
Whiteboard:
Depends On:
Blocks: 1359263
TreeView+ depends on / blocked
 
Reported: 2016-08-09 11:39 UTC by Pasi Sjöholm
Modified: 2017-03-21 09:25 UTC (History)
5 users (show)

Fixed In Version: perl-libwww-perl-5.833-4.el6
Doc Type: If docs needed, set a value
Doc Text:
Cause: Using an LWP Perl module that does a client TLS authentication and the client credentials are specified by HTTPS_CERT_FILE and HTTPS_KEY_FILE environment variables after updating perl-libwww-perl package to 5.833-3.el6 version. Consequence: The module does not send client certificate to a server. This usually leads to access denial to an HTTPS server. Fix: A support for HTTPS_CERT_FILE and HTTPS_KEY_FILE environment variables to specify files with client's certificate and client's private key was added to LWP's IO::Socket::SSL TLS back-end. Result: LWP applications that used environment variables for specifying their TLS credentials keep working even with updated perl-libwww-perl package that changed default TLS backend from Net::SSL to IO::Socket::SSL.
Clone Of:
Environment:
Last Closed: 2017-03-21 09:25:37 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
Fix (1.51 KB, patch)
2016-08-30 12:05 UTC, Petr Pisar 		no flags Details | Diff
Test case (571 bytes, text/plain)
2016-08-30 12:27 UTC, Petr Pisar 		no flags Details
View All


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 745800 0 high CLOSED perl-libwww-perl: add support for setting SSL options in LWP::UserAgent 2021-02-22 00:41:40 UTC
Red Hat Product Errata RHBA-2017:0599 0 normal SHIPPED_LIVE perl-libwww-perl bug fix update 2017-03-21 12:26:06 UTC

Description Pasi Sjöholm 2016-08-09 11:39:19 UTC 
Description of problem:

By default the RHEA-2016:0817-1 broke the usage of $ENV{HTTPS_CERT_FILE} and $ENV{HTTPS_KEY_FILE}. As the patch (https://bugzilla.redhat.com/attachment.cgi?id=1103499&action=diff) does not provide compability between IO::Socket:SSL and Net::SSL


Version-Release number of selected component (if applicable):
perl-libwww-perl-5.833-3.el6

How reproducible:
100%

Steps to Reproduce:
1. Use SSL client certificates through $ENV{HTTPS_CERT_FILE} and $ENV{HTTPS_KEY_FILE}

Actual results:
Failure.

Expected results:
Something that does not require people to modify using the code as the API gets broken between maintenance releases.
Comment 2 Petr Pisar 2016-08-30 11:34:59 UTC 
Net::SSL recognizes these environment variables:

HTTPS_CA_DIR
HTTPS_CA_FILE
HTTPS_CERT_FILE
HTTPS_DEBUG
HTTPS_KEY_FILE
HTTPS_PKCS12_FILE
HTTPS_PKCS12_PASSWORD
HTTPS_PROXY
HTTPS_PROXY_PASSWORD
HTTPS_PROXY_USERNAME
HTTPS_VERSION

Not all of them can be implemented on top of IO::Socket::SSL. Thus full compatibility is not possible. We can add support for HTTPS_KEY_FILE and HTTPS_CERT_FILE easily.

But please contact Red Hat support. These changes are driven by customer requests and Bugzilla is not a support tool.
Comment 3 Petr Pisar 2016-08-30 12:05:58 UTC 
Created attachment 1195865 [details]
Fix
Comment 4 Petr Pisar 2016-08-30 12:27:17 UTC 
Created attachment 1195881 [details]
Test case

For testing you can use certificate and key files from test case in bug #745800 and this attached script.

How to test:

(1) Create TLS server and client certificates and keys.
(2) Start an TLS server requiring client certificate.
(3) Use an LWP user agent to connect to the server. The LWP user agent should be invoked with HTTPS_CERT_FILE and HTTPS_KEY_FILE environment variables pointing client certificate and key file.
(4) Check the server accepts a connection from the client because the client sent certificate specified in the HTTPS_CERT_FILE environment variable.
Before: The server refuses the connection because the client does not send any certificate.
After: The server accepts the connection.

Please perform the test with perl-IO-Socket-SSL and without perl-Crypt-SSLeay packages installed. Then repeat the test with perl-Crypt-SSLeay and without perl-IO-Socket-SSL installed.

Please note that this special compatibility fix is intended for RHEL-6 only.
Comment 13 errata-xmlrpc 2017-03-21 09:25:37 UTC 
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, 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://rhn.redhat.com/errata/RHBA-2017-0599.html
Note You need to log in before you can comment on or make changes to this bug.