-
Notifications
You must be signed in to change notification settings - Fork 1k
.NET 8 TLS 1.3 connection drops when application data arrives before SslStream Authentication completes #636
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: dev
Are you sure you want to change the base?
Conversation
…ntication completed
…ntication completed
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Copilot reviewed 49 out of 49 changed files in this pull request and generated 2 comments.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
Co-authored-by: Copilot <[email protected]>
…Netty into hayang/tls13-1
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Pull request overview
Copilot reviewed 49 out of 49 changed files in this pull request and generated 1 comment.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
Co-authored-by: Copilot <[email protected]>
Customer are seeing intermittent TCP socket closures immediately after the TLS handshake when DPS is accessed using a Golang TLS client (around 30-50% percent). If application data is sent immediately after the TLS 1.3 Finished message,
SChannelintermittently closes the connection whenSslStreamnot completed the authentication(Async flow from DotNetty). Adding a very short delay (20–100ms) or sending the Session Ticket extension from client side removes the issue. This behavior has not been observed in .NET, OpenSSL, or any other customer environments.Changes includes: