[kopete-bugs] [Bug 196315] kopete fails to connect to Jabber if SSL=on allowPlain=off

[Tom Helner]

https://bugs.kde.org/show_bug.cgi?id=196315


Tom Helner <kdebugs.boog at spamgourmet.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |kdebugs.boog at spamgourmet.co
                   |                            |m




--- Comment #6 from Tom Helner <kdebugs boog spamgourmet com>  2010-03-10 20:13:34 ---
I am seeing similar behavior, and the same errors in Kopete 4.4.1.
Kopete can connect to talk.google.com using ssl with no problems. It cannot
however, connect to my work jabber using ssl. It does not matter if plain-auth
is enabled or disabled, if ssl is enabled it will not connect. I have found
that it will connect using only plain-text auth, but obviously sending
passwords in plain text is a bad idea.

Pidgin connects to my work jabber using ssl/tls without problem. Capturing
traffic while connecting to work with Pidgin I see that the protocol goes from
TCP to Jabber/XML with the contents of the packets are TLS encrypted. When I
attempt to connect using Kopete with SSL enabled the protocol goes from TCP to
TLSv1 and the connect fails.

I can include these captures if it helps.

Version:         4:4.4.1-0ubuntu1~karmic1~ppa1
Installed from:  ppa.launchpad.net/kubuntu-ppa/backports/ubuntu
OS:              Kubuntu 9.10

-- 
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.