Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.

Bug 1365490

Summary: RHEA-2016:0817-1 broke usage of $ENV{HTTPS_CERT_FILE} and $ENV{HTTPS_KEY_FILE}
Product: Red Hat Enterprise Linux 6 Reporter: Pasi Sjöholm <tigeli>
Component: perl-libwww-perlAssignee: Petr Pisar <ppisar>
Status: CLOSED ERRATA QA Contact: Martin Kyral <mkyral>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 6.8CC: bnater, jorton, perl-maint-list, ppisar, psabata
Target Milestone: rcKeywords: Patch, Regression
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
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.
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-03-21 09:25:37 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Bug Depends On:    
Bug Blocks: 1359263    
Description Flags
Test case none

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 ( does not provide compability between IO::Socket:SSL and Net::SSL

Version-Release number of selected component (if applicable):

How reproducible:

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

Actual results:

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:


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]

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.