Hi,
After some strange authentication issues, I saw that my problem occurs when a admin sets a new password or removes a user.
The backend authentification is only checked in logon at first popup, if something changes in LDAP the browser still always connected unlike basic ident.
Maybe I f
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 20/11/2014 4:21 a.m., wmunny william wrote:
> Hi, After some strange authentication issues, I saw that my problem
> occurs when a admin sets a new password or removes a user. The
> backend authentification is only checked in logon at first popup,
>
And it works great ! Thank you Amos for your patch.
In previous Squid 3.3.x DIGEST was very buggy , crash, 407, banners, but now it seems very stable. Perhaps there are some little bugs like this, but now it's usable.
Thanks for your works
http://bugs.squid-cache.org/show_bug.cgi?id=4066
It
>
>
> And it works great ! Thank you Amos for your patch.
> In previous Squid 3.3.x DIGEST was very buggy , crash, 407, banners,
> but now it seems very stable. Perhaps there are some little bugs
> like this, but now it's usable.
> Thanks for your works
>
Hi,
William to be more clear this pa
>
> William to be more clear this patch is not related at all with
> authenticate_ttl directive.
> authenticate_ttl doesn't works with Digest, but with basic and maybe another
> (ntlm, kerberos ?) there is no precision here
> http://www.squid-cache.org/Doc/config/authenticate_ttl/
>
> The pat
>
> Ok, thanks,
>
> Tested with both nonce_count and nonce_max_duration, no problem. Do
> you known if it works with squid 3.5 ?
>
>
No sorry I don't know, but if the patch can be applied I guess that yes it can
works.
Except if there are some changes in DIGEST between 3.4 and 3.5.
__
> > Ok, thanks,
> >
> > Tested with both nonce_count and nonce_max_duration, no problem. Do
> > you known if it works with squid 3.5 ?
> >
> >
>
> No sorry I don't know, but if the patch can be applied I guess that
> yes it can works.
> Except if there are some changes in DIGEST between 3.4 an
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 17/12/2014 3:03 a.m., FredB wrote:
>
>>> Ok, thanks,
>>>
>>> Tested with both nonce_count and nonce_max_duration, no
>>> problem. Do you known if it works with squid 3.5 ?
>>>
>>>
>>
>> No sorry I don't know, but if the patch can be applied I g
> Should be called auth/digest/Config.cc now. Contents should not be
> much different, just the filename.
>
> Amos
Hello,
Thnaks Amos,
Ok, so I will provide a patch in bug report this week
Fred
___
squid-users mailing list
squid-users@lists.squid-
Patch for squid 3.5.0.3
| Tested with both nonce_count and nonce_max_duration, no problem. Do you known
if it works with squid 3.5 ?
Be careful chech_nonce_count is broken, you can see in your log that there are
many unexpected 407, my advice is to set the value check_nonce_count to off
It's a
10 matches
Mail list logo
