[telepathy] [Bug 342972] New: Custom CA certs from kssl aren't passed to Telepathy

Elias Probst mail at eliasprobst.eu
Sat Jan 17 16:32:51 GMT 2015


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

            Bug ID: 342972
           Summary: Custom CA certs from kssl aren't passed to Telepathy
           Product: telepathy
           Version: unspecified
          Platform: Gentoo Packages
                OS: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: NOR
         Component: auth-handler
          Assignee: kde-telepathy-bugs at kde.org
          Reporter: mail at eliasprobst.eu

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 at eliasprobst.eu - The SSL/TLS
certificate received from server was not signed by a trusted certificate
authority
Could not connect mail at 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.

-- 
You are receiving this mail because:
You are the assignee for the bug.



More information about the Kde-telepathy-bugs mailing list