> INS must not be an odd one (1 3 5 ...) due to ACK protocol at transport level.
> CLA Must no be any 6X or 9X, most of the time user app may use 00. ISO
> standards indicates partitions in CLA, with reserved, forbidden and free
> ranges.
> SW1 must be one of 6X or 9X
>
> Reading ISO 7816_3 and 7816_4 standards is strongly recommanded.
>
> 90 00 ;)
> CH
I do not think that INS byte is so constrained, none of both GemXpresso211 and
Sun's examples mention such parity.
The examples are running, and since the ack is INS (or !INS, i am just awaken ;-)
), why the transport protocol should work only with odd INS numbers ?
I agree with you while saying that SW1 should be 6X (problem) or 9X (normal), but
in the case of OCF use, it is possible to use SWs that are not compliant to ISO if
needed.
Standards are just contexts, often broken, as bluetooth example.
cheers,
Baz
--
Sébastien Jean (a.k.a. Baz)
PhD candidate
LIFL - Université des Sciences et Technologies de Lille,
Batiment M3, bureau 111, F-59655 Villeneuve d'Ascq Cedex
France
Tel : (+33/0) 320 336 132 , Fax: (+33/0) 320 436 566
mailto:[EMAIL PROTECTED] , http://www.lifl.fr/~jean
"if you are aware...you can succeed(Jean-Claude Van Damme)"
---
> 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.
