Bug 342972

Summary:	Custom CA certs from kssl aren't passed to Telepathy
Product:	[Unmaintained] telepathy	Reporter:	Elias Probst <mail>
Component:	auth-handler	Assignee:	Telepathy Bugs <kde-telepathy-bugs>
Status:	RESOLVED UNMAINTAINED
Severity:	normal
Priority:	NOR
Version:	unspecified
Target Milestone:	Future
Platform:	Gentoo Packages
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description Elias Probst 2015-01-17 16:32:51 UTC

I'm using a self-signed server certificate.
So I imported the CA of this certificate into my local CA store (see also bug#342958).

When trying to connect now, I still get to see the error message:
There was a problem while trying to connect mail@eliasprobst.eu - The SSL/TLS certificate received from server was not signed by a trusted certificate authority
Could not connect mail@eliasprobst.eu. There was a network error, check your connection

So this looks to me like the custom CA cert isn't read and/or passed to Telepathy/mission-control/gabble.
The account is using gabble/jabber.

Running all latest KF5 + KTP (frameworks) components from git + Qt 5.4.0.

Versions of other components:
net-im/telepathy-mission-control-5.16.3
net-libs/telepathy-glib-0.24.1
net-libs/telepathy-qt-0.9.5
net-voip/telepathy-gabble-0.18.3

Tried to get more information using ktp-debugger and running 'ktp-auth-handler --persist --debug', but none of them showed any useful/relevant information.

Comment 1 Justin Zobel 2021-03-09 07:26:20 UTC

Thank you for the bug report.

As this report hasn't seen any changes in 5 years or more, we ask if you can please confirm that the issue still persists.

If this bug is no longer persisting or relevant please change the status to resolved.

Comment 2 Christoph Cullmann 2024-09-18 18:12:54 UTC

Dear user, unfortunately Telepathy is no longer maintained.

Please migrate to another solution, e.g. for Jabber a possibility is Kaidan, for Matrix a candidate is NeoChat.