Arch Linux User Repository

My card reader had an ID that was missing in the udev rule. Device name: Reiner SCT Kartensysteme GmbH cyberJack RFID basis contactless smartcard reader

This line needs to be added to the udev rule:

ATTR{idVendor}=="0c4b", ATTR{idProduct}=="9102", MODE="660", GROUP="pcscd"

Thanks :)

Given that the driver does not work without the udev rules, and REINER SCT support is not willing to fix this issue for the time being, I have updated this packages so that it installs the Debian udev rules file.

@Eike Yes, Ludovic clearly stated to me that he made the requirement for the pcscd group for pcscd version 2.4.0 early enough, and that the necessary rule files have to be provided by the producer of the readers (either directly or by the package that provide their drivers, i.e. this one). Furthermore, since the readers are not ccid, a separate file (the one below) is needed. There was a problem with upper and lower case characters in the ccid rule files anyway, which most probably has not been fixed yet, either.

In Debian sid / forky

root@debian-testing:~# dpkg -L libifd-cyberjack6 | grep rules
/usr/lib/udev/rules.d
/usr/lib/udev/rules.d/60-libifd-cyberjack6.rules

I.e. the rule file is installed by the equivalent of this package.

I've talked to Ludovic Rousseau (pcsclite / ccid) that the change of pcscd to the group of the same name seems to have broken my arch linux setup and asked to add the Reiner SCT reader to the list of CCID readers (https://salsa.debian.org/rousseau/CCID/-/tree/master/readers?ref_type=heads)

He let me know that the reader is not declared CCID compliant (the same applies for https://ccid.apdu.fr/ccid/disabled.html#0x0C4B0x0500).

Not sure if this information has any value as I'm also a bit lost with the entire situation.

The thing was reported upstream (due to SEGV in pcscd at several places now over the duration of 4 weeks, because nobody wants to take responsibility for this). Reiner refuses to provide the file in their SP17.tar.bz2 file as long as the version of the pcscd in their supported main distributions is not being upgraded to 2.4.0. They do not consider Arch a main or supported distro. Once their distros are changed to 2.4.0, their package will provide the file (they say).

Standard debian 13 has pcscd 2.3.*, where the rule file is not needed. Or to be precise, where it needs not be absent.

Arch has pcscd 2.4.0 ! and the pcscd crashes with Reiner readers, if the file is not present.

That's why you have to look in the Debian packages for Debian sid or Debian forky (which have pcscd 2.4.0). The rule file is installed there.

The main developer at Reiner told me to speak to the maintainer of this package to provide the rules, just like Debian does for sid and forky.

Updated to version 3.99.5_SP17.

Regarding the udev rules: This should be reported upstream. The latest debian package does not contain those rules, either.

# If not adding the device, go away
ACTION!="add", GOTO="cyberjack_rules_end"
SUBSYSTEM!="usb", GOTO="cyberjack_rules_end"
ENV{DEVTYPE}!="usb_device", GOTO="cyberjack_rules_end"

ATTR{idVendor}=="0c4b", ATTR{idProduct}=="0100", MODE="660", GROUP="pcscd"
ATTR{idVendor}=="0c4b", ATTR{idProduct}=="0300", MODE="660", GROUP="pcscd"
ATTR{idVendor}=="0c4b", ATTR{idProduct}=="0400", MODE="660", GROUP="pcscd"
ATTR{idVendor}=="0c4b", ATTR{idProduct}=="0401", MODE="660", GROUP="pcscd"
ATTR{idVendor}=="0c4b", ATTR{idProduct}=="0412", MODE="660", GROUP="pcscd"
ATTR{idVendor}=="0c4b", ATTR{idProduct}=="0485", MODE="660", GROUP="pcscd"
ATTR{idVendor}=="0c4b", ATTR{idProduct}=="0500", MODE="660", GROUP="pcscd"
ATTR{idVendor}=="0c4b", ATTR{idProduct}=="0501", MODE="660", GROUP="pcscd"
ATTR{idVendor}=="0c4b", ATTR{idProduct}=="0502", MODE="660", GROUP="pcscd"
ATTR{idVendor}=="0c4b", ATTR{idProduct}=="0503", MODE="660", GROUP="pcscd"
ATTR{idVendor}=="0c4b", ATTR{idProduct}=="0504", MODE="660", GROUP="pcscd"
ATTR{idVendor}=="0c4b", ATTR{idProduct}=="0505", MODE="660", GROUP="pcscd"
ATTR{idVendor}=="0c4b", ATTR{idProduct}=="0506", MODE="660", GROUP="pcscd"
ATTR{idVendor}=="0c4b", ATTR{idProduct}=="0507", MODE="660", GROUP="pcscd"
ATTR{idVendor}=="0c4b", ATTR{idProduct}=="0525", MODE="660", GROUP="pcscd"
ATTR{idVendor}=="0c4b", ATTR{idProduct}=="0580", MODE="660", GROUP="pcscd"
ATTR{idVendor}=="0c4b", ATTR{idProduct}=="2000", MODE="660", GROUP="pcscd"
ATTR{idVendor}=="0c4b", ATTR{idProduct}=="0551", MODE="660", GROUP="pcscd"
ATTR{idVendor}=="0c4b", ATTR{idProduct}=="2002", MODE="660", GROUP="pcscd"

# All done
LABEL="cyberjack_rules_end"

Version SP17 is available now on the Reiner SCT support page.

Furthermore (just like in the Debian "reference" package), the udev rule file

/lib/udev/rules.d/60-libifd-cyberjack6.rules

should be installed, because otherwise the pcscd will continue to crash.

I will provide the content of 60-libifd-cyberjack6.rules separately.

Somewhen witin the past few weeks the AusweisApp2 stopped recognizing the cyberJack RFID komfort. Not sure if it affects other readers or users. My solution was to add a udev rule for my device:

SUBSYSTEM=="usb", ENV{DEVTYPE}=="usb_device", ATTR{idVendor}=="0c4b", ATTR{idProduct}=="0501", GROUP="pcscd"