[Pidgin] #11546: Jabber w/ CYRUS-SASL and no saved password fails to prompt at connect time

[Pidgin]

#11546: Jabber w/ CYRUS-SASL and no saved password fails to prompt at connect time
--------------------+-------------------------------------------------------
 Reporter:  evands  |     Owner:  deryni
     Type:  defect  |    Status:  new   
Component:  XMPP    |   Version:  2.6.6 
 Keywords:          |  
--------------------+-------------------------------------------------------
 With CYRUS-SASL, passwords in Jabber are optional.  If you don't specify a
 password, the prpl is supposed to begin connecting and prompt if one turns
 out to be necessary.

 This is failing after a CRAM-MD5 challenge, apparently; I can reproduce
 the below both in libpurple 2.5.9 and in im.pidgin.pidgin HEAD.

 {{{
 18:32:22: ************ tekjew at jabber.org --step-- 7
 18:32:22: (Libpurple: jabber) Recv (ssl)(236): <challenge
 xmlns='urn:ietf:params:xml:ns:xmpp-
 sasl'>bm9uY2U9InJrQ1ZBZVppQnF4MHBPRVJvZnp1TGFNMlhtSEhZK2tBVVN2VUNkNjV6R2c9IixyZWFsbT0iamFiYmVyLm9yZyIscW9wPSJhdXRoIixtYXhidWY9MTYzODQsY2hhcnNldD11dGYtOCxhbGdvcml0aG09bWQ1LXNlc3M=</challenge>
 18:32:22: (Libpurple: jabber) decoded challenge (128):
 nonce="rkCVAeZiBqx0pOERofzuLaM2XmHHY+kAUSvUCd65zGg=",realm="jabber.org",qop="auth",maxbuf=16384,charset=utf-8,algorithm=md5-sess
 18:32:22: (Libpurple: jabber) decoded response (231):
 username="tekjew",realm="jabber.org",nonce="rkCVAeZiBqx0pOERofzuLaM2XmHHY+kAUSvUCd65zGg=",cnonce="eb023b8a1268526742389650d5",nc=00000001,qop=auth
 ,digest-
 uri="xmpp/jabber.org",response=7ec45f00c506b71cbf36b9440fb7955a,charset=utf-8
 18:32:22: (Libpurple: jabber) Sending (ssl) (tekjew at jabber.org/Shindig):
 <response xmlns='urn:ietf:params:xml:ns:xmpp-
 sasl'>dXNlcm5hbWU9InRla2pldyIscmVhbG09ImphYmJlci5vcmciLG5vbmNlPSJya0NWQWVaaUJxeDBwT0VSb2Z6dUxhTTJYbUhIWStrQVVTdlVDZDY1ekdnPSIsY25vbmNlPSJlYjAyM2I4YTEyNjg1MjY3NDIzODk2NTBkNSIsbmM9MDAwMDAwMDEscW9wPWF1dGgsZGlnZXN0LXVyaT0ieG1wcC9qYWJiZXIub3JnIixyZXNwb25zZT03ZWM0NWYwMGM1MDZiNzFjYmYzNmI5NDQwZmI3OTU1YSxjaGFyc2V0PXV0Zi04</response>
 18:32:22: (Libpurple: jabber) Recv (ssl)(78): <failure
 xmlns='urn:ietf:params:xml:ns:xmpp-sasl'><invalid-authzid/></failure>
 18:32:22: (Libpurple: sasl) Mechs found: CRAM-MD5 LOGIN PLAIN
 18:32:22: (Libpurple: jabber) Sending (ssl) (tekjew at jabber.org/Shindig):
 <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'/>
 18:32:22: (Libpurple: jabber) Recv (ssl)(116): <challenge
 xmlns='urn:ietf:params:xml:ns:xmpp-
 sasl'>PDUwNTA1NzA3MS4xMDIzNTYxN0BoZXJtZXMuamFiYmVyLm9yZz4=</challenge>
 18:32:22: (Libpurple: jabber) decoded challenge (38):
 <505057071.10235617 at hermes.jabber.org>
 18:32:22: (Libpurple: connection) Connection error on 0x1929eb80 (reason:
 0 description: Invalid challenge from server)
 18:32:22: Connection Disconnected: gc=1929eb80 (Invalid challenge from
 server)
 }}}

 It's also possible this is the result of something messed up in Adium's
 libpurple or cyrus-sasl build process.  I'd appreciate it if someone could
 test in another environment with cyrus-sasl enabled and comment in the
 ticket with the results.

-- 
Ticket URL: <http://developer.pidgin.im/ticket/11546>
Pidgin <http://pidgin.im>
Pidgin