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 1445309 - Please rebuild perl-WWW-Curl in rhel 7.3 to export extra CURL_SSLVERSION_TLSv1 symbols
Summary: Please rebuild perl-WWW-Curl in rhel 7.3 to export extra CURL_SSLVERSION_TLSv...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: perl-WWW-Curl
Version: 7.3
Hardware: All
OS: Linux
unspecified
medium
Target Milestone: rc
: ---
Assignee: Jitka Plesnikova
QA Contact: Jakub Heger
URL:
Whiteboard:
Depends On:
Blocks: 1420851 1466370
TreeView+ depends on / blocked
 
Reported: 2017-04-25 13:13 UTC by Paulo Andrade
Modified: 2021-06-10 12:14 UTC (History)
6 users (show)

Fixed In Version: perl-WWW-Curl-4.15-13.el7
Doc Type: Bug Fix
Doc Text:
Cause: Use extra CURL_SSLVERSION_TLSv1* symbol via perl-WWW-Curl Consequence: Using CURL_SSLVERSION_TLSv1_1 and CURL_SSLVERSION_TLSv1_2 failed with an undefined symbol error. Fix: Rebuilt perl-WWW-Curl against the latest libcurl-devel Result: Using of extra symbols from libcurl-devel works properly.
Clone Of:
Environment:
Last Closed: 2018-04-10 08:37:46 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2018:0662 0 None None None 2018-04-10 08:37:56 UTC

Description Paulo Andrade 2017-04-25 13:13:05 UTC
Currently on rhel 7.3 this works:
$ perl -e 'use WWW::Curl::Easy; print &CURL_SSLVERSION_TLSv1 . "\n";'

but these fail with an undefined symbol error:
perl -e 'use WWW::Curl::Easy; print &CURL_SSLVERSION_TLSv1_1 . "\n";'
perl -e 'use WWW::Curl::Easy; print &CURL_SSLVERSION_TLSv1_2 . "\n";'

for example:
Undefined subroutine &main::CURL_SSLVERSION_TLSv1_2 called at -e line 1.

  Just rebuilding from sources fetches the symbols from libcurl-devel
and the above examples work. For example:

$ perl -e 'use WWW::Curl::Easy; print &CURL_SSLVERSION_TLSv1_1 . "\n";'
5

Comment 2 Jitka Plesnikova 2017-04-26 08:36:13 UTC
The bug is solve just by rebuilding perl-WWW-Curl against current RHEL 7  libcurl-devel.

How to test:

1) Install latest perl-WWW-Curl
2) Run commands:

perl -MWWW::Curl::Easy -e 'print &CURL_SSLVERSION_TLSv1 . "\n";'
perl -MWWW::Curl::Easy -e 'print &CURL_SSLVERSION_TLSv1_1 . "\n";'
perl -MWWW::Curl::Easy -e 'print &CURL_SSLVERSION_TLSv1_2 . "\n";'


Before:
1
Undefined subroutine &main::CURL_SSLVERSION_TLSv1_1 called at -e line 1.
Undefined subroutine &main::CURL_SSLVERSION_TLSv1_2 called at -e line 1.

After:
1
5
6

Comment 9 errata-xmlrpc 2018-04-10 08:37:46 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://access.redhat.com/errata/RHBA-2018:0662


Note You need to log in before you can comment on or make changes to this bug.