Bill Janssen <[EMAIL PROTECTED]> added the comment: The 2.6/3.0 changes are now up-to-date. We could reconsider this problem. My guess is that we still don't quite know what to do.
I think the issue is that we need a way to "unwrap" the SSL-secured TCP stream, after it's been used. So we need to expose the SSL shutdown mechanism (already in the _ssl.c module) in the Python code. Something like socket = self.unwrap() which would return a plain socket.socket instance. _______________________________________ Python tracker <[EMAIL PROTECTED]> <http://bugs.python.org/issue2054> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
