I noticed that it calls syscall directly in gssd_proc.c. This fails
here as setgroups, setresuid and setresgid don't seem to work.
On Sun, Oct 15, 2017 at 09:06:51PM +0200, Sverd Johnsen wrote:
> I noticed that it calls syscall directly in gssd_proc.c. This fails
> here as setgroups, setresuid and setresgid don't seem to work.
Huh. I wonder what we're doing that's wrong for the aarch64/32-bit
userland case.
Any more details? How exactly does the call fail?
--b.