Technical article 115602

Why does documented behavior of setluid(S) depend on system security profile?

OpenServer 5.0.0OpenServer 5.0.2OpenServer 5.0.4OpenServer 5.0.5OpenServer 5.0.6

Written · Last revised

Problem

The man page for setluid(S) states that this function will return
-1 and set errno to EPERM if the LUID (login user ID) has already
been set prior to the call.  This behavior only applies if the
kernel parameter SECLUID has been set.  In "Traditional" (and "Low")
security mode, SECLUID is not set by default.  In this case,
root may successfully change the LUID through a call to setluid(S)
even if the LUID has already been set.  Only in "High" security
mode is SECLUID set.  In this case, once the LUID has been set,
it cannot be changed, and any subsequent call to setluid(S) will
return -1 and set EPERM.
NOTE:     Only root is authorized to set the LUID through setluid(S).

Solution

This documentation omission has been reported to SCO Engineering.

See also

ta 115442 "Cron jobs don't run after installing OSS642A on a system in high security mode."

From the Xinuos technical article database, record 115602. Reproduced with permission. The original is at www.sco.com/ta/115602, which is reachable but blocked from search engines.

Next step

Need this fixed rather than explained?

Tell us the release, what the system runs and what it is doing. We will reply by email with what we would do next.

  • You deal with the people who do the work
  • No obligation, and no upgrade required before we will help
  • We tell you plainly if something is not worth doing

Send an enquiry

We reply by email. If a server is down, say so in the first line. You can also write to help@scoexpert.com.