------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
http://bugs.kde.org/show_bug.cgi?id=163760
------- Additional Comments From emerald bluewin ch 2008-06-13 13:49 -------
Hi again Mark :o)
I don't know here how to initiate a move on the right direction. I agree that,
at least at the moment, all these
messages are coming from gpg and thus Kleopatra itself cannot influence the
smart card management. We could of course
simply remove my entry on Kleopatra bugs report system and then start a topic
on gpg side.
>From the other side, in my opinion it is not necessarily a good idea to assign
>(and consequently centralise) all
smartcard related tasks to a piece of software that is external to the
front-end application. Typically, the smartcard
reader initialisation should be made by the front-end itself (what will happen
for instance if several front-ends are
used simultaneously?). I think pcsc was made to manage this kind of things and
I don't really see an advantage adding a
new software-layer. Of course scdaemon should still be used but only to treat
the smartcard related objects that
concerns the certificates, keys and other crypto-objects; so I can imagine that
a collaboration between gpg and
kleopatra communities may be very helpful, but how to initiate it? What's your
point of view?
With warmest regards,
Manu Favre
P.S.
I not familiar in working in an open source environment, so if some of
proposals seem strange to you, please be
understanding :o|
[bugs.kde.org quoted mail]
_______________________________________________
Kdepim-bugs mailing list
[email protected]
https://mail.kde.org/mailman/listinfo/kdepim-bugs
