[issue40227] SSLError is not passed to the client during handshake

[Andrew Svetlov]

Andrew Svetlov  added the comment:

asyncio ssl support was rewritten from scratch.

--
resolution:  -> out of date
stage:  -> resolved
status: open -> closed

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue40227] SSLError is not passed to the client during handshake

[Ivan Ivanyuk]

New submission from Ivan Ivanyuk :

Due to the combination of the logic here: 
https://github.com/python/cpython/blob/master/Lib/asyncio/sslproto.py#L483 and 
changes introduced in the issue https://bugs.python.org/issue37035, the 
assumption that "Not-logged exceptions are not skipped but reported to the user 
by protocol.connection_lost(exc) callback." as stated in the issue is not valid.
 If SSLError happens during the handshake, no exception get's propagated even 
if it's possible to log stacktrace using loop.set_debug(True).

 As opposed to the usage pattern mentioned in the initial issue comment, we are 
very much interested in the errors there, so, for now, I just monkey patch 
SSLprotocol.connection_lost() in runtime to be like this 
https://github.com/anthrax-0/cpython/pull/1/commits/d652ed8d0e72bb839fe4841530cc48928b3c3bb0
 .

What should be the best solution for this?

--
components: asyncio
messages: 365988
nosy: asvetlov, iivanyuk, yselivanov
priority: normal
severity: normal
status: open
title: SSLError is not passed to the client during handshake
type: behavior
versions: Python 3.7, Python 3.8

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com