From kde-core-devel  Thu Apr 05 20:41:00 2012
From: David Edmundson <david () davidedmundson ! co ! uk>
Date: Thu, 05 Apr 2012 20:41:00 +0000
To: kde-core-devel
Subject: Exposing KSSL in KIO
Message-Id: <CAGeFrHCxSZnFXNea4NORWGOGu8ko_Y3gYhq1f7zs58v0BNt97A () mail ! gmail ! com>
X-MARC-Message: https://marc.info/?l=kde-core-devel&m=133366816318843

In KDE Telepathy one the tasks I'm currently doing is certificate
handling. We get the certificate from telepathy and have to prompt the
user if they want to accept an invalid certificate.
All the normal SSL work is done in this telepathy component shared by
gnome, but any user prompts have to go through us so we match our DE
and gnome can do their thing.

Looking at the documentation KIO has everything I need, namely
KSSLCertificate and KSSLCertDialog. Unfortunately the headers aren't
installed so that I can't use any of it. Even though I could duplicate
that code myself it would be nice to get a consistent interface.

Is this deliberate? If so, why?
Is there any way I can use it currently? (i.e can I just copy the
headers without getting in lots of trouble)
Could this be changed for Frameworks?

Dave