On Wed, 2011-06-08 at 16:35 +0200, Jean-Pierre Szikora wrote: > On 06/08/2011 03:50 PM, Andre Zepezauer wrote: > > On Wed, 2011-06-08 at 11:50 +0200, Jean-Pierre Szikora wrote: > >> On 06/07/2011 03:17 PM, Andre Zepezauer wrote: > >>> Hello Jean-Pierre, > >>> > >>> SC_PKCS15_PIN_FLAG_VERIFY_RC_COUNTER doesn't correspond to any flag > >>> defined in PKCS#15. Furthermore, the capability to modify the return > >>> code of the VERIFY command is not specific to PKCS#15. > >>> > >>> Why not using a different approach? In example it's possible to detect > >>> the installed packages of CardOS. Depending of the presence of the > >>> "Verify Retry Counter Package" the flags in TEST BSO could be set > >>> accordingly. > >>> > >> Hi Andre, > >> > >> Any comment/objection? > > A flag SC_CARD_FLAG_ISO_VERIFY would be of general use. If set, then > > it's possible to send the VERIFY command with *empty* data field to get > > the number of further allowed retries coded in SW '63CX'. > > > > That means, that cardos_have_verifyrc_package would be placed better in > > card-cardos.c and only "card->flags & SC_CARD_FLAG_ISO_VERIFY" needs to > > be checked in pkcs15-cardos.c > > > > Prerequisite is that opensc-tool -s "00 20 00 01" returns something > > like: Received (SW1=0x63, SW2=0xC3) > > > > Any comment/objection? > The pre-requirement is not fulfilled :-( > Using reader with a card: ACS ACR38U 00 00 > Sending: 00 20 00 01 > Received (SW1=0x6A, SW2=0x88) > > As suggested by Martin, it's probably not worth to create a general flag > for this particular usage...
Seems so, because there's no ticket requesting a new enhancement for something similar. That means, no demand for such a general flag. No objection left. Regards Andre _______________________________________________ opensc-devel mailing list opensc-devel@lists.opensc-project.org http://www.opensc-project.org/mailman/listinfo/opensc-devel
