On 5/27/19 6:09 AM, Stumpy wrote:
> I am trying to use an onlykey U2F but have run into some issues like it
> showing up in dom0 and sys-usb but seems like i cant use it.
>
> in sys-usb:
> [user@sys-usb ~]$ lsusb | grep Only
> Bus 004 Device 010: ID 1d50:60fc OpenMoko, Inc. OnlyKey Two-factor
> Authentication and Password Solution
>
> and in Dom0:
> [ralph@dom0 ~]$ qvm-usb | grep ONLY ; sudo qvm-usb a sys-usb sys-usb:42
> sys-usb:4-2 CRYPTOTRUST_ONLYKEY_346etc
> Device attach failed:
> [ralph@dom0 ~]$
>
> I decided to go with the chrome app but even though sys-usb seems to see
> the onlykey I cant seem to attach it to the chrome appvm i made?
>
so in dom0 you did
$qvm-usb
get the BDM number and do
$qvm-usb attach chromevm sys-usb:X-X
U2F keys will work in chromium for google logins with no
complicated passthrough setup necessary
OTP won't , if the key does more than U2F you may need to get a
configuration application for the key and make sure it's U2F only
slot 1 , 2 etc
--
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 view this discussion on the web visit
https://groups.google.com/d/msgid/qubes-users/fd0e81b4-68a9-b977-0966-de4df579764a%40riseup.net.
