aboutsummaryrefslogtreecommitdiffstats
path: root/man2
diff options
context:
space:
mode:
authorMichael Kerrisk <mtk.manpages@gmail.com>2005-07-18 14:25:42 +0000
committerMichael Kerrisk <mtk.manpages@gmail.com>2005-07-18 14:25:42 +0000
commit880f5b4bc39386da3a4315644519bd7b5c438d6c (patch)
tree524465d266e31b79f5cfba178311285fd07214d0 /man2
parentda2d9dad4e4da4a8a84998ce5d6e5d8ddf0ee793 (diff)
downloadman-pages-880f5b4bc39386da3a4315644519bd7b5c438d6c.tar.gz
Consistent use of "set-user-ID" and "set-group-ID".
Diffstat (limited to 'man2')
-rw-r--r--man2/access.23
-rw-r--r--man2/execve.24
-rw-r--r--man2/fcntl.22
-rw-r--r--man2/mount.212
-rw-r--r--man2/prctl.24
-rw-r--r--man2/ptrace.25
-rw-r--r--man2/setgid.23
-rw-r--r--man2/setuid.26
-rw-r--r--man2/statvfs.22
-rw-r--r--man2/truncate.23
10 files changed, 24 insertions, 20 deletions
diff --git a/man2/access.2 b/man2/access.2
index 66bbf55beb..d257990075 100644
--- a/man2/access.2
+++ b/man2/access.2
@@ -77,7 +77,8 @@ links encountered on the way.
The check is done with the process's
.I real
UID and GID, rather than with the effective IDs as is done when
-actually attempting an operation. This is to allow set-UID programs to
+actually attempting an operation.
+This is to allow set-user-ID programs to
easily determine the invoking user's authority.
Only access bits are checked, not the file type or contents. Therefore, if
diff --git a/man2/execve.2 b/man2/execve.2
index 4f4d092e25..d512939cd5 100644
--- a/man2/execve.2
+++ b/man2/execve.2
@@ -64,10 +64,10 @@ The SIGCHLD signal (when set to SIG_IGN) may or may not be reset to SIG_DFL.
If the current program is being ptraced, a \fBSIGTRAP\fP is sent to it
after a successful \fBexecve()\fP.
-If the set-uid bit is set on the program file pointed to by
+If the set-user-ID bit is set on the program file pointed to by
\fIfilename\fP, and the calling process is not being ptraced,
then the effective user ID of the calling process is changed
-to that of the owner of the program file. Similarly, when the set-gid
+to that of the owner of the program file. Similarly, when the set-group-ID
bit of the program file is set the effective group ID of the calling
process is set to the group of the program file.
diff --git a/man2/fcntl.2 b/man2/fcntl.2
index 838b88cf2f..4a1c98417c 100644
--- a/man2/fcntl.2
+++ b/man2/fcntl.2
@@ -335,7 +335,7 @@ To make use of mandatory locks, mandatory locking must be enabled
.BR mount (8))
for the file system containing the
file to be locked and enabled on the file itself (by disabling
-group execute permission on the file and enabling the set-GID
+group execute permission on the file and enabling the set-group-ID
permission bit).
Advisory locks are not enforced and are useful only between
diff --git a/man2/mount.2 b/man2/mount.2
index e5d746da91..8c98da9c08 100644
--- a/man2/mount.2
+++ b/man2/mount.2
@@ -138,10 +138,10 @@ Do not allow programs to be executed from this file system.
.\" users cannot execute files uploaded using ftp or so.)
.TP
.B MS_NOSUID
-Do not honour set-UID and set-GID bits when executing
+Do not honour set-user-ID and set-group-ID bits when executing
programs from this file system.
-.\" (This is a security feature to prevent users executing set-UID and
-.\" set-GID programs from removable disk devices.)
+.\" (This is a security feature to prevent users executing set-user-ID and
+.\" set-group-ID programs from removable disk devices.)
.TP
.B MS_RDONLY
Mount file system read-only.
@@ -348,13 +348,13 @@ in more than one place, so specifying the device does not suffice).
The original MS_SYNC flag was renamed MS_SYNCHRONOUS in 1.1.69
when a different MS_SYNC was added to <mman.h>.
.LP
-Before Linux 2.4 an attempt to execute a set-UID or set-GID program
+Before Linux 2.4 an attempt to execute a set-user-ID or set-group-ID program
on a filesystem mounted with
.B MS_NOSUID
would fail with
.BR EPERM .
-Since Linux 2.4 the set-UID and set-GID bits are just silently ignored
-in this case.
+Since Linux 2.4 the set-user-ID and set-group-ID bits are
+just silently ignored in this case.
.\" The change is in patch-2.4.0-prerelease.
.SH "SEE ALSO"
.BR path_resolution (2),
diff --git a/man2/prctl.2 b/man2/prctl.2
index 636381caab..41feedf6ef 100644
--- a/man2/prctl.2
+++ b/man2/prctl.2
@@ -64,8 +64,8 @@ Set the state of the flag determining whether core dumps are produced
for this process upon delivery of a signal whose default behaviour is
to produce a core dump.
(Normally this flag is set for a process by default, but it is cleared
-when a set-UID or set-GID program is executed and also by various system
-calls that manipulate process UIDs and GIDs).
+when a set-user-ID or set-group-ID program is executed and also by
+various system calls that manipulate process UIDs and GIDs).
.I arg2
must be either 0 (process is not dumpable) or 1 (process is dumpable).
.TP
diff --git a/man2/ptrace.2 b/man2/ptrace.2
index 99cbca52f2..169a7bfaf0 100644
--- a/man2/ptrace.2
+++ b/man2/ptrace.2
@@ -248,8 +248,9 @@ The specified process cannot be traced. This could be because the
parent has insufficient privileges (the required capability is
.BR CAP_SYS_PTRACE );
non-root processes cannot trace processes that they
-cannot send signals to or those running setuid/setgid programs, for obvious
-reasons. Alternatively, the process may already be being traced, or be
+cannot send signals to or those running set-user-ID/set-group-ID programs,
+for obvious reasons.
+Alternatively, the process may already be being traced, or be
.BR init
(pid 1).
.TP
diff --git a/man2/setgid.2 b/man2/setgid.2
index 0a19c93883..10a70df437 100644
--- a/man2/setgid.2
+++ b/man2/setgid.2
@@ -41,7 +41,8 @@ superuser, the real and saved group ID's are also set.
Under Linux,
.B setgid
is implemented like the POSIX version with the _POSIX_SAVED_IDS feature.
-This allows a setgid program that is not suid root to drop all of its group
+This allows a set-group-ID program that is not set-user-ID-root root
+to drop all of its group
privileges, do some un-privileged work, and then re-engage the original
effective group ID in a secure manner.
.SH "RETURN VALUE"
diff --git a/man2/setuid.2 b/man2/setuid.2
index e7266b1fe3..2e066fa958 100644
--- a/man2/setuid.2
+++ b/man2/setuid.2
@@ -43,11 +43,11 @@ the real and saved user ID's are also set.
Under Linux,
.B setuid
is implemented like the POSIX version with the _POSIX_SAVED_IDS feature.
-This allows a setuid (other than root) program to drop all of its user
+This allows a set-user-ID (other than root) program to drop all of its user
privileges, do some un-privileged work, and then re-engage the original
effective user ID in a secure manner.
.PP
-If the user is root or the program is setuid root, special care must be
+If the user is root or the program is set-user-ID-root, special care must be
taken. The
.B setuid
function checks the effective user ID of the caller and if it is
@@ -56,7 +56,7 @@ the superuser, all process related user ID's are set to
After this has occurred, it is impossible for the program to regain root
privileges.
.PP
-Thus, a setuid-root program wishing to temporarily drop root
+Thus, a set-user-ID-root program wishing to temporarily drop root
privileges, assume the identity of a non-root user, and then regain
root privileges afterwards cannot use
.BR setuid .
diff --git a/man2/statvfs.2 b/man2/statvfs.2
index bd0c16eee6..bcaeef231c 100644
--- a/man2/statvfs.2
+++ b/man2/statvfs.2
@@ -80,7 +80,7 @@ Bits defined by POSIX are
Read-only file system.
.TP
.B ST_NOSUID
-Setuid/setgid bits are ignored by
+Set-user-ID/set-group-ID bits are ignored by
.BR exec (2).
.LP
diff --git a/man2/truncate.2 b/man2/truncate.2
index 6abdaa84b1..cd30ce64f6 100644
--- a/man2/truncate.2
+++ b/man2/truncate.2
@@ -69,7 +69,8 @@ the extended part reads as zero bytes.
The file pointer is not changed.
.LP
If the size changed, then the ctime and mtime fields for the file
-are updated, and suid and sgid mode bits may be cleared.
+are updated,
+and set-user-ID and set-group-ID permission bits may be cleared.
.LP
With
.BR ftruncate ,