Google Titan Security Key on Linux

Fixing udev so a Titan security key works on Linux …

When trying to use these new fangled things on Debian (Stretch) I needed to edit/create /etc/udev/rules.d/titan.rules and put in it something like the following – else nothing happens when you try using them …

KERNEL=="hidraw", SUBSYSTEM=="hidraw", ATTRS{idVendor}=="096e", ATTRS{idProduct}=="0858", TAG+="uaccess"
KERNEL=="hidraw", SUBSYSTEM=="hidraw", ATTRS{idVendor}=="096e", ATTRS{idProduct}=="085b", TAG+="uaccess"

This is based on e.g. the ‘dmesg’ output looking something like :

[  194.111391] usb 1-3.3.2: new full-speed USB device number 11 using xhci_hcd
 [  194.320740] usb 1-3.3.2: New USB device found, idVendor=096e, idProduct=0858, bcdDevice=46.00
 [  194.320753] usb 1-3.3.2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
 [  194.320757] usb 1-3.3.2: Product: U2F
 [  194.320760] usb 1-3.3.2: Manufacturer: FT
 [  194.328476] hid-generic 0003:096E:0858.0005: hiddev1,hidraw2: USB HID v1.00 Device [FT U2F] on usb-0000:00:14.0-3.3.2/input0

(The wireless device has a different idProduct from the USB only one, hence the two rules).

Leave a Reply

Your email address will not be published. Required fields are marked *