Bug#1006614: libccid: support for Solo2 and Nitrokey 3

2022-03-01 Thread Dave Love
You wrote: 

> I can't fix or upgrade packages in Debian stable, unless that is a security 
> issue.
>
> What you can do instead is backport the libccid package from unstable
> to stable. That is what you did.
> This is also handled by the Debian backports project 
> https://backports.debian.org/

OK, thanks.  Sorry to bother you when I couldn't find info on the policy
on changes in stable; also I didn't know the backports site.  I should
fix being a Fedora maintainer and not a Debian one when I personally run
Debian.


Bug#1006614: libccid: support for Solo2 and Nitrokey 3

2022-02-28 Thread Ludovic Rousseau

Le 28/02/2022 à 18:25, Dave Love a écrit :

Package: libccid
Version: 1.4.34-1~solo2+1
Severity: wishlist
X-Debbugs-Cc: none, Dave Love 


Hello Dave,


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 .
Obviously I can send a patch if that's helpful.


I can't fix or upgrade packages in Debian stable, unless that is a security 
issue.

What you can do instead is backport the libccid package from unstable to 
stable. That is what you did.
This is also handled by the Debian backports project 
https://backports.debian.org/

Feel free to provide backported versions on your own web site if you want.

For the libccid package in Debian unstable, support of the Nitrokey 3 and 
SoloKeys Solo 2 is already included
https://ccid.apdu.fr/ccid/shouldwork.html#0x20A00x42B2
https://ccid.apdu.fr/ccid/shouldwork.html#0x12090xBEEE

So I have nothing to fix in Debian unstable.
I plan to close this bug report unless you think I can do something.

Bye

--
Dr. Ludovic Rousseau



Bug#1006614: libccid: support for Solo2 and Nitrokey 3

2022-02-28 Thread Dave Love
Package: libccid
Version: 1.4.34-1~solo2+1
Severity: wishlist
X-Debbugs-Cc: none, Dave Love 

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 .
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  

-- no debconf information