3 ms·
The complaints seem to be two-fold: * Websites are big and take a long time to download. * They had previously solved this problem with a caching server but t
by Spivak 8y ago
The complaints seem to be two-fold:
* Websites are big and take a long time to download.
* They had previously solved this problem with a caching server but theirs broke with TLS.
The author is apparently unaware of the options they have.
* Run a proxy server that caches pages. Basically all software supports proxies. Secure and well understood. No PKI to manage. And you can allow access to the proxy with no TLS or get a public cert. Works very well with those old devices too.
* Run a HTTPS caching server and add the CA to the systems. Little more effort but transparent.
- briandear 8y agoIt’s pretty easy to use TLS for caching. I do it with Varnish via Fastly. It just costs a bit more.
- slrz 8y agoThis doesn't help in their case. To get a caching node located in rural Uganda (so they don't have to max out their slow sat link), they'd have to negotiate a solution with each major CDN service. Before widespread HTTPS, they just put some box running Squid in the closet. Their problem is a real one, and I don't think we have a good solution for solving it. It'd be nice if their problems could be solved without requiring gross hacks or degraded security.
- zaarn 8y agoYou don't need to negotiate with the CDN. Squid supports HTTPS caching, the TLS connection is terminated at the proxy and the client gets a cert from a locally trusted CA. This is not very trivial to configure but the Squid Wiki should get you through it.
- milankragujevic 8y agoHi, care to point me to instructions to configure a recent Squid on a recent Ubuntu server i.e 18.04.1? With SSL termination and proper self signed cert generation. Thanks.
- zaarn 8y agoThe squid wiki is an excellent resource that explains this sufficiently. Complementary usage of a search engine helps too.
- Spivak 8y agoSquid supports MITMing TLS so that option is still on the table.
- zerkten 8y ago> The author is apparently unaware of the options they have. Do they really have the options you outlined? The author appears to dealing with a situation involving students in rural Uganda. It might not be as simple in that context as you suggest.
- Spivak 8y agoObviously I'm not there but it seems like it? They have a HTTP caching proxy already set up which just needs to have a software change to support TLS. I use Squid for this and it works pretty okay.
- marsokod 8y agoI thought that the ISP were providing that service as part of the package. Given they do a lot of IP traffic alteration (acknowledging TCP packets at the gateway level instead of letting the client doing it), this is not much.
- jankins 8y agoMy first thought was terminating SSL at a proxy or using sslstrip with a VPN or something - I feel like there’s definitely a way to do what he wants. Each option might come with some UX cost though. At the same time, I’d have to Google to figure it out, and I’d want to see if I could optimize for viewing new pages. I think optimizing new pages could also be really important for learning to code. Maybe mosh into a server with a fast, reliable connection and then use that server to access the web with lynx. The idea being that less data would need to be transferred between the mosh client and server than between the mosh server and website. I would suppose that every interaction like scrolling down would have some latency, but new page requests would have less latency. I’m not sure if bandwidth usage and latency would be good enough for their circumstances though.
- preinheimer 8y ago* Run a proxy server that caches pages. Basically all software supports proxies. Sure, basically everything supports proxies. But if you're not running a MiTM attack the proxy doesn't see much. The proxy server gets CONNECT <domain> and relays the request without ever even getting the full URI for the requested resource, so it certainly can't cache it. * Run a HTTPS caching server and add the CA to the systems. I think there's several challenges here: - This CA empowered MiTM attack isn't just proxying Wikipedia and other pubic sites anymore. It's also proxying banking information, and other things that should be secure. We've meaningfully reduced the security for everyone in that lab. - Where previously a computer playing the part of the proxy could just sit between the computers and the internet at large, allowing new machines to be added at will. Now every new computer will need some operating system & browser specific setup work. Machines that move around (laptops, rasberry pis are super portable) will end up with a variety of random certs on them. Even with a local SSL caching server, we're still looking much slower pages. The high ping & packet loss means that the extra requests required to set up the connection could add seconds of latency to even loading a page.