[Pidgin] #1024: Crash logging into certain XMPP servers

[Pidgin]

#1024: Crash logging into certain XMPP servers
------------------------------+---------------------------------------------
  Reporter:  faflu            |       Owner:  datallah
      Type:  defect           |      Status:  assigned
  Priority:  major            |   Milestone:          
 Component:  winpidgin (gtk)  |     Version:  2.0     
Resolution:                   |    Keywords:          
   Pending:  0                |  
------------------------------+---------------------------------------------
Changes (by datallah):

 * cc: deryni, nwalp (added)
  * priority:  minor => major
  * summary:  Application crashes just after a start => Crash logging into
              certain XMPP servers

Comment:

 The problem is that the following challenge is being sent from the server:
 `jabber: decoded challenge (108): realm="chrome.pl",
 nonce="joDPsz5QeDQ6ojo3obtFJw==", qop="auth, auth-int", charset=utf-8,
 algorithm=md5-sess`

 Pidgin parses it into the following Key value pairs (apostrophes added for
 clarity):
 {{{
 ' charset'='utf-8'
 ' nonce'='vfOAeAy26GUXwGbxRgmA0g=='
 ' algorithm'='md5-sess'
 ' qop'='"auth'
 'realm'='chrome.pl'
 }}}

 I can't tell if the server is sending invalid data, or we're just unable
 to parse the  challenge string containing spaces (and the quoted text
 containing a comma).

 At any rate, it shouldn't crash, but that part is easy to fix.

 deryni/nwalp: Thoughts about this? Should the parsing be fixed to work
 with such a challenge string?

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