You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I’m referring to git revision 4b3ffec.
Using this, procd does not respect a user’s groups (/etc/group) when starting a service.
In my case, I want a particular service running as a particular user (procd_set_param user foo). The user is a member of several groups, and they are needed when running that service.
Suppose user foo is in primary group bar, and in groups exampleA and exampleB.
The service runs as user foo, and as primary group bar. However, the service does not have the gids of exampleA and exampleB set as described in /etc/group. I verified it by using a wrapper script which wrote the output of ‘id’ to a file.
Steps to reproduce:
Create a user foo having primary group bar, and is a member of group exampleA and exampleB..
Write a short bash script which write the output of ‘id’ to a file.
Create a service that starts the aforementioned script.
Have a look at the output. It should say something like this: uid=XXX(foo) gid=xxx(foo).
I expect it to be: uid=XXX(foo) gid=XXX(bar) groups=XXX(exampleA) groups=XXX(exampleb).
flipreverse:
Hi folks!
I’m referring to git revision 4b3ffec.
Using this, procd does not respect a user’s groups (/etc/group) when starting a service.
In my case, I want a particular service running as a particular user (procd_set_param user foo). The user is a member of several groups, and they are needed when running that service.
Suppose user foo is in primary group bar, and in groups exampleA and exampleB.
The service runs as user foo, and as primary group bar. However, the service does not have the gids of exampleA and exampleB set as described in /etc/group. I verified it by using a wrapper script which wrote the output of ‘id’ to a file.
Steps to reproduce:
I expect it to be: uid=XXX(foo) gid=XXX(bar) groups=XXX(exampleA) groups=XXX(exampleb).
Cheers,
Alex
P.S.: I've already posted that isse as #988 (https://bugs.openwrt.org/index.php?do=details&task_id=988). It was closed due to my very late response.
The text was updated successfully, but these errors were encountered: