Hello, Le 21/04/2011 14:51, BLANC Gilles a écrit : > Hi, > > this is my first message, so first and foremost I want to tell you that I am > very pleased to develop in OpenSC.
welcome to club. > I am currently working on the Oberthur's Cosmo One card (V7.0.1-n) support, > for an important project. I have access to Oberthur ressources, and they are > ready to help. Basically, my wish is to contribute with Viktor Tarasov to the > IASECC support (my card is compliant). > > Sadly, I encounter a problem when I try to create or delete an object (or even > generate a key pair), whereas finding and reading objects seem to work > perfectly. It doesn't work at all because each time a bad "select" APDU refers > to a non existing file (always the same). > > Let's talk APDU ! :) > > Each time it fails and whatever the object is, I have something like: > > 99999999 APDU: 00 A4 04 00 10 A0 00 00 00 77 01 08 00 07 00 00 FE 00 00 01 00 > 00 > 00035159 SW: 90 00 > 00000163 APDU: 00 A4 09 04 04 50 15 49 46 00 > 00014831 SW: 6A 82 > > The second select (A4) fails, and it stops here (so basically, it only sends > two commands). I do not understand where the reference for this (wrong) EF > comes from. According to the source code, this path is directly given to the > concerned function (e.g. iasecc_delete_file) by opensc library core. How can > read work and delete fail ? Is there a wrong object reference in the driver > source code for my card ? Try to repeat your tests with the latest trunk . The profile of the oberthur's 'generic PKI' application was obsolete . Does your card has pre-allocated key-slots ? Creating of a new key-slots is not yet implemented (ported from the IAS/ECC dedicated branch). Kind wishes, Viktor. -- Viktor Tarasov <viktor.tara...@opentrust.com> _______________________________________________ opensc-devel mailing list opensc-devel@lists.opensc-project.org http://www.opensc-project.org/mailman/listinfo/opensc-devel
