Stable Release
The current stable release of the sudo 1.9 branch is version 1.9.11p3. For the sudo 1.8 branch, see legacy releases.
For full details of all changes, see the ChangeLog file or view the commit history via mercurial or GitHub
-
Fixed “connection reset” errors on AIX when running shell scripts with the intercept or log_subcmds sudoers options enabled. Bug #1034.
-
Fixed very slow execution of shell scripts when the intercept or log_subcmds sudoers options are set on systems that enable Nagle’s algorithm on the loopback device, such as AIX. Bug #1034.
-
Fixed a compilation error on Linux/x86_64 with the x32 ABI.
-
Fixed a regression introduced in 1.9.11p1 that caused a warning when logging to
sudo_logsrvdif the command returned no output.
-
Correctly handle
EAGAINin the I/O read/right events. This fixes a hang seen on some systems when piping a large amount of data through sudo, such as via rsync. Bug #963. -
Changes to avoid implementation or unspecified behavior when bit shifting signed values in the protobuf library.
-
Fixed a compilation error on Linux/aarch64.
-
Fixed the configure check for
seccomp(2)support on Linux. -
Corrected the EBNF specification for tags in the sudoers manual page. GitHub issue #153.
-
Fixed a crash in the Python module with Python 3.9.10 on some systems. Additionally,
make checknow passes for Python 3.9.10. -
Error messages sent via email now include more details, including the file name and the line number and column of the error. Multiple errors are sent in a single message. Previously, only the first error was included.
-
Fixed logging of parse errors in JSON format. Previously, the JSON logger would not write entries unless the command and runuser were set. These may not be known at the time a parse error is encountered.
-
Fixed a potential crash parsing sudoers lines larger than twice the value of
LINE_MAXon systems that lack thegetdelim()function. -
The tests run by
make checknow unset the LANGUAGE environment variable. Otherwise, localization strings will not match if LANGUAGE is set to a non-English locale. Bug #1025. -
The “starttime” test now passed when run under Debian faketime. Bug #1026.
-
The Kerberos authentication module now honors the custom password prompt if one has been specified.
-
The embedded copy of zlib has been updated to version 1.2.12.
-
Updated the version of libtool used by sudo to version 2.4.7.
-
Sudo now defines
_TIME_BITSto 64 on systems that define__TIMESIZEin the header files (currently only GNU libc). This is required to allow the use of 64-bit time values on some 32-bit systems. -
Sudo’s intercept and log_subcmds options no longer force the command to run in its own pseudo-terminal. It is now also possible to intercept the
system(3)function. -
Fixed a bug in
sudo_logsrvdwhen run in store-first relay mode where the commit point messages sent by the server were incorrect if the command was suspended or received a window size change event. -
Fixed a potential crash in
sudo_logsrvdwhen the tls_dhparams configuration setting was used. -
The intercept and log_subcmds functionality can now use
ptrace(2)on Linux systems that supportseccomp(2)filtering. This has the advantage of working for both static and dynamic binaries and can work with sudo’s SELinux RBAC mode. The following architectures are currently supported: i386, x86_64, aarch64, arm, mips (log_subcmds only), powerpc, riscv, and s390x. The default is to useptrace(2)where possible; the new intercept_type sudoers setting can be used to explicitly set the type. -
New Georgian translation from translationproject.org.
-
Fixed creating packages on CentOS Stream.
-
Fixed a bug in the intercept and log_subcmds support where the
execve(2)wrapper was using the current environment instead of the passed environment pointer. Bug #1030. -
Added AppArmor integration for Linux. A sudoers rule can now specify an
APPARMOR_PROFILEoption to run a command confined by the named AppArmor profile. -
Fixed parsing of the server_log setting in
sudo_logsrvd.conf. Non-paths were being treated as paths and an actual path was treated as an error.
-
Added new log_passwords and passprompt_regex sudoers options. If log_passwords is disabled, sudo will attempt to prevent passwords from being logged. If sudo detects any of the regular expressions in the passprompt_regex list in the terminal output, sudo will log ‘*’ characters instead of the terminal input until a newline or carriage return is found in the input or an output character is received.
-
Added new log_passwords and passprompt_regex settings to
sudo_logsrvdthat operate like the sudoers options when logging terminal input. -
Fixed several few bugs in the
cvtsudoersutility when merging multiple sudoers sources. -
Fixed a bug in
sudo_logsrvdparsing thesudo_logsrvd.conffile, where the retry_interval in the [relay] section was not being recognized. -
Restored the pre-1.9.9 behavior of not performing authentication when sudo’s
-noption is specified. A new noninteractive_auth sudoers option has been added to enable PAM authentication in non-interactive mode. GitHub issue #131. -
On systems with
/proc, if the/proc/self/stat(Linux) or/proc/pid/psinfo(other systems) file is missing or invalid, sudo will now check file descriptors 0-2 to determine the user’s terminal. Bug #1020. -
Fixed a compilation problem on Debian kFreeBSD. Bug #1021.
-
Fixed a crash in
sudo_logsrvdwhen running in relay mode if an alert message is received. -
Fixed an issue that resulting in “problem with defaults entries” email to be sent if a user ran
sudowhen the sudoers entry in thensswitch.conffile includes “sss” but no sudo provider is configured in/etc/sssd/sssd.conf. Bug #1022. -
Updated the warning displayed when the invoking user is not allowed to run sudo. If sudo has been configured to send mail on failed attempts (see the mail_* flags in sudoers), it will now print “This incident has been reported to the administrator.” If the mailto or mailerpath sudoers settings are disabled, the message will not be printed and no mail will be sent.
-
Fixed a bug where the user-specified command timeout was not being honored if the sudoers rule did not also specify a timeout.
-
Added support for using POSIX extended regular expressions in sudoers rules. A command and/or arguments in sudoers are treated as a regular expression if they start with a ‘^’ character and end with a ‘$’. The command and arguments are matched separately, either one (or both) may be a regular expression. Bug #578, GitHub issue #15.
-
A user may now only run
sudo -U otheruser -lif they have a “sudo ALL” privilege where the RunAs user contains either root or otheruser. Previously, having “sudo ALL” was sufficient, regardless of the RunAs user. GitHub issue #134. -
The sudo lecture is now displayed immediately before the password prompt. As a result, sudo will no longer display the lecture unless the user needs to enter a password. Authentication methods that don’t interact with the user via a terminal do not trigger the lecture.
-
Sudo now uses its own closefrom() emulation on Linux systems. The glibc version may not work in a chroot jail where
/procis not available. If close_range(2) is present, it will be used in preference to/proc/self/fd.
-
Sudo can now be built with OpenSSL 3.0 without generating warnings about deprecated OpenSSL APIs.
-
A digest can now be specified along with the ALL command in the LDAP and SSSD back-ends. Sudo 1.9.0 introduced support for this in the sudoers file but did not include corresponding changes for the other back-ends.
-
visudonow only warns about an undefined alias or a cycle in an alias once for each alias. -
The
sudoRolecn was truncated by a single character in warning messages. GitHub issue #115. -
The
cvtsudoersutility has new--group-fileand--passwd-fileoptions to use a custom passwd or group file when the--match-localoption is also used. -
The
cvtsudoersutility can now filter or match based on a command. -
The
cvtsudoersutility can now produce output in csv (comma-separated value) format. This can be used to help generate entitlement reports. -
Fixed a bug in
sudo_logsrvdthat could result in the connection being dropped for very long command lines. -
Fixed a bug where
sudo_logsrvdwould not accept a restore point of zero. -
Fixed a bug in
visudowhere the value of the editor setting was not used if it did not match the user’sEDITORenvironment variable. This was only a problem if the env_editor setting was not enabled. Bug #1000. -
Sudo now builds with the
-fcf-protectioncompiler option and the-z nowlinker option if supported. -
The output of
sudoreplay -lnow more closely matches the traditional sudo log format. -
The
sudo_sendlogutility will now use the full contents of the log.json file, if present. This makes it possible to send sudo-format I/O logs that use the newer log.json format to sudo_logsrvd without losing any information. -
Fixed compilation of the arc4random_buf() replacement on systems with arc4random() but no arc4random_buf(). Bug #1008.
-
Sudo now uses its own getentropy() by default on Linux. The GNU libc version of getentropy() will fail on older kernels that don’t support the getrandom() system call.
-
It is now possible to build sudo with WolfSSL’s OpenSSL compatibility layer by using the
--enable-wolfsslconfigure option. -
Fixed a bug related to Daylight Saving Time when parsing timestamps in Generalized Time format. This affected the NOTBEFORE and NOTAFTER options in sudoers. Bug #1006.
-
Added the
-Oand-Poptions tovisudo, which can be used to check or set the owner and permissions. This can be used in conjunction with the-coption to check that the sudoers file ownership and permissions are correct. Bug #1007. -
It is now possible to set resource limits in the sudoers file itself. The special values default and “user” refer to the default system limit and invoking user limit respectively. The core dump size limit is now set to 0 by default unless overridden by the sudoers file.
-
The
cvtsudoersutility can now merge multiple sudoers sources into a single, combined sudoers file. If there are conflicting entries,cvtsudoerswill attempt to resolve them but manual intervention may be required. The merging of sudoers rules is currently fairly simplistic but will be improved in a future release. -
Sudo was parsing but not applying the “deref” and “tls_reqcert” ldap.conf settings. This meant the options were effectively ignored which broke dereferencing of aliases in LDAP. Bug #1013.
-
Clarified in the sudo man page that the security policy may override the user’s PATH environment variable. Bug #1014.
-
When sudo is run in non-interactive mode (with the
-noption), it will now attempt PAM authentication and only exit with an error if user interaction is required. This allows PAM modules that don’t interact with the user to succeed. Previously, sudo would not attempt authentication if the-noption was specified. Bug #956 and GitHub issue #83. -
Fixed a regression introduced in version 1.9.1 when sudo is built with the
--with-fqdnconfigure option. The local host name was being resolved before the sudoers file was processed, making it impossible to disable DNS lookups by negating the fqdn sudoers option. Bug #1016. -
Added support for negated sudoUser attributes in the LDAP and SSSD sudoers back ends. A matching sudoUser that is negated will cause the sudoRole containing it to be ignored.
-
Fixed a bug where the stack resource limit could be set to a value smaller than that of the invoking user and not be reset before the command was run. Bug #1016.
-
Fixed a potential out-of-bounds read with
sudo -iwhen the target user’s shell is bash. This is a regression introduced in sudo 1.9.8. Bug #998. -
sudo_logsrvdnow only sends a log ID for first command of a session. There is no need to send the log ID for each sub-command. -
Fixed a few minor memory leaks in intercept mode.
-
Fixed a problem with
sudo_logsrvdin relay mode if store_first was enabled when handling sub-commands. A new zero-length journal file was created for each sub-command instead of simply using the existing journal file.
-
Fixed support for passing a prompt (
sudo -p) or a login class (sudo -c) on the command line. This is a regression introduced in sudo 1.9.8. Bug #993. -
Fixed a crash with sudo
ALLrules in the LDAP and SSSD back-ends. This is a regression introduced in sudo 1.9.8. Bug #994. -
Fixed a compilation error when the
--enable-static-sudoersconfigure option was specified. This is a regression introduced in sudo 1.9.8 caused by a symbol clash with the intercept and log server protobuf functions.
-
It is now possible to transparently intercepting sub-commands executed by the original command run via sudo. Intercept support is implemented using
LD_PRELOAD(or the equivalent supported by the system) and so has some limitations. The two main limitations are that only dynamic executables are supported and only theexecl,execle,execlp,execv,execve,execvp, andexecvpelibrary functions are currently intercepted. Its main use case is to support restricting privileged shells run via sudo.To support this, there is a new intercept Defaults setting and an
INTERCEPTcommand tag that can be used in sudoers. For example:Cmnd_Alias SHELLS=/bin/bash, /bin/sh, /bin/csh, /bin/ksh, /bin/zsh Defaults!SHELLS interceptwould cause sudo to run the listed shells in intercept mode. This can also be set on a per-rule basis. For example:
Cmnd_Alias SHELLS=/bin/bash, /bin/sh, /bin/csh, /bin/ksh, /bin/zsh chuck ALL = INTERCEPT: SHELLSwould only apply intercept mode to user chuck when running one of the listed shells.
In intercept mode, sudo will not prompt for a password before running a sub-command and will not allow a set-user-ID or set-group-ID program to be run by default. The new intercept_authenticate and intercept_allow_setid sudoers settings can be used to change this behavior.
-
The new log_subcmds sudoers setting can be used to log commands run in a privileged shell. It uses the same mechanism as the intercept support described above and has the same limitations.
-
The new log_exit_status sudoers setting can be used to log the exit status commands run via sudo. This is also a corresponding log_exit setting in the
sudo_logsrvd.confeventlog stanza. -
Support for logging
sudo_logsrvderrors via syslog or to a file. Previously, mostsudo_logsrvderrors were only visible in the debug log. -
Better diagnostics when there is a TLS certificate validation error.
-
Using the
+=or-=operators in a Defaults setting that takes a string, not a list, now produces a warning from sudo and a syntax error from inside visudo. -
Fixed a bug where the iolog_mode setting in sudoers and
sudo_logsrvdhad no effect when creating I/O log parent directories if the I/O log file name ended with the stringXXXXXX. -
Fixed a bug in the sudoers custom prompt code where the size parameter that was passed to the
strlcpy()function was incorrect. No overflow was possible since the correct amount of memory was already pre-allocated. -
The
mksignameandmksiglisthelper programs are now built with the host compiler, not the target compiler, when cross-compiling. Bug #989. -
Fixed compilation error when the
--enable-static-sudoersconfigure option was specified. This was due to a typo introduced in sudo 1.9.7. GitHub PR #113.
-
When formatting JSON output, octal numbers are now stored as strings, not numbers. The JSON spec does not actually support octal numbers with a
0prefix. -
Fixed a compilation issue on Solaris 9.
-
Sudo now can handle the
getgroups()function returning a different number of groups for subsequent invocations. GitHub PR #106. -
When loading a Python plugin,
python_plugin.sonow verifies that the module loaded matches the one we tried to load. This allows sudo to display a more useful error message when trying to load a plugin with a name that conflicts with a Python module installed in the system location. -
Sudo no longer sets the the open files resource limit to unlimited while it runs. This avoids a problem where sudo’s
closefrom()emulation would need to close a very large number of descriptors on systems without a way to determine which ones are actually open. -
Sudo now includes a configure check for
va_copyor__va_copyand only defines its own version if the configure test fails. -
Fixed a bug in sudo’s utmp file handling which prevented old entries from being reused. As a result, the utmp (or utmpx) file was appended to unnecessarily. GitHub PR #107.
-
Fixed a bug introduced in sudo 1.9.7 that prevented
sudo_logsrvdfrom accepting TLS connections when OpenSSL is used. Bug #988.
-
Fixed an SELinux
sudoeditbug when the edited temporary file could not be opened. Theseshhelper would still be run even when there are no temporary files available to install. -
Fixed a compilation problem on FreeBSD.
-
The
sudo_noexec.sofile is now built as a module on all systems other than macOS. This makes it possible to use otherlibtoolimplementations such asslibtool. On macOS shared libraries and modules are not interchangeable and the version oflibtoolshipped with sudo must be used. -
Fixed a few bugs in the
getgrouplist()emulation on Solaris when reading from the local group file. -
Fixed a bug in sudo_logsrvd that prevented periodic relay server connection retries from occurring in store_first mode.
-
Disabled the
nss_search()-basedgetgrouplist()emulation on HP-UX due to a crash when the group source is set to compat in/etc/nsswitch.conf. This is probably due to a mismatch betweeninclude/compat/nss_dbdefs.hand what HP-UX uses internally. On HP-UX we now just cycle through groups the slow way usinggetgrent(). Bug #978.
-
The fuzz Makefile target now runs all the fuzzers for 8192 passes (can be overridden via the
FUZZ_RUNSvariable). This makes it easier to run the fuzzers in-tree. To run a fuzzer indefinitely, setFUZZ_RUNS=-1, e.g.make FUZZ_RUNS=-1 fuzz. -
Fixed fuzzing on FreeBSD where the ld.lld linker returns an error by default when a symbol is multiply-defined.
-
Added support for determining local IPv6 addresses on systems that lack the
getifaddrs()function. This now works on AIX, HP-UX and Solaris (at least). Bug #969. -
Fixed a bug introduced in sudo 1.9.6 that caused
sudo -Vto report a usage error. Also, when invoked as sudoedit, sudo now allows a more restricted set of options that matches the usage statement and documentation. GitHub Issue #95. -
Fixed a crash in
sudo_sendlogwhen the specified certificate or key does not exist or is invalid. Bug #970. -
Fixed a compilation error when sudo is configured with the
disable-log-clientoption. -
Sudo’s limited support for
SUCCESS=returnentries in nsswitch.conf is now documented. Bug #971. -
Sudo now requires autoconf 2.70 or higher to regenerate the configure script. Bug #972.
-
sudo_logsrvdnow has a relay mode which can be used to create a hierarchy of log servers. By default, when a relay server is defined, messages from the client are forwarded immediately to the relay. However, if the store_first setting is enabled, the log will be stored locally until the command completes and then relayed. Bug #965. -
Sudo now links with OpenSSL by default if it is available unless the
--disable-opensslconfigure option is used or both the--disable-log-clientand--disable-log-serverconfigure options are specified. -
Fixed configure’s Python version detection when the version minor number is more than a single digit, for example Python 3.10.
-
The sudo Python module tests now pass for Python 3.10.
-
Sudo will now avoid changing the datasize resource limit as long as the existing value is at least 1GB. This works around a problem on 64-bit HP-UX where it is not possible to exactly restore the original datasize limit. Bug #973.
-
Fixed a race condition that could result in a hang when sudo is executed by a process where the
SIGCHLDhandler is set toSIG_IGN. This fixes the bug described by GitHub PR #98. -
Fixed an out-of-bounds read in sudoedit and visudo when the
EDITOR,VISUALorSUDO_EDITORenvironment variables end in an unescaped backslash. Also fixed the handling of quote characters that are escaped by a backslash. GitHub Issue #99. -
Fixed a bug that prevented the log_server_verify sudoers option from taking effect.
-
The
sudo_sendlogutility has a new -s option to cause it to stop sending I/O records after a user-specified elapsed time. This can be used to test the I/O log restart functionality ofsudo_logsrvd. -
Fixed a crash introduced in sudo 1.9.4 in
sudo_logsrvdwhen attempting to restart an interrupted I/O log transfer. -
The TLS connection timeout in the sudoers log client was previously hard-coded to 10 seconds. It now uses the value of log_server_timeout.
-
The configure script now outputs a summary of the user-configurable options at the end, separate from output of configure script tests. Bug #820.
-
Corrected the description of which groups may be specified via the -g option in the Runas_Spec section. Bug #975.
- Fixed a regression introduced in sudo 1.9.6 that resulted in an error message instead of a usage message when sudo is run with no arguments.
-
Fixed a
sudo_sendlogcompilation problem with the AIX xlC compiler. -
Fixed a regression introduced in sudo 1.9.4 where the
--disable-root-mailerconfigure option had no effect. -
Added a
--disable-leaksconfigure option that avoids some memory leaks on exit that would otherwise occur. This is intended to be used with development tools that measure memory leaks. It is not safe to use in production at this time. -
Plugged some memory leaks identified by oss-fuzz and ASAN.
-
Fixed the handling of
sudoOptionsfor an LDAPsudoRolethat contains multiple sudoCommands. Previously, some of the options would only be applied to the firstsudoCommand. -
Fixed a potential out of bounds read in the parsing of
NOTBEFOREandNOTAFTERsudoers command options (and their LDAP equivalents). -
The parser used for reading I/O log JSON files is now more resilient when processing invalid JSON.
-
Fixed typos that prevented
make uninstallfrom working. GitHub issue #87. -
Fixed a regression introduced in sudo 1.9.4 where the last line in a sudoers file might not have a terminating NUL character added if no newline was present.
-
Integrated oss-fuzz and LLVM’s libFuzzer with sudo. The new
--enable-fuzzerconfigure option can be combined with the--enable-sanitizeroption to build sudo with fuzzing support. Multiple fuzz targets are available for fuzzing different parts of sudo. Fuzzers are built and tested via make fuzz or as part of make check (even when sudo is not built with fuzzing support). Fuzzing support currently requires the LLVM clang compiler (not gcc). -
Fixed the
--enable-static-sudoersconfigure option. GitHub issue #92. -
Fixed a potential out of bounds read sudo when is run by a user with more groups than the value of max_groups in sudo.conf.
-
Added an admin_flag sudoers option to make the use of the
~/.sudo_as_admin_successfulfile configurable on systems where sudo is build with the--enable-admin-flagconfigure option. This mostly affects Ubuntu and its derivatives. GitHub issue #56. -
The max_groups setting in sudo.conf is now limited to 1024. This setting is obsolete and should no longer be needed.
-
Fixed a bug in the tilde expansion of
CHROOT=dirandCWD=dirsudoers command options. A path~/foowas expanded to/home/userfooinstead of/home/user/foo. This also affects the runchroot and runcwd Defaults settings. -
Fixed a bug on systems without a native getdelim(3) function where very long lines could cause parsing of the sudoers file to end prematurely. Bug #960.
-
Fixed a potential integer overflow when converting the timestamp_timeout and passwd_timeout sudoers settings to a timespec struct.
-
The default for the group_source setting in sudo.conf is now dynamic on macOS. Recent versions of macOS do not reliably return all of a user’s non-local groups via
getgroups(2), even when_DARWIN_UNLIMITED_GETGROUPSis defined. Bug #946. -
Fixed a potential use-after-free in the PAM conversation function. Bug #967.
-
Fixed potential redefinition of
sys/stat.hmacros in sudo_compat.h. Bug #968.
-
Fixed sudo’s
setprogname(3)emulation on systems that don’t provide it. -
Fixed a problem with the sudoers log server client where a partial write to the server could result the sudo process consuming large amounts of CPU time due to a cycle in the buffer queue. Bug #954.
-
Added a missing dependency on libsudo_util in libsudo_eventlog. Fixes a link error when building sudo statically.
-
The user’s
KRB5CCNAMEenvironment variable is now preserved when performing PAM authentication. This fixes GSSAPI authentication when the user has a non-default ccache. -
When invoked as
sudoedit, the same set of command line options are now accepted as forsudo -e. The -H and -P options are now rejected forsudoeditandsudo -ewhich matches the sudo 1.7 behavior. This is part of the fix for CVE-2021-3156. -
Fixed a potential buffer overflow when unescaping backslashes in the command’s arguments. Normally, sudo escapes special characters when running a command via a shell (
sudo -sorsudo -i). However, it was also possible to runsudoeditwith the -s or -i flags in which case no escaping had actually been done, making a buffer overflow possible. This fixes CVE-2021-3156.
- Fixed a regression introduced in sudo 1.9.5 where the editor run by sudoedit was set-user-ID root unless SELinux RBAC was in use. The editor is now run with the user’s real and effective user-IDs.
-
Fixed a crash introduced in 1.9.4 when running
sudo -ias an unknown user. This is related to but distinct from Bug #948. -
If the lecture_file setting is enabled in sudoers, it must now refer to a regular file or a symbolic link to a regular file.
-
Fixed a potential use-after-free bug in
sudo_logsrvdwhen the server shuts down if there are existing connections from clients that are only logging events and not session I/O data. -
Fixed a buffer size mismatch when serializing the list of IP addresses for configured network interfaces. This bug is not actually exploitable since the allocated buffer is large enough to hold the list of addresses.
-
If sudo is executed with a name other than sudo or sudoedit, it will now fall back to sudo as the program name. This affects warning, help and usage messages as well as the matching of Debug lines in the
/etc/sudo.conffile. Previously, it was possible for the invoking user to manipulate the program name by settingargv[0]to an arbitrary value when executing sudo. -
Sudo now checks for failure when setting the close-on-exec flag on open file descriptors. This should never fail but, if it were to, there is the possibility of a file descriptor leak to a child process (such as the command sudo runs).
-
Fixed CVE-2021-23239, a potential information leak in sudoedit that could be used to test for the existence of directories not normally accessible to the user in certain circumstances. When creating a new file, sudoedit checks to make sure the parent directory of the new file exists before running the editor. However, a race condition exists if the invoking user can replace (or create) the parent directory. If a symbolic link is created in place of the parent directory, sudoedit will run the editor as long as the target of the link exists. If the target of the link does not exist, an error message will be displayed. The race condition can be used to test for the existence of an arbitrary directory. However, it cannot be used to write to an arbitrary location.
-
Fixed CVE-2021-23240, a flaw in the temporary file handling of sudoedit’s SELinux RBAC support. On systems where SELinux is enabled, a user with sudoedit permissions may be able to set the owner of an arbitrary file to the user-ID of the target user. On Linux kernels that support protected symlinks setting
/proc/sys/fs/protected_symlinksto 1 will prevent the bug from being exploited. For more information, see Symbolic link attack in SELinux-enabled sudoedit. -
Added writability checks for
sudoeditwhen SELinux RBAC is in use. This makessudoeditbehavior consistent regardless of whether or not SELinux RBAC is in use. Previously, the sudoedit_checkdir setting had no effect for RBAC entries. -
A new sudoers option selinux can be used to disable sudo’s SELinux RBAC support.
-
Quieted warnings from PVS Studio, clang analyzer, and cppcheck. Added suppression annotations for PVS Studio false positives.
- Fixed a bug introduced in sudo 1.9.4p1 which could lead to a crash if the sudoers file contains a runas user-specific Defaults entry. Bug #951.
-
Sudo on macOS now supports users with more than 16 groups without needing to set group_source to dynamic in
sudo.conf. Previously, only the first 15 were used when matching group-based rules in sudoers. Bug #946. -
Fixed a regression introduced in version 1.9.4 where sudo would not build when configured using the
--without-sendmailoption. Bug #947. -
Fixed a problem where if I/O logging was disabled and sudo was unable to connect to sudo_logsrvd, the command would still be allowed to run even when the ignore_logfile_errors sudoers option was enabled.
-
Fixed a crash introduced in version 1.9.4 when attempting to run a command as a non-existent user. Bug #948.
-
The installed
sudo.conffile now has the default sudoers Plugin lines commented out. This fixes a potential conflict when there is both a system-installed version of sudo and a user-installed version. GitHub Issue #75. -
Fixed a regression introduced in sudo 1.9.4 where sudo would run the command as a child process even when a pseudo-terminal was not in use and the pam_session and pam_setcred options were disabled. GitHub Issue #76.
-
Fixed a regression introduced in sudo 1.8.9 where the closefrom sudoers option could not be set to a value of 3. Bug #950.
-
The sudoers parser will now detect when an upper-case reserved word is used when declaring an alias. Now instead of “syntax error, unexpected CHROOT, expecting ALIAS” the message will be syntax error, reserved word CHROOT used as an alias name. Bug #941.
-
Better handling of sudoers files without a final newline. The parser now adds a newline at end-of-file automatically which removes the need for special cases in the parser.
-
Fixed a regression introduced in sudo 1.9.1 in the sssd back-end where an uninitialized pointer could be freed on an error path. GitHub Issue #67.
-
The core logging code is now shared between
sudo_logsrvdand thesudoersplugin. -
JSON log entries sent to syslog now use minimal JSON which skips all non-essential whitespace.
-
The sudoers plugin can now produce JSON-formatted logs. The log_format sudoers option can be used to select sudo or json format logs. The default is sudo format logs.
-
The sudoers plugin and visudo now display the column number in syntax error messages in addition to the line number. Bug #841.
-
If I/O logging is not enabled but log_servers is set, the sudoers plugin will now log accept events to sudo_logsrvd. Previously, the accept event was only sent when I/O logging was enabled. The sudoers plugin now sends reject and alert events too.
-
The sudo logsrv protocol has been extended to allow an AlertMessage to contain an optional array of InfoMessage, as AcceptMessage and RejectMessage already do.
-
Fixed a bug in sudo_logsrvd where receipt of
SIGHUPwould result in duplicate entries in the debug log when debugging was enabled. -
The visudo utility now supports
EDITORenvironment variables that use single or double quotes in the command arguments. Bug #942. -
The PAM session modules now run when sudo is set-user-ID root, which allows a module to determine the original user-ID. Bug #944.
-
Fixed a regression introduced in sudo 1.8.24 in the LDAP back-end where sudoNotBefore and sudoNotAfter were applied even when the
SUDOERS_TIMEDsetting was not present inldap.conf. Bug #945. -
Sudo packages for macOS 11 now contain universal binaries that support both Intel and Apple Silicon CPUs.
-
For sudo_logsrvd, an empty value for the pid_file setting in sudo_logsrvd.con will now disable the process ID file.
-
Fixed a regression introduced in sudo 1.9.3 where the configure script would not detect the
cryptfunction if it was present in the C library, not an additional library. -
Fixed a regression introduced in sudo 1.8.23 with shadow passwd file authentication on OpenBSD. BSD authentication was not affected.
-
Sudo now logs when a user-specified command-line option is rejected by a sudoers rule. Previously, these conditions were written to the audit log, but the default sudo log file. Affected command line arguments include
-C(--close-from),-D(--chdir),-R(--chroot),-g(--group) and-u(--user).
-
sudoeditwill now prompt the user before overwriting an existing file with one that is zero-length after editing. Bug #922. -
Fixed building the Python plugin on systems with a compiler that doesn’t support symbol hiding.
-
Sudo now uses a linker script to hide symbols even when the compiler has native symbol hiding support. This should make it easier to detect omissions in the symbol exports file, regardless of the platform.
-
Fixed the libssl dependency in Debian packages for older releases that use
libssl1.0.0. -
sudoandvisudonow provide more detailed messages when a syntax error is detected insudoers. The offending line and token are now displayed. If the parser was generated by GNU bison, additional information about what token was expected is also displayed. Bug #841. -
Sudoers rules must now end in either a newline or the end-of-file. Previously, it was possible to have multiple rules on a single line, separated by white space. The use of an end-of-line terminator makes it possible to display accurate error messages.
-
Sudo no longer refuses to run if a syntax error in the sudoers file is encountered. The entry with the syntax error will be discarded and sudo will continue to parse the file. This makes recovery from a syntax error less painful on systems where sudo is the primary method of superuser access. The historic behavior can be restored by add
error_recovery=falseto the sudoers plugin’s optional arguments insudo.conf. Bug #618. -
Fixed the sample_approval plugin’s symbol exports file for systems where the compiler doesn’t support symbol hiding.
-
Fixed a regression introduced in sudo 1.9.1 where arguments to the sudoers_policy plugin in
sudo.confwere not being applied. The sudoers file is now parsed by the sudoers_audit plugin, which is loaded implicitly when sudoers_policy is listed insudo.conf. Starting with sudo 1.9.3, if there are plugin arguments forsudoers_policybutsudoers_auditis not listed, those arguments will be applied tosudoers_auditinstead. -
The user’s resource limits are now passed to sudo plugins in the
user_info[]list. A plugin cannot determine the limits itself because sudo changes the limits while it runs to prevent resource starvation. -
It is now possible to set the working directory or change the root directory on a per-command basis using the
CWDandCHROOToptions. There are also new Defaults settings, runchroot and runcwd, that can be used to set the working directory or root directory on a more global basis. -
New
-D(--chdir) and-R(--chroot) command line options can be used to set the working directory or root directory if the sudoers file allows it. This functionality is not enabled by default and must be explicitly enabled in the sudoers file.
-
Fixed package builds on RedHat Enterprise Linux 8.
-
The configure script now uses pkg-config to find the openssl cflags and libs where possible.
-
The contents of the log.json I/O log file is now documented in the sudoers manual.
-
The sudoers plugin now properly exports the sudoers_audit symbol on systems where the compiler lacks symbol visibility controls. This caused a regression in 1.9.1 where a successful sudo command was not logged due to the missing audit plugin. Bug #931.
-
Fixed a regression introduced in 1.9.1 that can result in crash when there is a syntax error in the sudoers file. Bug #934.
-
Fixed an AIX-specific problem when I/O logging was enabled. The terminal device was not being properly set to raw mode. Bug #927.
-
Corrected handling of
sudo_logsrvdconnections without associated I/O log data. This fixes support for RejectMessage as well as AcceptMessage when the expect_iobufs flag is not set. -
Added an iolog_path entry to the JSON-format event log produced by
sudo_logsrvd. Previously, it was only possible to determine the I/O log file an event belonged to using sudo-format logs. -
Fixed the bundle IDs for
sudo-logsrvdandsudo-pythonmacOS packages. -
I/O log files produced by the sudoers plugin now clear the write bits on the I/O log timing file when the log is complete. This is consistent with how
sudo_logsrvdindicates that a log is complete. -
The
sudoreplayutility has a new -F (follow) command line option to allow replaying a session that is still in progress, similar totail -f. -
The
@includeand@includedirdirectives can be used in sudoers instead of#includeand#includedir. In addition, include paths may now have embedded white space by either using a double-quoted string or escaping the space characters with a backslash. -
Fixed some Solaris 11.4 compilation errors.
-
When running a command in a pty, sudo will no longer try to suspend itself if the user’s tty has been revoked (for instance when the parent ssh daemon is killed). This fixes a bug where sudo would continuously suspend the command (which would succeed), then suspend itself (which would fail due to the missing tty) and then resume the command.
-
If sudo’s event loop fails due to the tty being revoked, remove the user’s tty events and restart the event loop (once). This fixes a problem when running
sudo rebootin a pty on some systems. When the event loop exited unexpectedly, sudo would kill the command running in the pty, which in the case ofreboot, could lead to the system being in a half-rebooted state. -
Fixed a regression introduced in sudo 1.8.23 in the LDAP and SSSD back-ends where a missing
sudoHostattribute was treated as anALLwildcard value. AsudoRolewith nosudoHostattribute is now ignored as it was prior to version 1.8.23. -
The audit plugin API has been changed slightly. The sudo front-end now audits an accept event itself after all approval plugins are run and the I/O logging plugins (if any) are opened. This makes it possible for an audit plugin to only log a single overall accept event if desired.
-
The sudoers plugin can now be loaded as an audit plugin. Logging of successful commands is now performed in the audit plugin’s accept function. As a result, commands are now only logged if allowed by sudoers and all approval plugins. Commands rejected by an approval plugin are now also logged by the sudoers plugin.
-
Romanian translation for sudo and sudoers from translationproject.org.
-
Fixed a regression introduced in sudo 1.9.0 where
sudoeditdid not remove its temporary files after installing them. Bug #929. -
Fixed a regression introduced in sudo 1.9.0 where the iolog_file setting in
sudoersandsudo_logsrvd.confcaused an error if the file name ended in six or more X’s.
-
Fixed a test failure in the
strsig_teston FreeBSD. -
The maximum length of a conversation reply has been increased from 255 to 1023 characters. This allows for longer user passwords. Bug #860.
-
Sudo now includes a logging daemon, sudo_logsrvd, which can be used to implement centralized logging of I/O logs. TLS connections are supported when sudo is configured with the
--enable-openssloption. For more information, see the sudo_logsrvd, sudo_logsrvd.conf and sudo_logsrv.proto manuals as well as the log_servers setting in the sudoers manual.The
--disable-log-serverand--disable-log-clientconfigure options can be used to disable building the I/O log server and/or remote I/O log support in the sudoers plugin. -
The new
sudo_sendlogutility can be used to testsudo_logsrvdor send existing sudo I/O logs to a centralized server. -
It is now possible to write sudo plugins in Python 4 when sudo is configured with the
--enable-pythonoption. See the sudo_plugin_python manual for details.Sudo 1.9.0 comes with several Python example plugins that get installed sudo’s
examplesdirectory.The sudo blog article What’s new in sudo 1.9: Python includes a simple tutorial on writing python plugins.
-
Sudo now supports an audit plugin type. An audit plugin receives accept, reject, exit and error messages and can be used to implement custom logging that is independent of the underlying security policy. Multiple audit plugins may be specified in the sudo.conf file. A sample audit plugin is included that writes logs in JSON format.
-
Sudo now supports an approval plugin type. An approval plugin is run only after the main security policy (such as sudoers) accepts a command to be run. The approval policy may perform additional checks, potentially interacting with the user. Multiple approval plugins may be specified in the sudo.conf file. Only if all approval plugins succeed will the command be allowed.
-
Sudo’s -S command line option now causes the sudo conversation function to write to the standard output or standard error instead of the terminal device.
-
Fixed a bug where if a #include or #includedir directive was the last line in sudoers and there was no final newline character, it was silently ignored. Bug #917.
-
It is now possible to use
Cmd_Aliasinstead ofCmnd_Aliasin sudoers for people who find the former more natural. -
The new pam_ruser and pam_rhost sudoers settings can be used to enable or disable setting the PAM remote user and/or host values during PAM session setup.
-
More than one SHA-2 digest may now be specified for a single command. Multiple digests must be separated by a comma.
-
It is now possible to specify a SHA-2 digest in conjunction with the
ALLreserved word in a command specification. This allows one to give permission to run any command that matches the specified digest, regardless of its path. -
sudoandsudo_logsrvdnow create an extended I/O log info file in JSON format that contains additional information about the command that was run, such as the host name. The sudoreplay utility uses this file in preference to the legacy log file. -
The
sudoreplayutility can now match on a host name in list mode. The list output also now includes the host name if one is present in the log file. -
For
sudo -i, if the target user’s home directory does not exist, sudo will now warn about the problem but run the command in the current working directory. Previously, this was a fatal error. Debian bug #598519. -
The command line arguments in the
SUDO_COMMANDenvironment variable are now truncated at 4096 characters. This avoids an “Argument list too long” error when executing a command with a large number of arguments. Bug #923 and Debian bug #596631. -
Sudo now properly ends the PAM transaction when the user authenticates successfully but sudoers denies the command. Debian bug #669687.
-
The sudoers grammar in the manual now indicates that
sudoeditrequires one or more arguments. Debian bug #571621. -
When copying the edited files to the original path, sudoedit now allocates any additional space needed before writing. Previously, it could truncate the destination file if the file system was full. Bug #922.
-
Fixed an issue where PAM session modules could be called with the wrong user name when multiple users in the passwd database share the the same user-ID. Debian bug #734752.
-
Sudo command line options that take a value may only be specified once. This is to help guard against problems caused by poorly written scripts that invoke sudo with user-controlled input. Bug #924.