On Sun, Sep 26, 2010 at 09:17, Viktor TARASOV <viktor.tara...@opentrust.com> wrote: >> 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.
Is this on Windows? I remember testing for exclusive access but maybe only with pcsc-lite. If it does not work if the reader is in exclusive mode it is a bug in pcsc-driver that should not be fixed via tools. opensc-tool --reader should work as expected with whatever states the readers are in. _______________________________________________ opensc-devel mailing list opensc-devel@lists.opensc-project.org http://www.opensc-project.org/mailman/listinfo/opensc-devel
