Your message dated Wed, 10 Sep 2025 00:11:33 -0400
with message-id <aMD6ddnrTXRdXCHl@colossus>
and subject line Re: Bug#768927: Use the vendor driver for PC/SC
has caused the Debian Bug report #768927,
regarding supports only PCSC (regression from squeeze)
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)


-- 
768927: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=768927
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
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



--- End Message ---
--- Begin Message ---
Version: 0.23.0

Given it's been a decade since OpenCT went away, I'm going to close this.

* Martin Paljak ([email protected]) wrote:
> http://acsccid.sourceforge.net/
> 
> OpenCT as a Linux only, unmaintained software interface should be
> discouraged and is hardly a sensible choice with modern and
> standards-compliant hardware (check the list of supported readers of
> libccid)
> 

-- 
Eric Dorland <[email protected]>
43CF 1228 F726 FD5B 474C  E962 C256 FBD5 0022 1E93

--- End Message ---

Reply via email to