On Thu, Sep 18, 2008 at 2:15 PM, Eric Will <[EMAIL PROTECTED]> wrote:
> Here it is, starting with the opening <stream> after successful TLS: > and decoded for the base64decoder'less people: (I use `fold -w 79 | openssl base64 -d`) challenge : realm=malkier.net ,nonce="134fea83d50a222b49a08c4427c75802",qop="auth",charset=utf-8,algorithm=md5-sess response : username="rakaur",realm="malkier.net ",nonce="134fea83d50a222b49a08c4427c75802",cnonce="8wOz7xs1xNIHJJGVY7gTrSaOdCgXAwZP/kI1jSRrQss=",nc=00000001,digest-uri="xmpp/ malkier.net ",qop=auth,response=e92dad582393b1f8b0165e6d20b827ee,charset=utf-8 failure and: challenge : realm=malkier.net ,nonce="2062054399a6396d31196a8d0530e800",qop="auth",charset=utf-8,algorithm=md5-sess response : charset=utf-8,username="rakaur",realm="malkier.net ",nonce="2062054399a6396d31196a8d0530e800",nc=00000001,cnonce="8b17fd4ba66b1ef220ac5be13521f5451386520a09df2799b",digest-uri="xmpp/ malkier.net",response=2d8c70364862e055fcce759aec9aaa92,qop=auth challenge : rspauth=310f6eb7f7d99306c5252201119529bc response : none success So I can only assume the response values are incorrect, because the other values are identical. Does your password has any non-ascii characters that might be being encoded as utf-8 correctly? Can you force the server to generate the same nonce for both clients? (It would require hacking at the DIGEST-MD5 code, but it would help validate that the response is being generated correctly. Cheers Norman -- - Norman Rasmussen - Email: [EMAIL PROTECTED] - Home page: http://norman.rasmussen.co.za/
_______________________________________________ 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] _______________________________________________
