SETUID(3)                  POSIX Programmer's Manual                 SETUID(3)



PPRROOLLOOGG
       This manual page is part of the POSIX Programmer's Manual.  The OS
       implementation of this interface may differ (consult the corresponding
       OS manual page for details of OS behavior), or the interface may not be
       implemented on OS.


NNAAMMEE
       setuid -- set user ID

SSYYNNOOPPSSIISS
       #include <unistd.h>

       int setuid(uid_t _u_i_d);

DDEESSCCRRIIPPTTIIOONN
       If the process has appropriate privileges, _s_e_t_u_i_d() shall set the real
       user ID, effective user ID, and the saved set-user-ID of the calling
       process to _u_i_d.

       If the process does not have appropriate privileges, but _u_i_d is equal
       to the real user ID or the saved set-user-ID, _s_e_t_u_i_d() shall set the
       effective user ID to _u_i_d; the real user ID and saved set-user-ID shall
       remain unchanged.

       The _s_e_t_u_i_d() function shall not affect the supplementary group list in
       any way.

RREETTUURRNN VVAALLUUEE
       Upon successful completion, 0 shall be returned. Otherwise, -1 shall be
       returned and _e_r_r_n_o set to indicate the error.

EERRRROORRSS
       The _s_e_t_u_i_d() function shall fail, return -1, and set _e_r_r_n_o to the
       corresponding value if one or more of the following are true:

       EEIINNVVAALL The value of the _u_i_d argument is invalid and not supported by
              the implementation.

       EEPPEERRMM  The process does not have appropriate privileges and _u_i_d does
              not match the real user ID or the saved set-user-ID.

       _T_h_e _f_o_l_l_o_w_i_n_g _s_e_c_t_i_o_n_s _a_r_e _i_n_f_o_r_m_a_t_i_v_e_.

EEXXAAMMPPLLEESS
       None.

AAPPPPLLIICCAATTIIOONN UUSSAAGGEE
       None.

