Am Dienstag 20 April 2010 07:03:51 schrieb Peter Stuge: > Basically remove the whole lot of APDUs, T=0/T=1, CCID and PC/SC, > and talk PKCS#11 nearly directly with hardware.
you still need to * select the reader to use (if there are several) * select the slot to use (if there are several) * select the card to use (e.g.on contactless readers) * map PKCS#11 API to some transport stream or data structures * handle locking, resets, enumeration, access control, etc. so "directly with the hardware" might not be as easy as it sounds. also the hardware wants to be independend from the host hardware used I guess? so you need to define if the exchange format used to talk with the hardware is big or little endian (or if the card side converts: tell it which format you used). and still you would have issues. for me pkcs#11 is quite a low level api, at least compared to microsoft crypto api. I'd prefer if the goal would be set high, with user stories and end user perspective in mind, and then an easy solution for that would be sought. if you stay with pkcs#11 you don't fix the problems we have despite implementing pkcs#11. Regards, Andreas _______________________________________________ opensc-devel mailing list opensc-devel@lists.opensc-project.org http://www.opensc-project.org/mailman/listinfo/opensc-devel
