4 ms·
Then maybe those platforms will finally implement it. In any case, there's an alternative: putting Cloudflare in front of the site. In fact, Google shows me a g
by icebraining 11y ago
Then maybe those platforms will finally implement it. In any case, there's an alternative: putting Cloudflare in front of the site. In fact, Google shows me a guide to do so when I search for "squarespace ssl".
Of course, that's hardly as secure as end-to-end HTTPS, but still, I trust the path between CF and SquareSpace much more than between the user's browser and SquareSpace.
- lambau 11y agoPlease do not put Cloudflare in front of your site. It makes it impossible for tor and VPN users to view your site since they have to solve an impossible captcha to even see the static content.
- mintplant 11y agoIt's possible to turn off security in the CloudFlare control panel. I think the bigger issue is that CloudFlare has become a single point of interception for MITM'ing huge portions of web traffic.
- ryanlol 11y agoI'm not sure, but I think CloudFlare will still hit Tor users with (unsolvable) captchas even with the lowest security settings. But yeah, this NSA slide is extremely relevant to cloudflare: http://cdn01.androidauthority.net/wp-content/uploads/2014/06/SSL-Added-and-Removed-Here.jpg http://cdn01.androidauthority.net/wp-content/uploads/2014/06...
- lambau 11y ago> I think CloudFlare will still hit Tor users with (unsolvable) captchas even with the lowest security settings. That is correct. I have not been able to get passed a Cloudflare captcha over tor for any website.
- ryanlol 11y agoBut putting CloudFlare in front of your site makes mass surveillance even easier than it would be for plaintext traffic without CloudFlare.
- leni536 11y agoI wonder how it's even allowed for CF to do this. "your site" <--- http ---> CF <--- https ---> clients is a poor solution and it only hides that the connection is actually not secure. Isn't this a misuse of many CA's TOS and should result in certificate revocation? Maybe I'm wrong though.
- Zarel 11y agoWell, at least for several threat models, "your site to CF" is at least slightly better than "CF to clients". It's not vulnerable to things like unsecured wi-fi sniffing. Then again, neither are self-signed certs and for some reason all browsers consider them even worse than no cert. On the other hand, it doesn't protect against government spying, but then again, I think some governments straight-up MitM HTTPS traffic anyway. For instance: https://news.ycombinator.com/item?id=10663843 https://news.ycombinator.com/item?id=10663843