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
