3 ms·
As a non-developer, ordinary computer user "providing service" for one user (yours truly) it's easy for me to configure the TLS forward proxy listening on the l
by 1vuio0pswjnm7 2y ago
As a non-developer, ordinary computer user "providing service" for one user (yours truly) it's easy for me to configure the TLS forward proxy listening on the loopback to send _all_ HTTP requests, from _any_ application, including ones sent to port 80, via HTTPS. This I find preferable to letting a browser try to convert HTTP to HTTPS, e.g., "HTTPS Everywhere", or letting a developer do it with a redirect. Personally, I compile clients without linking to a TLS library. They are smaller without it and I do not have to worry about every author having correctly added TLS support. When SSL/TLS changes, applications using it often need to be updated, and some authors have made mistakes, socat being one example that comes to mind. I do 100% of TLS negotiation using a single program: the proxy. Every HTTP request on the home network goes to the proxy.
- jagger27 2y agoThere’s absolutely nothing ordinary or easy about that setup, but I admire it. I’ve only seen that level of paranoia at a three letter agency. Do applications with pinned certificates break? A bunch of mobile apps do that to get in the way of Wireshark.
- 1vuio0pswjnm7 2y agohttps://f-droid.org https://f-droid.org
- jagger27 2y agoSomeday on iOS, if Tim wills it.
- 1vuio0pswjnm7 2y agohttps://www.metacritic.com/movie/steve-jobs/ https://www.metacritic.com/movie/steve-jobs/ According to this film, which Wozniak said was very accurate, Steve Jobs was a douchebag. Android sucks, too. I only use it out of necessity, not choice. Why do I use a TLS forward proxy. Because I loathe using popular, so-called "modern" web browsers. I prefer using smaller, simpler clients.