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

The TAG+="uaccess" has no effect in the udev rule #98

Closed
wucke13 opened this issue May 20, 2024 · 4 comments
Closed

The TAG+="uaccess" has no effect in the udev rule #98

wucke13 opened this issue May 20, 2024 · 4 comments

Comments

@wucke13
Copy link

wucke13 commented May 20, 2024

As hinted here, udev uaccess is granted by /usr/lib/udev/rules.d/73-seat-late.rules. So having a rule add the uaccess tag after 73-seat-late.rules ran has not effect. The rules are ran in lexical order, so to be compatible with the uacccess system, the rule must be renamed, i.e. to 70-CH341.rules.

SUBSYSTEM=="usb", ATTRS{idVendor}=="1a86", ATTRS{idProduct}=="5512", MODE="0660", GROUP="plugdev", TAG+="uaccess"

@bigbigmdm
Copy link
Owner

@wucke13 , GROUP=‘plugdev’ is not enough for the current user to get permissions?

@wucke13
Copy link
Author

wucke13 commented May 20, 2024

It is, on distros that use the plugdev group menchanism. Udev's uaccess is a completely orthogonal mechanism to provide access: essentially, for each device that was tagged uaccess, in 73-seat-late.rules an internal function of udev is called to grant access to all users that have a local seat.

The mechanism is widely used, but unfortunately under-documented, as pointed out in systemd/systemd#4288. However, many distros consider deprecating plugdev and instead moving to uaccess as the cleaner approach, i.e. as mentioned in the archwiki: https://wiki.archlinux.org/title/Udev#Allowing_regular_users_to_use_devices

@bigbigmdm
Copy link
Owner

@Fantu , may I have your opinion on this? (Pull request)

@wucke13
Copy link
Author

wucke13 commented May 27, 2024

Fixed by 947320f

@wucke13 wucke13 closed this as completed May 27, 2024
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

Successfully merging a pull request may close this issue.

2 participants