Tommaso Cucinotta wrote: > Karsten Ohme ha scritto: > >> No, they are not. At the moment I dramatically change the libmusclecard >> API to support arbitrary tokens, not only the MCardApplet, so that e.g. >> only PKCS#11 implementation is necessary to support arbitrary tokens, >> not one PKCS#11 implementation for each token. If this is done and I >> have proposed it, I will embed the changes. >> > > What do you mean by support for arbitary tokens ? libmusclecard already > had a "plugin" architecture > for supporting multiple cards, and the musclecard P#11 was working with > all cards supported by > the libmusclecard framework. Can you detail, please ?
No, libmusclecard is specific for the MuscleCard applet, i.e. the card edge specification. It does not support mutual authentication, internal authentication, biometric information, secure channels, key wrapping, deriving keys, object creation with flexible ACL and access restrictions, UTF-8 support for PINs and general, certificate formats, ... E.g. the object class did not allow to access FID on an ISO file system, the key numbering is not used by standards like PKCS#15, etc. > > In the libmusclecardchanges.html you mention this "dwControlCodeForX" > stuff which I didn't > really understand. Is that only related to card readers with keypad > support or does it deal with > how to communicate with the card as well ? This is only for cards with a keypad to enter the PIN. I have only readers with keypad and display, other readers are ever more useless as the security of these readers permits. When PC/SC 2.0 is the standard this will be more easy, at the moment the control codes etc. are necessary. > > Thanks, bye, > > T. > _______________________________________________ > Muscle mailing list > [email protected] > http://lists.drizzle.com/mailman/listinfo/muscle _______________________________________________ Muscle mailing list [email protected] http://lists.drizzle.com/mailman/listinfo/muscle
