[Pidgin] #2095: XMPP disconnect causes inability to reconnect

Pidgin trac at pidgin.im
Wed Aug 29 11:40:48 EDT 2007


#2095: XMPP disconnect causes inability to reconnect
---------------------------+------------------------------------------------
  Reporter:  akrherz       |       Owner:  deryni
      Type:  defect        |      Status:  new   
  Priority:  minor         |   Milestone:        
 Component:  pidgin (gtk)  |     Version:  2.0.2 
Resolution:                |    Keywords:        
   Pending:  0             |  
---------------------------+------------------------------------------------
Comment (by deryni):

 Ok, so I just did a little bit of digging into SASL and the use of it in
 XMPP and it looks to me like the java SASL implementation is just wrong.

 Given

 RFC3920 Section 6.2 Point 3: The initiating entity selects a mechanism by
 sending an <auth/> element qualified by the 'urn:ietf:params:xml:ns:xmpp-
 sasl' namespace to the receiving entity and including an appropriate value
 for the 'mechanism' attribute. This element MAY contain XML character data
 (in SASL terminology, the "initial response") if the mechanism supports or
 requires it; if the initiating entity needs to send a zero-length initial
 response, it MUST transmit the response as a single equals sign ("="),
 which indicates that the response is present but contains no data.

 and

 RFC2831 Section 2.2 (specifically 2.2.1): The client uses the values from
 the previous authentication and sends an initial response with a string
 formatted and computed according to the rules for a "digest-response", as
 defined above, but with a nonce-count one greater than used in the last
 "digest-response".

 It appears to me that Cyrus is attempting to do that shorter
 authentication and that the java SASL can't handle it.

 All that being said, it is entirely possible that there is some level of
 SASL configuration which allows for having turned that shorter method off,
 if there is such a thing and the java SASL is setting it than Cyrus is
 broken. But this is well beyond my level of knowledge.

-- 
Ticket URL: <http://developer.pidgin.im/ticket/2095#comment:9>
Pidgin <http://pidgin.im>
Pidgin


More information about the Tracker mailing list