2011/10/10 Stef Hoeben <[email protected]>: > Hi, > >>If, as an PC/SC application author, you think something is missing in >>the PC/SC standard just tell me. I will try to propose it for >>inclusion. > > Just my 3 cents: > > - A standard way to specify the messages to be written on the pinpad reader > (for readers with a display, of course)
OK > - A 'pin merge' feature: part of the PIN is provided by the app and > the other part is entered on the pinpad reader. (Some readers already > allow this: you just put part of the PIN in the APDU -- but some > readers seem to overwrite the APDU's PIN buffer with padding bytes..) How do you do that? What SCardControl() do you send? Please provide a real example. > - Currently, only Verify and Change pin commands exist. On most readers, > you can (ab)use them to do an Unblock without resp. with pin change; > but some readers check the INS byte during a Verify command -> so it's > not possible to do an Unblock without pin change. What INS code do you use to unblock? I can find 5 unbock commands in [1]. The best candidate I found is: UNBLOCK CHV, Reset a PIN retry counter that has reached its maximum value. INS: '2C’ Standard: TS 51.011 EN Do you abuse the FEATURE_VERIFY_PIN_DIRECT command for a PIN unblock? > Hope it's clear, and that those features aren't in already > (didn't do my homework either..) Thanks [1] http://www.wrankl.de/SCTables/SCTables.html -- Dr. Ludovic Rousseau _______________________________________________ Muscle mailing list [email protected] http://lists.drizzle.com/mailman/listinfo/muscle
