Fix the issue of TLS handshake failure in .NET 8 environment.#616
Merged
Conversation
Signed-off-by: nivalxer <nivalxer@gmail.com>
Contributor
Author
|
@microsoft-github-policy-service agree |
nivalxer
force-pushed
the
fix_tls_net8
branch
2 times, most recently
from
6f242ee to
f2b92b3
Compare
Signed-off-by: nivalxer <nivalxer@gmail.com>
nivalxer
force-pushed
the
fix_tls_net8
branch
from
6eb38e8 to
392137e
Compare
marcschier
approved these changes
Jan 8, 2024
Contributor
Author
|
I have been running in a production environment with TLS encrypted communication for 1 month in .NET 8 without any issues. I hope we can merge it as soon as possible. |
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
A recent change was made to SslStream which calls Stream.Read on the inner stream with a zero byte buffer. So, in the .NET 8 environment, all TLS sessions will get stuck at the initialization phase.
AppVeyor does not currently support the .NET 8 SDK.