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 1260406 - No TLS1.1 or TLS1.2 support in pycurl
Summary: No TLS1.1 or TLS1.2 support in pycurl
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: python-pycurl
Version: 6.7
Hardware: Unspecified
OS: Unspecified
high
medium
Target Milestone: rc
: ---
Assignee: Kamil Dudka
QA Contact: Jan Kepler
Robert Krátký
URL:
Whiteboard:
Depends On: 1260407
Blocks: 1162746 1253743 1254457 1269889 1310222
TreeView+ depends on / blocked
 
Reported: 2015-09-06 13:42 UTC by Filip Krska
Modified: 2019-10-10 10:09 UTC (History)
6 users (show)

Fixed In Version: python-pycurl-7.19.0-9.el6
Doc Type: Enhancement
Doc Text:
*pycurl* now provides options to require TLSv1.1 or 1.2 With this update, *pycurl* has been enhanced to support options that make it possible to require the use of the 1.1 or 1.2 versions of the TLS protocol, which improves the security of communication.
Clone Of:
: 1260407 (view as bug list)
Environment:
Last Closed: 2016-05-10 19:44:21 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
support for TLSv1_x options (744 bytes, patch)
2015-09-06 13:42 UTC, Filip Krska 		fkrska: review?
Details | Diff
View All


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHEA-2016:0757 0 normal SHIPPED_LIVE python-pycurl enhancement update 2016-05-10 22:32:33 UTC

Description Filip Krska 2015-09-06 13:42:16 UTC 
Created attachment 1070745 [details]
support for TLSv1_x options

Description of problem:

pycurl doesn't support the TLS1.1 and TLS1.2 options introduced in curl-7.19.7-43

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

python-pycurl-7.19.0-8.el6

How reproducible:

always

Steps to Reproduce:
1. create test script:

# cat /tmp/pycurl_TLS.py
import pycurl
from StringIO import StringIO

buffer = StringIO()

c=pycurl.Curl()
c.setopt(c.URL, "https://www.redhat.com")
c.setopt(c.SSLVERSION, c.SSLVERSION_TLSv1_2)


c.perform()
c.close()

body = buffer.getvalue()
print(body)

2.

# python /tmp/pycurl_TLS.py


Actual results:

Traceback (most recent call last):
  File "/tmp/pycurl_TLS.py", line 9, in <module>
    c.setopt(c.SSLVERSION, c.SSLVERSION_TLSv1_2)
AttributeError: SSLVERSION_TLSv1_2


Expected results:

<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
<html><head>
...

Additional info:

Easyfix patch attached.

needed to propagate to upstream
Comment 1 Kamil Dudka 2015-09-07 08:27:04 UTC 
upstream commit:

https://github.com/pycurl/pycurl/commit/83ccaa22
Comment 14 errata-xmlrpc 2016-05-10 19:44:21 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/RHEA-2016-0757.html
Note You need to log in before you can comment on or make changes to this bug.