This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author kiilerix
Recipients kiilerix, pitrou
Date 2012-01-06.22:14:34
SpamBayes Score 4.8546553e-06
Marked as misclassified No
Message-id <1325888075.0.0.00318737341897.issue13721@psf.upfronthosting.co.za>
In-reply-to
Content
I think it would be confusing if getpeercert returned None both for valid connections without certificates and also for invalid connections. I would almost prefer the current behaviour (AttributeError) if just it was documented and there was a documented way to check if the connection actually was alive. Do you agree that checking .cipher() is the recommended way to do that in a way that is compatible with past and future 2.x versions?

I hope the proper fix will ensure that an exception always is raised if the ssl handshake fails - and that a successful wrap_socket means that the ssl negotiation did succeed with the given constraints. It might however only be feasible to fix that for 3.x.

I filed Issue13724 for the create_socket documentation.
History
Date User Action Args
2012-01-06 22:14:35kiilerixsetrecipients: + kiilerix, pitrou
2012-01-06 22:14:34kiilerixsetmessageid: <1325888075.0.0.00318737341897.issue13721@psf.upfronthosting.co.za>
2012-01-06 22:14:34kiilerixlinkissue13721 messages
2012-01-06 22:14:34kiilerixcreate