Conversation
gregkh

Greg K-H

Dear lazyweb. One of my nitrokey 3 devices seems to have “stopped working” when attempting to access the key in it. Running the command line tools seems to say all is good (i.e. nitrocpy nk3 test says all is fine) but yet ssh seems to hate it with an error of:

ssh_sk_sign: fido_dev_get_assert: FIDO_ERR_NO_CREDENTIALS

and it never even attempts to let me “push the button”.

It’s running the latest firmware. Any hints on what to attempt/test to debug this or should I just give up on the thing?

My backup key is working just fine, so it’s not the USB kernel code on my system that is the issue for once :)

4
0
9
brauner@mastodon.social

Christian Brauner 🦊🐺

Reply to @gregkh

@gregkh do we still get new devices from them? I still have my first nitro key from years and years ago.

1
0
0
gregkh

Greg K-H

Reply to @brauner@mastodon.social
@brauner No idea, I just went and ordered a few more, and some solokeys as I really would like to just use USB C and not have a A->C converter to lug around.
1
0
1
totenlegionChris@metalhead.club

Chris damnified

Reply to @gregkh

@gregkh no experience so far with fido, but did you check the access rights of the magic node in /dev? Does the user who exec ssh has the creds to access the fido dev node?
Please ignore if senseless question.

1
0
0
brauner@mastodon.social

Christian Brauner 🦊🐺

Reply to @gregkh
Edited 22 days ago

@gregkh wait, they're still not offering a USB-C variant?

1
0
0
brauner@mastodon.social

Christian Brauner 🦊🐺

Reply to @brauner@mastodon.social

@gregkh Ah, well, the 3C NFC seems USB-C.

1
0
0
pink@norden.social

pink

Reply to @gregkh

@gregkh
Maybe @nitrokey can help?

0
0
0
gregkh

Greg K-H

Reply to @brauner@mastodon.social
@brauner Yeah, but they are out of stock :(
1
0
0
brauner@mastodon.social

Christian Brauner 🦊🐺

Reply to @gregkh

@gregkh ofc they are...

0
0
0
gregkh

Greg K-H

Reply to @totenlegionChris@metalhead.club
@totenlegionChris As the other key works, AND the command line tool test passes with the bad key, yes, the device nodes are correct.
0
0
1
nitrokey@nitrokey.com

Nitrokey

Reply to @gregkh

@gregkh Please reach out to our support team 🙂 https://www.nitrokey.com/contact

1
0
0
gregkh

Greg K-H

Reply to @nitrokey@nitrokey.com
@nitrokey Thanks, will do!
0
0
1
About social.kernel.org

Terms of service

  1. Please do not use this service in violation of the Linux Kernel Code of Conduct. Doing so will result in your account suspension with the referral of the matter to the CoC committee.

  2. "Repeating"/"boosting" someone else's status on this platform will be treated as endorsement and will fall under rule #1.

  3. You are encouraged to use this platform to promote your work on the Linux Kernel, but there is no restriction on permitted topics (with the exception of anything covered by #1 above).

  4. There is no requirement to post in English, but it should be considered the primary language of communication on this platform.

Privacy notice

The admins of this service have access to all posted statuses. They aren't looking, but if it's something they shouldn't know about, then you should not post it on this platform.

Please see the Linux Foundation Privacy Policy, which applies to this platform as well.

Getting your own account

If you would like an account on this instance, please check that the following applies to you:

  • You are listed in MAINTAINERS or CREDITS

  • OR: You have a kernel.org account or email address

  • OR: You have a long and established history of involvement with the Linux Kernel

If the above is true and you agree with the Terms of Service and Privacy Notice listed above, please use these instructions to request an account: