Hello, my organization have recently bought some nitrokey devices (nitrokey 2 pro ones). I started to experement with it and decided to reset it with a hex command like described in the FAQ. So I applied this file to the gpg agent [1]. Now my gpg smartcard does not work.
gpg --card-status
returns
gpg: selecting openpgp failed: No such device
gpg: OpenPGP card not available: No such device
[1] - https://www.nitrokey.com/sites/default/files/nitrokey-reset.txt
dmesg still detects it like:[ 1116.008178] usb 2-1.5: USB disconnect, device number 5
[ 1151.251659] usb 2-1.5: new full-speed USB device number 6 using ehci-pci
[ 1151.331386] usb 2-1.5: New USB device found, idVendor=20a0, idProduct=4108, bcdDevice= 1.01
[ 1151.331391] usb 2-1.5: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 1151.331395] usb 2-1.5: Product: Nitrokey Pro
[ 1151.331399] usb 2-1.5: Manufacturer: Nitrokey
nitrokey-app reset says “wrong admin pin” though (I tried the default one after a hex file application).
scdaemon reports:
scdaemon[18665] DBG: chan_7 → ERR 100696144 No such device
gpg version I use is 2.2.15 (Linux)
Any thougs?
Did you try restart all relevant services like scdaemon etc. (or just reboot) and unplug and plugging in the device again? Do you have conflicting applications like OpenSC installed as well? If so please try to remove it for now, as the very same message can appear because of blocking by another application.
In general, the device should be fine. You may start the Nitrokey App. Does the App recognize the device correctly?
hello!
pcscd daemon stopped so this is not the case I use this.
yes, nitrokey can be recognized in the nitrokey app (I am running this as nitrokey-app --admin
)
but when I try to change admin/user my current pins reported as invalid ones. (I tried both, pins I remember to set and default ones).
ok, we disasambled this by now and figured out that was stm32 chip death (at least part of it)
Hi!
Could you describe, how have you found the cause?
I am not convinced the cause here is STM32 chip being broken, as long as it registers in the system (confirmed by the lsusb
). I suspect either some misconfiguration on the hosting PC (however device was used successfully there before), or smart card issue.
If you would like to further pursue this issue, could you answer please:
- Are other devices working for you on the same PC?
- What Linux distribution do you use?
- Is red LED flashing constantly after device insertion? (it should not, unless there is a smart card communication issue)
- Could you check in the Nitrokey App, what is the firmware version of the affected device? (please see About window)
- Could you repeat the tests using
gpg2
, instead of gpg
? The latter is sometimes added for compatibility reasons, and it might be old GnuPG, which has no access to the device.