Package: opensc Version: 0.12.2-3 Severity: important opensc, until v0.12, had a feature where you could pick at runtime which reader driver you want to use (pcsc, openct, ctapi). The configuration runtime option was called "reader_drivers" and it was a list of drivers and their order.
In v0.12.0 upstream made this into a build-time option. NEWS say: * OpenSC uses a single reader driver, specified at compile time. There was an upstream bug report in favor of doing that: http://www.opensc-project.org/opensc/ticket/216 in which they mentioned Debian several times and someone even provided unofficial packages. Apparently their plan all along was that distributions (Debian included) should build multiple variants of libopensc, one for each driver, and ship multiple conflicting library packages, for users to pick (crazy, I know). However, this obviously didn't happen in Debian -- but the runtime to build-time "conversion" patch was not disabled either. This means that the current Debian packages only work with PCSC and have no way of using OpenCT (or the less popular CT-API) instead. My Aladdin eToken doesn't work with PCSC ("Generic read error" or something) and it worked fine with squeeze & OpenCT, so I consider this a regression (hence marking it as important). I guess others will be at the same position as mine. Regards, Faidon -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
