On 06/08/18 21:39, Antony Stone wrote:
On Monday 06 August 2018 at 13:32:32, --Ahmad-- wrote:
what could be the reason ?
Cookies on your computer, javascript in web pages, browser language
preferences, locally cached content...
I'm sure I haven't thought of everything.
Some sites check for the
Ignoring the Squid part, is it TLS 1.2 that's the root problem, or the
ciphers?
Are you aware XP schannel.dll has some ciphers and protocols disabled by
default, even though they're supported?
See here:
https://support.microsoft.com/en-au/help/245030/how-to-restrict-the-use-of-certain-cryptogr
I'd seen this licensing issue mentioned briefly before, but now I
actually understand what's going on. Thanks for explaining it in detail.
Good to know there's 2 paths moving along to solve the distro problem. I
feel more confident in moving forward with my little project now that I
know it's
On 14/05/2016 9:41 PM, Rafael Akchurin wrote:
The recompilation is quite easy btw
Oh, yeah... I know it's easy. I've already done it once on Debian. My
concern is that I won't be able to find time to keep it up to date.
Asking a package manager to download available updates takes about 10
mi
Are there any Linux distros with pre-compiled versions of Squid with SSL
Bump support compiled in?
Alternatively, does anyone reputable do a 3rd party repo for
Debian/Ubuntu that includes SSL Bump?
TB
___
squid-users mailing list
squid-users@lists.s
Is it possible to do this:
* Intercept HTTPS and send it via Squid?
* Apply ACLs to the intercepted HTTPS traffic based on host/domain name?
* Not change any configuration on clients?
Should I keep researching how this peeking and bumping and splicing and
such works, or is it impossible?
TB
_
