*-daemon: always call setgroups, defaulting to count = 0#952
*-daemon: always call setgroups, defaulting to count = 0#952
Conversation
services started by init don't get any supplementary groups, but anything started from a shell would inherit the groups, causing inconsistent behaviour we can either clear all groups, or always initalize root's groups. since other init systems does not initialize anything, including us at boot, let's just always clear them unconditionally
|
actually, on init, we get hmmm, unsure what we should do here |
|
hmm, this breaks user services actually... i don't really want to check rc_is_user(), our goal is to deprecate that function |
|
Maybe we do something like |
i thought of always adding the groups over clearing them, though iirc the person who reported this explicitly didn't want extra groups can non-root users set groups if those groups anyway? i think the right call might be to kind of feels like the simplest way to solve all those inconsistencies, would be to always run services from a dedicated runner daemon, eh |
services started by init don't get any supplementary groups, but anything started from a shell would inherit the groups, causing inconsistent behaviour
we can either clear all groups, or always initalize root's groups. since other init systems does not initialize anything, including us at boot, let's just always clear them unconditionally