[Pidgin] #4364: XMPP/GTalk Account Will Not Connect

[Pidgin]

#4364: XMPP/GTalk Account Will Not Connect
--------------------------+-------------------------------------------------
  Reporter:  pellis       |       Owner:  seanegan      
      Type:  defect       |      Status:  new           
  Priority:  minor        |   Milestone:                
 Component:  Google Talk  |     Version:  2.3.1         
Resolution:               |    Keywords:  not connecting
   Pending:  1            |  
--------------------------+-------------------------------------------------
Changes (by pellis):

  * pending:  1 => 0

Comment:

 I've tried setting the connect port to both of those options while
 checking or unchecking the force old ssl port (5223).  Nothing seems to
 work.  When I look at the gtalk application connecting through ethereal, I
 see that my PC talks directly to a google IP for authentication over port
 443.  After that I start seeing jabber-type messages on port 5222 from an
 internal IP, which as you stated, is my company monitoring my IMs.

 There's not really an option in Pidgin to force SSL over port 443 and
 continue connecting on port 5222.  The best I can do is try to force SSL
 over 5223 and try to connect on port 443 or 5222.  Other people have had
 luck with that, but I have not.  When I try to connect on port 5222 and
 force SSL on port 5223, I get a Jabber response error: <stream:error><bad-
 format xmlns="urn:ietf:params:xml:ns:xmpp-
 streams"/></stream:error></stream:stream>

 When I try to connect on port 443 and force SSL on port 5223,
 talk.google.com resolves to an internal IP and it looks like it goes
 through the song and dance of some type of authentication: "client hello,"
 "server hello, certificate, server hello done," "client key exchange,
 change cipher spec, encrypted handshake message," "change cipher spec,
 encrypted handshake message," "application data" (ack) "application data"
 (ack) then nothing.  No Jabber-type messages show up and no more
 communications from the internal-ip.  Eventually Pidgin disconnects with a
 cryptic "read error."

 I don't think there's any combination of currently available options that
 will work behind my corporate firewall and data tracking measures.

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