Hi!

> > Internally, the API should facilitate re-use by OpenSC components and
> > card drivers. Sorry, I have not had the time to learn about PACE more
> > than the generic overviews, nor how it fits into the
> > cards-and-readers-and-current-software-stack bigger picture. Given
> > that what you want to do can be done above PC/SC, extending the reader
> > callbacks structure with only a "control" function should be enough.
> > The rest should either fit into a card driver (if it makes no sense as
> > a generic function) or implemented/triggered by a layer different from
> > the card driver (like current pinpad code, inside reader-pcsc.c or in
> > some new file in src/libopensc)
> 
> As said, I added execute_pace to sc_reader_operations and implemented
> everything for the PC/SC reader driver. The npa-tool can be used to
> actually execute PACE on the reader. Next week I can test with Reiner
> SCT's readers. So far it works fine with the ccid-emulator. Source code
> is more or less derived from
> http://vsmartcard.sourceforge.net/
> and can be found here
> https://github.com/frankmorgner/OpenSC

Executing PACE is now also tested with Reiner SCT RFID standard and
Reiner SCT RFID komfort. Meaning that all known readers to be able to
perform PACE conforming to BSI TR-03119 or respectively PC/SC Pt. 10
amendment 1 can be used with my OpenSC branch.

Cheers, Frank.

Attachment: pgp64NlQaIg64.pgp
Description: PGP signature

_______________________________________________
opensc-devel mailing list
opensc-devel@lists.opensc-project.org
http://www.opensc-project.org/mailman/listinfo/opensc-devel

Reply via email to