[Pidgin] #2432: Pidgin is not connecting when using XMPP under special conditions

Pidgin trac at pidgin.im
Mon Aug 6 08:48:04 EDT 2007


#2432: Pidgin is not connecting when using XMPP under special conditions
----------------------+-----------------------------------------------------
Reporter:  Valgoerad  |       Owner:  datallah       
    Type:  defect     |      Status:  new            
Priority:  minor      |   Component:  winpidgin (gtk)
 Version:  2.1.0      |    Keywords:                 
 Pending:  0          |  
----------------------+-----------------------------------------------------
 I'm trying to use Pidgin at work where I have only couple of ports open. I
 have created a tunnel on port 443 for XMPP and everything works correctly
 when using Pandion or PSI but Pidgin has some problems unfortunately.

 I have created a new XMPP account, specified my own connect port, connect
 server and checked "Force old SSL". But with these options set-up I get:

 {{{
 (14:17:12) account: Connecting to account martel at aie.pl/Work
 (14:17:12) connection: Connecting. gc = 022C4BC0
 (14:17:12) dnsquery: Performing DNS lookup for aie.pl
 (14:17:12) dnsquery: IP resolved for aie.pl
 (14:17:12) proxy: Attempting connection to 62.233.139.74
 (14:17:12) proxy: Connecting to aie.pl:443 with no proxy
 (14:17:12) proxy: Connection in progress
 (14:17:12) proxy: Connected to aie.pl:443.
 (14:17:12) jabber: Sending (ssl): <?xml version='1.0' ?>
 (14:17:12) jabber: Sending (ssl): <stream:stream to='aie.pl'
 xmlns='jabber:client' xmlns:stream='http://etherx.jabber.org/streams'
 version='1.0'>
 (14:17:12) jabber: Recv (ssl)(435): <?xml version='1.0'?><stream:stream
 xmlns='jabber:client' xmlns:stream='http://etherx.jabber.org/streams'
 id='3676372883' from='aie.pl' version='1.0'
 xml:lang='en'><stream:features><starttls xmlns='urn:ietf:params:xml:ns
 :xmpp-tls'/><mechanisms xmlns='urn:ietf:params:xml:ns:xmpp-
 sasl'><mechanism>DIGEST-
 MD5</mechanism><mechanism>PLAIN</mechanism></mechanisms><register
 xmlns='http://jabber.org/features/iq-register'/></stream:features>
 (14:17:12) jabber: Sending (ssl): <starttls xmlns='urn:ietf:params:xml:ns
 :xmpp-tls'/>
 (14:17:12) jabber: Recv (ssl)(50): <proceed xmlns='urn:ietf:params:xml:ns
 :xmpp-tls'/>
 }}}

 As you can see form the script above, Pidgin connects to the server, talks
 to it and then fails to proceed with tls encryption. It just hangs there
 for eternity. I'm not sure if tls should even be used when using SSL but
 you're the experts so I'll leave it up to you :)

 You're doing a great job, guys - there's really no superior alternative
 for Pidgin. Thanks.

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


More information about the Tracker mailing list