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 desbma
Recipients desbma
Date 2014-11-27.20:23:06
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
When using xmlrpc.server it is possible (despite being intrusive) to use a custom SSL context, ie:

import ssl
import xmlrpc.server

rpc_server = xmlrpc.server.SimpleXMLRPCServer(...)
ssl_context = ssl.SSLContext()
# setup the context ...
rpc_server.socket = ssl_context.wrap_socket(rpc_server.socket, ...)

However it is not possible (unless using some ugly monkey patching, which I am ashamed of writing) to do the same for xmlrpc.client.

xmlrpc.client.ServerProxy() could accept a context constructor, and pass it to the SafeTransport instance, and then to the http.client.HTTPSConnection instance (

I would allow passing a SSL context more secure than the default one, and thus improve security.
Date User Action Args
2014-11-27 20:23:06desbmasetrecipients: + desbma
2014-11-27 20:23:06desbmasetmessageid: <>
2014-11-27 20:23:06desbmalinkissue22960 messages
2014-11-27 20:23:06desbmacreate