On 14/04/18 10:03, Alex Crow 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
>>
>>
>>
Yes that should do it. But to let Squid do its job against DoS and such
security attacks ...
On 14/04/18 17:36, xpro6000 wrote:
> This should do it
>
Move all these custom rules between here ...
> acl Allowed_IPs src "/etc/squid/Allowed_IPs.txt"
> http_access allow Allowed_IPs
>
> auth_param b
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
aut
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
http://lists.squid-ca
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 certi
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 curre
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
>>>
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 someone
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 using
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 anythi
Hello :)
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 certificate issued by CAs trusted by c
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 wor
12 matches
Mail list logo