2
0
mirror of https://github.com/sudo-project/sudo.git synced 2025-08-22 09:57:41 +00:00

Some DIAGNOSTICS updates:

Update error message for when the user's uid does not exist in passwd.
Remove "This error indicates" and some other cosmetic cleanups.
This commit is contained in:
Todd C. Miller 2018-10-13 06:21:52 -06:00
parent fbf396e336
commit 75d9c6f165
3 changed files with 38 additions and 34 deletions

View File

@ -622,25 +622,26 @@ DDIIAAGGNNOOSSTTIICCSS
information. information.
effective uid is not 0, is sudo installed setuid root? effective uid is not 0, is sudo installed setuid root?
This error indicates that ssuuddoo was not run with root privileges. ssuuddoo was not run with root privileges. The ssuuddoo binary must be
The ssuuddoo binary must be owned by the root user and have the Set- owned by the root user and have the Set-user-ID bit set. Also, it
user-ID bit set. Also, it must not be located on a file system must not be located on a file system mounted with the `nosuid'
mounted with the `nosuid' option or on an NFS file system that maps option or on an NFS file system that maps uid 0 to an unprivileged
uid 0 to an unprivileged uid. uid.
effective uid is not 0, is sudo on a file system with the 'nosuid' option effective uid is not 0, is sudo on a file system with the 'nosuid' option
set or an NFS file system without root privileges? set or an NFS file system without root privileges?
This error indicates that the ssuuddoo binary has the proper owner and ssuuddoo was not run with root privileges. The ssuuddoo binary has the
permissions but it still did not run with root privileges. The proper owner and permissions but it still did not run with root
most common reason for this is that the file system the ssuuddoo binary privileges. The most common reason for this is that the file
is located on is mounted with the `nosuid' option or it is an NFS system the ssuuddoo binary is located on is mounted with the `nosuid'
file system that maps uid 0 to an unprivileged uid. option or it is an NFS file system that maps uid 0 to an
unprivileged uid.
fatal error, unable to load plugins fatal error, unable to load plugins
An error occurred while loading or initializing the plugins An error occurred while loading or initializing the plugins
specified in sudo.conf(4). specified in sudo.conf(4).
invalid environment variable name: foo=bar invalid environment variable name
One or more environment variable names specified via the --EE option One or more environment variable names specified via the --EE option
contained an equal sign (`='). The arguments to the --EE option contained an equal sign (`='). The arguments to the --EE option
should be environment variable names without an associated value. should be environment variable names without an associated value.
@ -663,9 +664,9 @@ DDIIAAGGNNOOSSTTIICCSS
to store its intermediate files. to store its intermediate files.
sudo must be owned by uid 0 and have the setuid bit set sudo must be owned by uid 0 and have the setuid bit set
This error indicates that the ssuuddoo binary does not have the correct ssuuddoo was not run with root privileges. The ssuuddoo binary does not
owner or permissions. It must be owned by the root user and have have the correct owner or permissions. It must be owned by the
the Set-user-ID bit set. root user and have the Set-user-ID bit set.
sudoedit is not supported on this platform sudoedit is not supported on this platform
It is only possible to run ssuuddooeeddiitt on systems that support setting It is only possible to run ssuuddooeeddiitt on systems that support setting
@ -675,9 +676,8 @@ DDIIAAGGNNOOSSTTIICCSS
The user did not enter a password before the password timeout (5 The user did not enter a password before the password timeout (5
minutes by default) expired. minutes by default) expired.
unknown uid UID: who are you? you do not exist in the passwd database
ssuuddoo was unable to look up the invoking user's ID in the password Your user ID does not appear in the system passwd database.
database.
you may not specify environment variables in edit mode you may not specify environment variables in edit mode
It is only possible to specify environment variables when running a It is only possible to specify environment variables when running a
@ -736,4 +736,4 @@ DDIISSCCLLAAIIMMEERR
file distributed with ssuuddoo or https://www.sudo.ws/license.html for file distributed with ssuuddoo or https://www.sudo.ws/license.html for
complete details. complete details.
Sudo 1.8.26 October 8, 2018 Sudo 1.8.26 Sudo 1.8.26 October 13, 2018 Sudo 1.8.26

View File

@ -20,7 +20,7 @@
.\" Agency (DARPA) and Air Force Research Laboratory, Air Force .\" Agency (DARPA) and Air Force Research Laboratory, Air Force
.\" Materiel Command, USAF, under agreement number F39502-99-1-0512. .\" Materiel Command, USAF, under agreement number F39502-99-1-0512.
.\" .\"
.TH "SUDO" "8" "October 8, 2018" "Sudo @PACKAGE_VERSION@" "System Manager's Manual" .TH "SUDO" "8" "October 13, 2018" "Sudo @PACKAGE_VERSION@" "System Manager's Manual"
.nh .nh
.if n .ad l .if n .ad l
.SH "NAME" .SH "NAME"
@ -1234,7 +1234,6 @@ sudoers(@mansectform@)
for more information. for more information.
.TP 6n .TP 6n
\fReffective uid is not 0, is sudo installed setuid root?\fR \fReffective uid is not 0, is sudo installed setuid root?\fR
This error indicates that
\fBsudo\fR \fBsudo\fR
was not run with root privileges. was not run with root privileges.
The The
@ -1245,7 +1244,9 @@ Also, it must not be located on a file system mounted with the
option or on an NFS file system that maps uid 0 to an unprivileged uid. option or on an NFS file system that maps uid 0 to an unprivileged uid.
.TP 6n .TP 6n
\fReffective uid is not 0, is sudo on a file system with the 'nosuid' option set or an NFS file system without root privileges?\fR \fReffective uid is not 0, is sudo on a file system with the 'nosuid' option set or an NFS file system without root privileges?\fR
This error indicates that the \fBsudo\fR
was not run with root privileges.
The
\fBsudo\fR \fBsudo\fR
binary has the proper owner and permissions but it still did not run binary has the proper owner and permissions but it still did not run
with root privileges. with root privileges.
@ -1259,7 +1260,7 @@ option or it is an NFS file system that maps uid 0 to an unprivileged uid.
An error occurred while loading or initializing the plugins specified in An error occurred while loading or initializing the plugins specified in
sudo.conf(@mansectform@). sudo.conf(@mansectform@).
.TP 6n .TP 6n
\fRinvalid environment variable name: foo=bar\fR \fRinvalid environment variable name\fR
One or more environment variable names specified via the One or more environment variable names specified via the
\fB\-E\fR \fB\-E\fR
option contained an equal sign option contained an equal sign
@ -1295,7 +1296,9 @@ was unable to find a usable temporary directory in which to store its
intermediate files. intermediate files.
.TP 6n .TP 6n
\fRsudo must be owned by uid 0 and have the setuid bit set\fR \fRsudo must be owned by uid 0 and have the setuid bit set\fR
This error indicates that the \fBsudo\fR
was not run with root privileges.
The
\fBsudo\fR \fBsudo\fR
binary does not have the correct owner or permissions. binary does not have the correct owner or permissions.
It must be owned by the root user and have the Set-user-ID bit set. It must be owned by the root user and have the Set-user-ID bit set.
@ -1309,9 +1312,8 @@ on systems that support setting the effective user-ID.
The user did not enter a password before the password timeout The user did not enter a password before the password timeout
(5 minutes by default) expired. (5 minutes by default) expired.
.TP 6n .TP 6n
\fRunknown uid UID: who are you?\fR \fRyou do not exist in the passwd database\fR
\fBsudo\fR Your user ID does not appear in the system passwd database.
was unable to look up the invoking user's ID in the password database.
.TP 6n .TP 6n
\fRyou may not specify environment variables in edit mode\fR \fRyou may not specify environment variables in edit mode\fR
It is only possible to specify environment variables when running It is only possible to specify environment variables when running

View File

@ -19,7 +19,7 @@
.\" Agency (DARPA) and Air Force Research Laboratory, Air Force .\" Agency (DARPA) and Air Force Research Laboratory, Air Force
.\" Materiel Command, USAF, under agreement number F39502-99-1-0512. .\" Materiel Command, USAF, under agreement number F39502-99-1-0512.
.\" .\"
.Dd October 8, 2018 .Dd October 13, 2018
.Dt SUDO @mansectsu@ .Dt SUDO @mansectsu@
.Os Sudo @PACKAGE_VERSION@ .Os Sudo @PACKAGE_VERSION@
.Sh NAME .Sh NAME
@ -1125,7 +1125,6 @@ option in
.Xr sudoers @mansectform@ .Xr sudoers @mansectform@
for more information. for more information.
.It Li effective uid is not 0, is sudo installed setuid root? .It Li effective uid is not 0, is sudo installed setuid root?
This error indicates that
.Nm .Nm
was not run with root privileges. was not run with root privileges.
The The
@ -1135,7 +1134,9 @@ Also, it must not be located on a file system mounted with the
.Sq nosuid .Sq nosuid
option or on an NFS file system that maps uid 0 to an unprivileged uid. option or on an NFS file system that maps uid 0 to an unprivileged uid.
.It Li effective uid is not 0, is sudo on a file system with the 'nosuid' option set or an NFS file system without root privileges? .It Li effective uid is not 0, is sudo on a file system with the 'nosuid' option set or an NFS file system without root privileges?
This error indicates that the .Nm
was not run with root privileges.
The
.Nm .Nm
binary has the proper owner and permissions but it still did not run binary has the proper owner and permissions but it still did not run
with root privileges. with root privileges.
@ -1147,7 +1148,7 @@ option or it is an NFS file system that maps uid 0 to an unprivileged uid.
.It Li fatal error, unable to load plugins .It Li fatal error, unable to load plugins
An error occurred while loading or initializing the plugins specified in An error occurred while loading or initializing the plugins specified in
.Xr sudo.conf @mansectform@ . .Xr sudo.conf @mansectform@ .
.It Li invalid environment variable name: foo=bar .It Li invalid environment variable name
One or more environment variable names specified via the One or more environment variable names specified via the
.Fl E .Fl E
option contained an equal sign option contained an equal sign
@ -1179,7 +1180,9 @@ environment variable.
was unable to find a usable temporary directory in which to store its was unable to find a usable temporary directory in which to store its
intermediate files. intermediate files.
.It Li sudo must be owned by uid 0 and have the setuid bit set .It Li sudo must be owned by uid 0 and have the setuid bit set
This error indicates that the .Nm
was not run with root privileges.
The
.Nm .Nm
binary does not have the correct owner or permissions. binary does not have the correct owner or permissions.
It must be owned by the root user and have the Set-user-ID bit set. It must be owned by the root user and have the Set-user-ID bit set.
@ -1190,9 +1193,8 @@ on systems that support setting the effective user-ID.
.It Li timed out reading password .It Li timed out reading password
The user did not enter a password before the password timeout The user did not enter a password before the password timeout
(5 minutes by default) expired. (5 minutes by default) expired.
.It Li unknown uid UID: who are you? .It Li you do not exist in the passwd database
.Nm Your user ID does not appear in the system passwd database.
was unable to look up the invoking user's ID in the password database.
.It Li you may not specify environment variables in edit mode .It Li you may not specify environment variables in edit mode
It is only possible to specify environment variables when running It is only possible to specify environment variables when running
a command. a command.