-
Notifications
You must be signed in to change notification settings - Fork 5k
Expose QUIC TLS details on QuicConnection. #106391
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
Conversation
Note regarding the
|
Note regarding the
|
Tagging subscribers to this area: @dotnet/ncl |
No-Merge until main becomes 10.0 |
QUIC_CIPHER_SUITE.TLS_CHACHA20_POLY1305_SHA256 => TlsCipherSuite.TLS_CHACHA20_POLY1305_SHA256, | ||
_ => default | ||
}; | ||
_negotiatedSslProtocol = info.TlsProtocolVersion switch |
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.
I'm wondering if we need to bother at all ... at least until there is Tls 1.4. If anythiung I would Debug.Assert here as reminder.
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.
we actually don't need to bother with either of the switches, the enum values are the same so we can cast directly.
I added assert for TLS 1.3 and unit test for cipher suites so that we notice if something changes.
Alternative to #106368
Implements #70184.
Since TLS state is dropped by MsQuic after handshake since it is no longer needed, we need to retrieve TLS info during the CONNECTED event (as we do for negotiated ALPN)
cc: @wfurt