Hi, (Before to anwser, I have read all the posts.)
Ludovic Rousseau <[EMAIL PROTECTED]>: > I would like to introduce the ability to perform a "secure PIN > management" in my CCID driver (and also in pcsc-lite). Excellent idea! [... many good arguments ... ] > We then need a way for the application to know if the reader has this > "secure PIN management" feature. The PC/SC specification defines (in > part 3, page 7) a tag value (0x0142) for "User Authentication Input > Device". Value 0x00000002 is for "Numeric (that is PIN) pad" and value > 0x00000004 is for "keyboard". Of course I don't know which one to use :-) > I think 0x00000002 is the correct choice. IMHO the IFDHGetCapabilities return value may depend of the device used. For instance, using the CCID driver it may return 0x00000002 for the SPR532 and 0x00000004 for the SK-3106. > So I plan to: > - modify SCardControl to match Microsoft interface. > I will change the library major version since this modifies the API > and ABI. You will need to recompile to use (link to) the new lib. > - implement SCardGetReaderCapabilities/SCardSetReaderCapabilities in > pcsc-lite I am agree for this. > - Select an arbitrary tag value for SCardControl to indicate it is a > "secure PIN management" command. We can have one tag value for the > CCID way and another tag value for the CT-BCS way. Only the > application and the driver need to be in sync, no impact on pcsc-lite > (except documentation in an appendix of pcsc-lite doc). > My preference is 0x42000001. 0x42 [6] may be a pcsc-lite prefix. I have no special opinion about this tag value but if 42 is the meaning of the life I am agree ;-). My problem is just about the structure (and its name) given to SCardControl. If we use the PC_to_RDR_Secure, there are fields related to the CCID and it is not clean if the targeted reader is not CCID ... I have no idea on this point. Best Regards, -- Damien Sauveron ------------------------------------------------- This mail sent through IMP: http://horde.org/imp/ _______________________________________________ Muscle mailing list [EMAIL PROTECTED] http://lists.drizzle.com/mailman/listinfo/muscle
