diff options
| author | Michael Kerrisk | 2016-12-04 20:34:54 +0100 |
|---|---|---|
| committer | Karel Zak | 2016-12-09 13:45:09 +0100 |
| commit | aedd46f66ed5462c0e0193faa977a6dfef4fd0de (patch) | |
| tree | aa41e8c4ced3ee9cb1321eb00f0060c110ac78c1 /login-utils | |
| parent | docs: various pages: Format pathnames as italic (.I) (diff) | |
| download | kernel-qcow2-util-linux-aedd46f66ed5462c0e0193faa977a6dfef4fd0de.tar.gz kernel-qcow2-util-linux-aedd46f66ed5462c0e0193faa977a6dfef4fd0de.tar.xz kernel-qcow2-util-linux-aedd46f66ed5462c0e0193faa977a6dfef4fd0de.zip | |
docs: various pages: Use consistent terminology (set-user-ID and set-group-ID)
Use consistent terminology for set-user-ID and set-group-ID bits.
There's much inconsistency in the pages. "suid",
"set-user-identifier", "setuid". Stick with one terminology,
"set-user-ID" and set-grout-ID, as suggested in man-pages(7).
Signed-off-by: <mtk.man-pages@gmail.com>
Diffstat (limited to 'login-utils')
| -rw-r--r-- | login-utils/runuser.1 | 2 | ||||
| -rw-r--r-- | login-utils/su.1 | 3 |
2 files changed, 3 insertions, 2 deletions
diff --git a/login-utils/runuser.1 b/login-utils/runuser.1 index 04ce4ff01..e748b1ee5 100644 --- a/login-utils/runuser.1 +++ b/login-utils/runuser.1 @@ -24,7 +24,7 @@ does not ask for a password (because it may be executed by the root user only) a it uses a different PAM configuration. The command .B runuser -does not have to be installed with suid permissions. +does not have to be installed with set-user-ID permissions. .PP If the PAM session is not required then recommended solution is to use .BR setpriv (1) diff --git a/login-utils/su.1 b/login-utils/su.1 index 8685061ef..724755bdf 100644 --- a/login-utils/su.1 +++ b/login-utils/su.1 @@ -42,7 +42,8 @@ configured via PAM. .PP .B su is mostly designed for unprivileged users, the recommended solution for -privileged users (e.g. scripts executed by root) is to use non-suid command +privileged users (e.g. scripts executed by root) is to use +non-set-user-ID command .BR runuser (1) that does not require authentication and provide separate PAM configuration. If the PAM session is not required at all then the recommend solution is to use |