RRAATTIIOONNAALLEE
       The various behaviors of the _s_e_t_u_i_d() and _s_e_t_g_i_d() functions when
       called by non-privileged processes reflect the behavior of different
       historical implementations. For portability, it is recommended that new
       non-privileged applications use the _s_e_t_e_u_i_d() and _s_e_t_e_g_i_d() functions
       instead.

       The saved set-user-ID capability allows a program to regain the
       effective user ID established at the last _e_x_e_c call. Similarly, the
       saved set-group-ID capability allows a program to regain the effective
       group ID established at the last _e_x_e_c call. These capabilities are
       derived from System V. Without them, a program might have to run as
       superuser in order to perform the same functions, because superuser can
       write on the user's files. This is a problem because such a program can
       write on any user's files, and so must be carefully written to emulate
       the permissions of the calling process properly. In System V, these
       capabilities have traditionally been implemented only via the _s_e_t_u_i_d()
       and _s_e_t_g_i_d() functions for non-privileged processes. The fact that the
       behavior of those functions was different for privileged processes made
       them difficult to use. The POSIX.1-1990 standard defined the _s_e_t_u_i_d()
       function to behave differently for privileged and unprivileged users.
       When the caller had appropriate privileges, the function set the real
       user ID, effective user ID, and saved set-user ID of the calling
       process on implementations that supported it. When the caller did not
       have appropriate privileges, the function set only the effective user
       ID, subject to permission checks. The former use is generally needed
       for utilities like _l_o_g_i_n and _s_u, which are not conforming applications
       and thus outside the scope of POSIX.1-2008. These utilities wish to
       change the user ID irrevocably to a new value, generally that of an
       unprivileged user. The latter use is needed for conforming applications
       that are installed with the set-user-ID bit and need to perform
       operations using the real user ID.

       POSIX.1-2008 augments the latter functionality with a mandatory feature
       named _POSIX_SAVED_IDS. This feature permits a set-user-ID application
       to switch its effective user ID back and forth between the values of
       its _e_x_e_c-time real user ID and effective user ID. Unfortunately, the
       POSIX.1-1990 standard did not permit a conforming application using
       this feature to work properly when it happened to be executed with
       (implementation-defined) appropriate privileges. Furthermore, the
       application did not even have a means to tell whether it had this
       privilege. Since the saved set-user-ID feature is quite desirable for
       applications, as evidenced by the fact that NIST required it in FIPS
       151-2, it has been mandated by POSIX.1-2008. However, there are
       implementors who have been reluctant to support it given the limitation
       described above.

       The 4.3BSD system handles the problem by supporting separate functions:
       _s_e_t_u_i_d() (which always sets both the real and effective user IDs, like
       _s_e_t_u_i_d() in POSIX.1-2008 for privileged users), and _s_e_t_e_u_i_d() (which
       always sets just the effective user ID, like _s_e_t_u_i_d() in POSIX.1-2008
       for non-privileged users). This separation of functionality into
       distinct functions seems desirable. 4.3BSD does not support the saved
       set-user-ID feature. It supports similar functionality of switching the
       effective user ID back and forth via _s_e_t_r_e_u_i_d(), which permits
       reversing the real and effective user IDs. This model seems less
       desirable than the saved set-user-ID because the real user ID changes
       as a side-effect. The current 4.4BSD includes saved effective IDs and
       uses them for _s_e_t_e_u_i_d() and _s_e_t_e_g_i_d() as described above. The
       _s_e_t_r_e_u_i_d() and _s_e_t_r_e_g_i_d() functions will be deprecated or removed.

       The solution here is:

        *  Require that all implementations support the functionality of the
           saved set-user-ID, which is set by the _e_x_e_c functions and by
           privileged calls to _s_e_t_u_i_d().

        *  Add the _s_e_t_e_u_i_d() and _s_e_t_e_g_i_d() functions as portable alternatives
           to _s_e_t_u_i_d() and _s_e_t_g_i_d() for non-privileged and privileged
           processes.

       Historical systems have provided two mechanisms for a set-user-ID
       process to change its effective user ID to be the same as its real user
       ID in such a way that it could return to the original effective user
       ID: the use of the _s_e_t_u_i_d() function in the presence of a saved set-
       user-ID, or the use of the BSD _s_e_t_r_e_u_i_d() function, which was able to
       swap the real and effective user IDs. The changes included in
       POSIX.1-2008 provide a new mechanism using _s_e_t_e_u_i_d() in conjunction
       with a saved set-user-ID. Thus, all implementations with the new
       _s_e_t_e_u_i_d() mechanism will have a saved set-user-ID for each process, and
       most of the behavior controlled by _POSIX_SAVED_IDS has been changed to
       agree with the case where the option was defined. The _k_i_l_l() function
       is an exception. Implementors of the new _s_e_t_e_u_i_d() mechanism will
       generally be required to maintain compatibility with the older
       mechanisms previously supported by their systems. However,
       compatibility with this use of _s_e_t_r_e_u_i_d() and with the _POSIX_SAVED_IDS
       behavior of _k_i_l_l() is unfortunately complicated. If an implementation
       with a saved set-user-ID allows a process to use _s_e_t_r_e_u_i_d() to swap its
       real and effective user IDs, but were to leave the saved set-user-ID
       unmodified, the process would then have an effective user ID equal to
       the original real user ID, and both real and saved set-user-ID would be
       equal to the original effective user ID. In that state, the real user
       would be unable to kill the process, even though the effective user ID
       of the process matches that of the real user, if the _k_i_l_l() behavior of
       _POSIX_SAVED_IDS was used. This is obviously not acceptable. The
       alternative choice, which is used in at least one implementation, is to
       change the saved set-user-ID to the effective user ID during most calls
       to _s_e_t_r_e_u_i_d().  The standard developers considered that alternative to
       be less correct than the retention of the old behavior of _k_i_l_l() in
       such systems. Current conforming applications shall accommodate either
       behavior from _k_i_l_l(), and there appears to be no strong reason for
       _k_i_l_l() to check the saved set-user-ID rather than the effective user
       ID.

FFUUTTUURREE DDIIRREECCTTIIOONNSS
       None.

SSEEEE AALLSSOO
       _e_x_e_c, _g_e_t_e_g_i_d(), _g_e_t_e_u_i_d(), _g_e_t_g_i_d(), _g_e_t_u_i_d(), _s_e_t_e_g_i_d(), _s_e_t_e_u_i_d(),
       _s_e_t_g_i_d(), _s_e_t_r_e_g_i_d(), _s_e_t_r_e_u_i_d()

       The Base Definitions volume of POSIX.1-2008, <<ssyyss__ttyyppeess..hh>>, <<uunniissttdd..hh>>

CCOOPPYYRRIIGGHHTT
       Portions of this text are reprinted and reproduced in electronic form
       from IEEE Std 1003.1, 2013 Edition, Standard for Information Technology
       -- Portable Operating System Interface (POSIX), The Open Group Base
       Specifications Issue 7, Copyright (C) 2013 by the Institute of
       Electrical and Electronics Engineers, Inc and The Open Group.  (This is
       POSIX.1-2008 with the 2013 Technical Corrigendum 1 applied.) In the
       event of any discrepancy between this version and the original IEEE and
       The Open Group Standard, the original IEEE and The Open Group Standard
       is the referee document. The original Standard can be obtained online
       at http://www.unix.org/online.html .

       Any typographical or formatting errors that appear in this page are
       most likely to have been introduced during the conversion of the source
       files to man page format. To report such errors, see
       https://www.kernel.org/doc/man-pages/reporting_bugs.html .



IEEE/The Open Group                  2013                            SETUID(3)
