Bug 1445309
Summary: | Please rebuild perl-WWW-Curl in rhel 7.3 to export extra CURL_SSLVERSION_TLSv1 symbols | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 7 | Reporter: | Paulo Andrade <pandrade> |
Component: | perl-WWW-Curl | Assignee: | Jitka Plesnikova <jplesnik> |
Status: | CLOSED ERRATA | QA Contact: | Jakub Heger <jheger> |
Severity: | medium | Docs Contact: | |
Priority: | unspecified | ||
Version: | 7.3 | CC: | djez, jheger, jkejda, jorton, jplesnik, ppisar |
Target Milestone: | rc | Keywords: | EasyFix, FastFix |
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
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.
|
Story Points: | --- |
Clone Of: | Environment: | ||
Last Closed: | 2018-04-10 08:37:46 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: | |
Embargoed: | |||
Bug Depends On: | |||
Bug Blocks: | 1420851, 1466370 |
Description
Paulo Andrade
2017-04-25 13:13:05 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 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 |