possible XMPP SASL bug?

[Peter Saint-Andre]

Someone reported to me trouble logging in to jabber.org. It seems that
his copy of Adium (1.4b17 on Snow Leopard) is trying DIGEST-MD5 but then
immediately after sending a <response/> it also tries CRAM-MD5 without
having received a further challenge or response from the server.

The relevant snippet of debug output is:

16:23:43: (Libpurple: jabber) Sending (ssl) ([elided]@jabber.org/foo):
<response xmlns='urn:ietf:params:xml:ns:xmpp-sasl'>[elided]</response>

16:23:43: (Libpurple: jabber) Sending (ssl) ([elided]@jabber.org/foo):
<auth xmlns='urn:ietf:params:xml:ns:xmpp-sasl' mechanism='CRAM-MD5'
xmlns:ga='http://www.google.com/talk/protocol/auth'
ga:client-uses-full-bind-result='true'/>

It seems odd to send a DIGEST-MD5 response and then immediately try to
start a CRAM-MD5 negotiation. Am I missing something?

BTW this does not happen for me with 1.4b17 on Leopard. Could it be a
problem with his account credentials? It seems to me that Adium would at
least wait for another challenge or for SASL failure from the server
before starting the CRAM-MD5 attempt. Is this possibly a workaround for
iChat server?

Thanks!

Peter

-- 
Peter Saint-Andre
https://stpeter.im/



-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 6820 bytes
Desc: S/MIME Cryptographic Signature
URL: <http://adium.im/pipermail/devel_adium.im/attachments/20100203/c7b3aaed/attachment.p7s>