| Summary: | kopete fails to connect to Jabber if SSL=on allowPlain=off | ||
|---|---|---|---|
| Product: | [Unmaintained] kopete | Reporter: | Constantin Berzan <cberzan> |
| Component: | Jabber Plugin | Assignee: | Kopete Developers <kopete-bugs-null> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | cjiecapb-nsk, detlev.casanova, kdebugs.boog, pali.rohar, stevenjose |
| Priority: | NOR | ||
| Version First Reported In: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | Ubuntu | ||
| OS: | Unspecified | ||
| Latest Commit: | Version Fixed In: | 4.11 | |
| Sentry Crash Report: | |||
|
Description
Constantin Berzan
2009-06-13 11:41:03 UTC
Confirm the problem. I can't reproduce that. What server are you connecting to ? I am connecting to a server at my school. I have asked the admin for some details, and what shows up in the logs, and I will update this report when he gets back to me. Some details I remember from using Kopete with that server before: * If ssl was off OR plain-auth was enabled, the server wouldn't accept the connection. It was configured for "maximum security". The only way to connect was SSL=on, plain-auth=off. * With ssl on, Kopete would give a warning message about the certificate (it was either expired or self-signed, I don't remember exactly). This message showed up every time I connected, so eventually I clicked "do not show again". (In reply to comment #2) > I can't reproduce that. What server are you connecting to ? openfire 3.6.3 in my case Sorry. As there was my problem don't concern a SSL. Simply the jabber server is in a zone .local, and kopete don't resolved his dns. Though nslookup and ping worked for this dns. 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 Im having the same issue, which seems to be related to https://bugs.kde.org/show_bug.cgi?id=221533#c20 I think its because kopete has not upgraded to the new method of ssl connection. I really wish this could be resolved, i cant change the setting on the server, as I do not have the 'influence' for it. (In reply to comment #7) > Im having the same issue, which seems to be related to > > https://bugs.kde.org/show_bug.cgi?id=221533#c20 > > I think its because kopete has not upgraded to the new method of ssl > connection. I really wish this could be resolved, i cant change the setting on > the server, as I do not have the 'influence' for it. Looks like it might be fixed in oneric with libqca2-plugin-ossl v2.0 Nope... upgraded to oneric, bug still exists. (In reply to comment #8) > (In reply to comment #7) > > Im having the same issue, which seems to be related to > > > > https://bugs.kde.org/show_bug.cgi?id=221533#c20 > > > > I think its because kopete has not upgraded to the new method of ssl > > connection. I really wish this could be resolved, i cant change the setting on > > the server, as I do not have the 'influence' for it. > Looks like it might be fixed in oneric with libqca2-plugin-ossl v2.0 Kopete in svn has updated xmpp libiris library. Please test Kopete version from svn if this problem is fixed. |