[opensc-devel] Unsupported card
I have JCop v2.3.1 and I notice that this kind of card is not supported on Opensc Project. I have loaded the CardEdge.cap and when I run pkcs15-init -C, it returns: "Using reader with a card: CASTLES EZ100PU 0 Couldn't bind to the card: Not supported" Is it possible to fix it if I do some changes in the source code of MCardApplet or I will need to buy a card of the http://www.opensc-project.org/opensc/wiki/SupportedHardware list ? -- View this message in context: http://old.nabble.com/Unsupported-card-tp33969324p33969324.html Sent from the OpenSC - Dev mailing list archive at Nabble.com. ___ 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 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] Driver develop
2012/6/6 helpcrypto helpcrypto > > I'm not developing dnie driver, only I'm working with the documentation > for > > explain the way to develop a driver and I think that this knowledge can > be > > interesting for the community. > > That will be great. > > In the past we considered making a driver for our "very old not > cryptographic either pkcs#15 card", and finally we did our own pkcs#11 > library. > I think your best bet will be asking jonsito directly. and please, > post somewhere any progress/doc you find along the way. > I found a wiki page[1] with a start point, but only form index wiki. I will submit the dnie example. > > Maybe others like martin, viktor or ludovic can help you with this. I > sorry i cant. > I agree. Thank you very much! [1] https://www.opensc-project.org/opensc/wiki/DeveloperInformation/NewCardDriver Alejandro Díaz Torres Área de Proyectos Emergya Consultoría Tfno: +34 954 51 75 77 Fax: +34 954 51 64 73www.emergya.es ___ opensc-devel mailing list opensc-devel@lists.opensc-project.org http://www.opensc-project.org/mailman/listinfo/opensc-devel
Re: [opensc-devel] Driver develop
> I'm not developing dnie driver, only I'm working with the documentation for > explain the way to develop a driver and I think that this knowledge can be > interesting for the community. That will be great. In the past we considered making a driver for our "very old not cryptographic either pkcs#15 card", and finally we did our own pkcs#11 library. I think your best bet will be asking jonsito directly. and please, post somewhere any progress/doc you find along the way. Maybe others like martin, viktor or ludovic can help you with this. I sorry i cant. ___ opensc-devel mailing list opensc-devel@lists.opensc-project.org http://www.opensc-project.org/mailman/listinfo/opensc-devel
