[issue43622] TLS 1.3, client polling returns event without data

2021-03-30 Thread gchauvel
gchauvel added the comment: err: second item: copy/paste error, the exception is PySSLWantReadErrorObject -- ___ Python tracker <https://bugs.python.org/issue43

[issue43622] TLS 1.3, client polling returns event without data

2021-03-30 Thread gchauvel
gchauvel added the comment: Based on your first comment, poll returning an event and recv not able to read data is a behavior to expect with TLSv1.2/TLSv1.3 (or ...) So in order to use SSLContext in a polling loop with multiple file descriptors, a non-blocking mode (to avoid an fd event and

[issue43622] TLS 1.3, client polling returns event without data

2021-03-25 Thread gchauvel
gchauvel added the comment: that's not the polling in itself, it's: polling returning event + setblocking(False) + recv() which blocks note: the behavior is present for python3.6 -- ___ Python tracker <https://bugs.python.o

[issue43622] TLS 1.3, client polling returns event without data

2021-03-25 Thread gchauvel
New submission from gchauvel : A simple test in test_ssl.py [1][2] with following context: - client connects and listens to data without sending any first - traces to make sure no data is written at test level from server or client - TLSv1.3 is allowed or not using "context.op