Whoops, I stand corrected the ISO-spec clearly says that case 2 and 4 APDU's must
be handled in 2
goes (who the !#@!! thougth up that stupid idea), I got mislead for a while,
because the card that I have (claiming to do T=0) handles these cases like a
breeze.
Apologies
S�ren
S�ren Hilmer wrote:
> You say it is not possible, I say I have done it.
> You see the program on the card can read that Le byte from the command, and
> then it knows
> how many bytes to return, voila.
> -- S�ren
>
> [EMAIL PROTECTED] wrote:
>
> > With the ISO 7816-3 T=0 protocol, you CANNOT send directly APDU case 4
> > which is sending some data and receiving back some data (CLA INS P1 P2 Lc
> > Data1 Le and the answer is Data2 SW1 SW2) with only ONE command. This is
> > not possible.
> >
> > Christophe Colas
> > Bull Smart Cards & Terminals
> > Phone: 33 1 39 66 42 29
> > Fax: 33 1 39 66 43 51
> > mailto:[EMAIL PROTECTED]
> > Visit us at http://www.cp8.bull.net.
> >
> > S�ren Hilmer <[EMAIL PROTECTED]> sur 04/16/99 12:40:24 PM
> >
> > Veuillez r�pondre � [EMAIL PROTECTED]
> >
> > Pour : [EMAIL PROTECTED]
> > cc : [EMAIL PROTECTED] (ccc : Christophe Colas/FR/BULL)
> > Objet : Re: R�f. : [OCF-tech] Re: [OCF] Handling of T=0 Case4 etc. in
> > Terminals or Services ?
> >
> > Okay, I see the point about making the CardTerminals independant of how
> > the card handles the case 4 APDU, but it seams that everybody asumes that
> > the T=0 protocol needs to split APDU's into this scheme of first sending
> > the
> > command and then retrieving a 61xx response and then sending a getResponse
> > APDU, that is offcourse NOT the case some cards can perfectly well handle
> > case 4 APDU's in one go using the T=0 protocol.
> >
> > The most important thing to do is once and for all to make a decision about
> > the
> > correct CardTerminal behaviour, and even though it means some extra work
> > for
> > myself, as I have implemented a CardTerminal. I thing that hiding the
> > 61xx/6Cxx
> > stuff from the CardService is the most sensible.
> >
> > -- S�ren
> >
> > Visit the OpenCard Framework's WWW site at http://www.opencard.org/ for
> > access to documentation, code, presentations, and OCF announcements.
> > ---------------------------------------------------------------------------
> > --
> > To unsubscribe from the OCF Mailing list, send a mail to
> > "[EMAIL PROTECTED]" with the word "unsubscribe" in the BODY of
> > the
> > message.
>
> Visit the OpenCard Framework's WWW site at http://www.opencard.org/ for
> access to documentation, code, presentations, and OCF announcements.
> -----------------------------------------------------------------------------
> To unsubscribe from the OCF Mailing list, send a mail to
> "[EMAIL PROTECTED]" with the word "unsubscribe" in the BODY of the
> message.
Visit the OpenCard Framework's WWW site at http://www.opencard.org/ for
access to documentation, code, presentations, and OCF announcements.
-----------------------------------------------------------------------------
To unsubscribe from the OCF Mailing list, send a mail to
"[EMAIL PROTECTED]" with the word "unsubscribe" in the BODY of the
message.
