s/SUID/set-user-ID/

s/SGID/set-group-ID/
This commit is contained in:
Michael Kerrisk 2006-09-06 15:23:31 +00:00
parent e743a18476
commit 8106981956
1 changed files with 8 additions and 6 deletions

View File

@ -273,11 +273,12 @@ or a script or ELF interpreter is not a directory.
.B EPERM
The file system is mounted
.IR nosuid ,
the user is not the superuser, and the file has an SUID or SGID bit set.
the user is not the superuser,
and the file has the set-user-ID or set-group-ID bit set.
.TP
.B EPERM
The process is being traced, the user is not the superuser and the
file has an SUID or SGID bit set.
file has the set-user-ID or set-group-ID bit set.
.TP
.B ETXTBSY
Executable was open for writing by one or more processes.
@ -290,16 +291,17 @@ but is otherwise compatible.
.\" document ETXTBSY, EPERM, EFAULT, ELOOP, EIO, ENFILE, EMFILE, EINVAL,
.\" EISDIR or ELIBBAD error conditions.
.SH NOTES
SUID and SGID processes can not be \fBptrace\fP()d.
Set-user-ID and set-group-ID processes can not be \fBptrace\fP()d.
Linux ignores the SUID and SGID bits on scripts.
Linux ignores the set-user-ID and set-group-ID bits on scripts.
The result of mounting a filesystem
.I nosuid
vary between Linux kernel versions:
some will refuse execution of SUID/SGID executables when this would
some will refuse execution of set-user-ID and set-group-ID
executables when this would
give the user powers she did not have already (and return EPERM),
some will just ignore the SUID/SGID bits and
some will just ignore the set-user-ID and set-group-ID bits and
.BR exec ()
successfully.