kssl becoming private

[Thiago Macieira]

George Staikos wrote:
>Due to numerous factors including, but not limited to:
>1) Little progress in new features of KSSL
>2) Little improvement in the horrible API
>3) My inability to spend time on maintenance
>4) Absolutely broken applications using it improperly and introducing
>security holes
>5) Potential to replace some of the internals with QtSslSocket or
>possibly QCA
>
>I would like to make KSSL private.  That is, we will export the
>symbols but not install the headers.  The symbols become subject to
>change at any time.  KIO will continue to function properly, as will
>anything else in kdelibs using KSSL.  That also means that kcert has
>to be moved back to kdelibs, and we need a build solution for
>kcmcrypto.  I'm sure we can find one.  Does anyone have a substantial
>objection to this plan?

For what it's worth, I support it.

-- 
  Thiago Macieira  -  thiago (AT) macieira.info - thiago (AT) kde.org
    PGP/GPG: 0x6EF45358; fingerprint:
    E067 918B B660 DBD1 105C  966C 33F5 F005 6EF4 5358
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part.
URL: <http://mail.kde.org/pipermail/kde-core-devel/attachments/20070531/0a7adb16/attachment.sig>