Martin Paljak wrote: > Hello, > On Sep 25, 2010, at 11:19 PM, webmas...@opensc-project.org wrote: > > >> Revision: 4768 >> Author: viktor.tarasov >> Date: 2010-09-25 20:19:08 +0000 (Sat, 25 Sep 2010) >> >> Log Message: >> ----------- >> ias/ecc: simultaneous run of opensc tool that address different readers >> >> opensc-explorer and pkcs15-crypt >> > > Can you explain what is the requirement for this? Why does xxx-tool --reader > "Your Reader Name" not work? > > Other than that, the need to pass in a specific reader and bypass the reader > list detection needs a generalized approach. OpenSC.tokend could make use of > it, instead of filtering the readers itself and minidriver would need special > handling and fetch the card and context handles. But the overall impact would > still be the same: force pcsc_detect_readers do only discover a single > reader, based on context creation parameters. > In fact, that was the initial intention -- 'force pcsc reader to only discover a single reader'.
Actually in 'reader-pcsc', when getting the reader's list, the SCardConnect(SCARD_SHARE_DIRECT) is called for every reader. So, when one process holds the first reader, the second process cannot access the second reader -- it stopped on the first reader's mutex. I was looking to test the possible problems of multi OpenSC process, but finally it's revealed to be useless -- beyond the pcsc reader, 'multi OpenSC process' is not concerned by the 'multi OpenSC threads' problems. -- 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
