Ah, I didn't realize the protocol combined the realm and password in the hashed
value sent from client->server, thought those were separate.
Makes sense now. Thanks very much for the fantastically detailed explanation.
-Original Message-
From: Henrik Nordström [mailto:hen...@henriknordst
lör 2010-06-05 klockan 09:07 -0600 skrev David Parks:
> Hi, the digest authentication helper protocol requires that the helper
> return the encrypted digest authentication hash given the username and
> realm.
Yes..
> The problem is, if I have 2 different realms which authenticate against the
> s
fre 2010-06-04 klockan 19:39 -0600 skrev David Parks:
> >From what it looks like Digest Authentication doesn't support concurrency
> (sending multiple requests to a single helper). But Basic Auth, and ACL
> Helpers do.
Seems to be the case indeed. All the support is there, but the option is
missin
lör 2010-06-05 klockan 07:31 +0700 skrev Khemara Lyn:
> What would be the good values for these parameters?
> Any extra parameters i should add?
Add a zero to tcp_max_syn_backlog perhaps?
If that does not help then you need to investigate the issue further.
Regards
Henrik
fre 2010-06-04 klockan 20:07 +0200 skrev David Touzeau:
> Thanks amos
>
> How to force squid to not ask authentification method for localhost and
> squidclient ?
By removing the redundant "http_access allow ldapauth" line you have
around the auth_param settings.
The correct one is already way d
Hi, the digest authentication helper protocol requires that the helper
return the encrypted digest authentication hash given the username and
realm.
The problem is, if I have 2 different realms which authenticate against the
same user credentials, if I store the credentials in a one-way encrypted
