Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 560978

Summary: SSL for python API
Product: Red Hat Enterprise MRG Reporter: Rafael H. Schloming <rafaels>
Component: python-qpidAssignee: Rafael H. Schloming <rafaels>
Status: CLOSED UPSTREAM QA Contact: MRG Quality Engineering <mrgqe-bugs>
Severity: medium Docs Contact:
Priority: high    
Version: DevelopmentCC: gsim, jross, mkudlej, tross
Target Milestone: 1.3   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-07-05 14:48:58 UTC Type: ---
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: 552330    

Description Rafael H. Schloming 2010-02-02 11:59:04 UTC 
Description of problem:

Because the new python client uses non-blocking I/O, the simple ssl socket wrapping available in python 2.4 and 2.5 won't work. The ssl module available in 2.6 seems to have support for ssl on non-blocking sockets, however support for this will need to be integrated into the client. Once done this will still leave the python client without SSL on RHEL-4 and RHEL-5 as neither one has python 2.6. One option for addressing this would be to pull in the python-ssl package which backports the ssl module to python 2.3, 2.4, and 2.5.

The module backport can be found here: http://pypi.python.org/pypi/ssl/

It appears to have been packaged already. (Google python-ssl rpm to find).
Comment 1 Jonathan Robie 2011-02-01 19:43:55 UTC 
*** Bug 641330 has been marked as a duplicate of this bug. ***