Bug 973823 - Nectar's HTTPSCurlDownloader uses ssl_client_certs handed to other downloaders
Nectar's HTTPSCurlDownloader uses ssl_client_certs handed to other downloaders
Product: Pulp
Classification: Community
Component: z_other (Show other bugs)
Unspecified Unspecified
low Severity high
: ---
: ---
Assigned To: pulp-bugs
Preethi Thomas
: Triaged
Depends On:
  Show dependency treegraph
Reported: 2013-06-12 17:00 EDT by Randy Barlow
Modified: 2014-11-11 21:42 EST (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2014-11-11 21:42:24 EST
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Randy Barlow 2013-06-12 17:00:37 EDT
This is a tough one to track down so far, but if you instantiate two HTTPSCurlDownloaders, giving one an SSL client cert and not giving such a cert to the other, the one that wasn't given the certificate will still use it.
Comment 2 Randy Barlow 2013-06-12 17:10:43 EDT
I noticed that the curl.py file doesn't use the cleanup process described in the libcurl documentation[0]. I'm not sure that's the cause of the problem, but it might be.

[0] http://curl.haxx.se/libcurl/c/curl_multi_cleanup.html
Comment 3 Michael Hrivnak 2013-09-26 15:29:02 EDT
moving this to low priority since nothing is using the curl downloader now
Comment 4 Chris Duryee 2014-11-11 21:42:24 EST
This downloader was removed from nectar in version 1.1.7.

Closing bug as CLOSED/NOTABUG.

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