3 ms·
What are you talking about? It's using TLS 1.3 and is signed by the GlobalSign root CA! It's using the most compatible RSA 2048 crypto, and all the parameters l
by jiggawatts 7y ago
What are you talking about? It's using TLS 1.3 and is signed by the GlobalSign root CA! It's using the most compatible RSA 2048 crypto, and all the parameters look valid.
Maybe you are a victim of a man-in-the-middle attack right now and the "stupid warnings" you're blithely clicking through are informing you of this.
- emmelaich 7y agoFor me, GlobalSign lack of / failing to get GlobalSign intermediate certs pops up surprisingly often.
- jiggawatts 7y agoThat's typically a proxy problem. The intermediate certificates are automatically downloaded by all decent X.509 clients such as Windows, Firefox, or Chrome. However, if the proxy is occasionally dropping requests or replacing them with one of those stupid "log on to the proxy here" pages, then the chain discovery will fail randomly and you'll get these issues. It's also common in environments where the security trolls have blocked HTTP (as in, TCP port 80) because they think it's "insecure", but this just causes X.509 issues like this because it uses only HTTP and never HTTPS for CRLs, OCSP, and intermediate CA certificate downloads.
- emmelaich 7y agoThanks, that's great info.