Re: MUSCLE Is 61xx handled in your driver?
David Corcoran wrote: I think you should handle the Get Response if your APDU looks like the following: CLA INS p1 p2 p3 lentx xx xx xx xx xx lenrx Is this correct ? In the perfect world yes ! but, sadly, people sometimes doesn't follow correctly the ISO7816 or misunderstood it. I have cards (W4SC as an example) which send back a GET RESPONSE even for a APDU without data. This is really annoying as I have to modify my application to take care of this kind of cards. May be the highler level must be modify to hide this behaviour. But, from another point of view, it is interesting to know that you have a card with GET RESPONSE because sometimes those cards must run in terminals without management of the GET REPONSE apdus. -- Laurent Boulard Research Engineer Advanced Research SchlumbergerSema (Louveciennes) Tel: +33 (0)1 30 08 45 97 Fax: +33 (0)1 30 08 45 24 perl -e 'print(pack(h38,34f6e67627164757c6164796f6e63702b3d292))' *** Linux Smart Card Developers - M.U.S.C.L.E. (Movement for the Use of Smart Cards in a Linux Environment) http://www.linuxnet.com/smartcard/index.html ***
MUSCLE unsubscribe
unsubscribe *** Linux Smart Card Developers - M.U.S.C.L.E. (Movement for the Use of Smart Cards in a Linux Environment) http://www.linuxnet.com/smartcard/index.html ***
Re: MUSCLE Re: 61 XX
Mahlzeit On Wed, Aug 01, 2001 at 08:34:06AM -0700, David Corcoran wrote: Points well taken. It seems unanimous that the driver should take care of Get Response. I shall update the IFD Handler documentation to reflect this. Thank you so much for your suggestions. One question: How does the reader know which CLA byte to use? Mahlzeit endergone Zwiebeltuete *** Unix Smart Card Developers - M.U.S.C.L.E. (Movement for the Use of Smart Cards in a Linux Environment) http://www.linuxnet.com/ To unsubscribe send an email to [EMAIL PROTECTED] with unsubscribe sclinux ***
MUSCLE GPR400 ifd and T=0 vs T=1 from the driver perspective
I've got a mostly working GPR400 PCSC IFD. It's based on the PCMCIA driver found in the card-0.9.6.tar.gz file found on the MUSCLE website. By 'mostly working' I mean that I've used formaticc to send a few APDUs to a card and received the expected results. I'm having troubles understanding what the differences are between T=0 and T=1 from the IFD developer perspective. It's not apparent to me from looking through the other IFD source files. I have the Smart Card Developer's Kit and Java Card Technology for Smart Cards books already. I understand that T=0 and T=1 are two different protocols for communication between the reader and the card. It is not clear to me *how* they are different other than one is byte oriented and the other is block oriented. Can anyone offer any insight into the differences, if possible, from the IFD developer perspective? Can you point me to some documentation and/or code that will clear this up for me? Thanks in advance. -joe *** Unix Smart Card Developers - M.U.S.C.L.E. (Movement for the Use of Smart Cards in a Linux Environment) http://www.linuxnet.com/ To unsubscribe send an email to [EMAIL PROTECTED] with unsubscribe sclinux ***
