I would like to configure the server to refuse negotation of DES, RC4, MD5, etc. The mono 3.4 release notes say "Network Stack Now allows developers to control which cipher suites to use with TLS/SSL." ... But how?
相关问题
- “Zero out” sensitive String data in Swift
- Mechanize getting “Errno::ECONNRESET: Connection r
- High cost encryption but less cost decryption
- Tomcat and SSL Client certificate
- Can we add four protocols to ServicePointManager.S
相关文章
- ssl配置问题
- Visual Studio Code, MAC OS X, OmniSharp server is
- Intermittent “sslv3 alert handshake failure” under
- Bundling the Windows Mono runtime with an applicat
- Making a two way SSL authentication between apache
- decrypt TLS 1.2 AES-GCM packet
- How to use Jetty with Let's Encrypt certificat
- Sending email using php, gmail, and swiftmailer ca
(Thanks to Sebastien Pouliot for this answer)
You can set a callback for either ClientCipherSuitesCallback or ServerCipherSuitesCallback SSL/TLS. That will allow you to control which ciphers can be used and the selection order (in general most server select the first cipher suites they support).
Sample code is part of the documentation.
And also, since it will likely be difficult for some people to find the valid enumerations, see CipherSuiteFactory.cs