Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

USB Yubikey smartcard support #2568

Closed
Sekanato opened this issue Oct 17, 2017 · 11 comments
Closed

USB Yubikey smartcard support #2568

Sekanato opened this issue Oct 17, 2017 · 11 comments

Comments

@Sekanato
Copy link

Sekanato commented Oct 17, 2017

  • I'm running:
    Microsoft Windows [Version 10.0.16299.15]

  • In fresh Ubuntu instance with pcscd scdaemon and supplement libraries installed I'm getting:

user@machine:~$ gpg -vvv --card-status
gpg: using character set `utf-8'
gpg: pcsc_establish_context failed: no service (0x8010001d)
gpg: card reader not available
gpg: OpenPGP card not available: general error
  • Should be like:
user@machine:~$ gpg --card-status
Reader ...........: Yubico Yubikey 4 OTP U2F CCID 0
Application ID ...: D*************************
Version ..........: 2.1
Manufacturer .....: Yubico
Serial number ....: ****************
Name of cardholder: John Doe
Language prefs ...: en
Sex ..............: male
URL of public key : http://example.com/key.asc
Login data .......: john_doe
Signature PIN ....: forced
Key attributes ...: rsa4096 rsa4096 rsa4096
Max. PIN lengths .: 1
27 127 127
PIN retry counter : 3 0 3
Signature counter : 999
Signature key ....: ***
      created ....: 1917-08-06 12:00:00
Encryption key....: ***
      created ....: 1917-08-06 12:00:00
Authentication key: ***
      created ....: 1917-08-06 12:00:00
General key info..: sub  rsa4096/*** 1917-08-06 John Doe <[email protected]>
sec#  rsa4096/***  created: 1917-08-06  expires: never
ssb>  rsa4096/***  created: 1917-08-06  expires: 1938-08-06
                                card-no: *** ****
ssb>  rsa4096/***  created: 1917-08-06  expires: 1938-08-06
                                card-no: *** ****
ssb>  rsa4096/***  created: 1917-08-06  expires: 1938-08-06
                                card-no: *** ****
  • With native gpg in cmd the behavior is normal and command gpg --card-status gives expected result but not in WSL Ubuntu instance.
@therealkenc
Copy link
Collaborator

therealkenc commented Oct 17, 2017

#1521, #2195, #2287, #2185 et al.

@Sekanato
Copy link
Author

@therealkenc It seems that all those issues are for an earlier build. The one I'm at supposed to support usb devices as stated here.

@DHowett-MSFT
Copy link

I believe that only applies to USB devices that present as serial devices, not all USB devices.

@Sekanato
Copy link
Author

@DHowett-MSFT Thanks for the reply! Indeed. In this comment @bitcrazed said that security devices are not supposed to work yet. Maybe I've misunderstood the announcement.
It's a shame that those are not implemented yet though. This uservoice marked complete threw me off, because there was stated specifically USB devices support and not just serial and/or storage mounting.
So if that is the case, then that uservoice should be unmarked as complete and this issue should remain open as a stand in for all those about smartcards, that were closed like #1521 when USB serial and storage was announced, or those reopened. Just an opinion, though.

@Sekanato Sekanato reopened this Oct 17, 2017
@therealkenc
Copy link
Collaborator

then that uservoice should be unmarked as complete and this issue should remain open as a stand in for all those about smartcards

The suggestion in #2185 (message), for what it is worth, has been to re-open a new User Voice. This is about support for libusb; which applies to anything that wants raw access to a USB bitstream, be it a smart card reader, jtag dongle, or whatever.

@Sekanato
Copy link
Author

Ok, sounds reasonable. I've looked at uservoice and didn't find any libusb posts, so posted new one. Hope it's clear enough this time 😄
Should this issue remain open?

@therealkenc
Copy link
Collaborator

Let's dupe it, since that's what happened with #1521, and there is really only one actionable here. Subscribe to #412, and if the status flips, try your scenario again. If libusb support gets added but Yubikey readers still don't work, that would certainly be postworthy.

@svrooij
Copy link

svrooij commented Nov 9, 2019

The uservoice is closed referring to this issue tracker.
I would still like to be able to use my yubikey (for ssh authentication) inside wsl

Any updates???
https://wpdev.uservoice.com/forums/266908-command-prompt-console-bash-on-ubuntu-on-windo/suggestions/31920928-add-libusb-support-to-wsl

@chiefjester
Copy link

@svrooij looks like this was closed because of similar issue #412.

@chiefjester
Copy link

chiefjester commented Oct 11, 2020

Issue forwarded here (for libusb): #2195

@jamiehankins
Copy link

jamiehankins commented Mar 3, 2021

The uservoice is closed referring to this issue tracker.
I would still like to be able to use my yubikey (for ssh authentication) inside wsl

Any updates???
https://wpdev.uservoice.com/forums/266908-command-prompt-console-bash-on-ubuntu-on-windo/suggestions/31920928-add-libusb-support-to-wsl

@svrooij
Have you tried this?
https://polansky.co/blog/a-better-windows-wsl-openssh-experience/

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

6 participants