Yes, GET DATA and PUT DATA in 7816-4 are incompletely defined. But so is the ref in that doc: I hope they used the latest: 7816-4:2005 (I know: always use the latest, but it pays to be pedantic).

Peter

Peter Williams wrote:

http://csrc.nist.gov/publications/nistir/ir7284/nistir-7284.pdf page 15.

Context: strong names, functions acl, per named object, namespaces

Went looking for some ambiguous and open data semantics, found in PUT-DATA. For what benefit/purpose, one might ask. Pg 15 doesnt really say very much about the underlying issue motivating the choice of mechanism.


From: "Scott Guthery" <[EMAIL PROTECTED]>
Reply-To: MUSCLE  <[email protected]>
To: "MUSCLE" <[email protected]>
CC: Peter Tomlinson <[EMAIL PROTECTED]>
Subject: RE: [Muscle] Re: Muscle Digest, Vol 25, Issue 21
Date: Tue, 21 Mar 2006 17:23:26 -0500

Just as a note in passing, the ISO/IEC 7816-4 GET DATA and PUT DATA
commands for reading and writing TLV data objects do NOT require a file
system.  The PIV card application is an example of this approach.

Cheers, Scott

-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Shawn Willden
Sent: Tuesday, March 21, 2006 5:16 PM
To: [email protected]
Cc: Peter Tomlinson
Subject: Re: [Muscle] Re: Muscle Digest, Vol 25, Issue 21

On Tuesday 21 March 2006 14:38, Peter Tomlinson wrote:
> There is provision in ISO/IEC 7816 for a card to identify itself in
> several ways, but the majority of card suppliers either do not encode
> the necessary information or encode it inadequately - or it gets
changed
> to something else during personalisation. Typically the ATR may be the
> starting point, or there may be extended information in an ATR File -
> and there may also be a DIR file giving a directory of card
> applications. (EMV of course has its own method of application
selection.)
>
> GlobalPlatform also has provision for ID information, using data
objects
> stored at the MF level.

Both of which require a 7816 file system (or enough of one, anyway).  As
more
and more Javacards are deployed, fewer cards have a file system :-/

> We are still in the mindset that thinks bytes are extremely expensive,
> and we need to get out of that and do the job properly.

What's funny about that is I've seen one system that fires literally
dozens of
APDUs at a card in an attempt to determine what is on it... it would
take far
fewer bytes to query a file structure.

    Shawn.
_______________________________________________
Muscle mailing list
[email protected]
http://lists.drizzle.com/mailman/listinfo/muscle



_______________________________________________
Muscle mailing list
[email protected]
http://lists.drizzle.com/mailman/listinfo/muscle



_______________________________________________
Muscle mailing list
[email protected]
http://lists.drizzle.com/mailman/listinfo/muscle


_______________________________________________
Muscle mailing list
[email protected]
http://lists.drizzle.com/mailman/listinfo/muscle

Reply via email to