[squid-users] 回复:Re: cache_mem differs from output in mgr:config

2016-01-12 Thread XUFENG
Thank you very much for your help and advice. - 原始邮件 - 发件人:Amos Jeffries 收件人:squid-users@lists.squid-cache.org 主题:Re: [squid-users] cache_mem differs from output in mgr:config 日期:2016年01月13日 06点18分 On 12/01/2016 2:36 p.m., XUFENG wrote: > My squid's cache_mem in squid.conf differs from o

Re: [squid-users] Possible SSL Bug in v3.5.13?

2016-01-12 Thread Amos Jeffries
On 13/01/2016 3:42 p.m., David Marcos wrote: > I recently upgraded to Squid v3.5.13 and am encountering at least two > errors when processing certain HTTPS connections. I am not sure if it is a > bug or a configuration error on my part. > > The first error I am seeing is when shutterfly.com is ac

Re: [squid-users] guideline on limiting users per IP

2016-01-12 Thread Amos Jeffries
On 13/01/2016 3:23 p.m., 3@D4rkn3ss DuMb wrote: > Dear Amos, > > Thank you. I didn't know that it cannot yet work on token based auth.So > there is no work around? It cant work that way because the tokens are unique per login. The "username" is not part of the credentials, just a label the helper

Re: [squid-users] Possible SSL Bug in v3.5.13?

2016-01-12 Thread Eliezer Croitoru
For me SSL-BUMP works with the site you have mentioned but your settings are a bit different from mine. It seems that the site uses ssl v2 or v3 which I am almost sure you are denying the usage of. I would try another settings first but still if it causes the service to be down for about 30 se

[squid-users] Possible SSL Bug in v3.5.13?

2016-01-12 Thread David Marcos
I recently upgraded to Squid v3.5.13 and am encountering at least two errors when processing certain HTTPS connections. I am not sure if it is a bug or a configuration error on my part. The first error I am seeing is when shutterfly.com is accessed by a user. The issue occurs regardless of whethe

Re: [squid-users] guideline on limiting users per IP

2016-01-12 Thread 3@D4rkn3ss DuMb
Dear Amos, Thank you. I didn't know that it cannot yet work on token based auth.So there is no work around? Really appreciated. On 12 January 2016 at 15:00, wrote: > Send squid-users mailing list submissions to > squid-users@lists.squid-cache.org > > To subscribe or unsubscribe via the

Re: [squid-users] Authenticate_ip_ttl_strict

2016-01-12 Thread Amos Jeffries
On 13/01/2016 8:26 a.m., Murat Balkan wrote: > Hello, > > I want to use authenticate_ip_ttl_strict on configuration (I have > seen this mentioned in this group) but squid complains no such > parameter at the startup. I am using version 3.1.23 > Because there is no such configuration directive. N

Re: [squid-users] multiple client certfifcates for ssl bumping

2016-01-12 Thread Amos Jeffries
On 13/01/2016 2:53 a.m., Alexei Mayanov wrote: > Hello! > I use Squid 3.5.12. > For SSL bumping it is possible to specify client certificate and > private key by 'sslproxy_client_certificate' and 'sslproxy_client_key' No, that is not possible in any Squid at present. I am working slowly towards su

Re: [squid-users] cache_mem differs from output in mgr:config

2016-01-12 Thread Amos Jeffries
On 12/01/2016 2:36 p.m., XUFENG wrote: > My squid's cache_mem in squid.conf differs from output in mgr:config. > ... > > Anything wrong? Just a bug in the mgr report display code I think. There are some others known as well. The reporter code has often been overlooked by people changing the squ

Re: [squid-users] Compile install Squid, configure default options.

2016-01-12 Thread Eliezer Croitoru
On 04/01/2016 11:22, 郑伟 wrote: I want to use newest version Squid, but i think I perhaps missing something important option maybe, which can cause risk in some case? Could any please help me for a `standard necessary' configure arguments for current 3.5 serious? As was mentioned couple times h

Re: [squid-users] host header forgery false positives

2016-01-12 Thread Eliezer Croitoru
Hey Jason, I think we can divide the issue into two: - host forgery identification - host forgery action And you can also add intercepting compared to configured forward proxy. If you can draw a picture of the clients and the proxy network layout we can try somewhere. What you are talking about

Re: [squid-users] Compile install Squid, configure default options.

2016-01-12 Thread Mike
When I used CentOS 7 (a variation of it), this is what I had to use: * yum -y install perl gcc gcc-c++ autoconf automake make * *yum -**y **install epel-release* o (has a few packages we need below) * yum -y install libxml2-devel libcap-devel avr-gcc-c++ * yum

Re: [squid-users] Compile install Squid, configure default options.

2016-01-12 Thread Yuri Voinov
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Squid now completely written on C++ ;) 13.01.16 1:34, Billy.Zheng (zw963) пишет: > >>> >>> Or, just tell me, this worked, it is fine, and I will very happy to use. >>> >>> btw: When I first install, ./configure is passed, but make is failed. >>> b

Re: [squid-users] Compile install Squid, configure default options.

2016-01-12 Thread Yuri Voinov
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 That's it. You installed gcc but not g++. Simple. 13.01.16 1:34, Billy.Zheng (zw963) пишет: > checking for cc++... no -BEGIN PGP SIGNATURE- Version: GnuPG v2 iQEcBAEBCAAGBQJWlV63AAoJENNXIZxhPexGv2EIAIeL/q5cQBHLVhxFyqZoZZCn vCfaHslQsrj

Re: [squid-users] Compile install Squid, configure default options.

2016-01-12 Thread zw963
> > > > Or, just tell me, this worked, it is fine, and I will very happy to use. > > > > btw: When I first install, ./configure is passed, but make is failed. > > because I am not install gcc-c++. I have to install gcc-c++, reconfigure > > again, make is passed. I thought if ./configure could de

[squid-users] Authenticate_ip_ttl_strict

2016-01-12 Thread Murat Balkan
Hello, I want to use authenticate_ip_ttl_strict on configuration (I have seen this mentioned in this group) but squid complains no such parameter at the startup. I am using version 3.1.23 What I am trying to achieve is during the IP TTL period, if a second user tries to log in to the proxy wit

[squid-users] multiple client certfifcates for ssl bumping

2016-01-12 Thread Alexei Mayanov
Hello! I use Squid 3.5.12. For SSL bumping it is possible to specify client certificate and private key by 'sslproxy_client_certificate' and 'sslproxy_client_key' directives to authenticate Squid as a client on remote servers. But specified certificate and key will be used to authenticate on ALL or