[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-bugs-dist
Subject:    [Bug 116201] Add support of PKCS#11 (Smartcards) into KDE
From:       kaido kert <kaidokert () gmail ! com>
Date:       2008-02-29 13:51:13
Message-ID: 20080229135113.11956.qmail () ktown ! kde ! org
[Download RAW message or body]

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
         
http://bugs.kde.org/show_bug.cgi?id=116201         




------- Additional Comments From kaidokert gmail com  2008-02-29 14:51 -------
> > So you actually patching Qt to support engine? And provide the certificate from \
> > manual configuration?

Qt needs to be patched anyway. Previously, in KDE3.5 kssl talked directly to OpenSSL. \
Now, QtSSL does that and kssl is hands off. So Qt needs to work with client \
certificates first.

Look at my previously posted patch for 3.5

The certificate is still selected through a popup list on the UI, very much like \
FireFox, IE and previous KDE. In case there is only one applicable certificate, it \
can be autoselected, exactly like IE does.

It is a very valid solution for smartcard, and other pkcs11 token uses.

My last patch did not modify the existing UI in any way. In fact, i made it as \
unobtrusive as humanly possible so it can be painlessly applied without breaking \
anything, and i intend to do the same in KDE/Qt trunk.

I will stop wasting time commenting here and just post a patch when (if ever) its \
ready, that worked better with the last version. Unfortunately i dont have much free \
time to dedicate to this in next coming weeks.


[prev in list] [next in list] [prev in thread] [next in thread]