-
Notifications
You must be signed in to change notification settings - Fork 530
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
Add runtime platform support detection #92
Comments
Not a platform independent error code. Right now, at least one client, that type of error would result in TLS failing to initialize, which would result in a connection shutdown event to the app with whatever status code was returned by the TLS library. For schannel, it would be a fairly specific error code. For openssl, I believe it's just a generic TLS failed error code. |
Thanks. Lets make this a feature request then :) |
Related: dotnet/runtime#31689 |
Ok. Ideally, we'd define a cross-platform QUIC_STATUS for this, and then we need to figure out what TLS error codes need to be mapped to this. |
@scalablecory to be clear, we don't have a way to query "Is supported" from our TLS layers. For OpenSSL, it's currently statically linked, so it's always supported. For Schannel, the only way to know is to try it and see if it fails. With that in mind, what exactly is the ask here? |
Going to close this with no action, since there isn't really anything we can do here. @scalablecory if you have a specific ask here feel free to reopen with more info. |
It would be useful to have consistent error code(s) for
MsQuicOpen
to return when the current platform doesn't have a minimum Windows/OpenSSL version, registry for TLS 1.3 isn't enabled, etc.This would enable users to prompt the end-user, log, etc. with an obvious message indicating what they might do to get support.
The text was updated successfully, but these errors were encountered: