So far this seems to have address all of my issues. #Reboot, or run the following to reload your rules #Pull down the file from the yubikey github A few commands later, I was up and running with both keys. In searching for that fix I came across this document from YubiKey…and when I checked the udev rules file they provided it actually included the Feitian FIDO/U2F product id and codes. So initially I set up my own udev rules and that seemed to work for one device, but I had an issue with my second key. Usb 2-6.4: New USB device strings: Mfr=1, Product=2, SerialNumber=0 Usb 2-6.4: New USB device found, idVendor=096e, idProduct=085b, bcdDevice=32.10 Usb 2-6.4: new full-speed USB device number 14 using xhci_hcd When I checked dmesg after plugging in my key I could see that the vendor and product id’s did not match what google provided, as you can see below. Please try again.” (Twitter).Ī quick search returned the this article from Google on linux setup, however thse steps did not work. However, on my Arch Linux box I immediately ran into issues where the browser seemed to not see the key and raise an error that either “Something went really wrong” (GitHub) or “Incorrect response. So on my windows side the Titan keys worked right away without any issue. Hopefully it will in the future, but we’ll see. For example, my password manager still does not support FIDO/U2F.

In hindsight, the ecosystem and support around YubiKey is more advanced. I decided to try this over YubiKey for no good reason, other than the fact that with Google behind it I assume it will pick up extensively. One is a standard USB U2F key and the second is a bluetooth key.

In short, you purchase the Titan Security Bundle from Google, which includes two physical keys. For those not aware, Advanced protection is Google’s first party U2F authentication system. I recently decided to give Google Advanced Protection a shot.

Buy google titan security key