News for hackers. Stuff that matters.

A comment on Privoxy, a non-caching web proxy with filtering capabilities. Parent comment

Re:Privoxy, a non-caching web proxy with filtering capabilities by pmoriarty on Monday October 09, 2017 @03:20PM (#15436631)
Is there anywhere I could read more detail on this setup? I'm not exactly clear on how it works.

Do you have:

A: client -> squid -> privoxy -> internet

or

B: client -> privoxy -> squid -> internet

And some more details on the exact squid & privoxy setup would be nice too.

I've long wanted to get privoxy working over HTTPS, and would love to know the details of how this is done.

[ Parent | on HN ]
Re:Privoxy, a non-caching web proxy with filtering capabilities by bitexploder on Monday October 09, 2017 @08:42PM (#15438513)
Direct proxy, no transparent, client -> privoxy -> squid -> http(s) sites. I trust Squid at the tip a lot more. Forwarding Privoxy to another proxy is easy. Read the Forwarding section of the Privoxy manual. Setup Privoxy how you want. Forward to Squid. Follow: https://wiki.squid-cache.org/Features/DynamicSslCert

You should then have the perfect proxy centipede. For bonus fun use dnsmasq and blacklist domains via DNS too.

Things get much more complex if you want to do things transparently. Now you have to monkey with iptables. The idea is similar though. Start with Privoxy getting all HTTP traffic on a router. Forward to Squid. Have Squids dynamic SSL cert on your client devices.

[ Parent | on HN ]
Re:Privoxy, a non-caching web proxy with filtering capabilities by pmoriarty on Tuesday October 10, 2017 @12:21AM (#15439331)
So is privoxy happy handling HTTPS requests as long as it's fronted by Squid? I guess I'm still not clear on how/why that works. I thought privoxy could only handle HTTP.
[ Parent | on HN ]