3 ms·
I totally agree (although you need more than SRI, since you also need some way of signing the original content, but I'd love to see a full spec for this sort of
by geofft 12y ago
I totally agree (although you need more than SRI, since you also need some way of signing the original content, but I'd love to see a full spec for this sort of thing). However, SSL is what we have right now that works.
And I think, of the browsers that do support SRI (possibly in prerelease versions or behind feature flags), they require the page to be delivered over SSL anyway.
- Animats 12y agoHTTPS is broken by content delivery networks who terminate SSL connections. HTTPS Everywhere makes the problem worse, by increasing load for static pages and breaking caches, forcing sites to use a content delivery network. Take a look at that HTTPS certificate that you think means you're talking to the site of your choice. If it says "cloudflare.com", "incapsula.com", "edgecastcdn.com", "palmwebservices.com", "cdnetworks.net", there is a man in the middle of your HTTPS connection. This is the case for at least 38,000 sites we know about. There are probably more. (The list: http://john-nagle.github.io/certscan/whoamitalkingto04.pdf http://john-nagle.github.io/certscan/whoamitalkingto04.pdf) HTTPS Everywhere was well-intentioned, but the people behind it didn't realize that high-volume use of HTTPS forced less secure use of HTTPS. That's why it's a form of security theater.
- nitrogen 12y agoHTTPS Everywhere was well-intentioned, but the people behind it didn't realize that high-volume use of HTTPS forced less secure use of HTTPS. That's why it's a form of security theater. I still trust the link between CloudFlare and Hacker News more than I trust the link between a dodgy ISP and Hacker News. Further, there's no reason that a CDN can't use SSL to the backend, so in that case the only weak point is the CDN and the original site, not any of the links. Using HTTPS to a CDN is still far better than using HTTP to a CDN or to the original site.
- JoshTriplett 12y agoHTTPS does not break caches; that's FUD. Browsers can cache HTTPS pages just fine, and do by default unless told not to. Nothing forces sites to use a CDN. HTTPS, by itself, does not massively increase load. If the limiting factor of your web server is how fast you can do cryptographic operations for HTTPS, you're doing rather well; most of the time that won't be your limiting factor. Using a CDN is not wildly less secure than using a hosting service, and numerous sites use hosting services. "Secure to the CDN" is still a net improvement over "completely insecure". By all means, complain about sites using a CDN that you don't trust. That's not an argument against universal adoption of HTTPS, though.
- frankzinger 12y agoHTTPS does not break caches; that's FUD. Browsers can cache HTTPS pages just fine Yes, but caching by intermediaries is a very important part of HTTP caching, and HTTPS effectively breaks that, does it not?
- JoshTriplett 12y ago> Yes, but caching by intermediaries is a very important part of HTTP caching Proxies are not a common setup; approximately zero home users use them, and a subset of corporate networks do (only the obnoxious ones). In any case, caching proxies are far less important than caching browsers, and HTTPS does not in any way break caching browsers.
- hueving 12y agoYou seem to be extremely confused about how HTTPS works. If the site I'm visiting chooses to give a certificate to cloudflare for their service, that is their choice. What they choose to do server side is completely out of a customer's hands no matter how secure the protocol. Even with CDN terminating SSL, it protects you from injected malware and ADs between you and the CDN by your ISP.
- geofft 12y agoI agree with all this. However, HTTPS works today at least somewhat, and nothing else does, at all. If you want to work on a spec to make cacheable, signed hypertext documents, I will be totally down for helping. But no such spec exists today.