Yes, upon further investigation it appears cnonce should be an MD5 hexdigest of some random entropy generated by the client (gibberish in most cases). It seems Psi is doing a base64-encode instead of an MD5 hexdigest.
However, I'm not totally sure, because: 1. I can't fix this by decoding the base64 cnonce and using that to compute my response, and; 2. I can't fix this by decoding the base64 cnonce and then md5-hexing it to compute my response, and; 3. I can't fix this by md5-ing the base64-encoded cnonce and using that to compute my response. Silly DIGEST-MD5. -- Eric Will _______________________________________________ JDev mailing list FAQ: http://www.jabber.org/discussion-lists/jdev-faq Forum: http://www.jabberforum.org/forumdisplay.php?f=20 Info: http://mail.jabber.org/mailman/listinfo/jdev Unsubscribe: [EMAIL PROTECTED] _______________________________________________
