On Tue, 15 Mar 2005 10:31:46 +0100, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > Regarding the reader.h file: > I am not sure how you want to use this FEATURE definitions! Could you > please explain in more detail!? > The teletrust spec wants the application (which in fact is a PKCS#11 module > or other - vendor specific - software which makes use of the driver/device > features) to get a list of supported control codes by issuing the > SCARD_CTL_CODE(3400), for the usage of all further control codes the driver > and the application have to share a header file with the control codes > defined, pcsclite should not be bothered with this.
I agree pcsc-lite should not be bothered with this. But as you wrote the application and the driver have to share a header with the control code. Since some of them are defined by Teletrust (and I think also by PCSC v2) it is a good (I think) idea to define them in a "well known" header file. My proposal is to add a /usr/include/PCSC/reader.h file that contains something like: /* * Provide source compatibility on different platforms */ #define SCARD_CTL_CODE(code) (0x42000000 + (code)) /* * TeleTrust Class 2 reader tags */ #define CM_IOCTL_GET_FEATURE_REQUEST SCARD_CTL_CODE(3400) #define FEATURE_VERIFY_PIN_START 0x01 /* OMNIKEY Proposal */ #define FEATURE_VERIFY_PIN_FINISH 0x02 /* OMNIKEY Proposal */ #define FEATURE_MODIFY_PIN_START 0x03 /* OMNIKEY Proposal */ #define FEATURE_MODIFY_PIN_FINISH 0x04 /* OMNIKEY Proposal */ #define FEATURE_GET_KEY_PRESSED 0x05 /* OMNIKEY Proposal */ #define FEATURE_VERIFY_PIN_DIRECT 0x06 /* USB CCID PIN Verify */ #define FEATURE_MODIFY_PIN_DIRECT 0x07 /* USB CCID PIN Modify */ #define FEATURE_MCT_READERDIRECT 0x08 /* KOBIL Proposal */ #define FEATURE_MCT_UNIVERSAL 0x09 /* KOBIL Proposal */ #define FEATURE_IFD_PIN_PROP 0x0A /* Gemplus Proposal */ #define FEATURE_ABORT 0x0B /* SCM Proposal */ > We appreciate a solution which is as well convenient as as most standard > conform as possible, vendor specific features should be kept seperated in > order to ensure a clean pcsclite implementation. - It is not mandatory for your application or your driver to #include <PCSC/reader.h> but it should be convenient - you can define/use vendor specific features if you want to - the file PCSC/reader.h will be provided by pcsc-lite since I have no better idea Do you think this is acceptable? -- Dr. Ludovic Rousseau For private mail use [EMAIL PROTECTED] and not "big brother" Google _______________________________________________ Muscle mailing list [email protected] http://lists.drizzle.com/mailman/listinfo/muscle
