I have just built a testing version of Squid 5 at:
*
http://ngtech.co.il/repo/bin/amzn/1/x86_64/squid-5.0.0-20190127-rc1a2df008-6
4-bin.tar.xz
*
http://ngtech.co.il/repo/bin/amzn/2/x86_64/squid-5.0.0-20190127-rc1a2df008-6
4-bin.tar.xz
*
On 6/02/19 9:27 am, Walter H. wrote:
> Hello,
>
> in iptables I have this:
>
> *nat
> ...
> -A PREROUTING -i br0 -p tcp -s 192.168.1.100 --dport 80 -j DNAT
> --to-destination 192.168.1.1:3129
>
>
>
> 192.168.1.100 is my PC and 192.168.1.1 is my NAT-Router, that has squid,
> ... running
>
>
On 6/02/19 5:28 am, Walid A. Shaari wrote:
> Dear Amos,
>
>
> Thank you for your time and response. I have changed the configuration
> to the below. I believe the parent proxy is not using SSL/TLS. I do not
> see the Hello error message any longer ( I hope). I have not used your
> proposed
Hello,
in iptables I have this:
*nat
...
-A PREROUTING -i br0 -p tcp -s 192.168.1.100 --dport 80 -j DNAT
--to-destination 192.168.1.1:3129
192.168.1.100 is my PC and 192.168.1.1 is my NAT-Router, that has squid,
... running
here the log
192.168.1.100 - - [05/Feb/2019:20:57:09 +0100]
Dear Amos,
Thank you for your time and response. I have changed the configuration to
the below. I believe the parent proxy is not using SSL/TLS. I do not see
the Hello error message any longer ( I hope). I have not used your
proposed localnet as I just saw your email, at the time being, the ACL
On 6/02/19 3:33 am, Paul Doignon wrote:
> Hi,
>
> I'm struggling a lot to configure Squid. To improve the security of my app in
> my AWS private subnet,
If it is indeed *your* app; then please alter it not to require the
interception we see below. Ability to connect to a TLS explicit proxy or
Hi,
I'm struggling a lot to configure Squid. To improve the security of my app in
my AWS private subnet, I would like to build a HTTPS proxy to whitelist *only*
some URLs.
My wish is to *not* rely on SNI filtering but bump HTTPS traffic in order to
filter the URLs (path) of HTTPS requests. I
