My old laptop’s wifi went on the fritz, so I got a new Lenovo P50. Fedora 23 wouldn’t work with the Skylake architecture, so I had to jump headfirst into the Fedora 24 beta.
I’ve since hit one new issue: Yubikeys wouldn’t work for FIDO U2F authentication. Logging into a site using a Yubikey (inserting a Yubikey USB device and tapping the button when prompted) wouldn’t work. Attempting this on Github would display the error message, “Something went really wrong.” Nor would registering Yubikeys with sites work. On Github, attempting to register Yubikeys would give the error message, “This device cannot be registered.”
Interwebs sleuthing suggests that Yubikeys require special udev configuration to work on Linux. The problem is that udev doesn’t grant access to the Yubikey, so when the browser tries to access the key, things go Bad. A handful of resources pointed me toward a solution: tell udev to grant access to the device.
As root, go to the directory
/etc/udev/rules.d. It contains files with names of the form
*.rules, specifying rules for how to treat devices added and removed from the system. In that directory create the file
70-u2f.rules. Its contents should be those of
70-u2f.rules, from Yubico‘s
libu2f-host repository. (Most of this file is just selecting various Yubikey devices to apply rules against. The important part of this file is the
TAG+="uaccess" ending the various lines. This adds the “uaccess” tag to those devices;
systemd-logind recognizes this tag and will grant access to the device to the current logged-in user.) Finally, run these two commands to refresh udev state:
udevadm control --reload udevadm trigger
Yubikeys should now work for authentication.
These steps work for me, and they appear to me a sensible way to solve the problem. But I can’t say for sure that they’re the best way to solve it. (Nor am I sure why Fedora doesn’t handle this for me.) If anyone knows a better way, that doesn’t involve modifying the root file system, I’d love to hear it in comments.