[squid-users] SSL-bump and Ciphersuite?

2016-01-11 Thread Walter H.
Hello, I'd restrict the client by using a less resource consuming TLS encryption; I though doing just this e.g. http_port 3128 ... cipher=3DES ... (for restricting clients connecting to 3DES) or what would be less resource consuming? AES128? but where can I see, which ciphersuite is really

Re: [squid-users] SSL-bump and Ciphersuite?

2016-01-11 Thread Walter H.
Hello Amos, On Mon, January 11, 2016 11:13, Amos Jeffries wrote: > On 11/01/2016 10:50 p.m., Walter H. wrote: >> Hello, >> >> I'd restrict the client by using a less resource consuming TLS >> encryption; >> >> I though doing just this >> >> e.g. >> http_port 3128 ... cipher=3DES ... >> (for

Re: [squid-users] SSL-bump and Ciphersuite?

2016-01-11 Thread Amos Jeffries
On 11/01/2016 10:50 p.m., Walter H. wrote: > Hello, > > I'd restrict the client by using a less resource consuming TLS encryption; > > I though doing just this > > e.g. > http_port 3128 ... cipher=3DES ... > (for restricting clients connecting to 3DES) > > or what would be less resource

Re: [squid-users] SSL-bump and Ciphersuite?

2016-01-11 Thread Amos Jeffries
On 11/01/2016 11:51 p.m., Walter H. wrote: > > Ok, because the strange in connection with this: > > I had > > http_port 3128 ... dhparam=./dhparam.pem > > and before installing Kaspersky Anti-Virus there was not any error; but in > connection with the SSL-Interception of Kaspersky Anti-Virus,