fix(NetSSL_Win): Error during handshake: failed to read data #4275
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
aleks-f
pushed a commit
that referenced
this pull request
Nov 23, 2023
aleks-f
pushed a commit
that referenced
this pull request
Nov 27, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
On some machines the InitializeSecurityContext() will return SEC_I_INCOMPLETE_CREDENTIALS during TLS handshake. That case is not handled, it will try to continue reading, thus blocking until timeout. The handling of this case would be to repeat the InitializeSecurityContext once again, or as we do here, inform to use a client cert if available.
See also:
steffengy/schannel-rs#32
https://stackoverflow.com/a/47479968
Closes #3944