4 ms·
Unrelated to the content of the page, I'm really starting to hate the push for SSL everywhere. This website has misconfigured certs and because of that my brow
by echelon 7y ago
Unrelated to the content of the page, I'm really starting to hate the push for SSL everywhere.
This website has misconfigured certs and because of that my browser blocks it. Chrome is corp IT-managed and has no opt-out, whereas Firefox lets me accept the certs, but it's ultimately been blocked by our DNS/firewall for the same reason.
I really hate SSL. The majority of informational sites do not need it. I understand that it doesn't protect my privacy, but it doesn't frankly matter that I'm accessing an informational page about Coronavirus. If people are willing to give up their privacy to adtech platforms like Google and Facebook, the information about what websites you read is already out there.
I feel like Google has just created a deeper moat by pushing for SSL.
People complain about Kubernetes, but that's infra for large orgs that you shouldn't opt into unless you need it. SSL is being forced on the small guys who can't handle the complexity nor automation. It's not fair.
- chipperyman573 7y agoThe biggest benefit for me is, it guarantees my ISP can't mess with my pages. They already do it with mild stuff (https://www.zdnet.com/article/comcast-injects-copyright-warnings-into-your-browser/ https://www.zdnet.com/article/comcast-injects-copyright-warn...) so I wouldn't put it past them to inject ads or something if they thought they'd make any money.
- sigjuice 7y agoIt is not just about YOUR ISP messing with your pages. There are many ISPs (a different one, every few hops).
- sciurus 7y agoWhat errors are you seeing? Perhaps your IT department is the cause. The certs look fine. https://www.ssllabs.com/ssltest/analyze.html?d=www.donttouchyaface.com https://www.ssllabs.com/ssltest/analyze.html?d=www.donttouch... https://www.ssllabs.com/ssltest/analyze.html?d=lzdmsmujepoc2xlgp13srg%2don.drv.tw https://www.ssllabs.com/ssltest/analyze.html?d=lzdmsmujepoc2...
- zerocrates 7y ago1: What's wrong with the site's certificate? Seems fine to me. 2: How does a greater penetration of HTTPS help Google's moat specifically? To my understanding, all the vendors are pretty much pushing in the same direction.
- jiggawatts 7y agoWhat 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.
- nathancahill 7y agoSeems to be fixed now? Unless your corp doesn't have GlobalSign root?
- sigjuice 7y agoHow you know the coronavirus information that you are getting from an http site hasn't been tampered with before it reaches you?
- smitop 7y agoYou can bypass hard HSTS errors in Chrome by typing in "thisisunsafe". There is no textbox to type it into, you have the press the letters on your keyboard blindly.