Re: [squid-users] Squid and SSLBump

On 22/11/19 9:19 am, Monah Baki wrote: > I added the following: > > sslproxy_cert_error allow all > sslproxy_flags DONT_VERIFY_PEER > > and it works now. > > In my access.log: > > 172.16.84.241 - - [21/Nov/2019:15:15:05 -0500] "CONNECT > static.xx.fbcdn.net:443 "

Re: [squid-users] Squid and SSLBump

On 11/21/19 9:25 AM, Monah Baki wrote: > The certs/keys are legit from my company. Is your signing certificate (i.e. wildcardcert.pem) a CA certificate? If not, then you cannot use it to sign other certificates. SslBump with dynamic certificate generation requires a CA certificate to sign the gen

Re: [squid-users] Squid and SSLBump

On 06/09/2017 01:33 AM, FredB wrote: > There is way to approximately estimate the "cost" of CPU/Memory usage of > SSLbump ? Ballpark splicing speed/CPU estimates[1,2] for Squid v4+: * splicing during step 2: 75% of splicing during step1 performance * splicing during step 3: 25% of splicing

Re: [squid-users] Squid and SSLBump

On 10/06/17 06:01, Walter H. wrote: On 09.06.2017 09:33, FredB wrote: Hi all, There is way to approximately estimate the "cost" of CPU/Memory usage of SSLbump ? be careful, if there is a "cost" value now, this will be very probably wrong when SSL gets more common ... As far as I have see

Re: [squid-users] Squid and SSLBump

On 09.06.2017 09:33, FredB wrote: Hi all, There is way to approximately estimate the "cost" of CPU/Memory usage of SSLbump ? be careful, if there is a "cost" value now, this will be very probably wrong when SSL gets more common ... smime.p7s Description: S/MIME Cryptographic Signature ___

[squid-users] Squid and SSLBump

Hi all, There is way to approximately estimate the "cost" of CPU/Memory usage of SSLbump ? What do you see in practice ? Some features are incompatibles with SMP so I'm using a single process, Squid is using more or less 30/40 % of CPU I have approximately 1000 users simultaneously connected