kssl becoming private

[George Staikos]

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?

--
George Staikos
KDE Developer				http://www.kde.org/
Staikos Computing Services Inc.		http://www.staikos.net/