#uaccess — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #uaccess, aggregated by home.social.
-
Recently, when I dealt with some package issues around probe-rs, I found that some developers and packagers may have some misunderstandings about #systemd #udev giving some users access permission. systemd udev rules have two kinds of permission mechanisms: one is like chown, which can set the device file's owner to some user or group (normally #plugdev system group); another is #uaccess, systemd will give the active user session permission via ACL.
-
Recently, when I dealt with some package issues around probe-rs, I found that some developers and packagers may have some misunderstandings about #systemd #udev giving some users access permission. systemd udev rules have two kinds of permission mechanisms: one is like chown, which can set the device file's owner to some user or group (normally #plugdev system group); another is #uaccess, systemd will give the active user session permission via ACL.
-
Recently, when I dealt with some package issues around probe-rs, I found that some developers and packagers may have some misunderstandings about #systemd #udev giving some users access permission. systemd udev rules have two kinds of permission mechanisms: one is like chown, which can set the device file's owner to some user or group (normally #plugdev system group); another is #uaccess, systemd will give the active user session permission via ACL.
-
Recently, when I dealt with some package issues around probe-rs, I found that some developers and packagers may have some misunderstandings about #systemd #udev giving some users access permission. systemd udev rules have two kinds of permission mechanisms: one is like chown, which can set the device file's owner to some user or group (normally #plugdev system group); another is #uaccess, systemd will give the active user session permission via ACL.
-
huh, you always learn something new.
automatic temporary ACL permissions on video/audio/etc devices for the active #linux user has been a thing for more than 10yrs: #uaccess
(active==sitting in front of the screen in contrast to using ssh remotely)
https://enotty.pipebreaker.pl/2012/05/23/linux-automatic-user-acl-management/
yet, the issue of writing documentation for it, is still open.
-
huh, you always learn something new.
automatic temporary ACL permissions on video/audio/etc devices for the active #linux user has been a thing for more than 10yrs: #uaccess
(active==sitting in front of the screen in contrast to using ssh remotely)
https://enotty.pipebreaker.pl/2012/05/23/linux-automatic-user-acl-management/
yet, the issue of writing documentation for it, is still open.
-
huh, you always learn something new.
automatic temporary ACL permissions on video/audio/etc devices for the active #linux user has been a thing for more than 10yrs: #uaccess
(active==sitting in front of the screen in contrast to using ssh remotely)
https://enotty.pipebreaker.pl/2012/05/23/linux-automatic-user-acl-management/
yet, the issue of writing documentation for it, is still open.
-
huh, you always learn something new.
automatic temporary ACL permissions on video/audio/etc devices for the active #linux user has been a thing for more than 10yrs: #uaccess
(active==sitting in front of the screen in contrast to using ssh remotely)
https://enotty.pipebreaker.pl/2012/05/23/linux-automatic-user-acl-management/
yet, the issue of writing documentation for it, is still open.
-
huh, you always learn something new.
automatic temporary ACL permissions on video/audio/etc devices for the active #linux user has been a thing for more than 10yrs: #uaccess
(active==sitting in front of the screen in contrast to using ssh remotely)
https://enotty.pipebreaker.pl/2012/05/23/linux-automatic-user-acl-management/
yet, the issue of writing documentation for it, is still open.