Re: LOGNAME, USER, and get-uid; NIS

Show/hide message thread

LOGNAME, USER, and get-uid; NIS John Cowan (12 Aug 2019 16:29 UTC)
Re: LOGNAME, USER, and get-uid; NIS Lassi Kortela (12 Aug 2019 18:33 UTC)
Re: LOGNAME, USER, and get-uid; NIS hga@xxxxxx (12 Aug 2019 20:17 UTC)
Re: LOGNAME, USER, and get-uid; NIS Lassi Kortela (13 Aug 2019 09:13 UTC)
Re: LOGNAME, USER, and get-uid; NIS hga@xxxxxx (13 Aug 2019 11:26 UTC)
Re: LOGNAME, USER, and get-uid; NIS Lassi Kortela (13 Aug 2019 11:33 UTC)
Re: LOGNAME, USER, and get-uid; NIS hga@xxxxxx (13 Aug 2019 11:37 UTC)
Naming of "real" and "effective" ID procedures Lassi Kortela (14 Aug 2019 14:18 UTC)
(missing)
(missing)
Fwd: Naming of "real" and "effective" ID procedures John Cowan (14 Aug 2019 20:57 UTC)
Re: Fwd: Naming of "real" and "effective" ID procedures Lassi Kortela (14 Aug 2019 21:07 UTC)
Re: Naming of "real" and "effective" ID procedures hga@xxxxxx (14 Aug 2019 14:23 UTC)

Re: LOGNAME, USER, and get-uid; NIS Lassi Kortela 13 Aug 2019 11:33 UTC

> Sorry if I wasn't clear, I only did one set-uid, and it indeed
> changed the effective uid to 1000.  The problem is that the real
> uid [...] also changed to 1000.

The setuid() function sets the real and effective user IDs and the saved
set-user-ID of the current process to the specified value.

There's a separate seteuid() syscall (note the "e") to set only the
effective user ID.

Ditto for setgid() and setegid().