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
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
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.
I'm writing code to read the certificates on a Cyberflex Access 64K V2c
that has to be compiled with Visual Studio 6. When I get the T-Buffer the
data looks like the following (minus) the two length bytes.
06 00 15 01 72 27 00 00 80 00 FE 02 06 00 15 01 69 3F 06 00 15 01 68 FF 01
01 06 00 15 01
On 6/6/2012 7:35 AM, Jon wrote:
I'm writing code to read the certificates on a Cyberflex Access 64K V2c that
has to be compiled with Visual Studio 6. When I get the T-Buffer the data
looks like the following (minus) the two length
bytes.
Can you be more specific?
What command did you
