I'd really like an excuse to implement server-side SSL support one of these days. Could that be a sprint activity? Probably against 2.6 (I doubt the Modules/_ssl.c file will change much for 3K).
The idea is that if you call socket.ssl() on a socket that's bound to an address, the socket is assumed to be server-side, the cert passed in is assumed to be a server-side cert, and the SSLObject returned has a couple of extra methods, listen() and accept(). Calling accept() does the SSL dance with the remote side, and returns an SSLObject. Does this need a PEP? Bill _______________________________________________ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
