Re: MUSCLE VerifyKey using OCF

2001-07-31 Thread Emiliano Ida'
Hi All, Does anybody here use Cyberflex Access cards with OCF? If so, could you help me with the doubt below? In the Cyberflex Access card we have the idea of identity such as AUT0, AUT1, etc. In OCF to verify a Card Holder we must use the sendVerifyCommand. Now what do I

RE: MUSCLE Is 61xx handled in your driver?

2001-07-31 Thread John Otaegui
Most readers wont handle this response code. Some POS terminals will. You should send the get response/data command to retrieve the data. John -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of Naomaru Itoi Sent: Monday, July 30, 2001 6:43 PM To:

Re: MUSCLE Is 61xx handled in your driver?

2001-07-31 Thread David Corcoran
Hello, Most of the drivers pass the 61 XX back to the application to handle. I think it is bad practice to handle this in the driver since it is a card specific ISO function. This should happen above the reader abstraction where the card abstraction layer occurs. BTW - has anyone done an OSI

Re: MUSCLE VerifyKey using OCF

2001-07-31 Thread Luciano da Silva Coelho
Hi Emiliano, Thanks by your tip. But, what I want to know is: The idea of Identities (AUT0, AUT1, etc) that exists en Cyberflex is also valid in the OCF context? Are there others cards that have the same concept the identities? For example, to download a Cardlet to my card I need

Re: MUSCLE Is 61xx handled in your driver?

2001-07-31 Thread Jim Rees
When a card returns 61.xx, it means that the card has xx byte to return to host. Does a smartcard reader driver handle this, usually? My Todos driver does. It seemed useful at the time. I would like to know whether this is correct or not. Most other reader drivers I have looked at do

Re: MUSCLE Is 61xx handled in your driver?

2001-07-31 Thread Carlos Prados
Hi, I completly agree with Andreas. Get Response is dependant on T=0 transport protocol and must not be handled at application level. This is at least what ISO 7816 says. Towitoko driver 2.0.X handles authomatically the Get Response when the command is Case 3 or Case 4. Also the issues

Re: MUSCLE Is 61xx handled in your driver?

2001-07-31 Thread Jim Rees
I agree that the application should not have to deal with this. But I don't think the driver should either. Anything that every driver must do in the same way really belongs at a higher level, in pc/sc. *** Linux Smart Card Developers

Re: MUSCLE Is 61xx handled in your driver?

2001-07-31 Thread David Corcoran
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 ? Dave *** Linux Smart Card Developers - M.U.S.C.L.E. (Movement for the Use of Smart Cards