Changelog for sudo-policy-sudo-auth-self-1.9.15p5-279.11.x86_64.rpm :

* Mon Jul 29 2024 Simon Lees - A quick note that bsc#1227574 is expected behavior in this version of sudo. It was a regression in 15.6 which doesn\'t have the /etc/ split for pam.d yet.
* Tue Jan 02 2024 Otto Hollmann - Update to 1.9.15p5:
* Fixed evaluation of the lecture, listpw, verifypw, and fdexec sudoers Defaults settings when used without an explicit value. Previously, if specified without a value they were evaluated as boolean false, even when the negation operator (\'!\') was not present.
* Fixed a bug introduced in sudo 1.9.14 that prevented LDAP netgroup queries using the NETGROUP_BASE setting from being performed.
* Sudo will now transparently rename a user\'s lecture file from the older name-based path to the newer user-ID-based path. GitHub issue #342.
* Fixed a bug introduced in sudo 1.9.15 that could cause a memory allocation failure if sysconf(_SC_LOGIN_NAME_MAX) fails. Bug #1066.
* Mon Dec 18 2023 Otto Hollmann - For existing products (SLE15-SP
* and older) keep using /etc and don\'t switch to /usr/etc. So only SLES16/ALP, Tumbleweed and newer products will use both /etc and /usr/etc locations.
* Mon Dec 18 2023 Otto Hollmann - Update to 1.9.15p4:
* Fixed a bug introduced in sudo 1.9.15 that could prevent a user’s privileges from being listed by sudo -l if the sudoers entry in /etc/nsswitch.conf contains [SUCCESS=return]. This did not affect the ability to run commands via sudo. Bug #1063.- Update to 1.9.15p3:
* Always disable core dumps when sudo sends itself a fatal signal. Fixes a problem where sudo could potentially dump core dump when it re-sends the fatal signal to itself. This is only an issue if the command
* received a signal that would normally result in a core dump but the command did not actually dump core.
* Fixed a bug matching a command with a relative path name when the sudoers rule uses shell globbing rules for the path name. Bug #1062.
* Permit visudo to be run even if the local host name is not set. GitHub issue #332.
* Fixed an editing error introduced in sudo 1.9.15 that could prevent sudoreplay from replaying sessions correctly. GitHub issue #334.
* Fixed a bug introduced in sudo 1.9.15 where sudo -l > /dev/null could hang on Linux systems. GitHub issue #335.
* Fixed a bug introduced in sudo 1.9.15 where Solaris privileges specified in sudoers were not applied to the command being run.
* Wed Nov 22 2023 Otto Hollmann - Update to 1.9.15p2:
* Fixed a bug on BSD systems where sudo would not restore the terminal settings on exit if the terminal had parity enabled. GitHub issue #326.- Update to 1.9.15p1:
* Fixed a bug introduced in sudo 1.9.15 that prevented LDAP-based sudoers from being able to read the ldap.conf file. GitHub issue #325.- Update to 1.9.15:
* Fixed an undefined symbol problem on older versions of macOS when \"intercept\" or \"log_subcmds\" are enabled in sudoers. GitHub issue #276.
* Fixed \"make check\" failure related to getpwent(3) wrapping on NetBSD.
* Fixed the warning message for \"sudo -l command\" when the command is not permitted. There was a missing space between \"list\" and the actual command due to changes in sudo 1.9.14.
* Fixed a bug where output could go to the wrong terminal if \"use_pty\" is enabled (the default) and the standard input, output or error is redirected to a different terminal. Bug #1056.
* The visudo utility will no longer create an empty file when the specified sudoers file does not exist and the user exits the editor without making any changes. GitHub issue #294.
* The AIX and Solaris sudo packages on www.sudo.ws now support \"log_subcmds\" and \"intercept\" with both 32-bit and 64-bit binaries. Previously, they only worked when running binaries with the same word size as the sudo binary. GitHub issue #289.
* The sudoers source is now logged in the JSON event log. This makes it possible to tell which rule resulted in a match.
* Running \"sudo -ll command\" now produces verbose output that includes matching rule as well as the path to the sudoers file the matching rule came from. For LDAP sudoers, the name of the matching sudoRole is printed instead.
* The embedded copy of zlib has been updated to version 1.3.
* The sudoers plugin has been modified to make it more resilient to ROWHAMMER attacks on authentication and policy matching. This addresses CVE-2023-42465.
* The sudoers plugin now constructs the user time stamp file path name using the user-ID instead of the user name. This avoids a potential problem with user names that contain a path separator (\'/\') being interpreted as part of the path name. A similar issue in sudo-rs has been assigned CVE-2023-42456.
* A path separator (\'/\') in a user, group or host name is now replaced with an underbar character (\'_\') when expanding escapes in AATTinclude and AATTincludedir directives as well as the \"iolog_file\" and \"iolog_dir\" sudoers Default settings.
* The \"intercept_verify\" sudoers option is now only applied when the \"intercept\" option is set in sudoers. Previously, it was also applied when \"log_subcmds\" was enabled. Sudo 1.9.14 contained an incorrect fix for this. Bug #1058.
* Changes to terminal settings are now performed atomically, where possible. If the command is being run in a pseudo-terminal and the user\'s terminal is already in raw mode, sudo will not change the user\'s terminal settings. This prevents concurrent sudo processes from restoring the terminal settings to the wrong values. GitHub issue #312.
* Reverted a change from sudo 1.9.4 that resulted in PAM session modules being called with the environment of the command to be run instead of the environment of the invoking user. GitHub issue #318.
* New Indonesian translation from translationproject.org.
* The sudo_logsrvd server will now raise its open file descriptor limit to the maximum allowed value when it starts up. Each connection can require up to nine open file descriptors so the default soft limit may be too low.
* Better log message when rejecting a command if the \"intercept\" option is enabled and the \"intercept_allow_setid\" option is disabled. Previously, \"command not allowed\" would be logged and the user had no way of knowing what the actual problem was.
* Sudo will now log the invoking user\'s environment as \"submitenv\" in the JSON logs. The command\'s environment (\"runenv\") is no longer logged for commands rejected by the sudoers file or an approval plugin.
* Tue Nov 21 2023 Dominique Leuenberger - Package/ship empty /etc/sudoers.d directory for admins to discover where to put their won config.
* Wed Sep 20 2023 Ludwig Nussel - Introduce optional wheel and sudo group policies as separate packages (bsc#1203978, jsc#PED-260)
* Thu Sep 14 2023 Otto Hollmann - Install config files into /usr/etc and read from both location: /etc and /usr/etc (bsc#1205118)
* Tue Sep 12 2023 Otto Hollmann - Update to 1.9.14p3:
* Fixed a crash with Python 3.12 when the sudo Python python is unloaded. This only affects make check for the Python plugin.
* Adapted the sudo Python plugin test output to match Python 3.12.- Update to 1.9.14p2:
* Fixed a crash on Linux systems introduced in version 1.9.14 when running a command with a NULL argv[0] if log_subcmds or intercept is enabled in sudoers.
* Fixed a problem with \"stair-stepped\" output when piping or redirecting the output of a sudo command that takes user input when running a command in a pseudo-terminal.
* Fixed a bug introduced in sudo 1.9.14 that affects matching sudoers rules containing a Runas_Spec with an empty Runas user. These rules should only match when sudo’s -g option is used but were matching even without the -g option. #290.
* Wed Jul 12 2023 Paolo Stivanin - Update to 1.9.14p1:
* Fixed an invalid free bug in sudo_logsrvd that was introduced in version 1.9.14 which could cause sudo_logsrvd to crash.
* The sudoers plugin no longer tries to send the terminal name to the log server when no terminal is present. This bug was introduced in version 1.9.14.
* Fixed a bug where if the \"intercept\" or \"log_subcmds\" sudoers option was enabled and a sub-command was run where the first entry of the argument vector didn\'t match the command being run. This resulted in commands like \"sudo su -\" being killed due to the mismatch. Bug #1050.
* The sudoers plugin now canonicalizes command path names before matching (where possible). This fixes a bug where sudo could execute the wrong path if there are multiple symbolic links with the same target and the same base name in sudoers that a user is allowed to run. GitHub issue #228.
* Improved command matching when a chroot is specified in sudoers. The sudoers plugin will now change the root directory id needed before performing command matching. Previously, the root directory was simply prepended to the path that was being processed.
* When NETGROUP_BASE is set in the ldap.conf file, sudo will now perform its own netgroup lookups of the host name instead of using the system innetgr(3) function. This guarantees that user and host netgroup lookups are performed using the same LDAP server (or servers).
* Fixed a bug introduced in sudo 1.9.13 that resulted in a missing \" ; \" separator between environment variables and the command in log entries.
* The visudo utility now displays a warning when it ignores a file in an include dir such as /etc/sudoers.d.
* When running a command in a pseudo-terminal, sudo will initialize the terminal settings even if it is the background process. Previously, sudo only initialized the pseudo-terminal when running in the foreground. This fixes an issue where a program that checks the window size would read the wrong value when sudo was running in the background.
* Fixed a bug where only the first two digits of the TSID field being was logged. Bug #1046.
* The \"log_pty\" sudoers option is now enabled by default. To restore the historic behavior where a command is run in the user\'s terminal, add \"Defaults !use_pty\" to the sudoers file. GitHub issue #258.
* Sudo\'s \"-b\" option now works when the command is run in a pseudo-terminal.
* When disabling core dumps, sudo now only modifies the soft limit and leaves the hard limit as-is. This avoids problems on Linux when sudo does not have CAP_SYS_RESOURCE, which may be the case when run inside a container. GitHub issue #42.
* Sudo configuration file paths have been converted to colon-separated lists of paths. This makes it possible to have configuration files on a read-only file system while still allowing for local modifications in a different (writable) directory. The new - -enable-adminconf configure option can be used to specify a directory that is searched for configuration files in preference to the sysconfdir (which is usually /etc).
* The \"intercept_verify\" sudoers option is now only applied when the \"intercept\" option is set in sudoers. Previously, it was also applied when \"log_subcmds\" was enabled.
* The NETGROUP_QUERY ldap.conf parameter can now be disabled for LDAP servers that do not support querying the nisNetgroup object by its nisNetgroupTriple attribute, while still allowing sudo to query the LDAP server directly to determine netgroup membership.
* Fixed a long-standing bug where a sudoers rule without an explicit runas list allowed the user to run a command as root and any group instead of just one of the groups that root is a member of. For example, a rule such as \"myuser ALL = ALL\" would permit \"sudo -u root -g othergroup\" even if root did not belong to \"othergroup\".
* Fixed a bug where a sudoers rule with an explicit runas list allowed a user to run sudo commands as themselves. For example, a rule such as \"myuser ALL = (root) ALL\", \"myuser\" should only allow commands to be run as root (optionally using one of root\'s groups). However, the rule also allowed the user to run \"sudo -u myuser -g myuser command\".
* Fixed a bug that prevented the user from specifying a group on the command line via \"sudo -g\" if the rule\'s Runas_Spec contained a Runas_Alias.
* Sudo now requires a C compiler that conforms to ISO C99 or higher to build.
* Fri Mar 31 2023 Michal Koutný - sudo.pamd: Use common-session-nonlogin for >15 codestreams More info in https://github.com/SUSE/pam-config/pull/16
* Thu Mar 09 2023 Jason Sikes - Update to 1.9.13p3: Fixed a bug introduced in sudo 1.9.13 that caused a syntax error when list was used as a user or host name. GitHub issue #246. Fixed a bug that could cause sudo to hang when running a command in a pseudo-terminal when there is still input buffered after a command has exited. [bsc#1203201] Fixed sudo -U otheruser -l command. This is a regression in sudo 1.9.13. GitHub issue #248. Fixed sudo -l command args when matching a command in sudoers with command line arguments. This is a regression in sudo 1.9.13. GitHub issue #249.
* Tue Feb 28 2023 Jason Sikes - Update to 1.9.13p2 (bsc#1208595, CVE-2023-27320): Fixed the --enable-static-sudoers option, broken in sudo 1.9.13. GitHub issue #245. Fixed a potential double-free bug when matching a sudoers rule that contains a per-command chroot directive (CHROOT=dir). This bug was introduced in sudo 1.9.8.
* Sun Feb 19 2023 Jason Sikes - Update to 1.9.13p1: Fixed a typo in the configure script that resulted in a line like “]: command not found” in the output. GitHub issue #238. Corrected the order of the C23 [[noreturn]] attribute in function prototypes. This fixes a build error with GCC 13. GitHub issue #239. The check make target misbehaved when there was more than one version of the UTF-8 C locale in the output of locale -a. GitHub issue #241. Removed a dependency on the AC_SYS_YEAR2038 macro in configure.ac. This was added in autoconf 2.72 but sudo’s configure.ac only required autoconf 2.70. GitHub issue #242. Relaxed the autoconf version requirement to version 2.69.
* Wed Feb 15 2023 Jason Sikes - Update to 1.9.13:
* Changes in 1.9.13: Fixed a bug running relative commands via sudo when log_subcmds is enabled. GitHub issue #194. Fixed a signal handling bug when running sudo commands in a shell script. Signals were not being forwarded to the command when the sudo process was not run in its own process group. Fixed a bug in the cvtsudoers LDIF parsing when the file ends without a newline and a backslash is the last character of the file. Fixed a potential use-after-free bug with cvtsudoers filtering. GitHub issue #198. Added a reminder to the default lecture that the password will not echo. This line is only displayed when the pwfeedback option is disabled. GitHub issue #195. Fixed potential memory leaks in error paths. GitHub issue #199. GitHub issue #202. Fixed potential NULL dereferences on memory allocation failure. GitHub issue #204. GitHub issue #211. Sudo now uses C23-style attributes in function prototypes instead of gcc-style attributes if supported. Added a new list pseudo-command in sudoers to allow a user to list another user’s privileges. Previously, only root or a user with the ability to run any command as either root or the target user on the current host could use the -U option. This also includes a fix to the log entry when a user lacks permission to run sudo -U otheruser -l command. Previously, the logs would indicate that the user tried to run the actual command, now the log entry includes the list operation. JSON logging now escapes control characters if they happen to appear in the command or environment. New Albanian translation from translationproject.org. Regular expressions in sudoers or logsrvd.conf may no longer contain consecutive repetition operators. This is implementation- specific behavior according to POSIX, but some implementations will allocate excessive amounts of memory. This mainly affects the fuzzers. Sudo now builds AIX-style shared libraries and dynamic shared objects by default instead of svr4-style. This means that the default sudo plugins are now .a (archive) files that contain a .so shared object file instead of bare .so files. This was done to improve compatibility with the AIX Freeware ecosystem, specifically, the AIX Freeware build of OpenSSL. Sudo will still load svr4-style .so plugins and if a .so file is requested, either via sudo.conf or the sudoers file, and only the .a file is present, sudo will convert the path from plugin.so to plugin.a(plugin.so) when loading it. This ensures compatibility with existing configurations. To restore the old, pre-1.9.13 behavior, run configure using the –with-aix-soname=svr4 option. Sudo no longer checks the ownership and mode of the plugins that it loads. Plugins are configured via either the sudo.conf or sudoers file which are trusted configuration files. These checks suffered from time-of-check vs. time-of-use race conditions and complicate loading plugins that are not simple paths. Ownership and mode checks are still performed when loading the sudo.conf and sudoers files, which do not suffer from race conditions. The sudo.conf developer_mode setting is no longer used. Control characters in sudo log messages and sudoreplay -l output are now escaped in octal format. Space characters in the command path are also escaped. Command line arguments that contain spaces are surrounded by single quotes and any literal single quote or backslash characters are escaped with a backslash. This makes it possible to distinguish multiple command line arguments from a single argument that contains spaces. Improved support for DragonFly BSD which uses a different struct procinfo than either FreeBSD or 4.4BSD. Fixed a compilation error on Linux arm systems running older kernels that may not define EM_ARM in linux/elf-em.h. GitHub issue #232. Fixed a compilation error when LDFLAGS contains -Wl,–no-undefined. Sudo will now link using -Wl,–no-undefined by default if possible. GitHub issue #234. Fixed a bug executing a command with a very long argument vector when log_subcmds or intercept is enabled on a system where intercept_type is set to trace. GitHub issue #194. When sudo is configured to run a command in a pseudo-terminal but the standard input is not connected to a terminal, the command will now be run as a background process. This works around a problem running sudo commands in the background from a shell script where changing the terminal to raw mode could interfere with the interactive shell that ran the script. GitHub issue #237. A missing include file in sudoers is no longer a fatal error unless the error_recovery plugin argument has been set to false.
* Thu Jan 19 2023 Jason Sikes - Update to 1.9.12p2:
* Fixes bsc#1207082
* Changes in 1.9.12p2: Fixed a compilation error on Linux/aarch64. GitHub issue #197. Fixed a potential crash introduced in the fix GitHub issue #134. If a user’s sudoers entry did not have any RunAs user’s set, running sudo -U otheruser -l would dereference a NULL pointer. Fixed a bug introduced in sudo 1.9.12 that could prevent sudo from creating a I/O files when the iolog_file sudoers setting contains six or more Xs. Fixed a compilation issue on AIX with the native compiler. GitHub issue #231. Fixed CVE-2023-22809, a flaw in sudo’s -e option (aka sudoedit) that could allow a malicious user with sudoedit privileges to edit arbitrary files. For more information, see Sudoedit can edit arbitrary files.
* Mon Nov 21 2022 Jason Sikes - Update to 1.9.12p1:
* Changes in 1.9.12p1: - Sudo’s configure script now does a better job of detecting when the -fstack-clash-protection compiler option does not work. GitHub issue #191. - Fixed CVE-2022-43995, a potential out-of-bounds write for passwords smaller than 8 characters when passwd authentication is enabled. This does not affect configurations that use other authentication methods such as PAM, AIX authentication or BSD authentication. - Fixed a build error with some configurations compiling host_port.c.
* Dropped sudo-CVE-2022-43995.patch
* Thu Nov 03 2022 Jason Sikes - Added sudo-CVE-2022-43995.patch
* CVE-2022-43995
* bsc#1204986
* Fixed a potential heap-based buffer over-read when entering a password of seven characters or fewer and using the crypt() password backend.
* Tue Oct 25 2022 Jason Sikes - Update to 1.9.12:
* Dropped sudo-1.9.10-update_sudouser_to_utf8.patch
* Changes in Sudo 1.9.12:
* Fixed a bug when logging the command’s exit status in intercept mode. The wrong command could be logged with the exit status.
* For ptrace-based intercept mode, sudo will now attempt to verify that the command path name, arguments and environment have not changed from the time when they were authorized by the security policy. The new intercept_verify sudoers setting can be used to control this behavior.
* Fixed running commands with a relative path (e.g. ./foo) in intercept mode. Previously, this would fail if sudo’s current working directory was different from that of the command.
* Sudo now supports passing the execve(2) system call the NULL pointer for the argv and/or envp arguments when in intercept mode. Linux treats a NULL pointer like an empty array.
* The sudoers LDAP schema now allows sudoUser, sudoRunasUser and sudoRunasGroup to include UTF-8 characters, not just 7-bit ASCII.
* Fixed a problem with sudo -i on SELinux when the target user’s home directory is not searchable by sudo. GitHub issue #160.
* Neovim has been added to the list of visudo editors that support passing the line number on the command line.
* Fixed a bug in sudo’s SHA384 and SHA512 message digest padding.
* Added a new -N (no-update) command line option to sudo which can be used to prevent sudo from updating the user’s cached credentials. It is now possible to determine whether or not a user’s cached credentials are currently valid by running: $ sudo -Nnv and checking the exit value. One use case for this is to indicate in a shell prompt that sudo is “active” for the user.
* PAM approval modules are no longer invoked when running sub-commands in intercept mode unless the intercept_authenticate option is set. There is a substantial performance penalty for calling into PAM for each command run. PAM approval modules are still called for the initial command.
* Intercept mode on Linux now uses process_vm_readv(2) and process_vm_writev(2) if available.
* The XDG_CURRENT_DESKTOP environment variable is now preserved by default. This makes it possible for graphical applications to choose the correct theme when run via sudo.
* On 64-bit systems, if sudo fails to load a sudoers group plugin, it will use system-specific heuristics to try to locate a 64-bit version of the plugin.
* The cvtsudoers manual now documents the JSON and CSV output formats. GitHub issue #172.
* Fixed a bug where sub-commands were not being logged to a remote log server when log_subcmds was enabled. GitHub issue #174.
* The new log_stdin, log_stdout, log_stderr, log_ttyin, and log_ttyout sudoers settings can be used to support more fine-grained I/O logging. The sudo front-end no longer allocates a pseudo-terminal when running a command if the I/O logging plugin requests logging of stdin, stdout, or stderr but not terminal input/output.
* Quieted a libgcrypt run-time initialization warning. This fixes Debian bug #1019428 and Ubuntu bug #1397663.
* Fixed a bug in visudo that caused literal backslashes to be removed from the EDITOR environment variable. GitHub issue #179.
* The sudo Python plugin now implements the find_spec method instead of the the deprecated find_module. This fixes a test failure when a newer version of setuptools that doesn’t include find_module is found on the system.
* Fixed a bug introduced in sudo 1.9.9 where sudo_logsrvd created the process ID file, usually /var/run/sudo/sudo_logsrvd.pid, as a directory instead of a plain file. The same bug could result in I/O log directories that end in six or more X’s being created literally in addition to the name being used as a template for the mkdtemp(3) function.
* Fixed a long-standing bug where a sudoers rule with a command line argument of “”, which indicates the command may be run with no arguments, would also match a literal \"\" on the command line. GitHub issue #182.
* Added the -I option to visudo which only edits the main sudoers file. Include files are not edited unless a syntax error is found.
* Fixed sudo -l -U otheruser output when the runas list is empty. Previously, sudo would list the invoking user instead of the list user. GitHub issue #183.
* Fixed the display of command tags and options in sudo -l output when the RunAs user or group changes. A new line is started for RunAs changes which means we need to display the command tags and options again. GitHub issue #184.
* The sesh helper program now uses getopt_long(3) to parse the command line options.
* The embedded copy of zlib has been updated to version 1.2.13.
* Fixed a bug that prevented event log data from being sent to the log server when I/O logging was not enabled. This only affected systems without PAM or configurations where the pam_session and pam_setcred options were disabled in the sudoers file.
* Fixed a bug where sudo -l output included a carriage return after the newline. This is only needed when displaying to a terminal in raw mode. Bug #1042.
* Sat Sep 10 2022 Jason Sikes - Modified sudo-sudoers.patch
* bsc#1177578
* Removed redundant and confusing \'secure_path\' settings in sudo-sudoers file.
* Sat Aug 20 2022 Jason Sikes - Update to 1.9.11p3:
* Changes in Sudo 1.9.11
* Fixed a crash in the Python module with Python 3.9.10 on some systems. Additionally, make check now 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_MAX on systems that lack the getdelim() function.
* The tests run by make check now 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_BITS to 64 on systems that define __TIMESIZE in 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_logsrvd when 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_logsrvd when the tls_dhparams configuration setting was used.
* The intercept and log_subcmds functionality can now use ptrace(2) on Linux systems that support seccomp(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 use ptrace(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_PROFILE option 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.
* Changes in Sudo 1.9.11p1:
* Correctly handle EAGAIN in 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.
* Changes in Sudo 1.9.11p2:
* 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_logsrvd if the command returned no output.
* Changes in Sudo 1.9.11p3:
* 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.
* Modified sudo-sudoers.patch- Added sudo-1.9.10-update_sudouser_to_utf8.patch
* [bsc#1197998]
* Enable sudouser LDAP schema to use UTF-8 encodings.
* Sourced from https://github.com/sudo-project/sudo/pull/163
* Credit to William Brown, william.brownAATTsuse.com
* Mon Aug 08 2022 Thorsten Kukuk - Use %_pam_vendordir macro- Fix errors around LICENSE.md (fixes building on SLE12 SP5 again)
* Thu Mar 24 2022 Dirk Müller - update to 1.9.10:
* 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_logsrvd that operate like the sudoers options when logging terminal input.
* Fixed several few bugs in the cvtsudoers utility when merging multiple sudoers sources.
* Fixed a bug in sudo_logsrvd parsing the sudo_logsrvd.conf file, 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 -n option 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_logsrvd when 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 sudo when the sudoers entry in the nsswitch.conf file includes “sss” but no sudo provider is configured in /etc/sssd/sssd.conf.
* 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.
* A user may now only run sudo -U otheruser -l if 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 /proc is not available. If close_range(2) is present, it will be used in preference to /proc/self/fd.- drop sudo-1.9.9-honor-T_opt.patch , feature-upstream-restrict-sudo-U-other-l.patch (upstream)
* Thu Mar 03 2022 Jason Sikes - Add sudo-1.9.9-honor-T_opt.patch
* the -T option of sudo does nothing even when \'Defaults user_command_timeouts\' is present in the configuration.
* [bsc#1193446]
* Credit to Jaroslav Jindrak
* Wed Feb 16 2022 Simon Lees - Restrict use of sudo -U other -l to people who have permission to run commands as that user (bsc#1181703, jsc#SLE-22569)
* feature-upstream-restrict-sudo-U-other-l.patch
* Tue Feb 01 2022 Simon Lees - Update to 1.9.9
* 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.
* visudo now only warns about an undefined alias or a cycle in an alias once for each alias.
* The sudoRole cn was truncated by a single character in warning messages. GitHub issue #115.
* The cvtsudoers utility has new --group-file and --passwd-file options to use a custom passwd or group file when the - -match-local option is also used.
* The cvtsudoers utility can now filter or match based on a command.
* The cvtsudoers utility can now produce output in csv (comma-separated value) format. This can be used to help generate entitlement reports.
* Fixed a bug in sudo_logsrvd that could result in the connection being dropped for very long command lines.
* Fixed a bug where sudo_logsrvd would not accept a restore point of zero.
* Fixed a bug in visudo where the value of the editor setting was not used if it did not match the user’s EDITOR environment variable. This was only a problem if the env_editor setting was not enabled. Bug #1000.
* Sudo now builds with the -fcf-protection compiler option and the - z now linker option if supported.
* The output of sudoreplay -l now more closely matches the traditional sudo log format.
* The sudo_sendlog utility 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-wolfssl configure 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 -O and -P options to visudo, which can be used to check or set the owner and permissions. This can be used in conjunction with the -c option 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 cvtsudoers utility can now merge multiple sudoers sources into a single, combined sudoers file. If there are conflicting entries, cvtsudoers will 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 -n option), 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 -n option was specified. Bug #956 and GitHub issue #83.
* Fixed a regression introduced in version 1.9.1 when sudo is built with the --with-fqdn configure 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.- sudo no longer ships schema for LDAP.- sudo-feature-negated-LDAP-users.patch dropped, included upstream- refreshed sudo-sudoers.patch
* Thu Jan 27 2022 Simon Lees - Add support in the LDAP filter for negated users, patch taken from upstream (jsc#20068)
* Adds sudo-feature-negated-LDAP-users.patch
* Wed Sep 22 2021 Kristyna Streitova - update to 1.9.8p2
* Fixed a potential out-of-bounds read with \"sudo -i\" when the target user\'s shell is bash. This is a regression introduced in sudo 1.9.8. Bug #998.
* sudo_logsrvd now 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_logsrvd in 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.- update to 1.9.8p1
* Fixed support for passing a prompt (sudo -p) or a login class (sudo -l) on the command line. This is a regression introduced in sudo 1.9.8. Bug #993.
* Fixed a crash with \"sudo ALL\" rules 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-sudoers configure 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 the execl, execle, execlp, execv, execve, execvp, and execvpe library 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 INTERCEPT command tag that can be used in sudoers. For example: Cmnd_Alias SHELLS=/bin/bash, /bin/sh, /bin/csh, /bin/ksh, /bin/zsh Defaults!SHELLS intercept would 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: SHELLS would 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 additional 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.conf eventlog stanza.
* Support for logging sudo_logsrvd errors via syslog or to a file. Previously, most sudo_logsrvd errors 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_logsrvd had no effect when creating I/O log parent directories if the I/O log file name ended with the string \"XXXXXX\".
* 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 mksigname and mksiglist helper programs are now built with the host compiler, not the target compiler, when cross-compiling. Bug #989.
* Fixed compilation error when the --enable-static-sudoers configure option was specified. This was due to a typo introduced in sudo 1.9.7. GitHub PR #113.- pack /usr/libexec/sudo/sudo/sudo_intercept.so
* Fri Jul 30 2021 peter czanik - update to 1.9.7p2- enabled openssl support for secure central session recording collection (without it\'s clear text)- fixed SLES12 build
* When formatting JSON output, octal numbers are now stored as strings, not numbers. The JSON spec does not actually support octal numbers with a \'0\' prefix.
* 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.so now 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_copy or __va_copy and 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 #108.
* Fixed a bug introduced in sudo 1.9.7 that prevented sudo_logsrvd from accepting TLS connections when OpenSSL is used. Bug #988.
* Fixed an SELinux sudoedit bug when the edited temporary file could not be opened. The sesh helper would still be run even when there are no temporary files available to install.
* Fixed a compilation problem on FreeBSD.
* The sudo_noexec.so file is now built as a module on all systems other than macOS. This makes it possible to use other libtool implementations such as slibtool. On macOS shared libraries and modules are not interchangeable and the version of libtool shipped 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()-based getgrouplist() 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 between include/compat/nss_dbdefs.h and what HP-UX uses internally. On HP-UX we now just cycle through groups the slow way using getgrent(). Bug #978.
* Mon Jul 12 2021 Yaroslav Kurlaev - Fix commented out \"Defaults env_keep\" in sudo-sudoers.patch
* Mon Jul 12 2021 Yaroslav Kurlaev - Fix LC_TIME incorrectly named LC_ATIME
* Wed May 12 2021 Kristyna Streitova - update to 1.9.7
* The \"fuzz\" Makefile target now runs all the fuzzers for 8192 passes (can be overridden via the FUZZ_RUNS variable). This makes it easier to run the fuzzers in-tree. To run a fuzzer indefinitely, set FUZZ_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 -V\" to 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_sendlog when 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-client option.
* Sudo\'s limited support for SUCCESS=return entries in nsswitch.conf is now documented. Bug #971.
* Sudo now requires autoconf 2.70 or higher to regenerate the configure script. Bug #972.
* sudo_logsrvd now 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-openssl configure option is used or both the - -disable-log-client and --disable-log-server configure 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 SIGCHLD handler is set to SIG_IGN. This fixes the bug described by GitHub PR #98.
* Fixed an out-of-bounds read in sudoedit and visudo when the EDITOR, VISUAL or SUDO_EDITOR environment 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_sendlog utility 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 of sudo_logsrvd.
* Fixed a crash introduced in sudo 1.9.4 in sudo_logsrvd when 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.
* Sat Mar 20 2021 Dirk Müller - update to 1.9.6p1
* 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_sendlog compilation problem with the AIX xlC compiler.
* Fixed a regression introduced in sudo 1.9.4 where the - -disable-root-mailer configure option had no effect.
* Added a --disable-leaks configure 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 sudoOptions for an LDAP sudoRole that contains multiple sudoCommands. Previously, some of the options would only be applied to the first sudoCommand.
* Fixed a potential out of bounds read in the parsing of NOTBEFORE and NOTAFTER sudoers 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 uninstall\" from working.
* 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-fuzzer configure option can be combined with the - -enable-sanitizer option 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-sudoers configure option.
* 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_successful file configurable on systems where sudo is build with the --enable-admin-flag configure option. This mostly affects Ubuntu and its derivatives.
* 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=dir\" and \"CWD=dir\" sudoers command options. A path \"~/foo\" was expanded to \"/home/userfoo\" instead 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.
* 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_GETGROUPS is defined.
* Fixed a potential use-after-free in the PAM conversation function.
* Fixed potential redefinition of sys/stat.h macros in sudo_compat.h.
* Wed Jan 27 2021 Simon Lees - Update to 1.9.5.p2
* When invoked as sudoedit, the same set of command line options are now accepted as for sudo -e. The -H and -P options are now rejected for sudoedit and sudo -e which 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 -s or sudo -i). However, it was also possible to run sudoedit with the -s or -i flags in which case no escaping had actually been done, making a buffer overflow possible. This fixes CVE-2021-3156. (bsc#1181090)
* 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 KRB5CCNAME environment variable is now preserved when performing PAM authentication. This fixes GSSAPI authentication when the user has a non-default ccache.
* Thu Jan 14 2021 Kristyna Streitova - Update to 1.9.5.p1
* 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.- News in 1.9.5
* Fixed a crash introduced in 1.9.4 when running \"sudo -i\" as 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_logsrvd when 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.conf file. Previously, it was possible for the invoking user to manipulate the program name by setting argv[0] to an arbitrary value when executing sudo. (bsc#1180687)
* 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. (bsc#1180684)
* 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_symlinks to 1 will prevent the bug from being exploited. For more information see https://www.sudo.ws/alerts/sudoedit_selinux.html. (bsc#1180685)
* Added writability checks for sudoedit when SELinux RBAC is in use. This makes sudoedit behavior 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.