[Pidgin] #1392: X-GOOGLE-TOKEN confuses jabber client

[Pidgin]

#1392: X-GOOGLE-TOKEN confuses jabber client
--------------------------+-------------------------------------------------
 Reporter:  akrherz       |       Type:  defect
   Status:  new           |   Priority:  minor 
Component:  pidgin (gtk)  |    Version:  2.0.1 
 Keywords:                |    Pending:  0     
--------------------------+-------------------------------------------------
 This ticket may be a wild goose chase, so feel free to close it out if you
 aren't interested :)

 So, we have a situation where we are attempting to make Pidgin work with
 Openfire 3.3.1 Jabber server via an Akonix L7 Socks5 proxy.  This bug is
 sort of with Akonix, but perhaps Pidgin could help out.  The Akonix will
 blindly send the Pidgin client this stanza after initial connect:

 <stream:features><mechanisms xmlns="urn:ietf:params:xml:ns:xmpp-
 sasl"><mechanism>X-GOOGLE-TOKEN</mechanism></mechanisms></stream:features>

 Pidgin then responds to the user that this server doesn't have any
 supported authentication mechanisms.  Other Jabber clients (ex) miranda)
 seem to ignore this stanza and move on and thus work with the proxy.

 The Akonix folks tell us that this token is to turn off encryption in the
 GoogleTalk client. Any thoughts?  I appologize if I just wasted your time
 :(

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