> Its not a straight forward as you might think. Have you tried reading the 135 > page "Windows Smart Card Minidriver Specification"? > http://www.microsoft.com/whdc/device/input/smartcard/sc-minidriver.mspx
At least in so far to get a picture of the workings. And my impression is, that all the state management of cards is handled by the framework and thus the reader-driver is only required to do I/O (i.e. send/receive APDU:s). BTW: The main handle in OpenSC is 'sc_pkcs15_card_t' and not 'sc_context_t'. In fact 'sc_context_t' is really unimportant. But sc_pkcs15_card_t holds all the operational state the is required to make things working. Have a look at VENDOR_SPECIFIC, there is only one OpenSC specific field needed. _______________________________________________ opensc-devel mailing list opensc-devel@lists.opensc-project.org http://www.opensc-project.org/mailman/listinfo/opensc-devel
