Bug 248878

Summary:	ldap search does not accept self-signed certificate
Product:	[Applications] kaddressbook	Reporter:	Mathias Waack <M.Waack>
Component:	ldap search	Assignee:	kdepim bugs <kdepim-bugs>
Status:	RESOLVED UNMAINTAINED
Severity:	normal	CC:	bart.polot, ismail, tokoe
Priority:	NOR
Version:	unspecified
Target Milestone:	---
Platform:	openSUSE
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description Mathias Waack 2010-08-24 11:07:22 UTC

Version:           unspecified (using KDE 4.4.4) 
OS:                Linux

In the .xsession-errors log I get these error: 

[akonadiserver] Database "akonadi" opened using driver "QMYSQL"
[/usr/bin/akonadi_ical_resource] Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString)
[akonadiserver] Database "akonadi" opened using driver "QMYSQL"
[/usr/bin/akonadi_vcard_resource] Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString)
[akonadiserver] Database "akonadi" opened using driver "QMYSQL"
kdeinit4: preparing to launch /usr/lib64/kde4/kio_ldap.so
[akonadiserver] Database "akonadi" opened using driver "QMYSQL"
[/usr/bin/akonadi_kabc_resource] akonadi_kabc_resource_0(26751): Loading error:  "Could not connect to host error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed (self signed certificate in certificate chain)."
kio_ldap(26768)/kio (kioslave) KIO::SlaveBase::finished: finished() called after error()! Please fix the KIO slave. 

I've upgraded from opensuse 11.2 to 11.3, the ldap-lookup from kmail worked before. 

Reproducible: Always

Comment 1 Bart 2010-12-06 17:43:21 UTC

Also happens here with Arch on KDE 4.5.4

Comment 2 Denis Kurz 2016-09-24 20:51:50 UTC

This bug has only been reported for versions before 4.14, which have been unsupported for at least two years now. Can anyone tell if this bug still present?

If noone confirms this bug for a Framework-based version of kaddressbook (version 5.0 or later, as part of KDE Applications 15.08 or later), it gets closed in about three months.

Comment 3 Denis Kurz 2017-01-07 22:30:49 UTC

Just as announced in my last comment, I close this bug. If you encounter it again in a recent version (at least 5.0 aka 15.08), please open a new one unless it already exists. Thank you for all your input.