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
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
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.