[opensc-devel] T-Buffer Question

2012-06-07 Thread Jon
The T-buffer is the Tag Buffer. I think the card conforms to Government Smart Card Interoperability Specification. (GSC-IS) as defined in NIST 6887. In particular the card is a military Alt-Token. The commands I'm sending to the card are... Select the object. 00 A4 04 00 07 a0 00 00 00 79 02

Re: [opensc-devel] T-Buffer Question

2012-06-07 Thread Martin Paljak
Hello, On Thu, Jun 7, 2012 at 3:46 PM, Jon jonmark...@gmail.com wrote: The T-buffer is the Tag Buffer.  I think the card conforms to Government Smart Card Interoperability Specification. (GSC-IS) as defined in NIST 6887.  In particular the card is a military Alt-Token. Without knowing much

Re: [opensc-devel] T-Buffer Question

2012-06-07 Thread Douglas E. Engert
On 6/7/2012 7:46 AM, Jon wrote: The T-buffer is the Tag Buffer. I think the card conforms to Government Smart Card Interoperability Specification. (GSC-IS) as defined in NIST 6887. In particular the card is a military Alt-Token. That standard predates the PIV standards, NIST 800-73-3.

[opensc-devel] questions on {ERASE,WRITE,UPDATE} BINARY commands

2012-06-07 Thread Peter Marschall
Hi, I have questions on the {ERASE,WRITE,UPDATE} BINARY commands for which I do not find the answer in the spec (ISO-7816-4). Here they are: * What's the exact difference between WRITE BINARY UPDATE BINARY? My understanding of the spec is that WRITE BINARY can extend a file's size, while

Re: [opensc-devel] questions on {ERASE, WRITE, UPDATE} BINARY commands

2012-06-07 Thread Martin Paljak
Hello, On Thu, Jun 7, 2012 at 10:24 PM, Peter Marschall pe...@adpm.de wrote: Here they are: * What's the exact difference between WRITE BINARY UPDATE BINARY?  My understanding of the spec is that WRITE BINARY can extend a file's size,  while UPDATE BINARY can only update data elements that

Re: [opensc-devel] questions on {ERASE, WRITE, UPDATE} BINARY commands

2012-06-07 Thread Martin Paljak
On Thu, Jun 7, 2012 at 10:35 PM, Martin Paljak mar...@martinpaljak.net wrote: Hello, On Thu, Jun 7, 2012 at 10:24 PM, Peter Marschall pe...@adpm.de wrote: Here they are: * What's the exact difference between WRITE BINARY UPDATE BINARY?  My understanding of the spec is that WRITE BINARY can

Re: [opensc-devel] questions on {ERASE, WRITE, UPDATE} BINARY commands

2012-06-07 Thread Peter Marschall
Hi Martin, thanks for the quick reply. On Thursday, 7. June 2012, Martin Paljak wrote: On Thu, Jun 7, 2012 at 10:24 PM, Peter Marschall pe...@adpm.de wrote: Here they are: * What's the exact difference between WRITE BINARY UPDATE BINARY? My understanding of the spec is that WRITE BINARY

Re: [opensc-devel] questions on {ERASE, WRITE, UPDATE} BINARY commands

2012-06-07 Thread Martin Paljak
On Thu, Jun 7, 2012 at 10:44 PM, Peter Marschall pe...@adpm.de wrote: Why the question? If there would be a card that implements both, I think you would want to use UPDATE, at least in the context of OpenSC, unless it is *not* supported and WRITE is supported. What exactly is the context?

Re: [opensc-devel] questions on {ERASE, WRITE, UPDATE} BINARY commands

2012-06-07 Thread Peter Marschall
Hi, thanks for the quick reply/correction. On Thursday, 7. June 2012, Martin Paljak wrote: On Thu, Jun 7, 2012 at 10:35 PM, Martin Paljak mar...@martinpaljak.net wrote: Hello, On Thu, Jun 7, 2012 at 10:24 PM, Peter Marschall pe...@adpm.de wrote: Here they are: * What's the exact