Live data from Hacker News

Securing web sites with HTTPS made them less accessible

thenextweb.com

11–14 of 14 posts

Re: Securing web sites with HTTPS made them less accessible

#11
post #8

Earlier quoted context omitted.

It’s possible and is what Charles and MITM proxies do. Specifically, Charles generates its own certificates for sites, which it signs using a Charles Root Certificate. So the clients of this proxy would accept the proxy’s CA and continue as usual. This of course does make browsing less secure, as a compromised proxy negates the security of https of all of the proxied websites. A slightly more secure but less efficien…

Can local certificates not be restricted to the few domains you want cached, so that the user can be sure their browser isn't using the local proxy's certificate for anything other than the sites approved on the certificate (like Wikipedia)? I would've thought this is possible, but if not, I feel like browsers should implement the ability to restrict local certificates to specific sites. It shouldn't be hard. They'd…

Yes, come to think of it, that’s possible either manually or with a PAC file. It seems like a decent compromise too to whitelist the proxied sites the weakened security of which you are willing to tolerate, at least in the case where the alternative is not being able to teach/learn in that area, as in Eric’s case.

Re: Securing web sites with HTTPS made them less accessible

#12
post #4

> Google, Wikipedia Caching Google makes no sense beyond some static resources. Wikipedia can be made available off-line, just not by using a man-in-the-middle server. This may make sense for a school with limited connectivity to do. > That’s great for modern browsers, but not everyone has the option to be modern. Sometimes they’re constrained by old operating systems to run older browsers, ones with no service-worke…

> Caching Google makes no sense beyond some static resources. Really? So you cannot make any sense of the idea of caching, say, news articles? Blog posts? Software documentation? StackOverflow Qs/As? The cached pages are 100% useless in your mind?

All of those are not Google. OP was probably thinking of SERPs.

Re: Securing web sites with HTTPS made them less accessible

#13

Earlier quoted context omitted.

> Caching Google makes no sense beyond some static resources. Really? So you cannot make any sense of the idea of caching, say, news articles? Blog posts? Software documentation? StackOverflow Qs/As? The cached pages are 100% useless in your mind?

All of those are not Google. OP was probably thinking of SERPs.

Indeed.

Re: Securing web sites with HTTPS made them less accessible

#14

Earlier quoted context omitted.

> Caching Google makes no sense beyond some static resources. Really? So you cannot make any sense of the idea of caching, say, news articles? Blog posts? Software documentation? StackOverflow Qs/As? The cached pages are 100% useless in your mind?

All of those are not Google. OP was probably thinking of SERPs.

I think lack of sleep got the better of me there, sorry :\ but I still don't see what the issue with caching search engine results is. Why shouldn't result pages be cached? I would totally want to cache them locally when on such a high-latency connection, especially when I can expect similar queries (like in a classroom).
Post reply on HN