Marcus, not to distract from the very important main points being discussed
here but I have to question your last line:
"i.e. there is not yet an interface for this type of traffic inspection."
Is that not the whole point of Squid's ICAP interface and HTTPS bumping? Or
do you just mean that ufdbgu
onable
> solution, excluding sniffer/manual add to acl.
>
> Any ideas? Will be write helper?
>
> WBR, Yuri
>
> 05.01.2015 2:17, Douglas Davenport пишет:
> > I saw a very similar feature in ufdbGuard which is a URL filter
> implemented as a Squid Redirector. They have a fea
I saw a very similar feature in ufdbGuard which is a URL filter implemented
as a Squid Redirector. They have a feature which probes the destination
server for a valid HTTPS cert in parallel to the user's connection and
terminates it if it turns out not to be a valid HTTPS cert. Their code is
open s
Thanks! What is the recommendation on packages vs building from source?
On Sun, Oct 5, 2014 at 12:31 AM, Amos Jeffries wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On 5/10/2014 4:49 p.m., Douglas Davenport wrote:
> > I'm starting from scratch with an A
I'm starting from scratch with an AWS based squid setup, I would like to be
able stay up to date with the latest squid releases to have all the sslbump
fixes. Can someone suggest what is best to use, Centos 6, Ubuntu 14 or
another distro? I see a lot of the binary releases lag behind, does squid
bu
