On-by-default support for the latest draft of the TLS 1.3 specification
It's showing yes for me. By opening cloudflare blog, you can confirm that it is actually using TLS 1.3 (By opening the green padlock, arrow-show connection details and then selecting more information).But according to here
Qualys SSL Labs - Projects / SSL Client Test
My TLS 1.3 shows a 'No'.
If your TLS 1.3 is NOT enabled by default then visit the site below to turn it on
How to enable TLS 1.3 support in Firefox and Chrome - gHacks Tech News
I checked and, by default, the integer value is set to 4 for security.tls.version.max and yet TLS 1.3 is still a 'No' in
Qualys SSL Labs - Projects / SSL Client Test
Can someone confirm whether it's a Yes or No in the aforementioned ssllabs link?
Yah, I clicked on the green padlock and it shows only TLS 1.2. Like I said I checked and, by default, the integer value is set to 4 for security.tls.version.max. So, rightly speaking, FF should show a 'Yes' when checked withIt's showing yes for me. By opening cloudflare blog, you can confirm that it is actually using TLS 1.3 (By opening the green padlock, arrow-show connection details and then selecting more information).View attachment 191415View attachment 191416
Well, that's weird. Try disabling HTTPS scanning in your AV/security product, I have disabled it in KFA2019.Yah, I clicked on the green padlock and it shows only TLS 1.2. Like I said I checked and, by default, the integer value is set to 4 for security.tls.version.max. So, rightly speaking, FF should show a 'Yes' when checked with
Qualys SSL Labs - Projects / SSL Client Test
I'm getting something as below
https://cdn.ghacks.net/wp-content/uploads/2017/06/tls-1.3.jpg
Strange........
I got it right nowWell, that's weird. Try disabling HTTPS scanning in your AV/security product, I have disabled it in KFA2019.