Timeline for Unable to execute program without root privileges regardless of group or permissions
Current License: CC BY-SA 3.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| May 19, 2018 at 5:05 | comment | added | derobert | @greggo the processes groups are what actually matter, so that's why it doesn't work. The thing that comes to mind is if you didn't log out / back in after adding yourself to the group. Other than that, that's a good question, please ask it as a new question. (I haven't checked if it's already been asked, on a phone...) | |
| May 19, 2018 at 2:49 | comment | added | greggo | Any idea why being in plugdev group lets me access mode 660 files which are owned root:plugdev, but being in dialout doesn't allow access to mode 660 files owned by root:dialout? I've checked this with ordinary files too. One clue: 'groups $USER' lists all the groups I'm in, but 'groups' (process groups) lists all the same groups except dialout. So 'dialout' group membership doesn't seem to apply to processes owned by me. I'm on ubuntu. | |
| Jul 17, 2015 at 6:11 | comment | added | derobert | @sherrellbc A lot of the default permission rules are at 50, so I used 52 to be a little after them. | |
| Jul 17, 2015 at 6:09 | comment | added | sherrellbc | I was just reading about udev in general. It seems that the numbers in the rule names are used to order the execution of rules. Why did you choose 52? | |
| Jul 17, 2015 at 6:08 | vote | accept | sherrellbc | ||
| Jul 17, 2015 at 6:05 | history | answered | derobert | CC BY-SA 3.0 |