[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Linphone-users] Some info about Digest Auth

From: Aymeric Moizard
Subject: Re: [Linphone-users] Some info about Digest Auth
Date: Sat, 22 Apr 2006 16:17:30 +0200 (CEST)

I've already tested the qop support with nonce count with osip/exosip
and it worked (in eXosip2) at least for one transaction with minor
change in exosip2. A few code should be written to make it really work.
(check the previous nonce count and reuse it for next header: really
simple if I remember!

however, exosip does not announe support for qop to server, thus there
is no reason a server would refuse its authentication!?


On Sat, 22 Apr 2006, Simon Morlat wrote:


Thanks for this additional information.
I've asked Aymeric Moizard, author of libosip and exosip his point of view
about this problem.


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

The PABX seems to be requiring auth with qop=auth and cnonce/nonce-count

It would probably be good practice nonetheless to include these in auth

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?


Linphone-users mailing list

Linphone-users mailing list

reply via email to

[Prev in Thread] Current Thread [Next in Thread]