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 loewis
Recipients Nathanael.Noblet, loewis, orsenthil, pitrou
Date 2012-01-29.22:48:34
SpamBayes Score 1.6819716e-06
Marked as misclassified No
Message-id <1327877315.66.0.157783616911.issue13856@psf.upfronthosting.co.za>
In-reply-to
Content
For 3.x, xmlrpc.client should just pass-through the SSL context. Since the code to do so will be quite different from the current patch, I'm tempted to close this issue as rejected, unless Nathanael indicates that he would like to redo the patch for 3.x; this issue could then be recycled for that.

orsenthil: I don't fully understand your question (what kind of "carrying" should the clients do); the standard library most certainly supports validation of the server certificate.
History
Date User Action Args
2012-01-29 22:48:35loewissetrecipients: + loewis, orsenthil, pitrou, Nathanael.Noblet
2012-01-29 22:48:35loewissetmessageid: <1327877315.66.0.157783616911.issue13856@psf.upfronthosting.co.za>
2012-01-29 22:48:35loewislinkissue13856 messages
2012-01-29 22:48:34loewiscreate