Since the last update, translations have been added but the additional files
have not been included into PLIST. The build failed in such a case:
PKG_OPTIONS.sudo= +nls
PKG_DEVELOPER= yes
* Fixed a bug introduced in version 1.8.21 which prevented sudo
from using the PAM-supplied prompt. Bug 799
* Fixed a bug introduced in version 1.8.21 which could result in
sudo hanging when running commands that exit quickly. Bug 800
* Fixed a bug introduced in version 1.8.21 which prevented the
command from being run when the password was read via an external
program using the askpass interface. Bug 801
What's new in Sudo 1.8.21p1
* On systems that support both PAM and SIGINFO, the main sudo
process will no longer forward SIGINFO to the command if the
signal was generated from the keyboard. The command will have
already received SIGINFO since it is part of the same process
group so there's no need for sudo to forward it. This is
consistent with the handling of SIGINT, SIGQUIT and SIGTSTP.
Bug 796
* If SUDOERS_SEARCH_FILTER in ldap.conf does not specify a value,
the LDAP search expression used when looking up netgroups and
non-Unix groups had a syntax error if a group plugin was not
specified.
* "sudo -U otheruser -l" will now have an exit value of 0 even
if "otheruser" has no sudo privileges. The exit value when a
user attempts to lists their own privileges or when a command
is specified is unchanged.
* Fixed a regression introduced in sudo 1.8.21 where sudoreplay
playback would hang for I/O logs that contain terminal input.
* Sudo 1.8.18 contained an incomplete fix for the matching of
entries in the LDAP and SSSD backends when a sudoRunAsGroup is
specified but no sudoRunAsUser is present in the sudoRole.
What's new in Sudo 1.8.21
* The path that sudo uses to search for terminal devices can now
be configured via the new "devsearch" Path setting in sudo.conf.
* It is now possible to preserve bash shell functions in the
environment when the "env_reset" sudoers setting is disabled by
removing the "*=()*" pattern from the env_delete list.
* A change made in sudo 1.8.15 inadvertantly caused sudoedit to
send itself SIGHUP instead of exiting when the editor returns
an error or the file was not modified.
* Sudoedit now uses an exit code of zero if the file was not
actually modified. Previously, sudoedit treated a lack of
modifications as an error.
* When running a command in a pseudo-tty (pty), sudo now copies a
subset of the terminal flags to the new pty. Previously, all
flags were copied, even those not appropriate for a pty.
* Fixed a problem with debug logging in the sudoers I/O logging
plugin.
* Window size change events are now logged to the policy plugin.
On xterm and compatible terminals, sudoreplay is now capable of
resizing the terminal to match the size of the terminal the
command was run on. The new -R option can be used to disable
terminal resizing.
* Fixed a bug in visudo where a newly added file was not checked
for syntax errors. Bug 791.
* Fixed a bug in visudo where if a syntax error in an include
directory (like /etc/sudoers.d) was detected, the edited version
was left as a temporary file instead of being installed.
* On PAM systems, sudo will now treat "username's Password:" as
a standard password prompt. As a result, the SUDO_PROMPT
environment variable will now override "username's Password:"
as well as the more common "Password:". Previously, the
"passprompt_override" Defaults setting would need to be set for
SUDO_PROMPT to override a prompt of "username's Password:".
* A new "syslog_pid" sudoers setting has been added to include
sudo's process ID along with the process name when logging via
syslog. Bug 792.
* Fixed a bug introduced in sudo 1.8.18 where a command would
not be terminated when the I/O logging plugin returned an error
to the sudo front-end.
* A new "timestamp_type" sudoers setting has been added that replaces
the "tty_tickets" option. In addition to tty and global time stamp
records, it is now possible to use the parent process ID to restrict
the time stamp to commands run by the same process, usually the shell.
Bug 793.
* The --preserve-env command line option has been extended to accept
a comma-separated list of environment variables to preserve.
Bug 279.
* Friulian translation for sudo from translationproject.org.
upstream changelog:
2017-05-31 Todd C. Miller <Todd.Miller@courtesan.com>
* NEWS, configure, configure.ac:
Sudo 1.8.20p2
[47836f4c9834]
* src/ttyname.c:
A command name may also contain newline characters so read
/proc/self/stat until EOF. It is not legal for /proc/self/stat to
contain embedded NUL bytes so treat the file as corrupt if we see
any. With help from Qualys.
This is not exploitable due to the /dev traversal changes in sudo
1.8.20p1 (thanks Solar!).
[15a46f4007dd]
2017-05-30 Todd C. Miller <Todd.Miller@courtesan.com>
* src/ttyname.c:
Use /proc/self consistently on Linux. As far as I know, only AIX
doesn't support /proc/self.
[6f3d9816541b]
Fixes CVE-2017-1000367, local privilege escalation on linux.
What's new in Sudo 1.8.20p1
* Fixed "make check" when using OpenSSL or GNU crypt.
Bug #787.
* Fixed CVE-2017-1000367, a bug parsing /proc/pid/stat on Linux
when the process name contains spaces. Since the user has control
over the command name, this could potentially be used by a user
with sudo access to overwrite an arbitrary file on systems with
SELinux enabled. Also stop performing a breadth-first traversal
of /dev when looking for the device; only a hard-coded list of
directories are checked,
What's new in Sudo 1.8.20
* Added support for SASL_MECH in ldap.conf. Bug #764
* Added support for digest matching when the command is a glob-style
pattern or a directory. Previously, only explicit path matches
supported digest checks.
* New "fdexec" Defaults option to control whether a command
is executed by path or by open file descriptor.
* The embedded copy of zlib has been upgraded to version 1.2.11.
* Fixed a bug that prevented sudoers include files with a relative
path starting with the letter 'i' from being opened. Bug #776.
* Added support for command timeouts in sudoers. The command will
be terminated if the timeout expires.
* The SELinux role and type are now displayed in the "sudo -l"
output for the LDAP and SSSD backends, just as they are in the
sudoers backend.
* A new command line option, -T, can be used to specify a command
timeout as long as the user-specified timeout is not longer than
the timeout specified in sudoers. This option may only be
used when the "user_command_timeouts" flag is enabled in sudoers.
* Added NOTBEFORE and NOTAFTER command options to the sudoers
backend similar to what is already available in the LDAP backend.
* Sudo can now optionally use the SHA2 functions in OpenSSL or GNU
crypt instead of the SHA2 implementation bundled with sudo.
* Fixed a compilation error on systems without the stdbool.h header
file. Bug #778.
* Fixed a compilation error in the standalone Kerberos V authentication
module. Bug #777.
* Added the iolog_flush flag to sudoers which causes I/O log data
to be written immediately to disk instead of being buffered.
* I/O log files are now created with group ID 0 by default unless
the "iolog_user" or "iolog_group" options are set in sudoers.
* It is now possible to store I/O log files on an NFS-mounted
file system where uid 0 is remapped to an unprivileged user.
The "iolog_user" option must be set to a non-root user and the
top-level I/O log directory must exist and be owned by that user.
* Added the restricted_env_file setting to sudoers which is similar
to env_file but its contents are subject to the same restrictions
as variables in the invoking user's environment.
* Fixed a use after free bug in the SSSD backend when the fqdn
sudoOption is enabled and no hostname value is present in
/etc/sssd/sssd.conf.
* Fixed a typo that resulted in a compilation error on systems
where the killpg() function is not found by configure.
* Fixed a compilation error with the included version of zlib
when sudo was built outside the source tree.
* Fixed the exit value of sudo when the command is terminated by
a signal other than SIGINT. This was broken in sudo 1.8.15 by
the fix for Bug #722. Bug #784.
* Fixed a regression introduced in sudo 1.8.18 where the "lecture"
option could not be used in a positive boolean context, only
a negative one.
* Fixed an issue where sudo would consume stdin if it was not
connected to a tty even if log_input is not enabled in sudoers.
Bug #786.
* Clarify in the sudoers manual that the #includedir directive
diverts control to the files in the specified directory and,
when parsing of those files is complete, returns control to the
original file. Bug #775.
What's new in Sudo 1.8.19p2
* Fixed a crash in visudo introduced in sudo 1.8.9 when an IP address
or network is used in a host-based Defaults entry. Bug #766
* Added a missing check for the ignore_iolog_errors flag when
the sudoers plugin generates the I/O log file path name.
* Fixed a typo in sudo's vsyslog() replacement that resulted in
garbage being logged to syslog.
What's new in Sudo 1.8.19p1
* Fixed a bug introduced in sudo 1.8.19 that resulted in the wrong
syslog priority and facility being used.
What's new in Sudo 1.8.19
* New "syslog_maxlen" Defaults option to control the maximum size of
syslog messages generated by sudo.
* Sudo has been run against PVS-Studio and any issues that were
not false positives have been addressed.
* I/O log files are now created with the same group ID as the
parent directory and not the invoking user's group ID.
* I/O log permissions and ownership are now configurable via the
"iolog_mode", "iolog_user" and "iolog_group" sudoers Defaults
variables.
* Fixed configuration of the sudoers I/O log plugin debug subsystem.
Previously, I/O log information was not being written to the
sudoers debug log.
* Fixed a bug in visudo that broke editing of files in an include
dir that have a syntax error. Normally, visudo does not edit
those files, but if a syntax error is detected in one, the user
should get a chance to fix it.
* Warnings about unknown or unparsable sudoers Defaults entries now
include the file and line number of the problem.
* Visudo will now use the file and line number information about an
unknown or unparsable Defaults entry to go directly to the file
with the problem.
* Fixed a bug in the sudoers LDAP back-end where a negated sudoHost
entry would prevent other sudoHost entries following it from matching.
* Warnings from visudo about a cycle in an Alias entry now include the
file and line number of the problem.
* In strict mode, visudo will now use the file and line number
information about a cycle in an Alias entry to go directly to the
file with the problem.
* The sudo_noexec.so file is now linked with -ldl on systems that
require it for the wordexp() wrapper.
* Fixed linking of sudo_noexec.so on macOS systems where it must be
a dynamic library and not a module.
* Sudo's "make check" now includes a test for sudo_noexec.so
working.
* The sudo front-end now passes the user's umask to the plugin.
Previously the plugin had to determine this itself.
* Sudoreplay can now display the stdin and ttyin streams when they
are explicitly added to the filter list.
* Fixed a bug introduced in sudo 1.8.17 where the "all" setting
for verifypw and listpw was not being honored. Bug #762.
* The syslog priority (syslog_goodpri and syslog_badpri) can now
be negated or set to "none" to disable logging of successful or
unsuccessful sudo attempts via syslog.
What's new in Sudo 1.8.18p1
* When sudo_noexec.so is used, the WRDE_NOCMD flag is now added
if the wordexp() function is called. This prevents commands
from being run via wordexp() without disabling it entirely.
* On Linux systems, sudo_noexec.so now uses a seccomp filter to
disable execute access if the kernel supports seccomp. This is
more robust than the traditional method of using stub functions
that return an error.
What's new in Sudo 1.8.18
* The sudoers locale is now set before parsing the sudoers file.
If sudoers_locale is set in sudoers, it is applied before
evaluating other Defaults entries. Previously, sudoers_locale
was used when evaluating sudoers but not during the inital parse.
Bug #748.
* A missing or otherwise invalid #includedir is now ignored instead
of causing a parse error.
* During "make install", backup files are only used on HP-UX where
it is not possible to unlink a shared object that is in use.
This works around a bug in ldconfig on Linux which could create
links to the backup shared library file instead of the current
one.
* Fixed a bug introduced in 1.8.17 where sudoers entries with long
commands lines could be truncated, preventing a match. Bug #752.
* The fqdn, runas_default and sudoers_locale Defaults settings are
now applied before any other Defaults settings since they can
change how other Defaults settings are parsed.
* On systems without the O_NOFOLLOW open(2) flag, when the NOFOLLOW
flag is set, sudoedit now checks whether the file is a symbolic link
before opening it as well as after the open. Bug #753.
* Sudo will now only resolve a user's group IDs to group names
when sudoers includes group-based permissions. Group lookups
can be expensive on some systems where the group database is
not local.
* If the file system holding the sudo log file is full, allow
the command to run unless the new ignore_logfile_errors Defaults
option is disabled. Bug #751.
* The ignore_audit_errors and ignore_iolog_errors Defaults options
have been added to control sudo's behavior when it is unable to
write to the audit and I/O logs.
* Fixed a bug introduced in 1.8.17 where the SIGPIPE signal handler
was not being restored when sudo directly executes the command.
* Fixed a bug where "sudo -l command" would indicate that a command
was runnable even when denied by sudoers when using the LDAP or
SSSD backends.
* The match_group_by_gid Defaults option has been added to allow
sites where group name resolution is slow and where sudoers only
contains a small number of groups to match groups by group ID
instead of by group name.
* Fixed a bug on Linux where a 32-bit sudo binary could fail with
an "unable to allocate memory" error when run on a 64-bit system.
Bug #755
* When parsing ldap.conf, sudo will now only treat a '#' character
as the start of a comment when it is at the beginning of the
line.
* Fixed a potential crash when auditing is enabled and the audit
function fails with an error. Bug #756
* Norwegian Nynorsk translation for sudo from translationproject.org.
* Fixed a typo that broke short host name matching when the fqdn
flag is enabled in sudoers. Bug #757
* Negated sudoHost attributes are now supported by the LDAP and
SSSD backends.
* Fixed matching entries in the LDAP and SSSD backends when a
RunAsGroup is specified but no RunAsUser is present.
* Fixed "sudo -l" output in the LDAP and SSSD backends when a
RunAsGroup is specified but no RunAsUser is present.
MASTER_SITES= site1 \
site2
style continuation lines to be simple repeated
MASTER_SITES+= site1
MASTER_SITES+= site2
lines. As previewed on tech-pkg. With thanks to rillig for fixing pkglint
accordingly.
What's new in Sudo 1.8.17p1
* Fixed a bug introduced in 1.8.17 where the user's groups were
not set on systems that don't use PAM. Bug #749.
What's new in Sudo 1.8.17
* On AIX, if /etc/security/login.cfg has auth_type set to PAM_AUTH
but pam_start(3) fails, fall back to AIX authentication.
Bug #740.
* Sudo now takes all sudoers sources into account when determining
whether or not "sudo -l" or "sudo -b" should prompt for a password.
In other words, if both file and ldap sudoers sources are in
specified in /etc/nsswitch.conf, "sudo -v" will now require that
all entries in both sources be have NOPASSWD (file) or !authenticate
(ldap) in the entries.
* Sudo now ignores SIGPIPE until the command is executed. Previously,
SIGPIPE was only ignored in a few select places. Bug #739.
* Fixed a bug introduced in sudo 1.8.14 where (non-syslog) log
file entries were missing the newline when loglinelen is set to
a non-positive number. Bug #742.
* Unix groups are now set before the plugin session intialization
code is run. This makes it possible to use dynamic groups with
the Linux-PAM pam_group module.
* Fixed a bug where a debugging statement could dereference a NULL
pointer when looking up a group that doesn't exist. Bug #743.
* Sudo has been run through the Coverity code scanner. A number of
minor bugs have been fixed as a result. None were security issues.
* SELinux support, which was broken in 1.8.16, has been repaired.
* Fixed a bug when logging I/O where all output buffers might not
get flushed at exit.
* Forward slashes are no longer escaped in the JSON output of
"visudo -x". This was never required by the standard and not
escaping them improves readability of the output.
* Sudo no longer treats PAM_SESSION_ERR as a fatal error when
opening the PAM session. Other errors from pam_open_session()
are still treated as fatal. This avoids the "policy plugin
failed session initialization" error message seen on some systems.
* Korean translation for sudo and sudoers from translationproject.org.
* Fixed a bug on AIX where the stack size hard resource limit was
being set to 2GB instead of 4GB on 64-bit systems.
* The SSSD backend now properly supports "sudo -U otheruser -l".
* The SSSD backend now uses the value of "ipa_hostname"
from sssd.conf, if specified, when matching the host name.
* Fixed a hang on some systems when the command is being run in
a pty and it failed to execute.
* When performing a wildcard match in sudoers, check for an exact
string match if the user command was fully-qualified (or resolved
via the PATH). This fixes an issue executing scripts on Linux
when there are multiple wildcard matches with the same base name.
Bug #746.
What's new in Sudo 1.8.16
* Fixed a compilation error on Solaris 10 with Stun Studio 12.
Bug #727.
* When preserving variables from the invoking user's environment, if
there are duplicates sudo now only keeps the first instance.
* Fixed a bug that could cause warning mail to be sent in list
mode (sudo -l) for users without sudo privileges when the
LDAP and sssd backends are used.
* Fixed a bug that prevented the "mail_no_user" option from working
properly with the LDAP backend.
* In the LDAP and sssd backends, white space is now ignored between
an operator (!, +, +=, -=) when parsing a sudoOption.
* It is now possible to disable Path settings in sudo.conf
by omitting the path name.
* The sudoedit_checkdir Defaults option is now enabled by default
and has been extended. When editing files with sudoedit, each
directory in the path to be edited is now checked. If a directory
is writable by the invoking user, symbolic links will not be
followed. If the parent directory of the file to be edited is
writable, sudoedit will refuse to edit it.
Bug #707.
* The netgroup_tuple Defaults option has been added to enable matching
of the entire netgroup tuple, not just the host or user portion.
Bug #717.
* When matching commands based on the SHA2 digest, sudo will now
use fexecve(2) to execute the command if it is available. This
fixes a time of check versus time of use race condition when the
directory holding the command is writable by the invoking user.
* On AIX systems, sudo now caches the auth registry string along
with password and group information. This fixes a potential
problem when a user or group of the same name exists in multiple
auth registries. For example, local and LDAP.
* Fixed a crash in the SSSD backend when the invoking user is not
found. Bug #732.
* Added the --enable-asan configure flag to enable address sanitizer
support. A few minor memory leaks have been plugged to quiet
the ASAN leak detector.
* The value of _PATH_SUDO_CONF may once again be overridden via
the Makefile. Bug #735.
* The sudoers2ldif script now handles multiple roles with same name.
* Fixed a compilation error on systems that have the posix_spawn()
and posix_spawnp() functions but an unusable spawn.h header.
Bug #730.
* Fixed support for negating character classes in sudo's version
of the fnmatch() function.
* Fixed a bug in the LDAP and SSSD backends that could allow an
unauthorized user to list another user's privileges. Bug #738.
* The PAM conversation function now works around an ambiguity in the
PAM spec with respect to multiple messages. Bug #726.
sudoedit.
Note that it's a fairly large step and the package has only been tested
on NetBSD and there may be further breakage.
Testing on non-NetBSD would be appreciated.
Upstream changelog:
Major changes between version 1.8.15 and 1.8.14p3:
Fixed a bug that prevented sudo from building outside the source
tree on some platforms. Bug #708.
Fixed the location of the sssd library in the RHEL/Centos
packages. Bug #710.
Fixed a build problem on systems that don't implicitly include
sys/types.h from other header files. Bug #711.
Fixed a problem on Linux using containers where sudo would
ignore signals sent by a process in a different container.
Sudo now refuses to run a command if the PAM session module
returns an error.
When editing files with sudoedit, symbolic links will no longer
be followed by default. The old behavior can be restored by
enabling the sudoedit_follow option in sudoers or on a per-command
basis with the FOLLOW and NOFOLLOW tags. Bug #707.
Fixed a bug introduced in version 1.8.14 that caused the last
valid editor in the sudoers "editor" list to be used by visudo
and sudoedit instead of the first. Bug #714.
Fixed a bug in visudo that prevented the addition of a final
newline to edited files without one.
Fixed a bug decoding certain base64 digests in sudoers when
the intermediate format included a '=' character.
Individual records are now locked in the time stamp file instead
of the entire file. This allows sudo to avoid prompting for a
password multiple times on the same terminal when used in a
pipeline. In other words, sudo cat foo | sudo grep bar now only
prompts for the password once. Previously, both sudo processes
would prompt for a password, often making it impossible to
enter. Bug #705.
Fixed a bug where sudo would fail to run commands as a non-root
user on systems that lack both setresuid() and setreuid().
Bug #713.
Fixed a bug introduced in sudo 1.8.14 that prevented visudo
from re-editing the correct file when a syntax error was
detected.
Fixed a bug where sudo would not relay a SIGHUP signal to the
command when the terminal is closed and the command is not run
in its own pseudo-tty. Bug #719.
If some, but not all, of the LOGNAME, USER or USERNAME environment
variables have been preserved from the invoking user's
environment, sudo will now use the preserved value to set the
remaining variables instead of using the runas user. This
ensures that if, for example, only LOGNAME is present in the
env_keep list, that sudo will not set USER and USERNAME to the
runas user.
When the command sudo is running dies due to a signal, sudo
will now send itself that same signal with the default signal
handler installed instead of exiting. The bash shell appears
to ignore some signals, e.g. SIGINT, unless the command being
run is killed by that signal. This makes the behavior of commands
run under sudo the same as without sudo when bash is the shell.
Bug #722.
Slovak translation for sudo from translationproject.org.
Hungarian and Slovak translations for sudoers from
translationproject.org. Previously, when env_reset was enabled
(the default) and the -s option was not used, the SHELL
environment variable was set to the shell of the invoking user.
Now, when env_reset is enabled and the -s option is not used,
SHELL is set based on the target user.
Fixed challenge/response style BSD authentication.
Added the sudoedit_checkdir Defaults option to prevent sudoedit
from editing files located in a directory that is writable by
the invoking user.
Added the always_query_group_plugin Defaults option to control
whether groups not found in the system group database are passed
to the group plugin. Previously, unknown system groups were
always passed to the group plugin.
When creating a new file, sudoedit will now check that the
file's parent directory exists before running the editor.
Fixed the compiler stack protector test in configure for
compilers that support -fstack-protector but don't actually
have the ssp library available.
Major changes between version 1.8.14p3 and 1.8.14p2:
Fixed a bug introduced in sudo 1.8.14p2 that prevented sudo
from working when no tty was present. Bug #706.
Fixed tty detection on newer AIX systems where dev_t is 64-bit.
Major changes between version 1.8.14p2 and 1.8.14p1:
Fixed a bug introduced in sudo 1.8.14 that prevented the lecture
file from being created. Bug #704.
Major changes between version 1.8.14p1 and 1.8.14:
Fixed a bug introduced in sudo 1.8.14 that prevented the sssd
backend from working. Bug #703.
Major changes between version 1.8.14 and 1.8.13:
Log messages on Mac OS X now respect sudoers_locale when sudo
is build with NLS support.
The sudo manual pages now pass mandoc -Tlint with no warnings.
Fixed a compilation problem on systems with the sig2str()
function that do not define SIG2STR_MAX in signal.h.
Worked around a compiler bug that resulted in unexpected behavior
when returning an int from a function declared to return bool
without an explicit cast.
Worked around a bug in Mac OS X 10.10 BSD auditing where the
au_preselect() fails for AUE_sudo events but succeeds for
AUE_DARWIN_sudo.
Fixed a hang on Linux systems with glibc when sudo is linked
with jemalloc.
When the user runs a command as a user ID that is not present
in the password database via the -u flag, the command is now
run with the group ID of the invoking user instead of group ID 0.
Fixed a compilation problem on systems that don't pull in
definitions of uid_t and gid_t without sys/types.h or unistd.h.
Fixed a compilation problem on newer AIX systems which use a
struct st_timespec for time stamps in struct stat that differs
from struct timespec. Bug #702.
The example directory is now configurable via --with-exampledir
and defaults to DATAROOTDIR/examples/sudo on BSD systems.
The /usr/lib/tmpfiles.d/sudo.conf file is now installed as part
of "make install" when systemd is in use.
Fixed a linker problem on some systems with libintl. Bug #690.
Fixed compilation with compilers that don't support __func__
or __FUNCTION__.
Sudo no longer needs to uses weak symbols to support localization
in the warning functions. A registration function is used
instead.
Fixed a setresuid() failure in sudoers on Linux kernels where
uid changes take the nproc resource limit into account.
Fixed LDAP netgroup queries on AIX.
Sudo will now display the custom prompt on Linux systems with
PAM even if the "Password: " prompt is not localized by the
PAM module. Bug #701.
Double-quoted values in an LDAP sudoOption are now supported
for consistency with file-based sudoers.
Fixed a bug that prevented the btime entry in /proc/stat from
being parsed on Linux.
Major changes between version 1.8.13 and 1.8.12:
The examples directory is now a subdirectory of the doc dir to
conform to Debian guidelines. Bug #682.
Fixed a compilation error for siglist.c and signame.c on some
systems. Bug #686.
Weak symbols are now used for sudo_warn_gettext() and
sudo_warn_strerror() in libsudo_util to avoid link errors when
-Wl,--no-undefined is used in LDFLAGS. The --disable-weak-symbols
configure option can be used to disable the user of weak symbols.
Fixed a bug in sudo's mkstemps() replacement function that
prevented the file extension from being preserved in sudoedit.
A new mail_all_cmnds sudoers flag will send mail when a user
runs a command (or tries to). The behavior of the mail_always
flag has been restored to always send mail when sudo is run.
New MAIL and NOMAIL command tags have been added to toggle mail
sending behavior on a per-command (or Cmnd_Alias) basis.
Fixed matching of empty passwords when sudo is configured to
use passwd (or shadow) file authentication on systems where
the crypt() function returns NULL for invalid salts.
On AIX, sudo now uses the value of the auth_type setting in
/etc/security/login.cfg to determine whether to use LAM or PAM
for user authentication.
The all setting for listpw and verifypw now works correctly
with LDAP and sssd sudoers.
The sudo timestamp directory is now created at boot time on
platforms that use systemd.
Sudo will now restore the value of the SIGPIPE handler before
executing the command.
Sudo now uses struct timespec instead of struct timeval for
time keeping when possible. If supported, sudoedit and visudo
now use nanosecond granularity time stamps.
Fixed a symbol name collision with systems that have their own
SHA2 implementation. This fixes a problem where PAM could use
the wrong SHA2 implementation on Solaris 10 systems configured
to use SHA512 for passwords.
The editor invoked by sudoedit once again uses an unmodified
copy of the user's environment as per the documentation. This
was inadvertantly changed in sudo 1.8.0. Bug #688.
Major changes between version 1.8.12 and 1.8.11p2:
The embedded copy of zlib has been upgraded to version 1.2.8
and is now installed as a shared library where supported.
Debug settings for the sudo front end and sudoers plugin are
now configured separately.
Multiple sudo.conf Debug entries may now be specified per
program (or plugin).
The plugin API has been extended such that the path to the
plugin that was loaded is now included in the settings array.
This path can be used to register with the debugging subsystem.
The debug_flags setting is now prefixed with a file name and
may be specified multiple times if there is more than one
matching Debug setting in sudo.conf.
The sudoers regression tests now run with the locale set to C
since some of the tests compare output that includes
locale-specific messages. Bug #672.
Fixed a bug where sudo would not run commands on Linux when
compiled with audit support if audit is disabled. Bug #671.
Added __BASH_FUNC< to the environment blacklist to match Apple's
syntax for newer-style bash functions.
The default password prompt now includes a trailing space after
"Password:" for consistency with su(1) on most systems. Bug
#663.
Fixed a problem on DragonFly BSD where SIGCHLD could be ignored,
preventing sudo from exiting. Bug #676.
Visudo will now use the optional sudoers_file, sudoers_mode,
sudoers_uid and sudoers_gid arguments if specified on the
sudoers.so Plugin line in the sudo.conf file.
Fixed a problem introduced in sudo 1.8.8 that prevented the
full host name from being used when the fqdn sudoers option is
used. Bug #678.
French and Russian translations for sudoers from
translationproject.org.
Sudo now installs a handler for SIGCHLD signal handler immediately
before stating the process that will execute the command (or
start the monitor). The handler used to be installed earlier
but this causes problems with poorly behaved PAM modules that
install their own SIGCHLD signal handler and neglect to restore
sudo's original handler. Bug #657.
Removed a limit on the length of command line arguments expanded
by a wild card using sudo's version of the fnmatch() function.
This limit was introduced when sudo's version of fnmatch() was
replaced in sudo 1.8.4.
LDAP-based sudoers can now query an LDAP server for a user's
netgroups directly. This is often much faster than fetching
every sudoRole object containing a sudoUser that begins with
a `+' prefix and checking whether the user is a member of any
of the returned netgroups.
The mail_always sudoers option no longer sends mail for sudo
-l or sudo -v unless the user is unable to authenticate
themselves.
Fixed a crash when sudo is run with an empty argument vector.
Fixed two potential crashes when sudo is run with very low
resource limits.
The TZ environment variable is now checked for safety instead
of simply being copied to the environment of the command. This
fixes a potential security issue.
Major changes between version 1.8.11p2 and 1.8.11p1:
Fixed a bug where dynamic shared objects loaded from a plugin
could use the hooked version of getenv() but not the hooked
versions of putenv(), setenv() or unsetenv(). This can cause
problems for PAM modules that use those functions.
Major changes between version 1.8.11p1 and 1.8.11:
Fixed a compilation problem on some systems when the
--disable-shared-libutil configure option was specified.
The user can no longer interrupt the sleep after an incorrect
password on PAM systems using pam_unix. Bug #666.
Fixed a compilation problem on Linux systems that do not use
PAM. Bug #667.
"make install" will now work with the stock GNU autotools
install-sh script. Bug #669.
Fixed a crash with "sudo -i" when the current working directory
does not exist. Bug #670.
Fixed a potential crash in the debug subsystem when logging a
message larger that 1024 bytes.
Fixed a "make check" failure for ttyname when stdin is closed
and stdout and stderr are redirected to a different tty. Bug #643.
Added BASH_FUNC_* to environment blacklist to match newer-style
bash functions.
Major changes between version 1.8.11 and 1.8.10p3:
The sudoers plugin no longer uses setjmp/longjmp to recover
from fatal errors. All errors are now propagated to the caller
via return codes.
When running a command in the background, sudo will now forward
SIGINFO to the command (if supported).
Sudo will now use the system versions of the sha2 functions
from libc or libmd if available.
Visudo now works correctly on GNU Hurd. Bug #647.
Fixed suspend and resume of curses programs on some system when
the command is not being run in a pseudo-terminal. Bug #649.
Fixed a crash with LDAP-based sudoers on some systems when
Kerberos was enabled.
Sudo now includes optional Solaris audit support.
Catalan translation for sudoers from translationproject.org.
Norwegian Bokmaal translation for sudo from
translationproject.org.
Greek translation for sudoers from translationproject.org
The sudo source tree has been reorganized to more closely
resemble that of other gettext-enabled packages.
Sudo and its associated programs now link against a shared
version of libsudo_util. The --disable-shared-libutil configure
option may be used to force static linking if the
--enable-static-sudoers option is also specified.
The passwords in ldap.conf and ldap.secret may now be encoded
in base64.
Audit updates. SELinux role changes are now audited. For
sudoedit, we now audit the actual editor being run, instead of
just the sudoedit command.
Fixed bugs in the man page post-processing that could cause
portions of the manuals to be removed.
Fixed a crash in the system_group plugin. Bug #653.
Fixed sudoedit on platforms without a native version of the
getprogname() function. Bug #654.
Fixed compilation problems with some pre-C99 compilers.
Fixed sudo's -C option which was broken in version 1.8.9.
It is now possible to match an environment variable's value as
well as its name using env_keep and env_check. This can be used
to preserve bash functions which would otherwise be removed
from the environment.
New files created via sudoedit as a non-root user now have the
proper group id. Bug #656.
Sudoedit now works correctly in conjunction with sudo's SELinux
RBAC support. Temporary files are now created with the proper
security context.
The sudo I/O logging plugin API has been updated. If a logging
function returns an error, the command will be terminated and
all of the plugin's logging functions will be disabled. If a
logging function rejects the command's output it will no longer
be displayed to the user's terminal.
Fixed a compilation error on systems that lack openpty(),
_getpty() and grantpt(). Bug #660.
Fixed a hang when a sudoers source is listed more than once in
a single sudoers nsswitch.conf entry.
On AIX, shell scripts without a #! magic number are now passed
to /usr/bin/sh, not /usr/bin/bsh. This is consistent with what
the execvp() function on AIX does and matches historic sudo
behavior. Bug #661.
Fixed a cross-compilation problem building mksiglist and
mksigname. Bug #662.
Major changes between version 1.8.10p3 and 1.8.10p2:
Fixed expansion of the %p escape in the prompt for "sudo -l"
when rootpw, runaspw or targetpw is set. Bug #639.
Fixed matching of uids and gids which was broken in version
1.8.9. Bug #640.
PAM credential initialization has been re-enabled. It was
unintentionally disabled by default in version 1.8.8. The way
credentials are initialized has also been fixed. Bug #642.
Fixed a descriptor leak on Linux when determing boot time. Sudo
normally closes extra descriptors before running a command so
the impact is limited. Bug #645.
Fixed flushing of the last buffer of data when I/O logging is
enabled. This bug, introduced in version 1.8.9, could cause
incomplete command output on some systems. Bug #646.
Major changes between version 1.8.10p2 and 1.8.10p1:
Fixed a hang introduced in sudo 1.8.10 when timestamp_timeout
is set to zero. Bug #638.
Major changes between version 1.8.10p1 and 1.8.10:
Fixed a bug introduced in sudo 1.8.10 that prevented the
disabling of tty-based tickets.
Fixed a bug with netgated commands in "sudo -l command" that
could cause the command to be listed even when it was explicitly
denied. This only affected list mode when a command was specified.
Bug #636.
Major changes between version 1.8.10 and 1.8.9p5:
It is now possible to disable network interface probing in
sudo.conf by changing the value of the probe_interfaces setting.
When listing a user's privileges (sudo -l), the sudoers plugin
will now prompt for the user's password even if the targetpw,
rootpw or runaspw options are set.
The sudoers plugin uses a new format for its time stamp files.
Each user now has a single file which may contain multiple
records when per-tty time stamps are in use (the default). The
time stamps use a monotonic timer where available and are once
again located in a directory under /var/run. The lecture status
is now stored separately from the time stamps in a different
directory. Bug #616.
sudo's -K option will now remove all of the user's time stamps,
not just the time stamp for the current terminal. The -k option
can be used to only disable time stamps for the current terminal.
If sudo was started in the background and needed to prompt for
a password, it was not possible to suspend it at the password
prompt. This now works properly.
LDAP-based sudoers now uses a default search filter of
(objectClass=sudoRole) for more efficient queries. The netgroup
query has been modified to avoid falling below the minimum
length for OpenLDAP substring indices.
The new use_netgroups sudoers option can be used to explicitly
enable or disable netgroups support. For LDAP-based sudoers,
netgroup support requires an expensive substring match on the
server. If netgroups are not needed, this option can be disabled
to reduce the load on the LDAP server.
Sudo is once again able to open the sudoers file when the group
on sudoers doesn't match the expected value, so long as the
file is not group writable.
Sudo now installs an init.d script to clear the time stamp
directory at boot time on AIX and HP-UX systems. These systems
either lack /var/run or do not clear it on boot.
The JSON format used by visudo -x now properly supports the
negation operator. In addition, the Options object is now the
same for both Defaults and Cmnd_Specs.
Czech and Serbian translations for sudoers from
translationproject.org.
Catalan translation for sudo from translationproject.org.
Major changes between version 1.8.9p5 and 1.8.9p4:
Fixed a compilation error on AIX when LDAP support is enabled.
Fixed parsing of the "umask" defaults setting in sudoers. Bug
#632.
Fixed a failed assertion when the "closefrom_override" defaults
setting is enabled in sudoers and sudo's -C flag is used. Bug
#633.
Major changes between version 1.8.9p4 and 1.8.9p3:
Fixed a bug where sudo could consume large amounts of CPU while
the command was running when I/O logging is not enabled. Bug #631.
Fixed a bug where sudo would exit with an error when the debug
level is set to util@debug or all@debug and I/O logging is not
enabled. The command would continue runnning after sudo exited.
Major changes between version 1.8.9p3 and 1.8.9p2:
Fixed a bug introduced in sudo 1.8.9 that prevented the tty
name from being resolved properly on Linux systems. Bug #630.
Major changes between version 1.8.9p2 and 1.8.9p1:
Updated config.guess, config.sub and libtool to support the
ppc64le architecture (IBM PowerPC Little Endian).
Major changes between version 1.8.9p1 and 1.8.9:
Fixed a problem with gcc 4.8's handling of bit fields that
could lead to the noexec flag being enabled even when it was
not explicitly set.
Major changes between version 1.8.9 and 1.8.8:
Reworked sudo's main event loop to use a simple event subsystem
using poll(2) or select(2) as the back end.
It is now possible to statically compile the sudoers plugin
into the sudo binary without disabling shared library support.
The sudo.conf file may still be used to configure other plugins.
Sudo can now be compiled again with a C preprocessor that does
not support variadic macros.
Visudo can now export a sudoers file in JSON format using the
new -x flag.
The locale is now set correctly again for visudo and sudoreplay.
The plugin API has been extended to allow the plugin to exclude
specific file descriptors from the closefrom range.
There is now a workaround for a Solaris-specific problem where
NOEXEC was overriding traditional root DAC behavior.
Add user netgroup filtering for SSSD. Previously, rules for a
netgroup were applied to all even when they did not belong to
the specified netgroup.
On systems with BSD login classes, if the user specified a
group (not a user) to run the command as, it was possible to
specify a different login class even when the command was not
run as the super user.
The closefrom() emulation on Mac OS X now uses /dev/fd if
possible.
Fixed a bug where sudoedit would not update the original file
from the temporary when PAM or I/O logging is not enabled.
When recycling I/O logs, the log files are now truncated
properly.
Fixes bugs #617, #621, #622, #623, #624, #625, #626
Major changes between version 1.8.8 and 1.8.7:
Removed a warning on PAM systems with stacked auth modules
where the first module on the stack does not succeed.
Sudo, sudoreplay and visudo now support GNU-style long options.
The -h (--host) option may now be used to specify a host name.
This is currently only used by the sudoers plugin in conjunction
with the -l (--list) option.
Program usage messages and manual SYNOPSIS sections have been
simplified.
Sudo's LDAP SASL support now works properly with Kerberos.
Previously, the SASL library was unable to locate the user's
credential cache.
It is now possible to set the nproc resource limit to unlimited
via pam_limits on Linux (bug #565).
New pam_service and pam_login_service sudoers options that can
be used to specify the PAM service name to use.
New pam_session and pam_setcred sudoers options that can be
used to disable PAM session and credential support.
The sudoers plugin now properly supports UIDs and GIDs that
are larger than 0x7fffffff on 32-bit platforms.
Fixed a visudo bug introduced in sudo 1.8.7 where per-group
Defaults entries would cause an internal error.
If the tty_tickets sudoers option is enabled (the default),
but there is no tty present, sudo will now use a ticket file
based on the parent process ID. This makes it possible to
support the normal timeout behavior for the session.
Fixed a problem running commands that change their process
group and then attempt to change the terminal settings when
not running the command in a pseudo-terminal. Previously, the
process would receive SIGTTOU since it was effectively a
background process. Sudo will now grant the child the controlling
tty and continue it when this happens.
The closefrom_override sudoers option may now be used in a
command-specified Defaults entry (bug #610).
Sudo's BSM audit support now works on Solaris 11.
Brazilian Portuguese translation for sudo and sudoers from
translationproject.org.
Czech translation for sudo from translationproject.org.
French translation for sudo from translationproject.org.
Sudo's noexec support on Mac OS X 10.4 and above now uses
dynamic symbol interposition instead of setting
DYLD_FORCE_FLAT_NAMESPACE=1 which causes issues with some
programs.
Fixed visudo's -q (--quiet) flag, broken in sudo 1.8.6.
Root may no longer change its SELinux role without entering a
password.
Fixed a bug introduced in Sudo 1.8.7 where the indexes written
to the I/O log timing file are two greater than they should
be. Sudoreplay now contains a work-around to parse those files.
In sudoreplay's list mode, the this qualifier in fromdate or
todate expressions now behaves more sensibly. Previously, it
would often match a date that was "one more" than expected.
For example, "this week" now matches the current week instead
of the following week.
Major changes between version 1.8.7 and 1.8.6p8:
The non-Unix group plugin is now supported when sudoers data
is stored in LDAP.
Sudo now uses a workaround for a locale bug on Solaris 11.0
that prevents setuid programs like sudo from fully using locales.
User messages are now always displayed in the user's locale,
even when the same message is being logged or mailed in a
different locale.
Log files created by sudo now explicitly have the group set to
group ID 0 rather than relying on BSD group semantics (which
may not be the default).
A new exec_background sudoers option can be used to initially
run the command without read access to the terminal when running
a command in a pseudo-tty. If the command tries to read from
the terminal it will be stopped by the kernel (via SIGTTIN or
SIGTTOU) and sudo will immediately restart it as the forground
process (if possible). This allows sudo to only pass terminal
input to the program if the program actually is expecting it.
Unfortunately, a few poorly-behaved programs (like "su" on most
Linux systems) do not handle SIGTTIN and SIGTTOU properly.
Sudo now uses an efficient group query to get all the groups
for a user instead of iterating over every record in the group
database on HP-UX and Solaris.
Sudo now produces better error messages when there is an error
in the sudo.conf file.
Two new settings have been added to sudo.conf to give the admin
better control of how group database queries are performed.
The group_source specifies how the group list for a user will
be determined. Legal values are static (use the kernel groups
list), dynamic (perform a group database query) and adaptive
(only perform a group database query if the kernel list is
full). The max_groups setting specifies the maximum number of
groups a user may belong to when performing a group database
query.
The sudo.conf file now supports line continuation by using a
backslash as the last character on the line.
There is now a standalone sudo.conf manual page.
Sudo now stores its libexec files in a sudo subdirectory instead
of in libexec itself. For backwards compatibility, if the plugin
is not found in the default plugin directory, sudo will check
the parent directory if the default directory ends in /sudo.
The sudoers I/O logging plugin now logs the terminal size.
A new sudoers option maxseq can be used to limit the number of
I/O log entries that are stored.
The system_group and group_file sudoers group provider plugins
are now installed by default.
The list output (sudo -l) output from the sudoers plugin is
now less ambiguous when an entry includes different runas users.
The long list output (sudo -ll) for file-based sudoers is now
more consistent with the format of LDAP-based sudoers.
A uid may now be used in the sudoRunAsUser attributes for LDAP
sudoers.
Minor plugin API change: the close and version functions are
now optional. If the policy plugin does not provide a close
function and the command is not being run in a new pseudo-tty,
sudo may now execute the command directly instead of in a child
process.
A new sudoers option pam_session can be used to disable sudo's
PAM session support.
On HP-UX systems, sudo will now use the pstat() function to
determine the tty instead of ttyname().
Turkish translation for sudo and sudoers from
translationproject.org.
Dutch translation for sudo and sudoers from
translationproject.org.
Tivoli Directory Server client libraries may now be used with
HP-UX where libibmldap has a hidden dependency on libCsup.
The sudoers plugin will now ignore invalid domain names when
checking netgroup membership. Most Linux systems use the string
"(none)" for the NIS-style domain name instead of an empty
string.
New support for specifying a SHA-2 digest along with the command
in sudoers. Supported hash types are sha224, sha256, sha384
and sha512. See the description of Digest_Spec in the sudoers
manual or the description of sudoCommand in the sudoers.ldap
manual for details.
The paths to ldap.conf and ldap.secret may now be specified as
arguments to the sudoers plugin in the sudo.conf file.
Fixed potential false positives in visudo's alias cycle detection.
Fixed a problem where the time stamp file was being treated as
out of date on Linux systems where the change time on the
pseudo-tty device node can change after it is allocated.
Sudo now only builds Position Independent Executables (PIE) by
default on Linux systems and verifies that a trivial test
program builds and runs.
On Solaris 11.1 and higher, sudo binaries will now have the
ASLR tag enabled if supported by the linker.
Major changes between version 1.8.6p8 and 1.8.6p7:
Terminal detection now works properly on 64-bit AIX kernels.
This was broken by the removal of the ttyname() fallback in
Sudo 1.8.6p6. Sudo is now able to map an AIX 64-bit device
number to the corresponding device file in /dev.
Sudo now checks for crypt() returning NULL when performing
passwd-based authentication.
Major changes between version 1.8.6p7 and 1.8.6p6:
A time stamp file with the date set to the epoch by sudo -k is
now completely ignored regardless of what the local clock is
set to. Previously, if the local clock was set to a value
between the epoch and the time stamp timeout value, a time
stamp reset by sudo -k would be considered current. This is
a potential security issue.
The tty-specific time stamp file now includes the session ID
of the sudo process that created it. If a process with the same
tty but a different session ID runs sudo, the user will now be
prompted for a password (assuming authentication is required
for the command). This is a potential security issue.
Major changes between version 1.8.6p6 and 1.8.6p5:
On systems where the controlling tty can be determined via
/proc or sysctl(), sudo will no longer fall back to using
ttyname() if the process has no controlling tty. This prevents
sudo from using a non-controlling tty for logging and time
stamp purposes. This is a potential security issue.
Major changes between version 1.8.6p5 and 1.8.6p4:
Fixed a potential crash in visudo's alias cycle detection.
Improved performance on Solaris when retrieving the group list
for the target user. On systems with a large number of groups
where the group database is not local (NIS, LDAP, AD), fetching
the group list could take a minute or more.
Major changes between version 1.8.6p4 and 1.8.6p3:
The -fstack-protector is now used when linking visudo, sudoreplay
and testsudoers.
Avoid building PIE binaries on FreeBSD/ia64 as they don't run
properly.
Fixed a crash in visudo strict mode when an unknown Defaults
setting is encountered.
Do not inform the user that the command was not permitted by
the policy if they do not successfully authenticate. This is
a regression introduced in sudo 1.8.6.
Allow sudo to be build with sss support without also including
ldap support.
Fix running commands that need the terminal in the background
when I/O logging is enabled. E.g. sudo vi &. When the command
is foregrounded, it will now resume properly.
Major changes between version 1.8.6p3 and 1.8.6p2:
Fixed post-processing of the man pages on systems with legacy
versions of sed.
Fixed sudoreplay -l on Linux systems with file systems that
set DT_UNKNOWN in the d_type field of struct dirent.
Major changes between version 1.8.6p2 and 1.8.6p1:
Fixed suspending a command after it has already been resumed
once when I/O logging (or use_pty) is not enabled. This was a
regression introduced in version 1.8.6.
Major changes between version 1.8.6p1 and 1.8.6:
Fixed the setting of LOGNAME, USER and USERNAME variables in
the command's environment when env_reset is enabled (the
default). This was a regression introduced in version 1.8.6.
Sudo now honors SUCCESS=return in /etc/nsswitch.conf.
Major changes between version 1.8.6 and 1.8.5p3:
Sudo is now built with the -fstack-protector flag if the the
compiler supports it. Also, the -zrelro linker flag is used if
supported. The --disable-hardening configure option can be used
to build sudo without stack smashing protection.
Sudo is now built as a Position Independent Executable (PIE)
if supported by the compiler and linker.
If the user is a member of the exempt group in sudoers, they
will no longer be prompted for a password even if the -k flag
is specified with the command. This makes sudo -k command
consistent with the behavior one would get if the user ran sudo
-k immediately before running the command.
The sudoers file may now be a symbolic link. Previously, sudo
would refuse to read sudoers unless it was a regular file.
The sudoreplay command can now properly replay sessions where
no tty was present.
The sudoers plugin now takes advantage of symbol visibility
controls when supported by the compiler or linker. As a result,
only a small number of symbols are exported which significantly
reduces the chances of a conflict with other shared objects.
Improved support for the Tivoli Directory Server LDAP client
libraries. This includes support for using LDAP over SSL (ldaps)
as well as support for the BIND_TIMELIMIT, TLS_KEY and TLS_CIPHERS
ldap.conf options. A new ldap.conf option, TLS_KEYPW can be
used to specify a password to decrypt the key database.
When constructing a time filter for use with LDAP sudoNotBefore
and sudoNotAfter attributes, the current time now includes
tenths of a second. This fixes a problem with timed entries on
Active Directory.
If a user fails to authenticate and the command would be rejected
by sudoers, it is now logged with command not allowed instead
of N incorrect password attempts. Likewise, the mail_no_perms
sudoers option now takes precedence over mail_badpass
The sudo manuals are now formatted using the mdoc macros.
Versions using the legacy man macros are provided for systems
that lack mdoc.
New support for Solaris privilege sets. This makes it possible
to specify fine-grained privileges in the sudoers file on
Solaris 10 and above. A Runas_Spec that contains no Runas_Lists
can be used to give a user the ability to run a command as
themselves but with an expanded privilege set.
Fixed a problem with the reboot and shutdown commands on some
systems (such as HP-UX and BSD). On these systems, reboot sends
all processes (except itself) SIGTERM. When sudo received
SIGTERM, it would relay it to the reboot process, thus killing
reboot before it had a chance to actually reboot the system.
Support for using the System Security Services Daemon (SSSD)
as a source of sudoers data.
Slovenian translation for sudo and sudoers from
translationproject.org.
Visudo will now warn about unknown Defaults entries that are
per-host, per-user, per-runas or per-command.
Fixed a race condition that could cause sudo to receive SIGTTOU
(and stop) when resuming a shell that was run via sudo when
I/O logging (and use_pty) is not enabled.
Sending SIGTSTP directly to the sudo process will now suspend
the running command when I/O logging (and use_pty) is not
enabled.
Major changes between version 1.8.5p3 and 1.8.5p2:
Fixed the loading of I/O plugins that conform to a plugin API
version older than 1.2.
Major changes between version 1.8.5p2 and 1.8.5p1:
Fixed use of the SUDO_ASKPASS environment variable which was
broken in Sudo 1.8.5.
Fixed a problem reading the sudoers file when the file mode is
more restrictive than the expected mode. For example, when the
expected sudoers file mode is 0440 but the actual mode is 0400.
Major changes between version 1.8.5p1 and 1.8.5:
Fixed a bug that prevented files in an include directory from
being evaluated.
Major changes between version 1.8.5 and 1.8.4p5:
When "noexec" is enabled, sudo_noexec.so will now be prepended
to any existing LD_PRELOAD variable instead of replacing it.
The sudo_noexec.so shared library now wraps the execvpe(),
exect(), posix_spawn() and posix_spawnp() functions.
The user/group/mode checks on sudoers files have been relaxed.
As long as the file is owned by the sudoers uid, not
world-writable and not writable by a group other than the
sudoers gid, the file is considered OK. Note that visudo will
still set the mode to the value specified at configure time.
It is now possible to specify the sudoers path, uid, gid and
file mode as options to the plugin in the sudo.conf file.
Croatian, Galician, German, Lithuanian, Swedish and Vietnamese
translations from translationproject.org.
/etc/environment is no longer read directly on Linux systems
when PAM is used. Sudo now merges the PAM environment into the
user's environment which is typically set by the pam_env module.
The initial evironment created when env_reset is in effect now
includes the contents of /etc/environment on AIX systems and
the "setenv" and "path" entries from /etc/login.conf on BSD
systems.
The plugin API has been extended in three ways. First, options
specified in sudo.conf after the plugin pathname are passed to
the plugin's open function. Second, sudo has limited support
for hooks that can be used by plugins. Currently, the hooks
are limited to environment handling functions. Third, the
init_session policy plugin function is passed a pointer to the
user environment which can be updated during session setup.
The plugin API version has been incremented to version 1.2.
See the sudo_plugin manual for more information.
The policy plugin's init_session function is now called by the
parent sudo process, not the child process that executes the
command. This allows the PAM session to be open and closed in
the same process, which some PAM modules require.
Fixed parsing of "Path askpass" and "Path noexec" in sudo.conf,
which was broken in version 1.8.4.
On systems with an SVR4-style /proc file system, the
/proc/pid/psinfo file is now uses to determine the controlling
terminal, if possible. This allows tty-based tickets to work
properly even when, e.g. standard input, output and error are
redirected to /dev/null.
The output of "sudoreplay -l" is now sorted by file name (or
sequence number). Previously, entries were displayed in the
order in which they were found on the file system.
Sudo now behaves properly when I/O logging is enabled and the
controlling terminal is revoked (e.g. the running sshd is
killed). Previously, sudo may have exited without calling the
I/O plugin's close function which can lead to an incomplete
I/O log.
Sudo can now detect when a user has logged out and back in
again on Solaris 11, just like it can on Solaris 10.
The built-in zlib included with Sudo has been upgraded to
version 1.2.6.
Setting the SSL parameter to start_tls in ldap.conf now works
properly when using Mozilla-based SDKs that support the
ldap_start_tls_s() function.
The TLS_CHECKPEER parameter in ldap.conf now works when the
Mozilla NSS crypto backend is used with OpenLDAP.
A new group provider plugin, system_group, is included which
performs group look ups by name using the system groups database.
This can be used to restore the pre-1.7.3 sudo group lookup
behavior.
Major changes between version 1.8.4p5 and 1.8.4p4:
Fixed a potential security issue in the matching of hosts
against an IPv4 network specified in sudoers. The flaw may
allow a user who is authorized to run commands on hosts belonging
to one IPv4 network to run commands on a different host.
Major changes between version 1.8.4p4 and 1.8.4p3:
Fixed a bug introduced in Sudo 1.8.4 which prevented sudo -v
from working.
Major changes between version 1.8.4p3 and 1.8.4p2:
Fixed a crash on FreeBSD when there is no tty present.
When visudo is run with the -c (check) option, the sudoers
file(s) owner and mode are now also checked unless the -f option
was specified.
Major changes between version 1.8.4p2 and 1.8.4p1:
Fixed a bug introduced in Sudo 1.8.4 where insufficient space
was allocated for group IDs in the LDAP filter.
Fixed a bug introduced in Sudo 1.8.4 where the path to sudo.conf
was /sudo.conf instead of etc/sudo.conf.
Fixed a bug introduced in Sudo 1.8.4 which could cause a hang
when I/O logging is enabled and input is from a pipe or file.
Major changes between version 1.8.4p1 and 1.8.4:
Fixed a bug introduced in sudo 1.8.4 that broke adding to or
deleting from the env_keep, env_check and env_delete lists in
sudoers on some platforms.
Major changes between version 1.8.4 and 1.8.3p2:
The -D flag in sudo has been replaced with a more general
debugging framework that is configured in sudo.conf.
Fixed a false positive in visudo strict mode when aliases are
in use.
Fixed a crash with sudo -i when a runas group was specified
without a runas user.
The line on which a syntax error is reported in the sudoers
file is now more accurate. Previously it was often off by a
line.
Fixed a bug where stack garbage could be printed at the end of
the lecture when the lecture_file option was enabled.
make install now honors the LINGUAS environment variable.
The #include and #includedir directives in sudoers now support
relative paths. If the path is not fully qualified it is expected
to be located in the same directory of the sudoers file that
is including it.
New Serbian and Spanish translations for sudo from
translationproject.org.
LDAP-based sudoers may now access by group ID in addition to
group name.
visudo will now fix the mode on the sudoers file even if no
changes are made unless the -f option is specified.
The use_loginclass sudoers option works properly again.
On systems that use login.conf, sudo -i now sets environment
variables based on login.conf.
For LDAP-based sudoers, values in the search expression are
now escaped as per RFC 4515.
The plugin close function is now properly called when a login
session is killed (as opposed to the actual command being
killed). This can happen when an ssh session is disconnected
or the terminal window is closed.
The deprecated "noexec_file" sudoers option is no longer
supported.
Fixed a race condition when I/O logging is not enabled that
could result in tty-generated signals (e.g. control-C) being
received by the command twice.
If none of the standard input, output or error are connected
to a tty device, sudo will now check its parent's standard
input, output or error for the tty name on systems with /proc
and BSD systems that support the KERN_PROC_PID sysctl. This
allows tty-based tickets to work properly even when, e.g.
standard input, output and error are redirected to /dev/null.
Added the --enable-kerb5-instance configure option to allow
people using Kerberos V authentication to specify a custom
instance so the principal name can be, e.g. "username/sudo"
similar to how ksu uses "username/root".
Fixed a bug where a pattern like /usr/* included /usr/bin/ in
the results, which would be incorrectly be interpreted as if
the sudoers file had specified a directory.
visudo -c will now list any include files that were checked in
addition to the main sudoers file when everything parses OK.
Users that only have read-only access to the sudoers file may
now run visudo -c. Previously, write permissions were required
even though no writing is down in check-only mode.
It is now possible to prevent the disabling of core dumps from
within sudo itself by adding a line to the sudo.conf file like
Set disable_coredump false.
Major changes between version 1.8.3p2 and 1.8.3p1:
Fixed a format string vulnerability when the sudo binary (or
a symbolic link to the sudo binary) contains printf format
escapes and the -D (debugging) flag is used.
Major changes between version 1.8.3p1 and 1.8.3:
Fixed a crash in the monitor process on Solaris when NOPASSWD
was specified or when authentication was disabled.
Fixed matching of a Runas_Alias in the group section of a
Runas_Spec.
Major changes between version 1.8.3 and 1.8.2:
Fixed expansion of strftime() escape sequences in the log_dir
sudoers setting.
Esperanto, Italian and Japanese translations from
translationproject.org.
Sudo will now use PAM by default on AIX 6 and higher.
Added --enable-werror configure option for gcc's -Werror flag.
Visudo no longer assumes all editors support the +linenumber
command line argument. It now uses a whitelist of editors known
to support the option.
Fixed matching of network addresses when a netmask is specified
but the address is not the first one in the CIDR block.
The configure script now check whether or not errno.h declares
the errno variable. Previously, sudo would always declare errno
itself for older systems that don't declare it in errno.h.
The NOPASSWD tag is now honored for denied commands too, which
matches historic sudo behavior (prior to sudo 1.7.0).
Sudo now honors the DEREF setting in ldap.conf which controls
how alias dereferencing is done during an LDAP search.
A symbol conflict with the pam_ssh_agent_auth PAM module that
would cause a crash been resolved.
The inability to load a group provider plugin is no longer a
fatal error.
A potential crash in the utmp handling code has been fixed.
Two PAM session issues have been resolved. In previous versions
of sudo, the PAM session was opened as one user and closed as
another. Additionally, if no authentication was performed, the
PAM session would never be closed.
Sudo will now work correctly with LDAP-based sudoers using TLS
or SSL on Debian systems.
The LOGNAME, USER and USERNAME environment variables are
preserved correctly again in sudoedit mode.
Major changes between version 1.8.2 and 1.8.1p2:
Sudo, visudo, sudoreplay and the sudoers plug-in now have
natural language support (NLS). Sudo will use gettext(), if
available, to display translated messages. This can be disabled
by passing configure the --disable-nls option. All translations
are coordinated via The Translation Project,
translationproject.org. Sudo 1.8.2 includes translations for
Basque, Chinese (simplified), Danish, Finish, Polish, Russian
and Ukranian.
Plug-ins are now loaded with the RTLD_GLOBAL flag instead of
RTLD_LOCAL. This fixes missing symbol problems in PAM modules
on certain platforms, such as FreeBSD and SuSE Linux Enterprise.
I/O logging is now supported for commands run in background
mode (using sudo's -b flag).
Group ownership of the sudoers file is now only enforced when
the file mode on sudoers allows group readability or writability.
Visudo now checks the contents of an alias and warns about
cycles when the alias is expanded.
If the user specifes a group via sudo's -g option that matches
the target user's group in the password database, it is now
allowed even if no groups are present in the Runas_Spec.
The sudo Makefiles now have more complete dependencies which
are automatically generated instead of being maintained manually.
The use_pty sudoers option is now correctly passed back to the
sudo front end. This was missing in previous versions of sudo
1.8 which prevented use_pty from being honored.
sudo -i command now works correctly with the bash version 2.0
and higher. Previously, the .bash_profile would not be sourced
prior to running the command unless bash was built with
NON_INTERACTIVE_LOGIN_SHELLS defined.
When matching groups in the sudoers file, sudo will now match
based on the name of the group instead of the group ID. This
can substantially reduce the number of group lookups for sudoers
files that contain a large number of groups.
Multi-factor authentication is now supported on AIX.
Added support for non-RFC 4517 compliant LDAP servers that
require that seconds be present in a timestamp, such as Tivoli
Directory Server.
If the group vector is to be preserved, the PATH search for
the command is now done with the user's original group vector.
For LDAP-based sudoers, the runas_default sudoOption now works
properly in a sudoRole that contains a sudoCommand.
Spaces in command line arguments for sudo -s and sudo -i are
now escaped with a backslash when checking the security policy.
Major changes between version 1.8.1p2 and 1.8.1p1:
Two-character CIDR-style IPv4 netmasks are now matched correctly
in the sudoers file.
A build error with MIT Kerberos V has been resolved.
A crash on HP-UX in the sudoers plugin when wildcards are
present in the sudoers file has been resolved.
Sudo now works correctly on Tru64 Unix again.
Major changes between version 1.8.1p1 and 1.8.1:
Fixed a problem on AIX where sudo was unable to set the final
uid if the PAM module modified the effective uid.
A non-existent includedir is now treated the same as an empty
directory and not reported as an error.
Removed extraneous parens in LDAP filter when
sudoers_search_filter is enabled that can cause an LDAP search
error.
Fixed a make -j problem for make install
Major changes between version 1.8.1 and 1.8.0:
A new LDAP setting, sudoers_search_filter, has been added to
ldap.conf. This setting can be used to restrict the set of
records returned by the LDAP query. Based on changes from
Matthew Thomas.
White space is now permitted within a User_List when used in
conjunction with a per-user Defaults definition.
A group ID (%#gid) may now be specified in a User_List or
Runas_List. Likewise, for non-Unix groups the syntax is %:#gid.
Support for double-quoted words in the sudoers file has been
fixed. The change in 1.7.5 for escaping the double quote
character caused the double quoting to only be available at
the beginning of an entry.
The fix for resuming a suspended shell in 1.7.5 caused problems
with resuming non-shells on Linux. Sudo will now save the
process group ID of the program it is running on suspend and
restore it when resuming, which fixes both problems.
A bug that could result in corrupted output in "sudo -l" has
been fixed.
Sudo will now create an entry in the utmp (or utmpx) file when
allocating a pseudo-tty (e.g. when logging I/O). The "set_utmp"
and "utmp_runas" sudoers file options can be used to control
this. Other policy plugins may use the "set_utmp" and "utmp_user"
entries in the command_info list.
The sudoers policy now stores the TSID field in the logs even
when the "iolog_file" sudoers option is defined to a value
other than %{sessid}. Previously, the TSID field was only
included in the log file when the "iolog_file" option was set
to its default value.
The sudoreplay utility now supports arbitrary session IDs.
Previously, it would only work with the base-36 session IDs
that the sudoers plugin uses by default.
Sudo now passes "run_shell=true" to the policy plugin in the
settings list when sudo's -s command line option is specified.
The sudoers policy plugin uses this to implement the "set_home"
sudoers option which was missing from sudo 1.8.0.
The "noexec" functionality has been moved out of the sudoers
policy plugin and into the sudo front-end, which matches the
behavior documented in the plugin writer's guide. As a result,
the path to the noexec file is now specified in the sudo.conf
file instead of the sudoers file.
On Solaris 10, the PRIV_PROC_EXEC privilege is now used to
implement the "noexec" feature. Previously, this was implemented
via the LD_PRELOAD environment variable.
The exit values for "sudo -l", "sudo -v" and "sudo -l command"
have been fixed in the sudoers policy plugin.
The sudoers policy plugin now passes the login class, if any,
back to the sudo front-end.
The sudoers policy plugin was not being linked with requisite
libraries in certain configurations.
Sudo now parses command line arguments before loading any
plugins. This allows "sudo -V" or "sudo -h" to work even if
there is a problem with sudo.conf
Plugins are now linked with the static version of libgcc to
allow the plugin to run on a system where no shared libgcc is
installed, or where it is installed in a different location.
Major changes between version 1.8.0 and 1.7.5:
Sudo has been refactored to use a modular framework that can
support third-party policy and I/O logging plugins. The default
plugin is "sudoers" which provides the traditional sudo
functionality. See the sudo_plugin manual for details on the
plugin API and the sample in the plugins directory for a simple
example.
Problems found locating distfiles:
Package f-prot-antivirus6-fs-bin: missing distfile fp-NetBSD.x86.32-fs-6.2.3.tar.gz
Package f-prot-antivirus6-ws-bin: missing distfile fp-NetBSD.x86.32-ws-6.2.3.tar.gz
Package libidea: missing distfile libidea-0.8.2b.tar.gz
Package openssh: missing distfile openssh-7.1p1-hpn-20150822.diff.bz2
Package uvscan: missing distfile vlp4510e.tar.Z
Otherwise, existing SHA1 digests verified and found to be the same on
the machine holding the existing distfiles (morden). All existing
SHA1 digests retained for now as an audit trail.
Reported by @kusalananda on twitter, confirmed by comparing the output of sudo
-V as root between Apple bundled version & pkgsrc version.
It's not possible to use sudo from a unprivileged build as sudo expects to be
setuid to root so mark it as NOT_FOR_UNPRIVILEGED.
Reviewed by wiz@
Upstream Changelog:
+ The TZ environment variable is now checked for safety instead of
simply being copied to the environment of the command.
This fixes a potential security issue.
+ Sudo now only builds Position Independent Executables (PIE) by
default on Linux systems and verifies that a trivial test program
builds and runs.
+ On Solaris 11.1 and higher, sudo binaries will now have the ASLR tag
enabled if supported by the linker.
http://www.sudo.ws/sudo/alerts/env_add.html
What's new in Sudo 1.7.10p8?
* Sudo's exit code now indicates a failure if the user does not
successfully authenticate.
* On HP-UX systems, sudo will now use the pstat() function to
determine the tty instead of ttyname().
* Fixed compilation when --without-iologdir configure option is
specified.
* On systems with BSD login classes, if the user specified a group
(not a user) to run the command as, it was possible to specify
a different login class even when the command was not run as the
super user.
* The closefrom() emulation on Mac OS X now uses /dev/fd if possible.
It also now sets the close on exec flag instead of actually
closing the descriptors to avoid a crash in libdispatch.
* The sudoers plugin will now ignore invalid domain names when
checking netgroup membership. Most Linux systems use the string
"(none)" for the NIS-style domain name instead of an empty string.
* Fixed the logic when checking environment variables on the
command line against the env_check and env_delete blacklists.
This is only a problem when env_reset is disabled in sudoers.
What's new in Sudo 1.7.10p7?
* A time stamp file with the date set to the epoch by "sudo -k"
is now completely ignored regardless of what the local clock is
set to. Previously, if the local clock was set to a value between
the epoch and the time stamp timeout value, a time stamp reset
by "sudo -k" would be considered current.
What's new in Sudo 1.7.10p6?
* The tty-specific time stamp file now includes the session ID
of the sudo process that created it. If a process with the same
tty but a different session ID runs sudo, the user will now be
prompted for a password (assuming authentication is required for
the command).
What's new in Sudo 1.7.10p5?
* On systems where the controlling tty can be determined via /proc
or sysctl(), sudo will no longer fall back to using ttyname()
if the process has no controlling tty. This prevents sudo from
using a non-controlling tty for logging and time stamp purposes.
What's new in Sudo 1.7.10?
* If the user is a member of the "exempt" group in sudoers, they
will no longer be prompted for a password even if the -k flag
is specified with the command. This makes "sudo -k command"
consistent with the behavior one would get if the user ran "sudo
-k" immediately before running the command.
* The sudoers file may now be a symbolic link. Previously, sudo
would refuse to read sudoers unless it was a regular file.
* The user/group/mode checks on sudoers files have been relaxed.
As long as the file is owned by the sudoers uid, not world-writable
and not writable by a group other than the sudoers gid, the file
is considered OK. Note that visudo will still set the mode to
the value specified at configure time.
* /etc/environment is no longer read directly on Linux systems
when PAM is used. Sudo now merges the PAM environment into the
user's environment which is typically set by the pam_env module.
* The initial evironment created when env_reset is in effect now
includes the contents of /etc/environment on AIX systems and the
"setenv" and "path" entries from /etc/login.conf on BSD systems.
* On systems with an SVR4-style /proc file system, the /proc/pid/psinfo
file is now uses to determine the controlling terminal, if possible.
This allows tty-based tickets to work properly even when, e.g.
standard input, output and error are redirected to /dev/null.
* The sudoreplay command can now properly replay sessions where
no tty was present.
* Fixed a race condition that could cause sudo to receive SIGTTOU
(and stop) when resuming a shell that was run via sudo when I/O
logging (and use_pty) is not enabled.
Fix seuciry problem of CVE-2012-2337.
What's new in Sudo 1.7.9p1?
* Fixed a bug when matching against an IP address with an associated
netmask in the sudoers file. In certain circumstances, this
could allow users to run commands on hosts they are not authorized
for.
What's new in Sudo 1.7.9?
* Fixed a false positive in visudo strict mode when aliases are
in use.
* The line on which a syntax error is reported in the sudoers file
is now more accurate. Previously it was often off by a line.
* The #include and #includedir directives in sudoers now support
relative paths. If the path is not fully qualified it is expected
to be located in the same directory of the sudoers file that is
including it.
* visudo will now fix the mode on the sudoers file even if no changes
are made unless the -f option is specified.
* The "use_loginclass" sudoers option works properly again.
* For LDAP-based sudoers, values in the search expression are now
escaped as per RFC 4515.
* Fixed a race condition when I/O logging is not enabled that could
result in tty-generated signals (e.g. control-C) being received
by the command twice.
* If none of the standard input, output or error are connected to
a tty device, sudo will now check its parent's standard input,
output or error for the tty name on systems with /proc and BSD
systems that support the KERN_PROC_PID sysctl. This allows
tty-based tickets to work properly even when, e.g. standard
input, output and error are redirected to /dev/null.
* Fixed a bug where a pattern like "/usr/*" included /usr/bin/ in
the results, which would be incorrectly be interpreted as if the
sudoers file had specified a directory.
* "visudo -c" will now list any include files that were checked
in addition to the main sudoers file when everything parses OK.
* Users that only have read-only access to the sudoers file may
now run "visudo -c". Previously, write permissions were required
even though no writing is down in check-only mode.
What's new in Sudo 1.7.8p2?
* Fixed a crash in the monitor process on Solaris when NOPASSWD
was specified or when authentication was disabled.
What's new in Sudo 1.7.7
* I/O logging is now supported for commands run in background mode
(using sudo's -b flag).
* Group ownership of the sudoers file is now only enforced when
the file mode on sudoers allows group readability or writability.
* Visudo now checks the contents of an alias and warns about cycles
when the alias is expanded.
* If the user specifes a group via sudo's -g option that matches
the target user's group in the password database, it is now
allowed even if no groups are present in the Runas_Spec.
* "sudo -i command" now works correctly with the bash version
2.0 and higher. Previously, the .bash_profile would not be
sourced prior to running the command unless bash was built with
NON_INTERACTIVE_LOGIN_SHELLS defined.
* Multi-factor authentication is now supported on AIX.
* Added support for non-RFC 4517 compliant LDAP servers that require
that seconds be present in a timestamp, such as Tivoli Directory Server.
* If the group vector is to be preserved, the PATH search for the
command is now done with the user's original group vector.
* For LDAP-based sudoers, the "runas_default" sudoOption now works
properly in a sudoRole that contains a sudoCommand.
* Spaces in command line arguments for "sudo -s" and "sudo -i" are
now escaped with a backslash when checking the sudoers file.
What's new in Sudo 1.7.6p2
* Two-character CIDR-style IPv4 netmasks are now matched correctly
in the sudoers file.
* A build error with MIT Kerberos V has been resolved.
What's new in Sudo 1.7.6p1
* A non-existent includedir is now treated the same as an empty
directory and not reported as an error.
* Removed extraneous parens in LDAP filter when sudoers_search_filter
is enabled that can cause an LDAP search error.
* pkgsrc change: trying to use user-destdir.
What's new in Sudo 1.7.5?
* When using visudo in check mode, a file named "-" may be used to
check sudoers data on the standard input.
* Sudo now only fetches shadow password entries when using the
password database directly for authentication.
* Password and group entries are now cached using the same key
that was used to look them up. This fixes a problem when looking
up entries by name if the name in the retrieved entry does not
match the name used to look it up. This may happen on some systems
that do case insensitive lookups or that truncate long names.
* GCC will no longer display warnings on glibc systems that use
the warn_unused_result attribute for write(2) and other system calls.
* If a PAM account management module denies access, sudo now prints
a more useful error message and stops trying to validate the user.
* Fixed a potential hang on idle systems when the sudo-run process
exits immediately.
* Sudo now includes a copy of zlib that will be used on systems
that do not have zlib installed.
* The --with-umask-override configure flag has been added to enable
the "umask_override" sudoers Defaults option at build time.
* Sudo now unblocks all signals on startup to avoid problems caused
by the parent process changing the default signal mask.
* LDAP Sudoers entries may now specify a time period for which
the entry is valid. This requires an updated sudoers schema
that includes the sudoNotBefore and sudoNotAfter attributes.
Support for timed entries must be explicitly enabled in the
ldap.conf file. Based on changes from Andreas Mueller.
* LDAP Sudoers entries may now specify a sudoOrder attribute that
determines the order in which matching entries are applied. The
last matching entry is used, just like file-based sudoers. This
requires an updated sudoers schema that includes the sudOrder
attribute. Based on changes from Andreas Mueller.
* When run as sudoedit, or when given the -e flag, sudo now treats
command line arguments as pathnames. This means that slashes
in the sudoers file entry must explicitly match slashes in
the command line arguments. As a result, and entry such as:
user ALL = sudoedit /etc/*
will allow editing of /etc/motd but not /etc/security/default.
* NETWORK_TIMEOUT is now an alias for BIND_TIMELIMIT in ldap.conf for
compatibility with OpenLDAP configuration files.
* The LDAP API TIMEOUT parameter is now honored in ldap.conf.
* The I/O log directory may now be specified in the sudoers file.
* Sudo will no longer refuse to run if the sudoers file is writable
by root.
* Sudo now performs command line escaping for "sudo -s" and "sudo -i"
after validating the command so the sudoers entries do not need
to include the backslashes.
* Logging and email sending are now done in the locale specified
by the "sudoers_locale" setting ("C" by default). Email send by
sudo now includes MIME headers when "sudoers_locale" is not "C".
* The configure script has a new option, --disable-env-reset, to
allow one to change the default for the sudoers Default setting
"env_reset" at compile time.
* When logging "sudo -l command", sudo will now prepend "list "
to the command in the log line to distinguish between an
actual command invocation in the logs.
* Double-quoted group and user names may now include escaped double
quotes as part of the name. Previously this was a parse error.
* Sudo once again restores the state of the signal handlers it
modifies before executing the command. This allows sudo to be
used with the nohup command.
* Resuming a suspended shell now works properly when I/O logging
is not enabled (the I/O logging case was already correct).
What's new in Sudo 1.7.4p6?
* A bug has been fixed in the I/O logging support that could cause
visual artifacts in full-screen programs such as text editors.
What's new in Sudo 1.7.4p5?
* A bug has been fixed that would allow a command to be run without the
user entering a password when sudo's -g flag is used without the -u flag.
* If user has no supplementary groups, sudo will now fall back on checking
the group file explicitly, which restores historic sudo behavior.
* A crash has been fixed when sudo's -g flag is used without the -u flag
and the sudoers file contains an entry with no runas user or group listed.
* A bug has been fixed in the I/O logging support that could cause
visual artifacts in full-screen programs such as text editors,.
* A crash has been fixed when the Solaris project support is enabled
and sudo's -g flag is used without the -u flag.
* Sudo no longer exits with an error when support for auditing is
compiled in but auditing is not enabled.
* Fixed a bug introduced in sudo 1.7.3 where the ticket file was not
being honored when the "targetpw" sudoers Defaults option was enabled.
* The LOG_INPUT and LOG_OUTPUT tags in sudoers are now parsed correctly.
* A crash has been fixed in "sudo -l" when sudo is built with auditing
support and the user is not allowed to run any commands on the host.
* Install README.LDAP when "ldap" is enabled in PKG_OPTIONS.
* Fix build problem when "kerberos" is enabled in PKG_OPTIONS.
Bump PKGREVISION since default PLIST has changed.
relevant bugs) version:
Major changes between version 1.7.4p3 and 1.7.4p4:
* A potential security issue has been fixed with respect to the
handling of sudo's -g command line option when -u is also
specified. The flaw may allow an attacker to run commands as a
user that is not authorized by the sudoers file.
* A bug has been fixed where "sudo -l" output was incomplete if
multiple sudoers sources were defined in nsswitch.conf and there
was an error querying one of the sources.
* The log_input, log_output, and use_pty sudoers options now work
correctly on AIX. Previously, sudo would hang if they were
enabled.
* Fixed "make install" when sudo is built in a directory other
than the directory that holds the sources.
* The runas_default sudoers setting now works properly in a
per-command Defaults line.
* Suspending and resuming the bash shell when PAM is in use now
works properly. The SIGCONT signal was not being propagated to
the child process.
Major changes between version 1.7.4p2 and 1.7.4p3:
* A bug has been fixed where duplicate HOME environment variables
could be set when the env_reset setting was disabled and the
always_set_home setting was enabled in sudoers.
* The value of sysconfdir is now substituted into the path to the
sudoers.d directory in the installed sudoers file.
* Fixed compilation problems on Irix and other platforms.
* If multiple PAM "auth" actions are specified and the user enters
^C at the password prompt, sudo will now abort any subsequent
"auth" actions. Previously it was necessary to enter ^C once for
each "auth" action.
Major changes between version 1.7.4p1 and 1.7.4p2:
* Fixed a bug where sudo could spin in a cpu loop waiting for the
child process.
* Packaging fixes for sudo.pp to better handle patchlevels.
Major changes between version 1.7.4 and 1.7.4p1:
* Fix a bug introduced in sudo 1.7.3 that prevented the -k and -K
options from functioning when the tty_tickets sudoers option was
enabled.
* Sudo no longer prints a warning when the -k or -K options are
specified and the ticket file does not exist.
* Changes to the configure script to enable cross-compilation of
Sudo.
Major changes between version 1.7.3 and 1.7.4:
* Sudoedit will now preserve the file extension in the name of the
temporary file being edited. The extension is used by some
editors (such as emacs) to choose the editing mode.
* Time stamp files have moved from /var/run/sudo to either
/var/db/sudo, /var/lib/sudo or /var/adm/sudo. The directories
are checked for existence in that order. This prevents users
from receiving the sudo lecture every time the system reboots.
Time stamp files older than the boot time are ignored on systems
where it is possible to determine this.
* Ancillary documentation (README files, LICENSE, etc) is now
installed in a sudo documentation directory.
* Sudo now recognizes "tls_cacert" as an alias for "tls_cacertfile"
in ldap.conf.
* Defaults settings that are tied to a user, host or command may
now include the negation operator. For example:
Defaults:!millert lecture
will match any user but millert.
* The default PATH environment variable, used when no PATH variable
exists, now includes /usr/sbin and /sbin.
* Sudo now uses polypkg for cross-platform packing.
* On Linux, sudo will now restore the nproc resource limit before
executing a command, unless the limit appears to have been
modified by pam_limits. This avoids a problem with bash scripts
that open more than 32 descriptors on SuSE Linux, where
sysconf(_SC_CHILD_MAX) will return -1 when RLIMIT_NPROC is set
to RLIMIT_UNLIMITED (-1).
* Visudo will now treat an unrecognized Defaults entry as a parse
error (sudo will warn but still run).
* The HOME and MAIL environment variables are now reset based on
the target user's password database entry when the env_reset
sudoers option is enabled (which is the case in the default
configuration). Users wishing to preserve the original values
should use a sudoers entry like:
Defaults env_keep += HOME
to preserve the old value of HOME and
Defaults env_keep += MAIL
to preserve the old value of MAIL.
* The tty_tickets option is now on by default.
* Fixed a problem in the restoration of the AIX authdb registry
setting.
* If PAM is in use, wait until the process has finished before
closing the PAM session.
* Fixed "sudo -i -u user" where user has no shell listed in the
password database.
* When logging I/O, sudo now handles pty read/write returning ENXIO,
as seen on FreeBSD when the login session has been killed.
* Sudo now performs I/O logging in the C locale. This avoids
locale-related issues when parsing floating point numbers in the
timing file.
* Added support for Ubuntu-style admin flag dot files.
Major changes between version 1.7.2p8 and 1.7.3:
* Support for logging a command's input and output as well as the
ability to replay sessions. For more information, see the
documentation for the log_input and log_output Defaults options
in the sudoers manual. Also see the sudoreplay manual for
information on replaying I/O log sessions.
* The use_pty sudoers option can be used to force a command to be
run in a pseudo-pty, even when I/O logging is not enabled.
* On some systems, sudo can now detect when a user has logged out
and back in again when tty-based time stamps are in use.
Supported systems include Solaris systems with the devices file
system, Mac OS X, and Linux systems with the devpts filesystem
(pseudo-ttys only).
* On AIX systems, the registry setting in /etc/security/user is
now taken into account when looking up users and groups.
Sudo now applies the correct the user and group ids when running
a command as a user whose account details come from a different
source (e.g. LDAP or DCE vs. local files).
* Support for multiple sudoers_base and uri entries in ldap.conf.
When multiple entries are listed, sudo will try each one in the
order in which they are specified.
* Sudo's SELinux support should now function correctly when running
commands as a non-root user and when one of stdin, stdout or stderr
is not a terminal.
* Sudo will now use the Linux audit system with configure with the
--with-linux-audit flag.
* Sudo now uses mbr_check_membership() on systems that support it
to determine group membership. Currently, only Darwin (Mac OS X)
supports this.
* When the tty_tickets sudoers option is enabled but there is no
terminal device, sudo will no longer use or create a tty-based
ticket file. Previously, sudo would use a tty name of "unknown".
As a consequence, if a user has no terminal device, sudo will now
always prompt for a password.
* The passwd_timeout and timestamp_timeout options may now be
specified as floating point numbers for more granular timeout
values.
* Negating the fqdn option in sudoers now works correctly when sudo
is configured with the --with-fqdn option. In previous versions
of sudo the fqdn was set before sudoers was parsed.
Major changes between sudo 1.7.2p7 and 1.7.2p8:
* Fixed a crash on AIX when LDAP support is in use.
* Fixed problems with the QAS non-Unix group support
For more detail: http://www.sudo.ws/sudo/alerts/secure_path.html
Summary:
Sudo "secure path" feature works by replacing the PATH environment
variable with a value specified in the sudoers file, or at
compile time if the --with-secure-path configure option is used.
The flaw is that sudo only replaces the first instance of PATH
in the environment. If the program being run through sudo uses
the last instance of PATH in the environment, an attacker may
be able to avoid the "secure path" restrictions.
Sudo versions affected:
Sudo 1.3.1 through 1.6.9p22 and Sudo 1.7.0 through 1.7.2p6.
maya
triaxx
adam
wiz
spz
agc
kamil
jperkin
taca
sevan
kim
tron
ryoon
obache
asau
martin
sbd
hauke
abs
jmmv