[issue10127] ssl.SSLSocket().close() does not close the connection

2010-10-18 Thread Antoine Pitrou
Changes by Antoine Pitrou pit...@free.fr: -- status: pending - closed ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue10127 ___ ___ Python-bugs-list

[issue10127] ssl.SSLSocket().close() does not close the connection

2010-10-16 Thread R. David Murray
New submission from R. David Murray rdmur...@bitdance.com: Quoting PoltoS from issue 8293: If I do sock.close() (sock is instance of ssl.SSLSocket), the connection is not closed: I see it as Established in netstat and nothing is sent over network: tcpdump show nothing going thru the network.

[issue10127] ssl.SSLSocket().close() does not close the connection

2010-10-16 Thread PoltoS
PoltoS polto...@alsenet.com added the comment: After some investigations it seems that a dup() is called in ssl wrap_socket(), so on sock.close() the socket is not really closed, since there is still one more reference (file descriptor) in the kernel's tcp/ip stack. Can someone confirm this?

[issue10127] ssl.SSLSocket().close() does not close the connection

2010-10-16 Thread Antoine Pitrou
Antoine Pitrou pit...@free.fr added the comment: I cannot reproduce with 2.7, 3.1 or 3.2. It seems the issue is obsolete, many changes having been made to the ssl module since 2.6. -- resolution: - out of date status: open - pending ___ Python