Copyright (C) 1995, Thomas K. Dyas <firstname.lastname@example.org> %%%LICENSE_START(VERBATIM) Permission is granted to make and distribute verbatim copies of this manual provided the copyright notice and this permission notice are preserved on all copies. Permission is granted to copy and distribute modified versions of this manual under the conditions for verbatim copying, provided that the entire resulting derived work is distributed under the terms of a permission notice identical to this one. ...
NAMEsetfsuid - set user identity used for filesystem checks
int setfsuid(uid_t fsuid);
DESCRIPTIONThe system call setfsuid() changes the value of the caller's filesystem user ID---the user ID that the Linux kernel uses to check for all accesses to the filesystem. Normally, the value of the filesystem user ID will shadow the value of the effective user ID. In fact, whenever the effective user ID is changed, the filesystem user ID will also be changed to the new value of the effective user ID.
Explicit calls to setfsuid() and setfsgid(2) are usually used only by programs such as the Linux NFS server that need to change what user and group ID is used for file access without a corresponding change in the real and effective user and group IDs. A change in the normal user IDs for a program such as the NFS server is a security hole that can expose it to unwanted signals. (But see below.)
setfsuid() will succeed only if the caller is the superuser or if fsuid matches either the caller's real user ID, effective user ID, saved set-user-ID, or current filesystem user ID.
RETURN VALUEOn both success and failure, this call returns the previous filesystem user ID of the caller.
VERSIONSThis system call is present in Linux since version 1.2.
CONFORMING TOsetfsuid() is Linux-specific and should not be used in programs intended to be portable.
NOTESWhen glibc determines that the argument is not a valid user ID, it will return -1 and set errno to EINVAL without attempting the system call.
At the time when this system call was introduced, one process
could send a signal to another process with the same effective user ID.
This meant that if a privileged process changed its effective user ID
for the purpose of file permission checking,
then it could become vulnerable to receiving signals
sent by another (unprivileged) process with the same user ID.
The filesystem user ID attribute was thus added to allow a process to
change its user ID for the purposes of file permission checking without
at the same time becoming vulnerable to receiving unwanted signals.
Since Linux 2.0, signal permission handling is different (see
with the result that a process change can change its effective user ID
without being vulnerable to receiving signals from unwanted processes.
is nowadays unneeded and should be avoided in new applications
The original Linux setfsuid() system call supported only 16-bit user IDs. Subsequently, Linux 2.4 added setfsuid32() supporting 32-bit IDs. The glibc setfsuid() wrapper function transparently deals with the variation across kernel versions.