Hello, On 10/3/11 3:02 , Jean-Michel Pouré - GOOZE wrote: > 1) What is OpenSC/libccid current PINPAD support? I have to admit last > time I used PINPAD was more than a year ago. What exactly is your question? The support for pinpads has been there for several years for now. As noted in code, it often requires "vendor specific hacks" as many readers are bogus (they only support a subset of what is defined in CCID, for example restricted min/max PIN lengths or entry conditions).
> 2) What does it mean when a reader claims 'secure messaging'. Does it > need to be supported on the smartcard side also? Is it a real standard > in CCID? Is it well supported in OpenSC? I assume you refer to authenticated communication between terminal (firmware) and card? This would require support on card as well as in terminal. This would be quite closely coupled and does not really relate to OpenSC. > 3) I still wonder why we should declare PINAD in OpenSC configuration > file. Is there an alternative, when libccid would discover PINPAD and > OpenSC would automatically using it. Could you tell more of the current > way that OpenSC discovers the PINPAD. This is exactly how it is working. There is an option in opensc.conf to turn the pinpad *off* (as it is enabled by default) if there are problems with the device or some application. Note that pinpad support in applications and platform libraries (OS X, Windows) varies. -- @MartinPaljak +3725156495 _______________________________________________ opensc-devel mailing list opensc-devel@lists.opensc-project.org http://www.opensc-project.org/mailman/listinfo/opensc-devel
