Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
The `pycurl.POSTFIELDS` option of *PycURL* now works correctly
Previously, the *PycURL* interface violated the *libcurl* API, which requires a string passed by the `CURLOPT_POSTFIELDS` option to remain valid until the transfer finishes. Consequently, if the `pycurl.POSTFIELDS` option was used, *libcurl* accessed a string beyond its lifetime, which resulted in an undefined behavior. An upstream patch has been applied on the *PycURL* source code to make sure that the string passed to the `CURLOPT_POSTFIELDS` option of *libcurl* remains valid long enough, and the described problem no longer occurs.
DescriptionGiuseppe Paterno'
2014-10-15 18:48:38 UTC
Created attachment 947290[details]
Script to reproduce the problem
Description of problem:
A python script using pycurl running on RHEL7 is behaving differently from RHEL6. The same script works fine on Mac OS X and Debian, including RHEL6 and CentOS6.
The pycurl version is exactly the same in RHEL6, RHEL7, Debian and MacOS.
During a post containing urlencode version of a base64 (SSH key), a strange binary is sent under RHEL7, while a standard HTTP post is performed under RHEL6.
The included script is a reduced version of a bigger component (securepass-tools) to reproduce the problem.
Version-Release number of selected component (if applicable):
pip version -> pycurl (7.19.0)
RPM -> python-pycurl-7.19.0-17.el7.x86_64
How reproducible:
Always on RHEL7
Works on RHEL6, MacOS and Debian
Steps to Reproduce:
1. use nc -l 5000 to simulate a web server
2. Execute the included script (or optionally available on https://gist.github.com/gpaterno/8eae080e4d5d33970876)
3. See the strange result
Actual results:
POST /test/ HTTP/1.1
User-Agent: PycURL/7.29.0
Host: localhost:5000
Accept: */*
Content-Length: 438
Content-Type: application/x-www-form-urlencoded
??????8??????????A`??????@??p?????з?1??.?6zoK5D2T1??.?X8COpdH51??.?z%2FFP3X1??.?Evw%3D%31
Expected results:
POST /test/ HTTP/1.1
User-Agent: PycURL/7.24.0
Host: localhost:5000
Accept: */*
Content-Length: 438
Content-Type: application/x-www-form-urlencoded
USERNAME=foobar&ATTRIBUTE=sshkey&VALUE=ssh-rsa+AADDB3NzaC1yc2EAAAABIwAAAQEA6ezbY7Pb9Ld2fRRgIzEaQln66HgJL0MkHPv7fYsU3Eo%2B8F5gC%2BgY4nbxCCuvvJ652WltW786Es1kduWpT13gKkT2TCqvXhC%2BTDbml5Rp9ECvrSs4Xlc2nYQb%2BMVwbEnnu3c92WaXs4q4Sjj2lTAAo6ftsjT00uqWUbjX1NoshnH9mo34NCnI2XniI50dNfDx4VxMK5ZRn6zoK5D2T9bKEsAHsmQpNKo9ySKai4SMVP%2FGnhAhyjLQtq5X8COpdH5AUJy4RHYyL0upF0ClvWYnLpPZuPajsoOZgruu3OQz%2FFP3XsosMZ04ZNL84mSDSBKE%2F6N2DMBxw9tl4cuHRx1Evw%3D%3D+
Additional info:
Note that the payload is actually a form of binary.
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-2016-2156.html