Be careful with this. These udev rules usually grant uaccess to your entire keyboard. uaccess is explicitly disabled for keyboards by default because it presents the event device to all of userspace, which allows any unprivileged app to log all key presses. This includes any malicious scripts running in a browser. If you do want to set up these rules, use them only for the single session you’re setting up your device and don’t type any passwords with it active, or change them immediately after (you won’t be able to remove them without your sudo password).
For the same reason, stop using OpenRGB for devices that don’t have kernel drivers.
You’re right, one of the guides I’ve found explicitly mentioned that, and recommended toggling the rules on only when you need it.
If I’m not mistaken, you can make rules per device ID. Keychron devices show up as a keyboard/mouse and a “Link” device. You could make a passthrough rule just for the Link, thus not granting access to the actual input device.
Could you elaborate on the OpenRGB thing? I’ve used it a few times but never paid attention to the rules it asks for
If I’m not mistaken, you can make rules per device ID. Keychron devices show up as a keyboard/mouse and a “Link” device. You could make a passthrough rule just for the Link, thus not granting access to the actual input device.
That’s great, just be sure your rules are specific enough for that device but didn’t rely on some randomness for detection. I.e. Matching on the current evdev or hidraw devnode is bad because it can shift with more devices being added, changing ports, or some randomness in enumeration speed. Instead, do an attribute walk on the devnode to find specific unique attributes for that node, such as VID + PID + subsystem + bInterfaceNunber should be unique. Things like names and phys patch aren’t guaranteed to be unique or consistent in different operating modes. You’ll also want to check the devnodes of the other interfaces to be sure they won’t match by doing a test.
The commands for those things are:
udevadm info -a /path/to/devnodeudevadm test /path/to/devnode
Could you elaborate on the OpenRGB thing? I’ve used it a few times but never paid attention to the rules it asks for
Sure. While not technically necessary for some devices, they have pretty open blanket udev rules. This is because most keyboard devices require the use of hid reports directly to the device to make changes.
From their page:
On Linux, OpenRGB needs permission to access the hardware interfaces used for RGB control. These include USB and I2C interfaces. To make accessing these interfaces easier, OpenRGB provides a udev rules file that tells your operating system to allow your user account control over these hardware interfaces, allowing OpenRGB to run without root access while still controlling the hardware.
Notice the complete lack of warning about any security issue from doing this.
If they wanted to be secure they could make a root level daemon that does all the hardware interfacing, and provide a dbus interface managed through polkit to allow making those changes from the userspace UI.
You can configure Keychron peripherals via their website - Keychron Launcher.
It works on Linux, but there are two caveats:
I’ve tested it with my Keychain K3 keyboard and M4 mouse and it works.
I agree a compatibility with ex. Piper would be neat though
Be careful with this. These udev rules usually grant uaccess to your entire keyboard. uaccess is explicitly disabled for keyboards by default because it presents the event device to all of userspace, which allows any unprivileged app to log all key presses. This includes any malicious scripts running in a browser. If you do want to set up these rules, use them only for the single session you’re setting up your device and don’t type any passwords with it active, or change them immediately after (you won’t be able to remove them without your sudo password).
For the same reason, stop using OpenRGB for devices that don’t have kernel drivers.
You’re right, one of the guides I’ve found explicitly mentioned that, and recommended toggling the rules on only when you need it.
If I’m not mistaken, you can make rules per device ID. Keychron devices show up as a keyboard/mouse and a “Link” device. You could make a passthrough rule just for the Link, thus not granting access to the actual input device.
Could you elaborate on the OpenRGB thing? I’ve used it a few times but never paid attention to the rules it asks for
That’s great, just be sure your rules are specific enough for that device but didn’t rely on some randomness for detection. I.e. Matching on the current evdev or hidraw devnode is bad because it can shift with more devices being added, changing ports, or some randomness in enumeration speed. Instead, do an attribute walk on the devnode to find specific unique attributes for that node, such as VID + PID + subsystem + bInterfaceNunber should be unique. Things like names and phys patch aren’t guaranteed to be unique or consistent in different operating modes. You’ll also want to check the devnodes of the other interfaces to be sure they won’t match by doing a test.
The commands for those things are:
udevadm info -a /path/to/devnodeudevadm test /path/to/devnodeSure. While not technically necessary for some devices, they have pretty open blanket udev rules. This is because most keyboard devices require the use of hid reports directly to the device to make changes.
From their page:
Notice the complete lack of warning about any security issue from doing this.
If they wanted to be secure they could make a root level daemon that does all the hardware interfacing, and provide a dbus interface managed through polkit to allow making those changes from the userspace UI.
I REALLY fucking wish people would stop targeting Chromium for their apps.
I agree, but at least it’s not an app you have to download, which turns out to be Electron/CEF/etc.