Gods, I really hope they consider Linux or at least SteamOS for software support.
Having my Logitech and Corsair mice without the ability to actively rebind anything on my Linux host (without the use of Windows VMs) is painfully annoying.
It’s a fucking USB HID mouse? OS agnostic. In an ideal world, the buttons should just be really big number scancodes that aren’t mapped to anything. You can then do something like this (says sway but runs on basically everything X and Wayland). Research before buying a mouse. Actually, no, just buy it from a local store, and if the buttons aren’t functioning as buttons without OEM bullshit, return as defective.
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
They are talking about the firmware that runs on the device. The user front-end to easily configure it is another story. Hopefully it’s going to quickly get support for Linux as they are starting from well established Open-source projects for keyboard firmware (QMK and ZMK). If it works like for keyboards, you will be able to configure your mouse with something like VIA that runs on Chrome/Chromium (and maybe one day Firefox ?) using the WebUSB API.
I have 2 keychon keyboards, an old one and a newer one with QMK firmware. Both have worked perfectly well for Linux. The QMK one is easy to configure with VIA once the device permissions are sorted out.
that runs on Chrome/Chromium (and maybe one day Firefox ?) using the WebUSB API.
Please don’t bring webusb to firefox. It’s just a security liability. only use is for tools made out of mistakes. the web should never have direct access to usb devices and the filesystem.
Gods, I really hope they consider Linux or at least SteamOS for software support.
Having my Logitech and Corsair mice without the ability to actively rebind anything on my Linux host (without the use of Windows VMs) is painfully annoying.
It’s a fucking USB HID mouse? OS agnostic. In an ideal world, the buttons should just be really big number scancodes that aren’t mapped to anything. You can then do something like this (says sway but runs on basically everything X and Wayland). Research before buying a mouse. Actually, no, just buy it from a local store, and if the buttons aren’t functioning as buttons without OEM bullshit, return as defective.
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.
If it’s open source, there’s roughly a 100% chance someone will make it work on Linux.
They are talking about the firmware that runs on the device. The user front-end to easily configure it is another story. Hopefully it’s going to quickly get support for Linux as they are starting from well established Open-source projects for keyboard firmware (QMK and ZMK). If it works like for keyboards, you will be able to configure your mouse with something like VIA that runs on Chrome/Chromium (and maybe one day Firefox ?) using the WebUSB API.
I have 2 keychon keyboards, an old one and a newer one with QMK firmware. Both have worked perfectly well for Linux. The QMK one is easy to configure with VIA once the device permissions are sorted out.
Please don’t bring webusb to firefox. It’s just a security liability. only use is for tools made out of mistakes. the web should never have direct access to usb devices and the filesystem.
They already brought webserial.
yes and I don’t like it.
QMK VIA