Hi, all: This is a different and a more nuanced problem than recently discussed, and I'm not sure if there's a solution, but I wanted to ask. :)
Yubikey-4 can act in multiple capacities: - Smartcard - U2F device - HOTP HOTP functionality is really just a keyboard and registers with Linux as such (USB keyboard). With 3.2 I was attaching the USB controller directly to the VM where I was doing the work that required the smartcard/HOTP functionality and both worked just fine. With 4.0 I created a separate sys-usb VM and it seems I can use only one or the other, not both. When I plug in the yubikey, it registers correctly and I get a pop-up notification that it's available to be used. At that point, I am able to use HOTP-press without needing to attach the device to my work vm (because it's a "keyboard"). However, if I want to use the smartcard functionality, I have to assign the device to the work VM -- and gnupg interacts with it correctly. However, once I do that, I am no longer able to use HOTP -- pressing the button does nothing. Any ideas if this is fixable at all, or is it the downside of the way USB devices are assigned with usb-proxy? Best, -- Konstantin Ryabitsev Director, IT Infrastructure Security The Linux Foundation -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/0f889341-850c-23ba-8286-4b091bd2529b%40linuxfoundation.org. For more options, visit https://groups.google.com/d/optout.
signature.asc
Description: OpenPGP digital signature
