Hi,
Thanks for this additional information.
I've asked Aymeric Moizard, author of libosip and exosip his point of view
about this problem.
Simon
Le Vendredi 21 Avril 2006 17:06, Dermot McGahon a écrit :
Hi Simon,
I've been looking into why Digest Auth isn't working when registering
to a Tadiran PABX, here's what I've found out so far.
RFC 2617 says that qop "SHOULD be used if the server indicated that qop
is supported by providing a qop directive in the WWW-Authenticate header
field". And that if qop is sent, cnonce and nonce-count MUST be sent with
it.
The PABX seems to be requiring auth with qop=auth and cnonce/nonce-count
returned.
It would probably be good practice nonetheless to include these in auth
responses?
jauth.c/eXosip_create_authorization_header() sets CNonce to NULL but does
pass Qop and NonceCount into the digest calculation.
DigestCalcResponse() has some code that used these for qop=auth-int, and
it looks wrong that it also applies this to qop=auth. But anyway, I don't
think any of that code is compiled in at present.
libosip seems to have enough support for adding qop/cnonce/nc to the
response header but I'm not sure how to go about choosing a valid value
for cnonce.
I'm not really sure how to proceed. What do others know about this?
Dermot.
--
_______________________________________________
Linphone-users mailing list
address@hidden
http://lists.nongnu.org/mailman/listinfo/linphone-users
_______________________________________________
Linphone-users mailing list
address@hidden
http://lists.nongnu.org/mailman/listinfo/linphone-users