[opensc-devel] T-Buffer Question
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 FE. Next I send a read buffer... 80 52 00 00 02 01 d0 Retrieve the Tag Buffer. then 80 52 00 00 02 02 FF Retrieve FF bytes of the Value buffer. The tag buffer has the form Tag 1 (length 1 - 3 bytes) Tag 2 ( length 1- 3 - bytes) The value buffer is Value 1, Value 2, Value 3, The tags in the tag buffer are what I'm trying to figure out.. Thanks. ___ opensc-devel mailing list opensc-devel@lists.opensc-project.org http://www.opensc-project.org/mailman/listinfo/opensc-devel
Re: [opensc-devel] T-Buffer Question
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 about the US related standards, shouldn't PIV be the current game ? Martin ___ opensc-devel mailing list opensc-devel@lists.opensc-project.org http://www.opensc-project.org/mailman/listinfo/opensc-devel
Re: [opensc-devel] T-Buffer Question
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. What is the ATR? I might be a dual PIV/CAC card. OpenSC can use PIV. (Windows 7 also has a built in driver for PIV, and if you insert your card, you can see the certificates using the Control panel- Internet Options-Content-Certificates) The commands I'm sending to the card are... Select the object. 00 A4 04 00 07 a0 00 00 00 79 02 FE. This AID looks like it is a CAC card. (Appendix D1 in 6887) and I think the above should be : 00 A4 04 00 05 a0 00 00 00 79 Then select the file with the certificate container: 00 FE 00 A4 01 00 02 02 FE (Not sure if this is correct. I think you can then read the T-buffer and V-Buffers. Next I send a read buffer... 80 52 00 00 02 01 d0 Retrieve the Tag Buffer. Since you did not select another file, I think you were reading the directory as a file. then 80 52 00 00 02 02 FF Retrieve FF bytes of the Value buffer. The T-Buffer would most likely fit in 256 bytes, but the certificates in the V-buffer will not. You may have to read this in chunks using the P1 P2 to give the offset of the data The tag buffer has the form Tag 1 (length 1 - 3 bytes) Tag 2 ( length 1- 3 - bytes) The value buffer is Value 1, Value 2, Value 3, The tags in the tag buffer are what I'm trying to figure out.. Thanks. ___ opensc-devel mailing list opensc-devel@lists.opensc-project.org http://www.opensc-project.org/mailman/listinfo/opensc-devel -- Douglas E. Engert deeng...@anl.gov Argonne National Laboratory 9700 South Cass Avenue Argonne, Illinois 60439 (630) 252-5444 ___ opensc-devel mailing list opensc-devel@lists.opensc-project.org http://www.opensc-project.org/mailman/listinfo/opensc-devel
[opensc-devel] T-Buffer Question
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 67 DD 06 00 15 01 DC 0B 06 00 15 01 66 FF 45 04 00 FF 20 02 C8 25 00 FF 20 02 DC 05 00 00 90 00 FE 05 07 00 15 01 72 27 07 00 15 01 69 39 07 00 15 01 68 FF 01 01 08 00 15 01 72 27 08 00 15 01 69 3A 08 00 15 01 68 FF 01 01 07 00 15 01 67 ED 07 00 15 01 DC 0B 07 00 15 01 66 FF 60 04 08 00 15 01 67 ED 08 00 15 01 DC 0B 08 00 15 01 66 FF I can't find anything that helps me identify the tags. If any one can help it would be greatly appreciated. Jon ___ opensc-devel mailing list opensc-devel@lists.opensc-project.org http://www.opensc-project.org/mailman/listinfo/opensc-devel
Re: [opensc-devel] T-Buffer Question
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 send to the card and how? What was the length returned? Are you writing the APDU commands? What is a T-Buffer? 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 67 DD 06 00 15 01 DC 0B 06 00 15 01 66 FF 45 04 00 FF 20 02 C8 25 00 FF 20 02 DC 05 00 00 90 00 FE 05 07 00 15 01 72 27 07 00 15 01 69 39 07 00 15 01 68 FF 01 01 08 00 15 01 72 27 08 00 15 01 69 3A 08 00 15 01 68 FF 01 01 07 00 15 01 67 ED 07 00 15 01 DC 0B 07 00 15 01 66 FF 60 04 08 00 15 01 67 ED 08 00 15 01 DC 0B 08 00 15 01 66 FF A certificate would be much longer, and would most likely be in ASN1, maybe gzip-ed. The above does not look like any of these. The vendor may also have their own profile with lots of data elements including certificates in one big file. The above maybe just the first part of it. I can't find anything that helps me identify the tags. If any one can help it would be greatly appreciated. Jon ___ opensc-devel mailing list opensc-devel@lists.opensc-project.org http://www.opensc-project.org/mailman/listinfo/opensc-devel -- Douglas E. Engert deeng...@anl.gov Argonne National Laboratory 9700 South Cass Avenue Argonne, Illinois 60439 (630) 252-5444 ___ opensc-devel mailing list opensc-devel@lists.opensc-project.org http://www.opensc-project.org/mailman/listinfo/opensc-devel
