Bug 790863

Summary:	[RFE] Server (broker) certificate validation for Python client connected over ssl
Product:	Red Hat Enterprise MRG	Reporter:	Trevor McKay <tmckay>
Component:	python-qpid	Assignee:	messaging-bugs <messaging-bugs>
Status:	CLOSED DUPLICATE	QA Contact:	MRG Quality Engineering <mrgqe-bugs>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	Development	CC:	iboverma, jross, matt
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2013-02-27 10:57:18 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:

Description Trevor McKay 2012-02-15 15:31:59 UTC

Description of problem:

For secure connections from Python clients over ssl to the broker, we need the ability to do server certificate validation (including hostname validation) of the broker.

Comment 1 Trevor McKay 2012-02-16 14:27:26 UTC

For reference, a very similar problem was solved in BZ733447 for ssl communication with server certificate validation from Cumin (the Python client) to the condor-aviary server.

The final solution uses python-ssl if the module is available, but falls back on m2crypto if not.  This provides a solution on el6 with python-ssl and also a solution on el5 whether or not the unofficial backport of python-ssl has been installed.

Comment 2 Justin Ross 2013-02-27 10:57:18 UTC


*** This bug has been marked as a duplicate of bug 885167 ***