KDE and smartcard support

George Staikos staikos at kde.org
Tue May 22 16:23:35 BST 2007

On 22-May-07, at 11:13 AM, Alon Bar-Lev wrote:

> On 5/22/07, George Staikos <staikos at kde.org> wrote:
>>    I think you are the one who is confused now.  You are welcome to
>> use QCA for any of those.  However, SSL policy has been centralized
>> in KDE and should be handled through the centralized system.  KIO
>> also has built-in SSL protocol support which works, and without any
>> additional dependency we can move to using QtSslSocket there, which I
>> think is a good thing.  Your smartcard implementation could easily be
>> done by providing an abstract interface in kdelibs and then
>> implementing it elsewhere.  This is part of what we realized when we
>> started writing smartcard code for KDE 7 years ago (and abandoned it
>> due to lack of interest and support).
> Hello George,
> I do not believe that I am confused.
> Smartcards is not a separate implementation, it should be available at
> any cryptographic operation in the framework. This should be
> transparent to applications.
> If KDE offers TLS/SSL operations via a specific interface, such as
> "KIO", the KIO should provide this service for software and hardware
> based cryptography.

   Via an interface that is implemented elsewhere.  Therefore all  
that is needed in KIO is an interface.  The library and  
implementation choice is irrelevant.

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

More information about the kde-core-devel mailing list