homepage

With the patch applied on 3.2 (it doesn't apply on default), the test passes,
but it also prints out this exception traceback:
 test_protocol_sslv3 (test.test_ssl.ThreadedTests)
 Connecting to an SSLv3 server with various client options ... 
 SSLv3->SSLv3 CERT_NONE
 SSLv3->SSLv3 CERT_OPTIONAL
 SSLv3->SSLv3 CERT_REQUIRED
 {SSLv23->SSLv3} CERT_NONE
 Exception in thread Thread-8:
 Traceback (most recent call last):
 File "/home/nadeem/src/cpython/3.2/Lib/threading.py", line 741, in _bootstrap_inner
 self.run()
 File "/home/nadeem/src/cpython/3.2/Lib/test/test_ssl.py", line 810, in run
 if not self.wrap_conn():
 File "/home/nadeem/src/cpython/3.2/Lib/test/test_ssl.py", line 764, in wrap_conn
 self.sock, server_side=True)
 File "/home/nadeem/src/cpython/3.2/Lib/ssl.py", line 189, in wrap_socket
 _context=self)
 File "/home/nadeem/src/cpython/3.2/Lib/ssl.py", line 276, in __init__
 raise x
 File "/home/nadeem/src/cpython/3.2/Lib/ssl.py", line 272, in __init__
 self.do_handshake()
 File "/home/nadeem/src/cpython/3.2/Lib/ssl.py", line 451, in do_handshake
 self._sslobj.do_handshake()
 socket.error: [Errno 104] Connection reset by peer
 {TLSv1->SSLv3} CERT_NONE
 SSLv23->SSLv3 CERT_NONE
 ok
I'm assuming it's unrelated, though - I get the same traceback on earlier
revisions (before the test started hanging). Should I file a separate bug?