Yubico Forum

Re: [RESOLVED] W10 - Yubikey 4 not detected by the CLI tools

2016-02-25T02:46:28+01:00

I have finally solved the issue: My laptop is provided with a smartcard reader that I have never cared about. I had to disable it and all finally works as expected.

It is not a problem to keep it disabled but would you know of a way to make GPG select the right device?

Thank you again for your support.

Statistics: Posted by pbreau — Thu Feb 25, 2016 2:46 am

Re: [RESOLVED] W10 - Yubikey 4 not detected by the CLI tools

2016-02-24T02:30:43+01:00

There are a few things you can try:

(1) Terminate the GnuPG private key daemon and GnuPG smartcard daemon processes in Task Manager

(2) Try the OpenPGP reset procedure (viewtopic.php?f=35&t=2193&p=8245&hilit=openpgp+applet+reset#p8245)

I've received the "not supported" message a couple of times in Windows, but terminating the GnuPG processes and trying again using resolves it for me.

Statistics: Posted by ChrisHalos — Wed Feb 24, 2016 2:30 am

Re: [RESOLVED] W10 - Yubikey 4 not detected by the CLI tools

2016-02-24T00:26:44+01:00

Thank you Chris for your support.

I have tried so far to find by myself. Here are constantly the outputs I get:
powershell_2016-02-22_02-03-11.png

I have successfully generated some RSA keys with the PIV manager...

Have missed something obvious?

Best regards

Statistics: Posted by pbreau — Wed Feb 24, 2016 12:26 am

Re: [RESOLVED] W10 - Yubikey 4 not detected by the CLI tools

2016-02-20T02:47:47+01:00

Do you have any screenshots of the issue with GPG4Win? Version number? Are you trying to run commands like "gpg --card-status", etc?

I'm using Windows 10 and GPG4Win version 2.3.0 (note - card is loaded with an authentication key for testing only)

Statistics: Posted by ChrisHalos — Sat Feb 20, 2016 2:47 am

Re: [Question] W10 - Yubikey 4 not detected by the CLI tools

2016-02-19T23:20:55+01:00

I have found the reason if my issue: The version 1.16.0 of the CLI tools were in the PATH. It works fine now that I really run the 1.17.3 version.

Now I have to investigate on why gpg4win detects no card...

Thank you for your help!

Statistics: Posted by pbreau — Fri Feb 19, 2016 11:20 pm

Re: [Question] W10 - Yubikey 4 not detected by the CLI tools

2016-02-19T17:55:57+01:00

Hello Chris

Thanks a lot for your answer.

I can see the Yubikey in Devices and Printers as you describe it:
yubi2.png

I have checked successfully with Neo Manager that the connection mode was OTP+U2F+CCID. I can confirm that OTP is enabled:
neoman_2016-02-19_17-48-29.png

And I run the command lines from an Administrator's Powershell Window.

If fact, I tried both, Administrator and non-Adminitrator, without success.
yubi3.png

I also detect no card with the last version of gpg4win.

Would I have a way to generate some log files?

Best regards

Statistics: Posted by pbreau — Fri Feb 19, 2016 5:55 pm

Re: [Question] W10 - Yubikey 4 not detected by the CLI tools

2016-02-19T17:17:37+01:00

How is the YubiKey 4 identified in Devices and Printers? It should look like this:

How about the YubiKey NEO Manager? You just need to make sure OTP mode isn't disabled, as this is required to use the Personalization Tool (both GUI and CLI). If no mode switches have occurred, the YubiKey NEO Manager should look like this:

If you confirm OTP is enabled, either through the YubiKey NEO Manager or Devices and Printers, you may need to run the Personalization Tool GUI as Administrator (or Command Prompt as Administrator, if you're using the CLI).

Statistics: Posted by ChrisHalos — Fri Feb 19, 2016 5:17 pm

[RESOLVED] W10 - Yubikey 4 not detected by the CLI tools

2016-02-19T23:21:56+01:00

Hello

My new Yubikey 4 has a firmware 4.2.7.

Under Windows 10, it is well detected with the GUI version 3.1.23 of the personalization tool (library version 1.7.2).

With the CLI personalization tools version 1.7.2 or 1.7.3, I only get a:
Yubikey core error: no yubikey present

May I have missed some prerequisite? How should I troubleshoot?

Thank you for your help

Statistics: Posted by pbreau — Fri Feb 19, 2016 8:30 am