-
Notifications
You must be signed in to change notification settings - Fork 4.7k
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
[QUIC] Support for OpenSSL build of MsQuic on Windows #69978
Comments
Tagging subscribers to this area: @dotnet/ncl Issue DetailsCurrently, we assume that on Windows, MsQuic uses Schannel for TLS operations and on LInux it uses OpenSSL. This influences how we pass certificates to MsQuic Lines 183 to 221 in a4223dc
And also some certificate related flags: Lines 55 to 58 in a4223dc
However, it is possible to build MsQuic with OpenSSL for Windows (e.g. to use on older Windows without TLS 1.3 support via Schannel). So we should instead make these decision based on the actual TLS backend being used. This information can be retrieved via recently added API: microsoft/msquic#2762.
|
Currently, we assume that on Windows, MsQuic always uses Schannel for TLS operations and on Linux it uses OpenSSL. This influences how we pass certificates to MsQuic
runtime/src/libraries/System.Net.Quic/src/System/Net/Quic/Implementations/MsQuic/Interop/SafeMsQuicConfigurationHandle.cs
Lines 183 to 221 in a4223dc
And also some certificate related flags:
runtime/src/libraries/System.Net.Quic/src/System/Net/Quic/Implementations/MsQuic/Interop/SafeMsQuicConfigurationHandle.cs
Lines 55 to 58 in a4223dc
However, it is possible to build MsQuic with OpenSSL for Windows (e.g. to use on older Windows without TLS 1.3 support via Schannel). So we should instead make these decision based on the actual TLS backend being used. This information can be retrieved via recently added API: microsoft/msquic#2762.
The text was updated successfully, but these errors were encountered: