Wrap SSL sockets after connecting #1754
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fix for #1741 . Previously we have been wrapping sockets with an SSLContext before connection, and calling
connect_ex
to do a non-blocking connect, then callingdo_handshake
. But the TCP connect itself does not require the SSLContext, and it appears that in general, and definitely on python3.7, non-blocking connect_ex w/ ssl sockets is not fully supported.So this PR defers wrap_ssl until after the TCP socket is connected, which should side-step all of the ValueError / OSError issues raised by python3.7 due to poor support for connect_ex. Also it is simpler, which I like.
This change is![Reviewable](https://camo.githubusercontent.com/1541c4039185914e83657d3683ec25920c672c6c5c7ab4240ee7bff601adec0b/68747470733a2f2f72657669657761626c652e696f2f7265766965775f627574746f6e2e737667)