|
| 1 | +What's new in Sudo 1.9.11 |
| 2 | + |
| 3 | + * Fixed a crash in the Python module with Python 3.9.10 on some |
| 4 | + systems. Additionally, "make check" now passes for Python 3.9.10. |
| 5 | + |
| 6 | + * Error messages sent via email now include more details, including |
| 7 | + the file name and the line number and column of the error. |
| 8 | + Multiple errors are sent in a single message. Previously, only |
| 9 | + the first error was included. |
| 10 | + |
| 11 | + * Fixed logging of parse errors in JSON format. Previously, |
| 12 | + the JSON logger would not write entries unless the command and |
| 13 | + runuser were set. These may not be known at the time a parse |
| 14 | + error is encountered. |
| 15 | + |
| 16 | + * Fixed a potential crash parsing sudoers lines larger than twice |
| 17 | + the value of LINE_MAX on systems that lack the getdelim() function. |
| 18 | + |
| 19 | + * The tests run by "make check" now unset the LANGUAGE environment |
| 20 | + variable. Otherwise, localization strings will not match if |
| 21 | + LANGUAGE is set to a non-English locale. Bug #1025. |
| 22 | + |
| 23 | + * The "starttime" test now passed when run under Debian faketime. |
| 24 | + Bug #1026. |
| 25 | + |
| 26 | + * The Kerberos authentication module now honors the custom password |
| 27 | + prompt if one has been specified. |
| 28 | + |
| 29 | + * The embedded copy of zlib has been updated to version 1.2.12. |
| 30 | + |
| 31 | + * Updated the version of libtool used by sudo to version 2.4.7. |
| 32 | + |
| 33 | + * Sudo now defines _TIME_BITS to 64 on systems that define __TIMESIZE |
| 34 | + in the header files (currently only GNU libc). This is required |
| 35 | + to allow the use of 64-bit time values on some 32-bit systems. |
| 36 | + |
| 37 | + * Sudo's "intercept" and "log_subcmds" options no longer force the |
| 38 | + command to run in its own pseudo-terminal. It is now also |
| 39 | + possible to intercept the system(3) function. |
| 40 | + |
| 41 | + * Fixed a bug in sudo_logsrvd when run in store-first relay mode |
| 42 | + where the commit point messages sent by the server were incorrect |
| 43 | + if the command was suspended or received a window size change |
| 44 | + event. |
| 45 | + |
| 46 | + * Fixed a potential crash in sudo_logsrvd when the "tls_dhparams" |
| 47 | + configuration setting was used. |
| 48 | + |
| 49 | + * The "intercept" and "log_subcmds" functionality can now use |
| 50 | + ptrace(2) on Linux systems that support seccomp(2) filtering. |
| 51 | + This has the advantage of working for both static and dynamic |
| 52 | + binaries and can work with sudo's SELinux RBAC mode. The following |
| 53 | + architectures are currently supported: i386, x86_64, aarch64, |
| 54 | + arm, mips (log_subcmds only), powerpc, riscv, and s390x. The |
| 55 | + default is to use ptrace(2) where possible; the new "intercept_type" |
| 56 | + sudoers setting can be used to explicitly set the type. |
| 57 | + |
| 58 | + * New Georgian translation from translationproject.org. |
| 59 | + |
| 60 | + * Fixed creating packages on CentOS Stream. |
| 61 | + |
| 62 | + * Fixed a bug in the intercept and log_subcmds support where |
| 63 | + the execve(2) wrapper was using the current environment instead |
| 64 | + of the passed environment pointer. Bug #1030. |
| 65 | + |
| 66 | + * Added AppArmor integration for Linux. A sudoers rule can now |
| 67 | + specify an APPARMOR_PROFILE option to run a command confined by |
| 68 | + the named AppArmor profile. |
| 69 | + |
| 70 | + * Fixed parsing of the "server_log" setting in sudo_logsrvd.conf. |
| 71 | + Non-paths were being treated as paths and an actual path was |
| 72 | + treated as an error. |
| 73 | + |
1 | 74 | What's new in Sudo 1.9.10 |
2 | 75 |
|
3 | 76 | * Added new "log_passwords" and "passprompt_regex" sudoers options. |
|
0 commit comments