➜

This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author steve.dower
Recipients Paul Monson, christian.heimes, paul.moore, steve.dower, tim.golden, zach.ware
Date 2019-05-14.17:15:18
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1557854118.9.0.608047016453.issue35926@roundup.psfhosted.org>
In-reply-to
Content 
This PR has stalled because of errors raised by TLS 1.3

It seems that there may be a difference between sockets on Windows being non-blocking by default and other platforms being blocking by default. However, we think that is probably just causes TLS 1.3/OpenSSL 1.1.1b errors to show up in different places.

Has anyone figured out the TLS 1.3 issues yet?

Also, does anyone know why we default to different sockets on Windows?
History
Date User Action Args
2019-05-14 17:15:18steve.dowersetrecipients: + steve.dower, paul.moore, christian.heimes, tim.golden, zach.ware, Paul Monson
2019-05-14 17:15:18steve.dowersetmessageid: <1557854118.9.0.608047016453.issue35926@roundup.psfhosted.org>
2019-05-14 17:15:18steve.dowerlinkissue35926 messages
2019-05-14 17:15:18steve.dowercreate