Bug 94301 - use central KDE certificate management
Summary: use central KDE certificate management
Status: CONFIRMED
Alias: None
Product: kopete
Classification: Applications
Component: libkopete (show other bugs)
Version: 0.40.0
Platform: Gentoo Packages Linux
: NOR wishlist
Target Milestone: ---
Assignee: Kopete Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-12-02 23:22 UTC by Jose Gonzalez Gomez
Modified: 2010-01-06 00:46 UTC (History)
4 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Jose Gonzalez Gomez 2004-12-02 23:22:21 UTC
Version:           0.9.1 (using KDE KDE 3.3.1)
Installed from:    Gentoo Packages
Compiler:          gcc-3.3.4, glibc-2.3.4.20040808-r1 
OS:                Linux

Kopete doesn't seem to be using the root CA configured in KDE (security -> crypto -> SSL signers)

I have installed and configured a corporate Jabber server (JabberD), and have activated the use of SSL, using our own root CA, and a server certificate signed by that root CA. This setup is working properly, and we have tested it with Konqueror after adding our root certificate to the KDE SSL signers.

When Kopete connects to the server, we get an error saying the following:

Certificate of server [server name] could not be validated for account [account name] : The Certificate Authority is invalid

So Kopete seems to be ignoring the KDE SSL signers store. In my investigations I have found that Kopete relies on app-crypt/qca-tls for the TLS/SSL part, but I have found little information about this library. I have also found that I'm not the only one with this problem:

http://www.kde-forum.org/viewtopic.php?t=3676&start=0&postdays=0&postorder=asc&highlight=

As you can see in this forum, the problem happens also with self signed certificates although you add it to the KDE SSL signers. So this seems to be a bug or missing feature in Kopete (although I don't understand why somebody would include SSL support without trust chain checking).
Comment 1 Matt Rogers 2005-01-28 07:51:25 UTC
need to revisit for KDE 4
Comment 2 Will Stephenson 2005-03-02 08:47:26 UTC
This is also the case for Groupwise, and any other protocol using SSL.  We'll have to have a rethink for KDE4 as Matt said.
Comment 3 quazgar 2010-01-06 00:45:12 UTC
Can new CA certificates be added at all in KDE4?  See also http://forum.kde.org/viewtopic.php?f=18&t=82926
Comment 4 quazgar 2010-01-06 00:46:08 UTC
PS: This bug might be related to bug #210356