To see the suites, close all browser windows, then open this exact page directly. (1) When a browser supports SSL 2, its SSL 2-only suites are shown only on the very first connection to this site. TLS_RSA_WITH_NULL_SHA256 ( 0x3b ) INSECURE 0 TLS_ECDH_RSA_WITH_NULL_SHA ( 0xc00b ) INSECURE 0 TLS_ECDH_ECDSA_WITH_NULL_SHA ( 0xc001 ) INSECURE 0 TLS_ECDHE_RSA_WITH_NULL_SHA ( 0xc010 ) INSECURE 0 TLS_ECDHE_ECDSA_WITH_NULL_SHA ( 0xc006 ) INSECURE 0 TLS_DHE_RSA_WITH_3DES_EDE_CBC_SHA ( 0x16 ) WEAK 112 TLS_RSA_WITH_3DES_EDE_CBC_SHA ( 0xa ) WEAK 112 TLS_ECDH_RSA_WITH_3DES_EDE_CBC_SHA ( 0xc00d ) WEAK 112
TLS_ECDH_ECDSA_WITH_3DES_EDE_CBC_SHA ( 0xc003 ) WEAK 112 TLS_ECDHE_RSA_WITH_3DES_EDE_CBC_SHA ( 0xc012 ) WEAK 112 TLS_ECDHE_ECDSA_WITH_3DES_EDE_CBC_SHA ( 0xc008 ) WEAK 112 TLS_EMPTY_RENEGOTIATION_INFO_SCSV ( 0xff ). This is the detailed TLS support report: Protocol Features So while it’s old (and I’m aware that it’s far away from Discourse‘s minimum supported OS+browser) I‘d like to enable them to a least connect to the site and see how their browser fares with the modern HTML and JavaScript. Your user agent supports TLS 1.2, which is recommended protocol version at the moment. Your user agent has good protocol support.
#SAFARI 10.1.2 MAC OS#
User Agent: Mozilla/5.0 (iPod CPU iPhone OS 6_1_6 like Mac OS X) AppleWebKit/536.26 (KHTML, like Gecko) Version/6.0 Mobile/10B500 Safari/8536.25 Protocol Support Thank you, I got a response from my user.
#SAFARI 10.1.2 HOW TO#
This is the URL, in case you have an idea how to check whether something is incorrectly configured: Is there a way to do a check first, something like “only if Browser supports TLS 1.2” or “only if Browser/OS greater than version”, otherwise stay with http? Is there another reason except for TLS 1.2, which would cause a browser/operating system to fail to establish a secure connection to a default Discourse installation using the default TLS support via Let’s Encrypt? I’m trying to figure out what questions I should ask of my users to figure out what their issue is and on what end it should be fixed.Īs a workaround: Afaict, the default is to redirect the traffic going to http to https. Support tables for HTML5, CSS3, etc Safari should be supporting TLS 1.2 since version 7. I first suspected TLS 1.2 support to be the issue, but the user I checked with is running Safari 10.1.2 on macOS (unknown version) and according to Can I use. Judging by the context those users seem to have somewhat older operating systems/browsers. It’s a browser-side error and the users don’t even see anything from Discourse. One screenshot I got from a user clearly points to an SSL/TLS error. After setting up my Discourse instance using the default Let’s Encrupt support, I got reports from some of my users that their browser can’t establish a secure connection to Discourse.
0 kommentar(er)
