On Sat, 09 Nov 2024 23:25:00 +0100,
Rubén Llorente <port...@use.startmail.com> wrote:
>
> Most likely you gave rw permissions against the wrong uhid.
>
> When I plug my Nitrokey Storage 2 I get a line such as this in dmesg:
>
> uhid1 at uhidev3: input=64, output=64, feature=64
>
> Quick and dirty way to check this is to give rw permissions against all
> the /dev/uhid* devices.
>
> Also, important, due to a bug in the libnitrokey library, if you use
> your Nitrokey for GPG/smartcard related stuff, you won't be able to
> perform libnitrokey operations afterwards. This is: if you sign an
> OpenPGP message then you will need to kill the gpg-agent before you can
> do "nitrocli list".
>
Without giving enough permission list command returns instantly:
No Nitrokey device connected
When I run it as root, it had the same behaviour with blocking.
BTW I see the key via gpg --card-status. So, something works.
I've tried to stop pcscd and kill gpg-agent, it doesn't help.
and when I plug I do have lines:
uhidev0 at uhub0 port 2 configuration 1 interface 1 "Nitrokey Nitrokey 3"
rev 2.10/1.07 addr 2
uhidev0: iclass 3/0
fido0 at uhidev0: input=64, output=64, feature=0
ugen0 at uhub0 port 2 configuration 1 "Nitrokey Nitrokey 3" rev 2.10/1.07
addr 2
which is almost the same that I do have when replace it into YubiKey:
uhidev0 at uhub0 port 2 configuration 1 interface 0 "Yubico YubiKey
FIDO+CCID" rev 2.00/5.10 addr 2
uhidev0: iclass 3/0
fido0 at uhidev0: input=64, output=64, feature=0
ugen0 at uhub0 port 2 configuration 1 "Yubico YubiKey FIDO+CCID" rev
2.00/5.10 addr 2
and this Nitrokey seens by system as:
addr 02: 20a0:42b2 Nitrokey, Nitrokey 3
full speed, power 100 mA, config 1, rev 1.07
driver: uhidev0
driver: ugen0
--
wbr, Kirill
