Package: libccid Version: 1.4.34-1~solo2+1 Severity: wishlist X-Debbugs-Cc: none, Dave Love <dave.l...@manchester.ac.uk>
Various functions of the new free software/hardware Solo 2 security key don't work in Debian 11 because libccid doesn't support it. The same probably goes for the Nitrokey 3 when it's available as it shares basic firmware. It seems worth supporting them since they're free devices, either by backporting from unstable or patching the version in stable. I don't know which is the best solution (or whether patching for extra support is within policy), but I've tried both with success. I built 1.5 from unstable on buster and bullseye (lowering the debhelper version so it would also work on 10, and also Ubuntu 18.04 and 20.04). Installing it solves at least that part of problems with the solo2 cli. Then I tried the version from bullseye plus the /etc/libccid_Info.plist from 1.5, which works; I'll probably post it for Solo 2 users. As that worked I rebuilt the bullseye version with a patch for readers/supported_readers.txt to add Solo2 and Nitrokey entries, though I guess it could have all the additions from the 1.5 version. The results are under <https://build.opensuse.org/repositories/home:fx>. Obviously I can send a patch if that's helpful. -- System Information: Debian Release: 11.2 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.10.0-11-amd64 (SMP w/4 CPU threads) Kernel taint flags: TAINT_CPU_OUT_OF_SPEC, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages libccid depends on: ii libc6 2.31-13+deb11u2 ii libusb-1.0-0 2:1.0.24-3 libccid recommends no packages. Versions of packages libccid suggests: pn pcmciautils <none> -- no debconf information
