[issue25292] ssl socket gets into broken state when client exits during handshake

Carl Bordum Hansen added the comment: I have submitted a proposed solution Just found this similar issue https://bugs.python.org/issue35840 -- ___ Python tracker ___

[issue25292] ssl socket gets into broken state when client exits during handshake

Change by Carl Bordum Hansen : -- keywords: +patch nosy: +carlbordum nosy_count: 5.0 -> 6.0 pull_requests: +21544 stage: -> patch review pull_request: https://github.com/python/cpython/pull/22541 ___ Python tracker

[issue25292] ssl socket gets into broken state when client exits during handshake

Christian Heimes added the comment: This looks like a problem in asyncio. When the client closes the writer, the TLS and TCP connections are shut down. The server's writer still accept data although it is not written to the underlying ssl object: (Pdb) writer.transport._ssl_protocol._extra['ss

[issue25292] ssl socket gets into broken state when client exits during handshake

Yury Selivanov added the comment: Christian, would you be able to look into this before b2? -- ___ Python tracker ___ ___ Python-bugs-

[issue25292] ssl socket gets into broken state when client exits during handshake

Changes by Christian Heimes : -- assignee: -> christian.heimes components: +SSL nosy: +christian.heimes type: -> behavior versions: +Python 3.6, Python 3.7 ___ Python tracker _

[issue25292] ssl socket gets into broken state when client exits during handshake

New submission from Oleg: when i run the server in one terminal and the client in another the server output wold be: Serving on ('127.0.0.1', 8443) my transport None my backlog len 2 my backlog size 4200 that output proves that it is trying to write into socket, while there is no transport!