tls1.3

How to handle HttpWebRequest C# with Tls 1.3

半世苍凉 提交于 2020-06-28 07:58:16
问题 I am unable to connect to an HTTPS server (TLS 1.3) using WebRequest because of this error message: The request was aborted: Could not create SSL/TLS secure channel. The previous TLS version was 1.2 and with below code I could GET the page properly but as the page ssl upgraded to TLS 1.3 I got the error and also I cannot find any solution about it: ServicePointManager.Expect100Continue = true; ServicePointManager.SecurityProtocol = SecurityProtocolType.Tls12; In fact, I think it should be

How to enable TLSv1.3 for OkHttp 3.12.x on Android 8/9?

六月ゝ 毕业季﹏ 提交于 2020-01-13 09:37:10
问题 I'm using OkHttp 3.12.2 on Android 9 (Pixel 2 device) and try to connect to an nginx 1.14.0 running with OpenSSL 1.1.1. The nginx is capable of TLSv1.3, I verified this with Firefox 66.0.2 on Ubuntu 18.04, Chrome 73.0 on Android 9 and ChromeOS 72.0. However, OkHttp always negotiates TLSv1.2 . I also tried to set a RESTRICTED_TLS ConnectionSpec, but it didn't help. I did not find a specific instruction on how to get TLSv1.3 working on Android. I know that only Android 8 and 9 support TLSv1.3

How to properly use TLS 1.3 cipher suites in HiveMQ? (Getting a SSL exception: closing inbound before receiving peer's close_notify)

為{幸葍}努か 提交于 2019-12-11 04:28:20
问题 I want to use TLS 1.3 for my secure communication with HiveMQ. I've configured the HiveMQ community edition server config.xml file to specify to use TLS 1.3 cipher suites and I pointed it to the keystore containing a key pair for a 256-bit Elliptic curve key (EC NOT DSA) using the curve: secp256r1 (which is one of the few curves supported by TLS 1.3). The 256-bit key pair is for this TLS 1.3 cipher suite I want to use: TLS_AES_128_GCM_SHA256 . I'm also generated a 384-bit elliptic curve key