Skip to contentSkip to conversation

new setprocuid syscall

PATCH Petr Vandrovec 1 participant 1 message Feb 20, 2001

lore
Share & tools
lore
#0 lore raw
Quoted 6 lines · Peter Samuelson

[Alan Cox]

Quoted 2 lines

There is an assumption in the kernel that only the task changes its own uid and other related data.

Fair enough but could you explain the potential problems? And how is it different from sys_setpriority?

Look at what fs/open.c:sys_access does, at least. It switches fsuid/fsgid/capabilities during its execution.

sys_setpriority is completely different, no piece of kernel changes that and nothing except schedule() touches that. But {,fs,e}[ug]id are used here and there through whole kernel. Also, changing priority does not remove some access rights from your process, while changing uid/gid does...
Petr Vandrovec [email protected]