Hello Martin, First of all thanks for your quick response.
On Tue, 2006-03-21 at 13:04 +0200, Martin Paljak wrote: > I recall your original problem was that a dynamic driver got removed > on last sc_unlock() ? No... I was in need of a sc_reset, but since I didn't have it, i decided to try sc_unlocked as a workaround, which didn't work for me > > This seems odd and useless for me (Nils, you deal with dynamic > drivers?) and i would suggest to get a fix for that behavior first > (if it's so (the driver is removed) then why?) I can look further into this, but it's not a soluction to our needs, because sc_unlock is reference counted and i can't assure pcsc_unlock is called (unless i call it directly). > Then you can use the pcsc specific transaction_reset configuration > parameter to force a reset on final sc_unlock(), or disconnect from > the card and the card shall be reset too. In addition to the reference count problem, there's also the problem that configuration is not only for PCSC (but not OpenCT or CTAPI) but for all PCSC, and affects all cards (could any card eventually need the opposite setting?). In additions it's easy for the user to misconfigure this required setting, and a potential source of problems. > > Why and where do you need to reset the card 'inside a transaction' ? This is to recreate a secure channel. When a operation which is performed under a secure channel fails, it reports an error and secure channel creation procedure needs the card to be reset previously. The solution of setting a reset on transaction and recreating the secure channel on login may work when different processes access to the card, but doesn't work on secure channel failure due to some kind of communication error, for instance. Perhaps I've overlooked something. Have you got any suggestion? Regards, -- Josep Monés [EMAIL PROTECTED] C3PO, S.L. http://www.c3po.es C/ Bertran, 113 - 08023 Barcelona Tel. 93 417 99 55 - Fax 93 253 12 80 _______________________________________________ opensc-devel mailing list [email protected] http://www.opensc-project.org/mailman/listinfo/opensc-devel
