Opened at 2009-07-09T12:06:51Z
Closed at 2010-03-14T17:00:12Z
#509 closed defect (duplicate)
TLS connectivity issue
Reported by: | Owned by: | wilmer | |
---|---|---|---|
Priority: | normal | Milestone: | |
Component: | Jabber | Version: | 1.2.3 |
Keywords: | Cc: | ||
IRC client+version: | Client-independent | Operating System: | Public server |
OS version/distro: |
Description
I'm experiencing trouble connecting via BitlBee to an XMPP service provided by a Zimbra Server:
jabber(i.galic@brainsware.org) - Logging in: Connecting jabber(i.galic@brainsware.org) - Logging in: Connected to server, logging in jabber(i.galic@brainsware.org) - Logging in: Converting stream to TLS jabber(i.galic@brainsware.org) - Logging in: Connected to server, logging in jabber(i.galic@brainsware.org) - Couldn't log in: XML stream error jabber(i.galic@brainsware.org) - Logging in: Signing off.. jabber(i.galic@brainsware.org) - Logging in: Reconnecting in 900 seconds..
I have enabled xmlconsole:
TX: <?xml version='1.0' ?><stream:stream to="brainsware.org" xmlns="jabber:client" xmlns:stream="http://etherx.jabber.org/streams" version="1.0"> RX: <stream:features><starttls xmlns="urn:ietf:params:xml:ns:xmpp-tls"></starttls><mechanisms xmlns="urn:ietf:params:xml:ns:xmpp-sasl"><mechanism>PLAIN</mechanism></mechanisms><compression xmlns="http://jabber.org/features/compress"><method>zlib</method></compression><auth xmlns="http://jabber.org/features/iq-auth"/></stream:features> TX: <starttls xmlns="urn:ietf:params:xml:ns:xmpp-tls"/> RX: <proceed xmlns="urn:ietf:params:xml:ns:xmpp-tls"/> TX: <?xml version='1.0' ?><stream:stream to="brainsware.org" xmlns="jabber:client" xmlns:stream="http://etherx.jabber.org/streams" version="1.0"> TX: </stream:stream>
At first I thought this was related to #437, but it seems not to be, as I'm not even able to login.
wilmer has looked into this on IRC, and asked me to open this ticket. To repro:
auto_connect = `true' auto_reconnect = `true' password is empty username = `i.galic@brainsware.org' port = `5222' priority = `0' resource = `BitlBee' resource_select = `priority' server = `mail.brainsware.org' ssl = `false' tls = `try' xmlconsole = `true'
Attachments (0)
Change History (3)
comment:1 Changed at 2009-10-18T00:55:29Z by
comment:2 Changed at 2009-11-11T15:38:30Z by
I had the same problem. TLS worked fine with other clients, had to use SSL for bitlbee though.
comment:3 Changed at 2010-03-14T17:00:12Z by
Resolution: | → duplicate |
---|---|
Status: | new → closed |
Sorry for taking so long. In the end someone else came to #bitlbee with the same problem and I root-caused it (#547). The fix is now checked in, changeset:devel,504. Sorry for taking so long with the actual fix. :-(
I wanted to add, that it does work with the following settings: