Am Samstag 10 April 2010 15:45:13 schrieb Ludovic Rousseau: > > and I can't list the readers using the PCSC interface. > > Is there a way to configure pcsc to use openct ? > > You have to configure OpenCT to be used by pcsc-lite. But I have no > idea how to do that. You should as on the opensc-user mailing list [1] > (in copy).
openct has an ifdhandler for pcsc-lite, that accepts calls from pcscd and translates them into a call for the openct middleware. but it should only be used with applications that use pcsc only. for opensc it is best to use opensc->openct directly. also the code is very old, hasn't been tested much even then. and since then pcsc-lite has evolved and improved a lot, especially in the usb section. in the same time openct hasn't been changed, not even seen much maintenance, so no idea if that code still works. I think it was more of a "proof of concept" and "works for me" but not much used. > Another idea is to disable the CCID driver in OpenCT. I don't know if > it is possible. edit udev rules and openct.conf and remove the reference that matches your driver (e.g. the general rule for the interface type, or the product/vendor matches). then openct won't know about that reader. however I'm not sure about the generic match for the ccid interface type - maybe that one isn't configureable but build in :( still if you start pcscd first, then pcscd+ccid should always win. openct has a one second sleep to allow pcscd+ccid precendece. it will log one or two lines with a warning, but not cause any issues or interfere with pcscd+ccid. > Maybe OpenCT should support (by default) only the CCID readers not > supported by my CCID driver to avoid collision? Does OpenCT support > CCID reader not supported by my CCID driver? If yes which ones? I don't think anyone has a collection of readers like you have, so this is hard to compare. openct with ccid driver is still useful, if you want only one subsystem. for many old tokens there is no pcsc-lite driver, and writing one would be a lot of work, unless we can somehow copy or integrate all the infrastructure that your ccid driver contains. for example copying t=1 protocoll and maintaining many copies would be a waste of time and energy - maybe the original reason for "usbtoken" and later "openct". same with all the work for usb scanning, hotplugging, supporting several tokens (in several threads, several processes or with appropriate multiplexing technique (not sure what pcsc-lite uses exactly these days, I guess threads)). all that infrastructure would be the real work for writing a driver. for example "aladdin etoken" only needs that, a few IDs to identify it, and 4 lines or so that take the frame from t=1 and pass it via usb control transfer to the kernel, and back. add generic open/close/reset and the driver is done. same with several other drivers. if we could port such drivers, openct could become obsolete and the we could suggest to migrate completely to pcsc-lite plus drivers. Regards, Andreas _______________________________________________ Muscle mailing list [email protected] http://lists.drizzle.com/mailman/listinfo/muscle
