Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Via on Linux forces overly permissive udev rules, even when adequate rules already exist #292

Open
Eltiech opened this issue Jan 24, 2025 · 1 comment

Comments

@Eltiech
Copy link

Eltiech commented Jan 24, 2025

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"

@Seegras
Copy link

Seegras commented Feb 13, 2025

Yes please, don't insist on wanting to insert any rule before even checking if you have access.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants