Bug 202672

Summary:	Setting SSL and not setting port for Jabber produces "Connection Refused" error
Product:	[Unmaintained] kopete	Reporter:	Björn Tantau <bugs.kde.org>
Component:	Jabber Plugin	Assignee:	Kopete Developers <kopete-bugs-null>
Status:	RESOLVED FIXED
Severity:	major	CC:	kde, koersen, mattr, ottmarm, pali.rohar
Priority:	NOR
Version First Reported In:	unspecified
Target Milestone:	---
Platform:	Ubuntu
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:	4.11
Sentry Crash Report:

Description Björn Tantau 2009-08-05 19:18:38 UTC

Version:           0.70.90 (using KDE 4.3.0)
OS:                Linux
Installed from:    Ubuntu Packages

After upgrading from KDE 4.2 to 4.3 in Kubuntu 9.04 Kopete wouldn't connect to my SSL-encrypted Jabber-server anymore.
The error-message was "Connection refused"

Wireshark revealed that kopete was trying to connect to port 5222 instead of 5223 like the settings dialogue hinted at in the grayed out Portnumber.

I could connect after setting "Override default server information".

I think if a jabber-server accepts connections on both ports it might lead to a user thinking that his connection is encrypted although it is not.

Comment 1 ottmarm 2009-08-19 18:35:11 UTC

Hi,

I can confirm it:
After update to KDE-4.3.0 from KDE-4.2.3 (on my both machines), I have a problem with secured connection to jabber networks. There was not a problem before. I have archlinux on my notebook and gentoo on my home PC.

I'm using three networks: my own jabber server, jabber server in our free community network, and our corporation jabber server in other country.
Everything is with SSL encryption.

With the new Kopete, only my jabber server is accessible from everywhere. But only via non-encrypted port, which could be a 'security' problem, because of my communication should be encrypted by settings, and I expect it really is.
Other two networks are inaccessible from outside, because of non-encrypted communication is not allowed from outside.

There is this error message after a minute of connecting:
There was a connection error: Connection refused

With PSI, I'm able connect to all three networks to secured ports within two seconds. But PSI is not Kopete. :-)

Overriding of default server informations 'solves' the problem.

Comment 2 Martin Droessler 2009-08-20 13:30:07 UTC

I can also confirm this behaviour.
I can connect if I explicit override the servername and port, but otherwise get the mentioned error-message after 30 - 60 seconds.
I'm also using KDE 4.3 (Kopete-Version 0.70.90)

Comment 3 koersen 2009-12-29 09:49:28 UTC

Hi,

Checking "Override default server information" box makes my Jabber connection work. When I don't check I get an error message (popup w/o focus) saying:

Connection problem with Jabber server <servername>

There was an error in the protocol stream: Policy fiolation in the protocol stream. STARTTLS is required for this stream.

Maybe it is my server that does not do STARTTLS. When I check "Override default server information" the connection works.

Comment 4 Pali Rohár 2013-06-04 16:53:35 UTC

libiris - client XMPP library used by Kopete was updated to last version. I also fixed Kopete code for legacy SSL support, so problems should be fixed.

By default jabber servers listen on 5222 port and use STARTTLS for secure connections. Old servers listen on port 5223 and using legacy SSL encryption.