Re: [Python-Dev] Other SSL issues in the tracker have been marked
On 8/28/07, Bill Janssen <janssen@parc.com> wrote:
Well, that's just what you get with two independent implementations of a spec. We don't try to hide the differences between the sockets stack in Unix and Windows -- you'll just have to work around it. -- --Guido van Rossum (home page: http://www.python.org/~guido/)
Bill Janssen schrieb:
I think "the spec" would be the socket API. For sockets, that is POSIX. According to http://www.opengroup.org/pubs/online/7908799/xns/getsockname.html the result is unspecified if the socket has not been bound to a local name. However, Windows does not implement POSIX here; instead, it implements WinSock, which specifies that WSAEINVAL is returned. Regards, Martin
So, the patch is attached to issue 1052. I sent it out to python-dev, but it got blocked (too big). http://bugs.python.org/file8352/ssl-patch-5 This contains a number of things: 1) Improve the documentation of the SSL module, with a fuller explanation of certificate usage, another reference, proper formatting of this and that. 2) Fix Windows bug in ssl.py, and general bug in sslsocket.close(). Remove some unused code from ssl.py. Allow accept() to be called on sslsocket sockets. 3) Use try-except-else in import of ssl in socket.py. Deprecate use of socket.ssl(). 4) Remove use of socket.ssl() in every library module, except for test_socket_ssl.py and test_ssl.py. Bill
Yes, the Windows buildbots seem happy now with ssl. I'm going to expand the test suite. Bill
Bill Janssen schrieb:
I think "the spec" would be the socket API. For sockets, that is POSIX. According to http://www.opengroup.org/pubs/online/7908799/xns/getsockname.html the result is unspecified if the socket has not been bound to a local name. However, Windows does not implement POSIX here; instead, it implements WinSock, which specifies that WSAEINVAL is returned. Regards, Martin
So, the patch is attached to issue 1052. I sent it out to python-dev, but it got blocked (too big). http://bugs.python.org/file8352/ssl-patch-5 This contains a number of things: 1) Improve the documentation of the SSL module, with a fuller explanation of certificate usage, another reference, proper formatting of this and that. 2) Fix Windows bug in ssl.py, and general bug in sslsocket.close(). Remove some unused code from ssl.py. Allow accept() to be called on sslsocket sockets. 3) Use try-except-else in import of ssl in socket.py. Deprecate use of socket.ssl(). 4) Remove use of socket.ssl() in every library module, except for test_socket_ssl.py and test_ssl.py. Bill
Yes, the Windows buildbots seem happy now with ssl. I'm going to expand the test suite. Bill
participants (3)
-
"Martin v. Löwis" -
Bill Janssen -
Guido van Rossum