Important: only Python2 versions are affected. Python3 works OK.
Possibly related issue: http://bugs.python.org/issue12378 (differs: see the line above)


Having a server with SSLSocket waiting for connections, the incoming connection, failed on automatic do_handshake(), stays open forever — accept() raises the SSLError and does not return client connection socket.

Steps to reproduce
==================

server side:

1. create a SOCK_STREAM socket
2. wrap it with wrap_socket()
3. listen()
4. accept()

client side:

1. telnet to this port
2. enter any random text

How reproducible
================

In all 146%

Expected results
================

1. Incoming connection is closed and client disconnected

Actual results
==============

1. On the server side, due to exception, the reference to the incoming connection gets lost.
2. The client stays connected as long as the server operates.

Possible solution would be something like that in SSLSocket.do_handshake():

    try:
        self._sslobj.do_handshake()
    except SSLError as e:  # or even any Exception?
        self._sock.close()
        raise e

Thanks for reporting. For maximum backwards compatibility, the safer fix is to close the socket only in SSLSocket.accept().
Unfortunately I can't think of a way to write a unittest for it, so I'll just commit the fix.

New changeset 85e5a93e534e by Antoine Pitrou in branch '2.7':
Issue #17918: When using SSLSocket.accept(), if the SSL handshake failed on the new socket, the socket would linger indefinitely.
http://hg.python.org/cpython/rev/85e5a93e534e