hi i'm trying to use the pinpad of a spr 532 for authentification. i'm sending theSCardControl sequence for pin verification as shown in the example in the pc/sc manual, adapted to the apdu my card uses and adding the length field for the bTeoPrologue field...
so the message looks like this: apdu: 00 20 00 81 08 24 00 00 ff ff ff ff ff followed by the pin verification data structur: 00 89 07 04 04 0c 03 00 04 09 00 and finaly the bTeoPrologue: 00 00 0d (length of apdu = 13) i receive the message 00 00 02 90 00 92 indicating the authentification went well, but the next call to SCardTransmit hangs for 2 minutes and then fails with SCARD_F_COMM_ERROR i have to remove the card and reinsert it to use the reader again... also the led which was blinking to indicate i should enter the pin is lighted after the authentification was done, which propably indicates that the authentification was successful, as it is turned of if i enter a wrong pin... (though it still hangs at the next call) of course, if i send the apdu directly using scardtransmit to enter the pin without the pad there is no hang... i guess the problem is the i-block prologue? another thing which i noticed is, if i try to tell the reader to set the length information for the pin in the apdu (the second half byte of the byte following Lc (24 above) should contain the length) i always get a message that the pin is to short or to long from the card... though the same format is used in the example 3 for pin verification in the ccid specification (appendix E) (the only change to the above header is setting bmPinBlockString to 0x47 (07 above)) any ideas what might go wrong here? thanks, Sven Matner _______________________________________________ Muscle mailing list [EMAIL PROTECTED] http://lists.drizzle.com/mailman/listinfo/muscle
