On 03.05.2007, at 0:00, Micha Lenk wrote: > Please have a look at libchipcard[1]. In fact its [2]major design goal > was to abstract the details of reader access and communication and to > provide a unified and somewhat highlevel access on a chipcard - > independent of the actual reader type. > > 1. http://www.libchipcard.de/ > 2. http://www.libchipcard.de/files/libchipcard3.pdf
the PDF reads: One of the most important differences between pcsclite and Libchipcard3 is that Libchipcard3 only accesses the readers when a Libchipcard3-client uses them while pcsclite always grabs and locks all readers it can get – it never releases unused readers. This makes it impossible for non-pcsclite applications to access a reader while the PC/SC daemon is running. My question: Do you really want to talk to a reader ? Can't you communicate with the reader via pcsc (SCardControl should do that)? Why not? > Unfortunately the public presentation (i.e. the homepage) isn't very > eye-candied and the development is mainly done by two peoples only: > Martin Preuss and Christian Stimming. But PR is an area where probably > any help is appreciated. I think it is because of a different reason: libchipcard seems to be targeting German banking cards (and related secure readers) whereas opensc is for card initalization as well as read only cards (like eID cards) Different areas (cards), same problems (readers). m. -- Martin Paljak _______________________________________________ opensc-devel mailing list opensc-devel@lists.opensc-project.org http://www.opensc-project.org/mailman/listinfo/opensc-devel
