I ended up using redsocks for doing the transparent proxy, that is working
perfectly for me now. I don't need to configure squid for this after all.
On Wed, Feb 24, 2021 at 7:21 AM Justin Schwartzbeck
wrote:
> I believe I have solved the forwarding loop issue by adding a preceding
> rule to -j A
I believe I have solved the forwarding loop issue by adding a preceding rule to
-j ACCEPT all traffic originating from the docker network. Now I still have the
SSL_ERROR_RX_RECORD_TOO_LONG issue, which seems to be unrelated. I will set
logging to debug and do a wireshark session to see what migh
On 24/02/21 3:14 pm, Justin Michael Schwartzbeck wrote:
Hi all,
For some years I have used squid 3.5 with SSL bump and transparent proxy
locally on my laptop. I have been using the following in my squid.conf:
ssl_bump server-first all
http_port 3128
http_port 3129 intercept
http_port 3130 ss
Hi all,
For some years I have used squid 3.5 with SSL bump and transparent proxy
locally on my laptop. I have been using the following in my squid.conf:
ssl_bump server-first all
http_port 3128
http_port 3129 intercept
http_port 3130 ssl-bump intercept generate-host-certificates=on
dynamic_cert_
