Re: gsasl - digest-md5 question.

[Simon Josefsson]

Andery Melnikov <address@hidden> writes:

> Simon, just a stuppid question - did you test integrity signing
> messages ? After fixing jabberd2 (adding hooks for encode/decode) - we
> still no luck. As I see - there is problem with converting internal
> data from/to network byte order.
>
>       0x0030:  xxxx xxxx 0000 007f 3c73 7472 6561 6d3a  ........<stream:
>       0x0040:  7374 7265 616d 2074 6f3d 276b 6d76 2e72  stream.to='kmv.r
>       0x0050:  7527 2078 6d6c 6e73 3d27 6a61 6262 6572  u'.xmlns='jabber
>       0x0060:  3a63 6c69 656e 7427 2078 6d6c 6e73 3a73  :client'.xmlns:s
>       0x0070:  7472 6561 6d3d 2768 7474 703a 2f2f 6574  tream='http://et
>       0x0080:  6865 7278 2e6a 6162 6265 722e 6f72 672f  herx.jabber.org/
>       0x0090:  7374 7265 616d 7327 2076 6572 7369 6f6e  streams'.version
>       0x00a0:  3d27 312e 3027 3e28 8eea abd2 f37b c633  ='1.0'>(.....{.3
>       0x00b0:  2800 0100 0000 00                        (......
>
> byte from 0x34-0x37 - message len (127 bytes), but C2I macros in
> digest_md5_decode() read value 2130706432 instead of 127.
> Can you check this ?

Hello!  Thanks for the report.  You are right, this was broken, and
several places needed to be patched to make integrity layer work with
DIGEST-MD5.  I believe it now works again.  Please test a daily
snapshot:

http://daily.josefsson.org/gsasl/gsasl-20090318.tar.gz

This also includes the QOP/QOPS stuff, a bit modified since my last
e-mail.

If you can confirm that it solves your problem, I can quickly make a new
release of it.

/Simon