The specific format of the VERIFY command depends on the application like, GSM, EMV etc. P2 specifies the specific format. In simpler applications it defines the number of the CHV file. In EMV for instance, you have to supply a rather complex data structure, which
specifically is defines by P2.


The coding of the PIN is also dependent on the application and could, besides the suggestions I saw already on your request, also be BCD: 0x12, 0x34.

Do you have the Technical manual for the specific card you are using ? I have a Schlumberger manual here that defines the length to be 8 on
this command to verify a CHV.


Willem Lobbezoo

Germano Paciocco wrote:

Willem Lobbezoo ha scritto:

What errors do you get ?


An example: if I try the subsequent VERIFY command
CLA  INS  P1   P2   Lc   >DATA
0x00 0x20 0x00 0x01 0x04 0x01 0x02 0x03 0x04

the card answer "6700": on the ISO this corresponds to "Wrong length".
Now, the PIN of my card is 1234, and I'm not sure I have to encode it in this way, but I don't understand this error in any way! What has "wrong length"? The Data Field? the entire APDU? How hava I to encode the PIN?
Other errors on next issues... ;)








---
Visit the OpenCard web site at http://www.opencard.org/ for more
information on OpenCard---binaries, source code, documents.
This list is being archived at http://www.opencard.org/archive/opencard/

! To unsubscribe from the [EMAIL PROTECTED] mailing list send an email
! to
! [EMAIL PROTECTED]
! containing the word
! unsubscribe ! in the body.




Reply via email to