Allow changing cipher suites offered in SSL/TLS handshake #19914
Labels
api-needs-work
API needs work before it is approved, it is NOT ready for implementation
area-System.Net.Security
help wanted
[up-for-grabs] Good issue for external contributors
Milestone
Some servers require clients to use specific suite of ciphers, that is different from the one netcore offers by default.
This is the list that netcore on Windows 10 defaults to (on my PC)
For comparison, here's the list netcore offers on OS X Sierra
Here's the cipher suites offered by .NET for Windows (TLS 1.0 is default unless different SslProtocol specified in call to AuthenticateAsClient)
One way to solve this in corefx would be to add something akin to Xamarin's ClientCipherSuitesCallback to the ServicePointManager.
Possible workarounds:
See workaround posted in Add SmtpClient support #14288.
See Microsoft knowledge base article on how to restrict the use of certain cryptographic algorithms and protocols in Schannel.dll (applicable to Windows only).
The text was updated successfully, but these errors were encountered: