Re: [squid-users] IP auth, simple username/pass authentication, if ip not authorized?

2018-04-13 Thread xpro6000
This should do it acl Allowed_IPs src "/etc/squid/Allowed_IPs.txt" http_access allow Allowed_IPs auth_param basic program /usr/lib/squid3/basic_ncsa_auth /etc/squid/passwd auth_param basic children 5 auth_param basic realm Squid proxy-caching web server auth_param basic credentialsttl 2 hours

[squid-users] IP auth, simple username/pass authentication, if ip not authorized?

2018-04-13 Thread xpro
Right now I'm using Squid with IP based authentication. Would it be possible to also allow the user access if their IP is not allowed, but they provide username/pass? ___ squid-users mailing list squid-users@lists.squid-cache.org

Re: [squid-users] Certificate transparency: problem for ssl-bumping, no effect, or?

2018-04-13 Thread Alex Rousskov
On 04/13/2018 02:41 PM, MK2018 wrote: > Alex Rousskov wrote >> Believe it or not, there are still many Squid use cases where bumping is >> unnecessary. This includes, but is not limited to, HTTPS proxying cases >> with peek/splice/terminate rules and environments where Squid possesses >> the

Re: [squid-users] Squid is very slow after moving to production environment

2018-04-13 Thread MK2018
Roberto Carna wrote > Thanks to everybody... > > I've reviewed what you tell me. I've executed "squid -k parse" and > everything is ok, and I've restarted de Squid entire server. > > When I use the server with IP#1, it works OK, is fastbut when I > change its IP to IP#2 (the IP from the

Re: [squid-users] Certificate transparency: problem for ssl-bumping, no effect, or?

2018-04-13 Thread MK2018
MK2018 wrote > Alex Crow-2 wrote >>> Unless the protocol design changes to expose full URLs and/or MIME >>> types, >>> nothing will replace Squid Bumping. >>> >>> That being said, we are headed to the vortex by 2018.05.01. Let's drown >>> together, while we yell and curse at Google! >>> >>> MK >>>

Re: [squid-users] Certificate transparency: problem for ssl-bumping, no effect, or?

2018-04-13 Thread MK2018
Alex Crow-2 wrote >> Unless the protocol design changes to expose full URLs and/or MIME types, >> nothing will replace Squid Bumping. >> >> That being said, we are headed to the vortex by 2018.05.01. Let's drown >> together, while we yell and curse at Google! >> >> MK >> >> >> > > Erm, can

Re: [squid-users] SSL intercept in explicit mode

2018-04-13 Thread MK2018
Aaron Turner wrote > Thanks Yuri. That helps. As for the "sslproxy_flags > DONT_VERIFY_PEER", yes I understand the risks. In my specific case, > where my "users" are actually a bunch of automated web clients doing > some web crawling it's the right thing to do. > -- > Aaron Turner I tried

Re: [squid-users] Certificate transparency: problem for ssl-bumping, no effect, or?

2018-04-13 Thread Alex Crow
Unless the protocol design changes to expose full URLs and/or MIME types, nothing will replace Squid Bumping. That being said, we are headed to the vortex by 2018.05.01. Let's drown together, while we yell and curse at Google! MK Erm, can someone elucidate the issue here? Can't see

[squid-users] [icap] Web Safety 6.2 web filter plugin for Squid proxy is Release Candidate

2018-04-13 Thread Rafael Akchurin
Greetings all, Next version of Web Safety web filter for Squid proxy (version 6.2.0.FD48, built on April 13, 2018, Release Candidate) is now available for download. This version contains the following fixes and improvements: *Added new dynamic site categorization module. This module