Re: Bug#1132588: runuser: missing whitelist-environment option
Christian Albrecht Goeschel Ndjomouo <[email protected]> Fri, 3 Apr 2026 23:23:42 +0000
| Newsgroups | org.kernel.vger.util-linux |
|---|---|
| Message-ID | <SJ0P220MB0541E236A2387E8EBDB7C94BE95EA@SJ0P220MB0541.NAMP220.PROD.OUTLOOK.COM> |
Hey Chris,=0A=0AThe issue is indeed caused by the mentioned commit ac0147f,= however=0Athe change is necessary for proper functioning of su(1). Neverth= eless, I=0Ahave created a PR that separates the short option strings used f= or su(1)=0Aand runuser(1) as we need a different scanning mode for the form= er.=0A=0AI have also added regression tests for runuser(1) and slightly imp= roved=0Athe one for su(1) so we can catch regressions earlier.=0A=0AWith th= e patch the issue with runuser should be fixed. Can you please=0Avalidate t= his ?=0A=0APR: https://github.com/util-linux/util-linux/pull/4185=0A=0AEdit= :=0A=0AAfter taking a closer look at the runuser(1) man page it seems to me= that=0Athe actual documented syntax implies that options should always be = put=0Abefore the username and potential arguments that are to be passed to = the=0Ashell or defined command. This aligns with the usage of su(1) and see= ms=0Amore coherent. Let's see what Karel thinks about this :D=0A=0ARegards,= =0A=0AChristian Goeschel Ndjomouo=0A