Even if the string is incorrect, shouldn't FreeSWITCH use it without modification in it's calculations (and return the same nonce in the response)?

On Tue, Mar 2, 2010 at 8:41 PM, Brian West <brian@freeswitch.org> wrote:

What really really concerns me about this is the fact this is MD5 digest auth.

Neither of these:

4b8cc1780000440a8d49b0854a8a7abb76fec907e6381eec

4b8cc1780000a33fc486f1017a5155a74fc6e3e611e28f47

Are NOT the right length to be an MD5 of any auth data which would be a33fc486f1017a5155a74fc6e3e611e28f47 so this stray 4b8cc1780000 really does concern me.

Anyone else have input on this one?

/b