Hi! > > BTW, what is the status of SM in trunk. It used to be scheduled for > > 0.12.3. If there is clearity about how to integrate it, I could also > > provide a generic implementation of PACE (generic = "PACE done by OpenSC > > not by the reader"). > > > There is SM dedicated github branch > https://github.com/viktorTarasov/OpenSC/tree/secure-messaging > > > The main development is almost finished -- still pkcs#11 has to be redesigned > to meet the multi on-card application needs. > http://www.opensc-project.org/pipermail/opensc-devel/2011-November/017338.html > > > Two SM protocols are supported -- GP and CWA14890; > two types of SM usage -- 'apdu-transmit' and 'ACL'. > > > Development and tests where done with an external loadable SM module > (commited the 'local' version of SM module), > there is the possibility to implement (rather invitation to improve) static > card specific SM module. > # grep encode_apdu ./src/libopensc/*.[c,h] > > > GP & 'apdu-transmit' is tested with Oberthur AuthentIC 3.2, > CWA14890 & 'acl' tested with IAS/ECC card from different producers.
We discussed earlier that GP is a SM encoding for itself. Is CWA14890 (or an other implementation in the sm branch) conforming to ISO 7816-8? Greets, Frank.
pgpmDWWyH9Uy8.pgp
Description: PGP signature
_______________________________________________ opensc-devel mailing list opensc-devel@lists.opensc-project.org http://www.opensc-project.org/mailman/listinfo/opensc-devel
