-
Notifications
You must be signed in to change notification settings - Fork 5k
SslStream not working with ephemeral keys #114640
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
Comments
Tagging subscribers to this area: @dotnet/area-system-security, @bartonjs, @vcsjones |
As discussed in the linked issue #103101, this ephemeral key restriction comes from Windows, not .NET.
The obsoletion message should direct you towards using the non-obsolete API. It should look something like this: X509CertificateLoader.LoadPkcs12(current.Export(X509ContentType.Pkcs12), null); |
Thanks, will check that!
I get it but there are two issues in .NET there:
Indeed I'd prefer to fix it with the fallback mode since it would make it more widely adopted. For example this case happens with minikube. |
Tagging subscribers to this area: @dotnet/ncl, @bartonjs, @vcsjones |
Description
Same issue than #103101
Reproduction Steps
See #103101
Expected behavior
It just works since code is there (
new X509Certificate2(current.Export(X509ContentType.Pkcs12))
makes it working)Actual behavior
It fails as in Same issue than #103101
Regression?
I do not know
Known Workarounds
Using
new X509Certificate2(current.Export(X509ContentType.Pkcs12))
but it relies on obsolete code which is undesiredConfiguration
No response
Other information
No response
The text was updated successfully, but these errors were encountered: