I received my Nitrokey Start device today morning and since then, I’m not able to use it. I followed the instruction in the official documentation (link), but the system simply doesn’t recognise the key. I tried on 2 Mac OS devices, one of them running version 10.14, the other 10.15, none of them worked.
I installed gnupg and gnupg2 as well, hoping one of them may see the NKS:
gpg --version
gpg (GnuPG) 2.2.17
libgcrypt 1.8.5
The gpg --card-status reports the following:
gpg: selecting openpgp failed: Operation not supported by device
gpg: OpenPGP card not available: Operation not supported by device
I read here, among the topics (link) that I should compiled and install pcsc-tools (current version 1.5.4), but the compile process failed.
What else should or can I do?
Try ioreg | grep Nitrokey in the terminal while the Nitrokey is plugged in. If you don’t see a text, the Nitrokey is not recognized by macOS. You don’t need any driver for this as teh USB subsystem will use a generic USB driver.
Thank you for the suggestion. It seems the Mac (10.15) really doesn’t recognise the key. I successfully compiled and installed the pcsc-tool, running the pcsc_scan diesn’t show the Nitrokey while it’s plugged in, plus the ioreg also cannot find it:
Plug’n play reader name not supported. Using polling every 1000 ms.
Scanning present readers…
Waiting for the first reader…
peter@localhost:~/Downloads/pcsc-tools-1.5.4$ ioreg | grep Nitrokey
peter@localhost:~/Downloads/pcsc-tools-1.5.4$ ioreg | grep -i Nitrokey
peter@localhost:~/Downloads/pcsc-tools-1.5.4$
I got on a Windows 10 laptop, plugged in the Nitrokey and that machine also didn’t recognise the device. Nothing at all. No notification that something unknown is connected or a driver is missing.
Can be the device has a defect?
It looks so unfortunately. We do tests of each device after the production, but such devices are occurring from time to time.
Please contact shop@nitrokey.com (linking to this page) for further information.
Before that, a last chance test - I will run the same commands on my side to confirm, how the output should look like with the device inserted.