Hi Pekka
Thanks for your tips
If It uses a "Digest-HA1" scheme, it would need to receive the same from the
registrar server (matching schemes). It would be good to be server agnostic
(Digest)
int ca_credentials(...
... ...
if ((scheme != NULL && !su_casematch(scheme, ca->ca_scheme)) ||
(realm != NULL && !su_strmatch(realm, ca->ca_realm)))
return 0;
It needs to somehow to ignore above code, maybe checking for "Digest-HA1"
Regards
Paulo
On Wed, Dec 15, 2010 at 2:46 PM, Pekka Pessi <ppe...@gmail.com> wrote:
> Hi Paulo,
>
> 2010/12/15 Paulo Vicentini <vicentini.pa...@gmail.com>:
> > I using sofia-SIP as an UAC to register with a SIP registrar
> > I'd like to avoid using the secret (it is indeed not available) directly
> > while creating a digest authorization header with:
> > int auc_digest_authorization(auth_client_t *ca,
> > su_home_t *home,
> > char const *method,
> > url_t const *url,
> > msg_payload_t const *body,
> > msg_header_t **return_headers)
> >
> > Only HA1 = md5(username:realm:password) is available
> > So that I intend to use HA1 = md5(username:realm:password) instead
> > What do you say about that?
>
> It is doable with some modifications to iptsec/auth_client.c. You
> could modify the ca_credentials to store only the HA1 in the
> ca_client_t structure instead of the password (in case of Digest) and
> add a special scheme, e.g., Digest-HA1 where the password would
> contain the HA1.
>
> Patches are welcome.
>
> --
> Pekka.Pessi mail at nokia.com
>
------------------------------------------------------------------------------
Lotusphere 2011
Register now for Lotusphere 2011 and learn how
to connect the dots, take your collaborative environment
to the next level, and enter the era of Social Business.
http://p.sf.net/sfu/lotusphere-d2d
_______________________________________________
Sofia-sip-devel mailing list
Sofia-sip-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sofia-sip-devel
