You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.
Show more details
GitHub fields:
assignee='https://github.com/tiran'closed_at=<Date2019-05-17.20:51:33.647>created_at=<Date2019-02-07.02:53:23.060>labels= ['expert-SSL', 'type-feature', '3.8', 'OS-windows']
title='Need openssl 1.1.1 support on Windows for ARM and ARM64'updated_at=<Date2019-05-17.20:51:33.646>user='https://github.com/paulmon'
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?
Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.
Show more details
GitHub fields:
bugs.python.org fields:
The text was updated successfully, but these errors were encountered: