You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Via asks to add a udev rule that gives full access to ALL of hidraw. Obviously this is unnecessary and possibly dangerous. For my own uses I added a rule that gives permissions for just my Keychron keyboard's vendor ID and product ID, and nothing else.
However, Via still insists on adding the hazardous "access absolutely everything" rule, even when the permissions for my keyboard are already present.
At very least it should check that the permissions it needs already exist, and not force the addition of a new rule. The ideal option would be for Via to only create rules for intended/compatible devices.
As an example, here's the rule for my keychron K5 H:
Via asks to add a udev rule that gives full access to ALL of hidraw. Obviously this is unnecessary and possibly dangerous. For my own uses I added a rule that gives permissions for just my Keychron keyboard's vendor ID and product ID, and nothing else.
However, Via still insists on adding the hazardous "access absolutely everything" rule, even when the permissions for my keyboard are already present.
At very least it should check that the permissions it needs already exist, and not force the addition of a new rule. The ideal option would be for Via to only create rules for intended/compatible devices.
As an example, here's the rule for my keychron K5 H:
KERNEL=="hidraw*", SUBSYSTEM=="hidraw", ATTRS{idVendor}=="3434", ATTRS{idProduct}=="0250", MODE="0660", GROUP="users", TAG+="uaccess", TAG+="udev-acl"
The rule that Via unreasonably insists upon is:
KERNEL=="hidraw*", SUBSYSTEM=="hidraw", MODE="0666", TAG+="uaccess", TAG+="udev-acl"
The text was updated successfully, but these errors were encountered: