head 1.27; access; symbols pkgsrc-2026Q1:1.27.0.6 pkgsrc-2026Q1-base:1.27 pkgsrc-2025Q4:1.27.0.4 pkgsrc-2025Q4-base:1.27 pkgsrc-2025Q3:1.27.0.2 pkgsrc-2025Q3-base:1.27 pkgsrc-2025Q2:1.26.0.8 pkgsrc-2025Q2-base:1.26 pkgsrc-2025Q1:1.26.0.6 pkgsrc-2025Q1-base:1.26 pkgsrc-2024Q4:1.26.0.4 pkgsrc-2024Q4-base:1.26 pkgsrc-2024Q3:1.26.0.2 pkgsrc-2024Q3-base:1.26 pkgsrc-2024Q2:1.25.0.6 pkgsrc-2024Q2-base:1.25 pkgsrc-2024Q1:1.25.0.4 pkgsrc-2024Q1-base:1.25 pkgsrc-2023Q4:1.25.0.2 pkgsrc-2023Q4-base:1.25 pkgsrc-2023Q3:1.24.0.6 pkgsrc-2023Q3-base:1.24 pkgsrc-2023Q2:1.24.0.4 pkgsrc-2023Q2-base:1.24 pkgsrc-2023Q1:1.24.0.2 pkgsrc-2023Q1-base:1.24 pkgsrc-2022Q4:1.23.0.2 pkgsrc-2022Q4-base:1.23 pkgsrc-2022Q3:1.22.0.2 pkgsrc-2022Q3-base:1.22 pkgsrc-2022Q2:1.21.0.2 pkgsrc-2022Q2-base:1.21 pkgsrc-2022Q1:1.19.0.10 pkgsrc-2022Q1-base:1.19 pkgsrc-2021Q4:1.19.0.8 pkgsrc-2021Q4-base:1.19 pkgsrc-2021Q3:1.19.0.6 pkgsrc-2021Q3-base:1.19 pkgsrc-2021Q2:1.19.0.4 pkgsrc-2021Q2-base:1.19 pkgsrc-2021Q1:1.19.0.2 pkgsrc-2021Q1-base:1.19 pkgsrc-2020Q4:1.18.0.10 pkgsrc-2020Q4-base:1.18 pkgsrc-2020Q3:1.18.0.8 pkgsrc-2020Q3-base:1.18 pkgsrc-2020Q2:1.18.0.6 pkgsrc-2020Q2-base:1.18 pkgsrc-2020Q1:1.18.0.2 pkgsrc-2020Q1-base:1.18 pkgsrc-2019Q4:1.18.0.4 pkgsrc-2019Q4-base:1.18 pkgsrc-2019Q3:1.17.0.8 pkgsrc-2019Q3-base:1.17 pkgsrc-2019Q2:1.17.0.6 pkgsrc-2019Q2-base:1.17 pkgsrc-2019Q1:1.17.0.4 pkgsrc-2019Q1-base:1.17 pkgsrc-2018Q4:1.17.0.2 pkgsrc-2018Q4-base:1.17 pkgsrc-2018Q3:1.13.0.2 pkgsrc-2018Q3-base:1.13 pkgsrc-2018Q2:1.12.0.2 pkgsrc-2018Q2-base:1.12 pkgsrc-2018Q1:1.11.0.2 pkgsrc-2018Q1-base:1.11 pkgsrc-2017Q4:1.10.0.2 pkgsrc-2017Q4-base:1.10 pkgsrc-2017Q3:1.9.0.16 pkgsrc-2017Q3-base:1.9 pkgsrc-2017Q2:1.9.0.12 pkgsrc-2017Q2-base:1.9 pkgsrc-2017Q1:1.9.0.10 pkgsrc-2017Q1-base:1.9 pkgsrc-2016Q4:1.9.0.8 pkgsrc-2016Q4-base:1.9 pkgsrc-2016Q3:1.9.0.6 pkgsrc-2016Q3-base:1.9 pkgsrc-2016Q2:1.9.0.4 pkgsrc-2016Q2-base:1.9 pkgsrc-2016Q1:1.9.0.2 pkgsrc-2016Q1-base:1.9 pkgsrc-2015Q4:1.7.0.12 pkgsrc-2015Q4-base:1.7 pkgsrc-2015Q3:1.7.0.10 pkgsrc-2015Q3-base:1.7 pkgsrc-2015Q2:1.7.0.8 pkgsrc-2015Q2-base:1.7 pkgsrc-2015Q1:1.7.0.6 pkgsrc-2015Q1-base:1.7 pkgsrc-2014Q4:1.7.0.4 pkgsrc-2014Q4-base:1.7 pkgsrc-2014Q3:1.7.0.2 pkgsrc-2014Q3-base:1.7 pkgsrc-2014Q2:1.6.0.32 pkgsrc-2014Q2-base:1.6 pkgsrc-2014Q1:1.6.0.30 pkgsrc-2014Q1-base:1.6 pkgsrc-2013Q4:1.6.0.28 pkgsrc-2013Q4-base:1.6 pkgsrc-2013Q3:1.6.0.26 pkgsrc-2013Q3-base:1.6 pkgsrc-2013Q2:1.6.0.24 pkgsrc-2013Q2-base:1.6 pkgsrc-2013Q1:1.6.0.22 pkgsrc-2013Q1-base:1.6 pkgsrc-2012Q4:1.6.0.20 pkgsrc-2012Q4-base:1.6 pkgsrc-2012Q3:1.6.0.18 pkgsrc-2012Q3-base:1.6 pkgsrc-2012Q2:1.6.0.16 pkgsrc-2012Q2-base:1.6 pkgsrc-2012Q1:1.6.0.14 pkgsrc-2012Q1-base:1.6 pkgsrc-2011Q4:1.6.0.12 pkgsrc-2011Q4-base:1.6 pkgsrc-2011Q3:1.6.0.10 pkgsrc-2011Q3-base:1.6 pkgsrc-2011Q2:1.6.0.8 pkgsrc-2011Q2-base:1.6 pkgsrc-2011Q1:1.6.0.6 pkgsrc-2011Q1-base:1.6 pkgsrc-2010Q4:1.6.0.4 pkgsrc-2010Q4-base:1.6 pkgsrc-2010Q3:1.6.0.2 pkgsrc-2010Q3-base:1.6 pkgsrc-2010Q2:1.4.0.10 pkgsrc-2010Q2-base:1.4 pkgsrc-2010Q1:1.4.0.8 pkgsrc-2010Q1-base:1.4 pkgsrc-2009Q4:1.4.0.6 pkgsrc-2009Q4-base:1.4 pkgsrc-2009Q3:1.4.0.4 pkgsrc-2009Q3-base:1.4 pkgsrc-2009Q2:1.4.0.2 pkgsrc-2009Q2-base:1.4 pkgsrc-2009Q1:1.3.0.2 pkgsrc-2009Q1-base:1.3 pkgsrc-2008Q4:1.2.0.12 pkgsrc-2008Q4-base:1.2 pkgsrc-2008Q3:1.2.0.10 pkgsrc-2008Q3-base:1.2 cube-native-xorg:1.2.0.8 cube-native-xorg-base:1.2 pkgsrc-2008Q2:1.2.0.6 pkgsrc-2008Q2-base:1.2 cwrapper:1.2.0.4 pkgsrc-2008Q1:1.2.0.2 pkgsrc-2008Q1-base:1.2 pkgsrc-2007Q4:1.1.0.4 pkgsrc-2007Q4-base:1.1 pkgsrc-2007Q3:1.1.0.2 pkgsrc-2007Q3-base:1.1; locks; strict; comment @# @; 1.27 date 2025.07.30.06.29.47; author triaxx; state Exp; branches; next 1.26; commitid 8ojeDgraR5wHFJ4G; 1.26 date 2024.09.15.15.22.56; author adam; state Exp; branches 1.26.8.1; next 1.25; commitid wvQcnYX3LKOiQUpF; 1.25 date 2023.11.09.12.17.07; author adam; state Exp; branches; next 1.24; commitid NYLuwn2fyn1iOVLE; 1.24 date 2023.02.20.13.36.42; author taca; state Exp; branches; next 1.23; commitid Jjlfjod4UQSNFgeE; 1.23 date 2022.10.24.10.29.19; author adam; state Exp; branches; next 1.22; commitid lbhZd9C0rv4DsXYD; 1.22 date 2022.07.05.11.01.38; author adam; state Exp; branches 1.22.2.1; next 1.21; commitid GNx2CTve26XZcHKD; 1.21 date 2022.05.14.06.48.11; author adam; state Exp; branches; next 1.20; commitid SGdf3za9XLePtZDD; 1.20 date 2022.05.14.05.41.00; author adam; state Exp; branches; next 1.19; commitid 5KOI9I8ncroj6ZDD; 1.19 date 2021.01.18.14.32.23; author taca; state Exp; branches; next 1.18; commitid MzSY3yDZ1mfDvdEC; 1.18 date 2019.10.31.14.43.13; author triaxx; state Exp; branches 1.18.10.1; next 1.17; commitid QiTxwooQ7fQRR1JB; 1.17 date 2018.11.30.18.08.05; author triaxx; state Exp; branches; next 1.16; commitid DxOptKR6kyb0MZ1B; 1.16 date 2018.11.14.15.30.42; author leot; state Exp; branches; next 1.15; commitid kYM1kvlzYY5FpVZA; 1.15 date 2018.11.14.12.59.41; author adam; state Exp; branches; next 1.14; commitid 2wjssvA6RSTVzUZA; 1.14 date 2018.10.03.03.53.31; author triaxx; state Exp; branches; next 1.13; commitid cZoFVfILe0HxUsUA; 1.13 date 2018.08.14.13.18.37; author adam; state Exp; branches; next 1.12; commitid QfXOoS0gE3fUD5OA; 1.12 date 2018.05.02.07.33.13; author triaxx; state Exp; branches; next 1.11; commitid 73zck065wqZ64HAA; 1.11 date 2018.03.07.09.17.06; author adam; state Exp; branches; next 1.10; commitid nzVxLYZFvXWOrvtA; 1.10 date 2017.11.30.07.39.33; author triaxx; state Exp; branches; next 1.9; commitid DK3PXMbygQWT12hA; 1.9 date 2016.01.09.11.22.12; author adam; state Exp; branches 1.9.16.1; next 1.8; commitid BJlnSDfFd8wntfQy; 1.8 date 2016.01.01.17.00.49; author spz; state Exp; branches; next 1.7; commitid GNUG4kFUncQWyfPy; 1.7 date 2014.07.28.20.07.42; author jperkin; state Exp; branches 1.7.12.1; next 1.6; commitid sf0gvN9UGRqxpbKx; 1.6 date 2010.09.21.03.05.27; author taca; state Exp; branches; next 1.5; 1.5 date 2010.09.10.17.11.27; author spz; state Exp; branches; next 1.4; 1.4 date 2009.06.14.18.13.40; author joerg; state Exp; branches 1.4.10.1; next 1.3; 1.3 date 2009.02.05.13.48.12; author taca; state Exp; branches; next 1.2; 1.2 date 2008.03.29.14.16.58; author taca; state Exp; branches 1.2.12.1; next 1.1; 1.1 date 2007.07.04.20.37.50; author jlam; state Exp; branches; next ; 1.26.8.1 date 2025.07.30.06.18.06; author triaxx; state Exp; branches; next 1.26.8.2; commitid n5xR0oTXvg9xBJ4G; 1.26.8.2 date 2025.07.30.06.22.01; author triaxx; state Exp; branches; next ; commitid Va4lipx8nHvLCJ4G; 1.22.2.1 date 2022.11.11.19.59.11; author bsiegert; state Exp; branches; next ; commitid 3z9VzCTudbFt2k1E; 1.18.10.1 date 2021.01.28.08.09.40; author bsiegert; state Exp; branches; next ; commitid LWkq0Z0QjPhr4tFC; 1.9.16.1 date 2017.11.30.07.37.59; author triaxx; state Exp; branches; next ; commitid 5SbF2kavpdOm12hA; 1.7.12.1 date 2016.01.26.19.52.04; author bsiegert; state Exp; branches; next 1.7.12.2; commitid 5xabgCjwAjCpKtSy; 1.7.12.2 date 2016.01.26.20.45.45; author bsiegert; state Exp; branches; next ; commitid 9DQEWu94QpBP2uSy; 1.4.10.1 date 2010.09.11.17.24.16; author tron; state Exp; branches; next ; 1.2.12.1 date 2009.02.05.17.00.25; author tron; state Exp; branches; next ; desc @@ 1.27 log @sudo: Fix installation with nls option enabled Add cantonese locale. @ text @@@comment $NetBSD: PLIST,v 1.26 2024/09/15 15:22:56 adam Exp $ bin/cvtsudoers bin/sudo bin/sudoedit bin/sudoreplay include/sudo_plugin.h lib/sudo/audit_json.la lib/sudo/group_file.la lib/sudo/libsudo_util.la ${PLIST.noexec}lib/sudo/sudo_noexec.la lib/sudo/sudoers.la lib/sudo/system_group.la man/man1/cvtsudoers.1 man/man5/sudo.conf.5 man/man5/sudo_logsrv.proto.5 man/man5/sudo_logsrvd.conf.5 man/man5/sudo_plugin.5 man/man5/sudoers.5 ${PLIST.ldap}man/man5/sudoers.ldap.5 man/man5/sudoers_timestamp.5 man/man8/sudo.8 man/man8/sudo_logsrvd.8 man/man8/sudo_sendlog.8 man/man8/sudoedit.8 man/man8/sudoreplay.8 man/man8/visudo.8 sbin/sudo_logsrvd sbin/sudo_sendlog sbin/visudo share/doc/sudo/CONTRIBUTING.md share/doc/sudo/CONTRIBUTORS.md share/doc/sudo/ChangeLog share/doc/sudo/HISTORY.md share/doc/sudo/LICENSE.md share/doc/sudo/NEWS ${PLIST.ldap}share/doc/sudo/README.LDAP.md share/doc/sudo/README.md share/doc/sudo/SECURITY.md share/doc/sudo/TROUBLESHOOTING.md share/doc/sudo/UPGRADE.md ${PLIST.ldap}share/doc/sudo/schema.ActiveDirectory ${PLIST.ldap}share/doc/sudo/schema.IBM_LDAP ${PLIST.ldap}share/doc/sudo/schema.OpenLDAP ${PLIST.ldap}share/doc/sudo/schema.iPlanet ${PLIST.ldap}share/doc/sudo/schema.olcSudo share/examples/sudo/cvtsudoers.conf share/examples/sudo/pam.conf share/examples/sudo/sudo.conf share/examples/sudo/sudo_logsrvd.conf share/examples/sudo/sudoers share/examples/sudo/syslog.conf ${PLIST.nls}share/locale/ast/LC_MESSAGES/sudo.mo ${PLIST.nls}share/locale/ast/LC_MESSAGES/sudoers.mo ${PLIST.nls}share/locale/ca/LC_MESSAGES/sudo.mo ${PLIST.nls}share/locale/ca/LC_MESSAGES/sudoers.mo ${PLIST.nls}share/locale/cs/LC_MESSAGES/sudo.mo ${PLIST.nls}share/locale/cs/LC_MESSAGES/sudoers.mo ${PLIST.nls}share/locale/da/LC_MESSAGES/sudo.mo ${PLIST.nls}share/locale/da/LC_MESSAGES/sudoers.mo ${PLIST.nls}share/locale/de/LC_MESSAGES/sudo.mo ${PLIST.nls}share/locale/de/LC_MESSAGES/sudoers.mo ${PLIST.nls}share/locale/el/LC_MESSAGES/sudoers.mo ${PLIST.nls}share/locale/eo/LC_MESSAGES/sudo.mo ${PLIST.nls}share/locale/eo/LC_MESSAGES/sudoers.mo ${PLIST.nls}share/locale/es/LC_MESSAGES/sudo.mo ${PLIST.nls}share/locale/es/LC_MESSAGES/sudoers.mo ${PLIST.nls}share/locale/eu/LC_MESSAGES/sudo.mo ${PLIST.nls}share/locale/eu/LC_MESSAGES/sudoers.mo ${PLIST.nls}share/locale/fa/LC_MESSAGES/sudo.mo ${PLIST.nls}share/locale/fi/LC_MESSAGES/sudo.mo ${PLIST.nls}share/locale/fi/LC_MESSAGES/sudoers.mo ${PLIST.nls}share/locale/fr/LC_MESSAGES/sudo.mo ${PLIST.nls}share/locale/fr/LC_MESSAGES/sudoers.mo ${PLIST.nls}share/locale/fur/LC_MESSAGES/sudo.mo ${PLIST.nls}share/locale/fur/LC_MESSAGES/sudoers.mo ${PLIST.nls}share/locale/gl/LC_MESSAGES/sudo.mo ${PLIST.nls}share/locale/hr/LC_MESSAGES/sudo.mo ${PLIST.nls}share/locale/hr/LC_MESSAGES/sudoers.mo ${PLIST.nls}share/locale/hu/LC_MESSAGES/sudo.mo ${PLIST.nls}share/locale/hu/LC_MESSAGES/sudoers.mo ${PLIST.nls}share/locale/id/LC_MESSAGES/sudo.mo ${PLIST.nls}share/locale/id/LC_MESSAGES/sudoers.mo ${PLIST.nls}share/locale/it/LC_MESSAGES/sudo.mo ${PLIST.nls}share/locale/it/LC_MESSAGES/sudoers.mo ${PLIST.nls}share/locale/ja/LC_MESSAGES/sudo.mo ${PLIST.nls}share/locale/ja/LC_MESSAGES/sudoers.mo ${PLIST.nls}share/locale/ka/LC_MESSAGES/sudo.mo ${PLIST.nls}share/locale/ka/LC_MESSAGES/sudoers.mo ${PLIST.nls}share/locale/ko/LC_MESSAGES/sudo.mo ${PLIST.nls}share/locale/ko/LC_MESSAGES/sudoers.mo ${PLIST.nls}share/locale/lt/LC_MESSAGES/sudoers.mo ${PLIST.nls}share/locale/nb/LC_MESSAGES/sudo.mo ${PLIST.nls}share/locale/nb/LC_MESSAGES/sudoers.mo ${PLIST.nls}share/locale/nl/LC_MESSAGES/sudo.mo ${PLIST.nls}share/locale/nl/LC_MESSAGES/sudoers.mo ${PLIST.nls}share/locale/nn/LC_MESSAGES/sudo.mo ${PLIST.nls}share/locale/pl/LC_MESSAGES/sudo.mo ${PLIST.nls}share/locale/pl/LC_MESSAGES/sudoers.mo ${PLIST.nls}share/locale/pt/LC_MESSAGES/sudo.mo ${PLIST.nls}share/locale/pt/LC_MESSAGES/sudoers.mo ${PLIST.nls}share/locale/pt_BR/LC_MESSAGES/sudo.mo ${PLIST.nls}share/locale/pt_BR/LC_MESSAGES/sudoers.mo ${PLIST.nls}share/locale/ro/LC_MESSAGES/sudo.mo ${PLIST.nls}share/locale/ro/LC_MESSAGES/sudoers.mo ${PLIST.nls}share/locale/ru/LC_MESSAGES/sudo.mo ${PLIST.nls}share/locale/ru/LC_MESSAGES/sudoers.mo ${PLIST.nls}share/locale/sk/LC_MESSAGES/sudo.mo ${PLIST.nls}share/locale/sk/LC_MESSAGES/sudoers.mo ${PLIST.nls}share/locale/sl/LC_MESSAGES/sudo.mo ${PLIST.nls}share/locale/sl/LC_MESSAGES/sudoers.mo ${PLIST.nls}share/locale/sq/LC_MESSAGES/sudo.mo ${PLIST.nls}share/locale/sr/LC_MESSAGES/sudo.mo ${PLIST.nls}share/locale/sr/LC_MESSAGES/sudoers.mo ${PLIST.nls}share/locale/sv/LC_MESSAGES/sudo.mo ${PLIST.nls}share/locale/sv/LC_MESSAGES/sudoers.mo ${PLIST.nls}share/locale/tr/LC_MESSAGES/sudo.mo ${PLIST.nls}share/locale/tr/LC_MESSAGES/sudoers.mo ${PLIST.nls}share/locale/uk/LC_MESSAGES/sudo.mo ${PLIST.nls}share/locale/uk/LC_MESSAGES/sudoers.mo ${PLIST.nls}share/locale/vi/LC_MESSAGES/sudo.mo ${PLIST.nls}share/locale/vi/LC_MESSAGES/sudoers.mo ${PLIST.nls}share/locale/yue/LC_MESSAGES/sudo.mo ${PLIST.nls}share/locale/zh_CN/LC_MESSAGES/sudo.mo ${PLIST.nls}share/locale/zh_CN/LC_MESSAGES/sudoers.mo ${PLIST.nls}share/locale/zh_TW/LC_MESSAGES/sudo.mo ${PLIST.nls}share/locale/zh_TW/LC_MESSAGES/sudoers.mo @ 1.26 log @sudo: updated to 1.9.16 What's new in Sudo 1.9.16 * Added the "cmddenial_message" sudoers option to provide additional information to the user when a command is denied by the sudoers policy. The default message is still displayed. * The time stamp used for file-based logs is now more consistent with the time stamp produced by syslog. * Sudo will now warn the user if it can detect the user's terminal but cannot determine the path to the terminal device. The sudoers time stamp file will now use the terminal device number directly. * The embedded copy of zlib has been updated to version 1.3.1. * Improved error handling if generating the list of signals and signal names fails at build time. * Fixed a compilation issue on Linux systems without process_vm_readv(). * Fixed cross-compilation with WolfSSL. * Added a "json_compact" value for the sudoers "log_format" option which can be used when logging to a file. The existing "json" value has been aliased to "json_pretty". In a future release, "json" will be an alias for "json_compact". * A new "pam_silent" sudoers option has been added which may be negated to avoid suppressing output from PAM authentication modules. * Fixed several cvtsudoers JSON output problems. * When sudo runs a command in a pseudo-terminal and the user's terminal is revoked, the pseudo-terminal's foreground process group will now receive SIGHUP before the terminal is revoked. This emulates the behavior of the session leader exiting and is consistent with what happens when, for example, an ssh session is closed. * Fixed "make test" with Python 3.12. * In schema.ActiveDirectory, fixed the quoting in the example command. * Paths specified via a Chdir_Spec or Chroot_Spec in sudoers may now be double-quoted. * Sudo insults are now included by default, but disabled unless the --with-insults configure option is specified or the "insults" sudoers option is enabled. * The default sudoers file now enables the "secure_path" option by default and preserves the EDITOR, VISUAL, and SUDO_EDITOR environment variables when running visudo. The new --with-secure-path-value configure option can be used to set the value of "secure_path" in the default sudoers file. * A sudoers schema for IBM Directory Server (aka IBM Tivoli Directory Server, IBM Security Directory Server, and IBM Security Verify Directory) is now included. * When cross-compiling sudo, the configure script now assumes that the snprintf() function is C99-compliant if the C compiler supports the C99 standard. Previously, configure would use sudo's own snprintf() when cross-compiling. @ text @d1 1 a1 1 @@comment $NetBSD: PLIST,v 1.25 2023/11/09 12:17:07 adam Exp $ d122 1 @ 1.26.8.1 log @sudo: Fix installation with nls option enabled Add cantonese locale. @ text @d1 1 a1 1 @@comment $NetBSD: PLIST,v 1.26 2024/09/15 15:22:56 adam Exp $ a121 1 ${PLIST.nls}share/locale/yue/LC_MESSAGES/sudoers.mo @ 1.26.8.2 log @sudo: Revert change on frozen branch @ text @d1 1 a1 1 @@comment $NetBSD: PLIST,v 1.26.8.1 2025/07/30 06:18:06 triaxx Exp $ d122 1 @ 1.25 log @sudo: updated to 1.9.15p1 What's new in Sudo 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. What's new in Sudo 1.9.15 * Fixed an undefined symbol problem on older versions of macOS when "intercept" or "log_subcmds" are enabled in sudoers. * 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. * 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. * 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. * 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 @@include and @@includedir 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. * 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. * 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. * 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. @ text @d1 1 a1 1 @@comment $NetBSD: PLIST,v 1.24 2023/02/20 13:36:42 taca Exp $ d42 1 d82 1 @ 1.24 log @security/sudo: update to 1.9.13p1 pkgsrc change: avoid use empty in options.mk. What's new in Sudo 1.9.13 (2023-02-14) * 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 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 issues #199, #202. * Fixed potential NULL dereferences on memory allocation failure. GitHub issues #204, #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. What's new in Sudo 1.9.13p1 (2023-02-17) * 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. * Relaxed the autoconf version requirement to version 2.69. @ text @d1 1 a1 1 @@comment $NetBSD: PLIST,v 1.23 2022/10/24 10:29:19 adam Exp $ d80 1 @ 1.23 log @sudo: updated to 1.9.12 What's new in Sudo 1.9.12 * Fixed a bug in the ptrace-based intercept mode where the current working directory could include garbage at the end. * Fixed a compilation error on systems that lack the stdint.h header. * 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. * 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. * Fixed a bug where sub-commands were not being logged to a remote log server when log_subcmds was enabled. * 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. * Fixed a bug in visudo that caused literal backslashes to be removed from the EDITOR environment variable. * 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. * 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. * 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. * 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. @ text @d1 1 a1 1 @@comment $NetBSD: PLIST,v 1.22 2022/07/05 11:01:38 adam Exp $ d85 1 d108 1 @ 1.22 log @sudo: updated to 1.9.11p3 What's new in Sudo 1.9.11p3 * Fixed "connection reset" errors on AIX when running shell scripts with the "intercept" or "log_subcmds" sudoers options enabled. * 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. What's new 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. What's new 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. * 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. What's new 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. * The "starttime" test now passed when run under Debian faketime. * 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. * 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. @ text @d1 1 a1 1 @@comment $NetBSD: PLIST,v 1.21 2022/05/14 06:48:11 adam Exp $ a9 1 lib/sudo/sample_approval.la @ 1.22.2.1 log @Pullup ticket #6702 - requested by taca security/sudo: security fix Revisions pulled up: - security/sudo/Makefile 1.191-1.192 - security/sudo/PLIST 1.23 - security/sudo/distinfo 1.123-1.124 - security/sudo/patches/patch-plugins_sudoers_auth_passwd.c 1.1 --- Module Name: pkgsrc Committed By: adam Date: Mon Oct 24 10:29:20 UTC 2022 Modified Files: pkgsrc/security/sudo: Makefile PLIST distinfo Log Message: sudo: updated to 1.9.12 What's new in Sudo 1.9.12 * Fixed a bug in the ptrace-based intercept mode where the current working directory could include garbage at the end. * Fixed a compilation error on systems that lack the stdint.h header. * 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. * 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. * Fixed a bug where sub-commands were not being logged to a remote log server when log_subcmds was enabled. * 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. * Fixed a bug in visudo that caused literal backslashes to be removed from the EDITOR environment variable. * 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. * 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. * 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. * 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. --- Module Name: pkgsrc Committed By: taca Date: Fri Nov 4 00:58:00 UTC 2022 Modified Files: pkgsrc/security/sudo: Makefile distinfo Added Files: pkgsrc/security/sudo/patches: patch-plugins_sudoers_auth_passwd.c Log Message: security/sudo: add fix for CVE-2022-43995 Add patch from upstream to fix CVE-2022-43995. Bump PKGREVISION. @ text @d1 1 a1 1 @@comment $NetBSD$ d10 1 @ 1.21 log @sudo: fix PLIST for LDAP @ text @d1 1 a1 1 @@comment $NetBSD: PLIST,v 1.20 2022/05/14 05:41:00 adam Exp $ d18 1 a23 1 man/man8/sudo_plugin.8 d85 1 @ 1.20 log @sudo: updated to 1.9.10 What's new in Sudo 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 when 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. * 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. * Fixed a compilation problem on Debian kFreeBSD. * 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. * 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. What's new in Sudo 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. * 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. * 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(). * 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. * 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. * 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. * Clarified in the sudo man page that the security policy may override the user's PATH environment variable. * 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. * 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. * 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. What's new in Sudo 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. * 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. * Fixed a bug where sudoedit would fail if one of the directories in the path to be edited had the immutable flag set (BSD, Linux or macOS). What's new in Sudo 1.9.8p1 * 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. * Fixed a crash with "sudo ALL" rules in the LDAP and SSSD back-ends. This is a regression introduced in sudo 1.9.8. * 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. What's new in Sudo 1.9.8 * 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. * Fixed compilation error when the --enable-static-sudoers configure option was specified. This was due to a typo introduced in sudo 1.9.7. @ text @d1 1 a1 1 @@comment $NetBSD: PLIST,v 1.19 2021/01/18 14:32:23 taca Exp $ d37 1 a37 1 share/doc/sudo/README.LDAP.md @ 1.19 log @security/sudo: update to 1.9.5p1 Update sudo package to 1.9.5p1. CHanges from 1.8.31p2 are too many to write here. Please refer . 1.9.5 fixes these security problems: * 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_symlinks to 1 will prevent the bug from being exploited. For more information, see Symbolic link attack in SELinux-enabled sudoedit. Quote from 1.9.0 features: * 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-openssl option. 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-server and --disable-log-client configure 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_sendlog utility can be used to test sudo_logsrvd or 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-python option. See the sudo_plugin_python manual for details. Sudo 1.9.0 comes with several Python example plugins that get installed sudo's examples directory. 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. @ text @d1 1 a1 1 @@comment $NetBSD: PLIST,v 1.18 2019/10/31 14:43:13 triaxx Exp $ d31 2 a32 1 share/doc/sudo/CONTRIBUTORS d34 2 a35 2 share/doc/sudo/HISTORY share/doc/sudo/LICENSE d37 5 a41 4 share/doc/sudo/README ${PLIST.ldap}share/doc/sudo/README.LDAP share/doc/sudo/TROUBLESHOOTING share/doc/sudo/UPGRADE d46 1 d66 1 d69 1 @ 1.18 log @sudo: add missing files in PLIST pkgsrc changes: --------------- * Add missing locale files in PLIST. * Bump revision. @ text @d1 1 a1 1 @@comment $NetBSD: PLIST,v 1.17 2018/11/30 18:08:05 triaxx Exp $ d7 1 d10 1 d16 2 d22 1 d24 1 d28 2 d46 1 d94 2 @ 1.18.10.1 log @Pullup ticket #6415 - requested by spz security/sudo: security fix Revisions pulled up: - security/sudo/Makefile 1.181-1.182 - security/sudo/PLIST 1.19 - security/sudo/distinfo 1.112-1.113 - security/sudo/patches/patch-configure 1.4 - security/sudo/patches/patch-examples_Makefile.in 1.1 - security/sudo/patches/patch-logsrvd_Makefile.in 1.1 - security/sudo/patches/patch-plugins_sudoers_Makefile.in 1.4 --- Module Name: pkgsrc Committed By: taca Date: Mon Jan 18 14:32:24 UTC 2021 Modified Files: pkgsrc/security/sudo: Makefile PLIST distinfo pkgsrc/security/sudo/patches: patch-configure patch-plugins_sudoers_Makefile.in Added Files: pkgsrc/security/sudo/patches: patch-examples_Makefile.in patch-logsrvd_Makefile.in Log Message: security/sudo: update to 1.9.5p1 Update sudo package to 1.9.5p1. CHanges from 1.8.31p2 are too many to write here. Please refer . 1.9.5 fixes these security problems: * 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_symlinks to 1 will prevent the bug from being exploited. For more information, see Symbolic link attack in SELinux-enabled sudoedit. Quote from 1.9.0 features: * 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-openssl option. 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-server and --disable-log-client configure 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_sendlog utility can be used to test sudo_logsrvd or 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-python option. See the sudo_plugin_python manual for details. Sudo 1.9.0 comes with several Python example plugins that get installed sudo's examples directory. 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. --- Module Name: pkgsrc Committed By: jperkin Date: Tue Jan 26 20:18:43 UTC 2021 Modified Files: pkgsrc/security/sudo: Makefile distinfo Log Message: sudo: Update to 1.9.5p2 for CVE-2021-3156. What's new in Sudo 1.9.5p2 * 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. * 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. @ text @d1 1 a1 1 @@comment $NetBSD$ a6 1 lib/sudo/audit_json.la a8 1 lib/sudo/sample_approval.la a13 2 man/man5/sudo_logsrv.proto.5 man/man5/sudo_logsrvd.conf.5 a17 1 man/man8/sudo_logsrvd.8 a18 1 man/man8/sudo_sendlog.8 a21 2 sbin/sudo_logsrvd sbin/sudo_sendlog a37 1 share/examples/sudo/sudo_logsrvd.conf a84 2 ${PLIST.nls}share/locale/ro/LC_MESSAGES/sudo.mo ${PLIST.nls}share/locale/ro/LC_MESSAGES/sudoers.mo @ 1.17 log @sudo: fix PLIST (new locales) @ text @d1 1 a1 1 @@comment $NetBSD: PLIST,v 1.16 2018/11/14 15:30:42 leot Exp $ d41 1 d104 1 @ 1.16 log @sudo: Fix PLIST share/doc/sudo/schema.olcSudo is installed only when ldap support is enabled. @ text @d1 1 a1 1 @@comment $NetBSD: PLIST,v 1.15 2018/11/14 12:59:41 adam Exp $ d40 1 d80 2 @ 1.15 log @sudo: updated to 1.8.26 What's new in Sudo 1.8.26 * Fixed a bug in cvtsudoers when converting to JSON format when alias expansion is enabled. * Sudo no long sets the USERNAME environment variable when running commands. This is a non-standard environment variable that was set on some older Linux systems. * Sudo now treats the LOGNAME and USER environment variables (as well as the LOGIN variable on AIX) as a single unit. If one is preserved or removed from the environment using env_keep, env_check or env_delete, so is the other. * Added support for OpenLDAP's TLS_REQCERT setting in ldap.conf. * Sudo now logs when the command was suspended and resumed in the I/O logs. This information is used by sudoreplay to skip the time suspended when replaying the session unless the new -S flag is used. * Fixed documentation problems found by the igor utility. * Sudo now prints a warning message when there is an error or end of file while reading the password instead of exiting silently. * Fixed a bug in the sudoers LDAP back-end parsing the command_timeout, role, type, privs and limitprivs sudoOptions. This also affected cvtsudoers conversion from LDIF to sudoers or JSON. * Fixed a bug that prevented timeout settings in sudoers from functioning unless a timeout was also specified on the command line. * Asturian translation for sudo from translationproject.org. * When generating LDIF output, cvtsudoers can now be configured to pad the sudoOrder increment such that the start order is used as a prefix. * Fixed a bug introduced in sudo 1.8.25 that prevented sudo from properly setting the user's groups on AIX. * If the user specifies a group via sudo's -g option that matches any of the target user's groups, it is now allowed even if no groups are present in the Runas_Spec. Previously, it was only allowed if it matched the target user's primary group. * The sudoers LDAP back-end now supports negated sudoRunAsUser and sudoRunAsGroup entries. * Sudo now provides a proper error message when the "fqdn" sudoers option is set and it is unable to resolve the local host name. * Portuguese translation for sudo and sudoers from translationproject.org. * Sudo now includes sudoers LDAP schema for the on-line configuration supported by OpenLDAP. @ text @d1 1 a1 1 @@comment $NetBSD: PLIST,v 1.14 2018/10/03 03:53:31 triaxx Exp $ d35 1 a35 1 share/doc/sudo/schema.olcSudo @ 1.14 log @sudo: update PLIST for zh_TW locale @ text @d1 1 a1 1 @@comment $NetBSD: PLIST,v 1.13 2018/08/14 13:18:37 adam Exp $ d35 1 @ 1.13 log @sudo: updated to 1.8.23 Sudo 1.8.23 * PAM account management modules and BSD auto approval modules are now run even when no password is required. * For kernel-based time stamps, if no terminal is present, fall back to parent-pid style time stamps. * The new cvtsudoers utility replaces both the "sudoers2ldif" script and the "visudo -x" functionality. It can read a file in either sudoers or LDIF format and produce JSON, LDIF or sudoers output. It is also possible to filter the generated output file by user, group or host name. * The file, ldap and sss sudoers backends now share a common set of formatting functions for "sudo -l" output, which is also used by the cvtsudoers utility. * The /run directory is now used in preference to /var/run if it exists. * More accurate descriptions of the --with-rundir and --with-vardir configure options. * The setpassent() and setgroupent() functions are now used on systems that support them to keep the passwd and group database open. Sudo performs a lot of passwd and group lookups so it can be beneficial to avoid opening and closing the files each time. * The new case_insensitive_user and case_insensitive_group sudoers options can be used to control whether sudo does case-sensitive matching of users and groups in sudoers. Case insensitive matching is now the default. * Fixed a bug on some systems where sudo could hang on command exit when I/O logging was enabled. * Fixed the build-time process start time test on Linux when the test is run from within a container. * When determining which temporary directory to use, sudoedit now checks the directory for writability before using it. Previously, sudoedit only performed an existence check. * Sudo now includes an optional set of Monty Python-inspired insults. * Fixed the execution of scripts with an associated digest (checksum) in sudoers on FreeBSD systems. FreeBSD does not have a proper /dev/fd directory mounted by default and its fexecve(2) is not fully POSIX compliant when executing scripts. * Chinese (Taiwan) translation for sudo from translationproject.org. @ text @d1 1 a1 1 @@comment $NetBSD: PLIST,v 1.12 2018/05/02 07:33:13 triaxx Exp $ d98 1 @ 1.12 log @sudo: fix PR 53248 @ text @d1 2 a2 1 @@comment $NetBSD: PLIST,v 1.11 2018/03/07 09:17:06 adam Exp $ d12 1 a34 1 ${PLIST.ldap}share/doc/sudo/sudoers2ldif @ 1.11 log @sudo: updated to 1.8.22 What's new in Sudo 1.8.22 * Commands run in the background from a script run via sudo will no longer receive SIGHUP when the parent exits and I/O logging is enabled. * A particularly offensive insult is now disabled by default. * The description of "sudo -i" now correctly documents that the "env_keep" and "env_check" sudoers options are applied to the environment. * Fixed a crash when the system's host name is not set. * The sudoers2ldif script now handles #include and #includedir directives. * Fixed a bug where sudo would silently exit when the command was not allowed by sudoers and the "passwd_tries" sudoers option was set to a value less than one. * Fixed a bug with the "listpw" and "verifypw" sudoers options and multiple sudoers sources. If the option is set to "all", a password should be required unless none of a user's sudoers entries from any source require authentication. * Fixed a bug with the "listpw" and "verifypw" sudoers options in the LDAP and SSSD back-ends. If the option is set to "any", and the entry contained multiple rules, only the first matching rule was checked. If an entry contained more than one matching rule and the first rule required authentication but a subsequent rule did not, sudo would prompt for a password when it should not have. * When running a command as the invoking user (not root), sudo would execute the command with the same group vector it was started with. Sudo now executes the command with a new group vector based on the group database which is consistent with how su(1) operates. * Fixed a double free in the SSSD back-end that could occur when ipa_hostname is present in sssd.conf and is set to an unqualified host name. * When I/O logging is enabled, sudo will now write to the terminal even when it is a background process. Previously, sudo would only write to the tty when it was the foreground process when I/O logging was enabled. If the TOSTOP terminal flag is set, sudo will suspend the command (and then itself) with the SIGTTOU signal. * A new "authfail_message" sudoers option that overrides the default "N incorrect password attempt(s)". * An empty sudoRunAsUser attribute in the LDAP and SSSD backends will now match the invoking user. This is more consistent with how an empty runas user in the sudoers file is treated. * Documented that in check mode, visudo does not check the owner/mode on files specified with the -f flag. * It is now an error to specify the runas user as an empty string on the command line. Previously, an empty runas user was treated the same as an unspecified runas user. * When "timestamp_type" option is set to "tty" and a terminal is present, the time stamp record will now include the start time of the session leader. When the "timestamp_type" option is set to "ppid" or when no terminal is available, the start time of the parent process is used instead. This significantly reduces the likelihood of a time stamp record being re-used when a user logs out and back in again. * The sudoers time stamp file format is now documented in the new sudoers_timestamp manual. * The "timestamp_type" option now takes a "kernel" value on OpenBSD systems. This causes the tty-based time stamp to be stored in the kernel instead of on the file system. If no tty is present, the time stamp is considered to be invalid. * Visudo will now use the SUDO_EDITOR environment variable (if present) in addition to VISUAL and EDITOR. @ text @d1 1 a1 1 @@comment $NetBSD: PLIST,v 1.10 2017/11/30 07:39:33 triaxx Exp $ d57 1 @ 1.10 log @Add missing .mo files to PLIST Since the last update, translations have been added but the additional files have not been included into PLIST. The build failed in such a case: PKG_OPTIONS.sudo= +nls PKG_DEVELOPER= yes @ text @d1 1 a1 1 @@comment $NetBSD: PLIST,v 1.9 2016/01/09 11:22:12 adam Exp $ d14 1 @ 1.9 log @Add nls as an option, but also fix builds where system gettext gets detected and used. @ text @d1 1 a1 1 @@comment $NetBSD: PLIST,v 1.8 2016/01/01 17:00:49 spz Exp $ d55 1 d59 1 d65 2 d72 1 @ 1.9.16.1 log @Add missing .mo files to PLIST Since the last update, translations have been added but the additional files have not been included into PLIST. The build failed in such a case: PKG_OPTIONS.sudo= +nls PKG_DEVELOPER= yes @ text @d1 1 a1 1 @@comment $NetBSD: PLIST,v 1.9 2016/01/09 11:22:12 adam Exp $ a54 1 ${PLIST.nls}share/locale/fur/LC_MESSAGES/sudo.mo a57 1 ${PLIST.nls}share/locale/hu/LC_MESSAGES/sudo.mo a62 2 ${PLIST.nls}share/locale/ko/LC_MESSAGES/sudo.mo ${PLIST.nls}share/locale/ko/LC_MESSAGES/sudoers.mo a67 1 ${PLIST.nls}share/locale/nn/LC_MESSAGES/sudo.mo @ 1.8 log @Update to 1.8.15, which fixes CVE-2015-5602, a symlink vulnerability in sudoedit. Note that it's a fairly large step and the package has only been tested on NetBSD and there may be further breakage. Testing on non-NetBSD would be appreciated. Upstream changelog: Major changes between version 1.8.15 and 1.8.14p3: Fixed a bug that prevented sudo from building outside the source tree on some platforms. Bug #708. Fixed the location of the sssd library in the RHEL/Centos packages. Bug #710. Fixed a build problem on systems that don't implicitly include sys/types.h from other header files. Bug #711. Fixed a problem on Linux using containers where sudo would ignore signals sent by a process in a different container. Sudo now refuses to run a command if the PAM session module returns an error. When editing files with sudoedit, symbolic links will no longer be followed by default. The old behavior can be restored by enabling the sudoedit_follow option in sudoers or on a per-command basis with the FOLLOW and NOFOLLOW tags. Bug #707. Fixed a bug introduced in version 1.8.14 that caused the last valid editor in the sudoers "editor" list to be used by visudo and sudoedit instead of the first. Bug #714. Fixed a bug in visudo that prevented the addition of a final newline to edited files without one. Fixed a bug decoding certain base64 digests in sudoers when the intermediate format included a '=' character. Individual records are now locked in the time stamp file instead of the entire file. This allows sudo to avoid prompting for a password multiple times on the same terminal when used in a pipeline. In other words, sudo cat foo | sudo grep bar now only prompts for the password once. Previously, both sudo processes would prompt for a password, often making it impossible to enter. Bug #705. Fixed a bug where sudo would fail to run commands as a non-root user on systems that lack both setresuid() and setreuid(). Bug #713. Fixed a bug introduced in sudo 1.8.14 that prevented visudo from re-editing the correct file when a syntax error was detected. Fixed a bug where sudo would not relay a SIGHUP signal to the command when the terminal is closed and the command is not run in its own pseudo-tty. Bug #719. If some, but not all, of the LOGNAME, USER or USERNAME environment variables have been preserved from the invoking user's environment, sudo will now use the preserved value to set the remaining variables instead of using the runas user. This ensures that if, for example, only LOGNAME is present in the env_keep list, that sudo will not set USER and USERNAME to the runas user. When the command sudo is running dies due to a signal, sudo will now send itself that same signal with the default signal handler installed instead of exiting. The bash shell appears to ignore some signals, e.g. SIGINT, unless the command being run is killed by that signal. This makes the behavior of commands run under sudo the same as without sudo when bash is the shell. Bug #722. Slovak translation for sudo from translationproject.org. Hungarian and Slovak translations for sudoers from translationproject.org. Previously, when env_reset was enabled (the default) and the -s option was not used, the SHELL environment variable was set to the shell of the invoking user. Now, when env_reset is enabled and the -s option is not used, SHELL is set based on the target user. Fixed challenge/response style BSD authentication. Added the sudoedit_checkdir Defaults option to prevent sudoedit from editing files located in a directory that is writable by the invoking user. Added the always_query_group_plugin Defaults option to control whether groups not found in the system group database are passed to the group plugin. Previously, unknown system groups were always passed to the group plugin. When creating a new file, sudoedit will now check that the file's parent directory exists before running the editor. Fixed the compiler stack protector test in configure for compilers that support -fstack-protector but don't actually have the ssp library available. Major changes between version 1.8.14p3 and 1.8.14p2: Fixed a bug introduced in sudo 1.8.14p2 that prevented sudo from working when no tty was present. Bug #706. Fixed tty detection on newer AIX systems where dev_t is 64-bit. Major changes between version 1.8.14p2 and 1.8.14p1: Fixed a bug introduced in sudo 1.8.14 that prevented the lecture file from being created. Bug #704. Major changes between version 1.8.14p1 and 1.8.14: Fixed a bug introduced in sudo 1.8.14 that prevented the sssd backend from working. Bug #703. Major changes between version 1.8.14 and 1.8.13: Log messages on Mac OS X now respect sudoers_locale when sudo is build with NLS support. The sudo manual pages now pass mandoc -Tlint with no warnings. Fixed a compilation problem on systems with the sig2str() function that do not define SIG2STR_MAX in signal.h. Worked around a compiler bug that resulted in unexpected behavior when returning an int from a function declared to return bool without an explicit cast. Worked around a bug in Mac OS X 10.10 BSD auditing where the au_preselect() fails for AUE_sudo events but succeeds for AUE_DARWIN_sudo. Fixed a hang on Linux systems with glibc when sudo is linked with jemalloc. When the user runs a command as a user ID that is not present in the password database via the -u flag, the command is now run with the group ID of the invoking user instead of group ID 0. Fixed a compilation problem on systems that don't pull in definitions of uid_t and gid_t without sys/types.h or unistd.h. Fixed a compilation problem on newer AIX systems which use a struct st_timespec for time stamps in struct stat that differs from struct timespec. Bug #702. The example directory is now configurable via --with-exampledir and defaults to DATAROOTDIR/examples/sudo on BSD systems. The /usr/lib/tmpfiles.d/sudo.conf file is now installed as part of "make install" when systemd is in use. Fixed a linker problem on some systems with libintl. Bug #690. Fixed compilation with compilers that don't support __func__ or __FUNCTION__. Sudo no longer needs to uses weak symbols to support localization in the warning functions. A registration function is used instead. Fixed a setresuid() failure in sudoers on Linux kernels where uid changes take the nproc resource limit into account. Fixed LDAP netgroup queries on AIX. Sudo will now display the custom prompt on Linux systems with PAM even if the "Password: " prompt is not localized by the PAM module. Bug #701. Double-quoted values in an LDAP sudoOption are now supported for consistency with file-based sudoers. Fixed a bug that prevented the btime entry in /proc/stat from being parsed on Linux. Major changes between version 1.8.13 and 1.8.12: The examples directory is now a subdirectory of the doc dir to conform to Debian guidelines. Bug #682. Fixed a compilation error for siglist.c and signame.c on some systems. Bug #686. Weak symbols are now used for sudo_warn_gettext() and sudo_warn_strerror() in libsudo_util to avoid link errors when -Wl,--no-undefined is used in LDFLAGS. The --disable-weak-symbols configure option can be used to disable the user of weak symbols. Fixed a bug in sudo's mkstemps() replacement function that prevented the file extension from being preserved in sudoedit. A new mail_all_cmnds sudoers flag will send mail when a user runs a command (or tries to). The behavior of the mail_always flag has been restored to always send mail when sudo is run. New MAIL and NOMAIL command tags have been added to toggle mail sending behavior on a per-command (or Cmnd_Alias) basis. Fixed matching of empty passwords when sudo is configured to use passwd (or shadow) file authentication on systems where the crypt() function returns NULL for invalid salts. On AIX, sudo now uses the value of the auth_type setting in /etc/security/login.cfg to determine whether to use LAM or PAM for user authentication. The all setting for listpw and verifypw now works correctly with LDAP and sssd sudoers. The sudo timestamp directory is now created at boot time on platforms that use systemd. Sudo will now restore the value of the SIGPIPE handler before executing the command. Sudo now uses struct timespec instead of struct timeval for time keeping when possible. If supported, sudoedit and visudo now use nanosecond granularity time stamps. Fixed a symbol name collision with systems that have their own SHA2 implementation. This fixes a problem where PAM could use the wrong SHA2 implementation on Solaris 10 systems configured to use SHA512 for passwords. The editor invoked by sudoedit once again uses an unmodified copy of the user's environment as per the documentation. This was inadvertantly changed in sudo 1.8.0. Bug #688. Major changes between version 1.8.12 and 1.8.11p2: The embedded copy of zlib has been upgraded to version 1.2.8 and is now installed as a shared library where supported. Debug settings for the sudo front end and sudoers plugin are now configured separately. Multiple sudo.conf Debug entries may now be specified per program (or plugin). The plugin API has been extended such that the path to the plugin that was loaded is now included in the settings array. This path can be used to register with the debugging subsystem. The debug_flags setting is now prefixed with a file name and may be specified multiple times if there is more than one matching Debug setting in sudo.conf. The sudoers regression tests now run with the locale set to C since some of the tests compare output that includes locale-specific messages. Bug #672. Fixed a bug where sudo would not run commands on Linux when compiled with audit support if audit is disabled. Bug #671. Added __BASH_FUNC< to the environment blacklist to match Apple's syntax for newer-style bash functions. The default password prompt now includes a trailing space after "Password:" for consistency with su(1) on most systems. Bug #663. Fixed a problem on DragonFly BSD where SIGCHLD could be ignored, preventing sudo from exiting. Bug #676. Visudo will now use the optional sudoers_file, sudoers_mode, sudoers_uid and sudoers_gid arguments if specified on the sudoers.so Plugin line in the sudo.conf file. Fixed a problem introduced in sudo 1.8.8 that prevented the full host name from being used when the fqdn sudoers option is used. Bug #678. French and Russian translations for sudoers from translationproject.org. Sudo now installs a handler for SIGCHLD signal handler immediately before stating the process that will execute the command (or start the monitor). The handler used to be installed earlier but this causes problems with poorly behaved PAM modules that install their own SIGCHLD signal handler and neglect to restore sudo's original handler. Bug #657. Removed a limit on the length of command line arguments expanded by a wild card using sudo's version of the fnmatch() function. This limit was introduced when sudo's version of fnmatch() was replaced in sudo 1.8.4. LDAP-based sudoers can now query an LDAP server for a user's netgroups directly. This is often much faster than fetching every sudoRole object containing a sudoUser that begins with a `+' prefix and checking whether the user is a member of any of the returned netgroups. The mail_always sudoers option no longer sends mail for sudo -l or sudo -v unless the user is unable to authenticate themselves. Fixed a crash when sudo is run with an empty argument vector. Fixed two potential crashes when sudo is run with very low resource limits. The TZ environment variable is now checked for safety instead of simply being copied to the environment of the command. This fixes a potential security issue. Major changes between version 1.8.11p2 and 1.8.11p1: Fixed a bug where dynamic shared objects loaded from a plugin could use the hooked version of getenv() but not the hooked versions of putenv(), setenv() or unsetenv(). This can cause problems for PAM modules that use those functions. Major changes between version 1.8.11p1 and 1.8.11: Fixed a compilation problem on some systems when the --disable-shared-libutil configure option was specified. The user can no longer interrupt the sleep after an incorrect password on PAM systems using pam_unix. Bug #666. Fixed a compilation problem on Linux systems that do not use PAM. Bug #667. "make install" will now work with the stock GNU autotools install-sh script. Bug #669. Fixed a crash with "sudo -i" when the current working directory does not exist. Bug #670. Fixed a potential crash in the debug subsystem when logging a message larger that 1024 bytes. Fixed a "make check" failure for ttyname when stdin is closed and stdout and stderr are redirected to a different tty. Bug #643. Added BASH_FUNC_* to environment blacklist to match newer-style bash functions. Major changes between version 1.8.11 and 1.8.10p3: The sudoers plugin no longer uses setjmp/longjmp to recover from fatal errors. All errors are now propagated to the caller via return codes. When running a command in the background, sudo will now forward SIGINFO to the command (if supported). Sudo will now use the system versions of the sha2 functions from libc or libmd if available. Visudo now works correctly on GNU Hurd. Bug #647. Fixed suspend and resume of curses programs on some system when the command is not being run in a pseudo-terminal. Bug #649. Fixed a crash with LDAP-based sudoers on some systems when Kerberos was enabled. Sudo now includes optional Solaris audit support. Catalan translation for sudoers from translationproject.org. Norwegian Bokmaal translation for sudo from translationproject.org. Greek translation for sudoers from translationproject.org The sudo source tree has been reorganized to more closely resemble that of other gettext-enabled packages. Sudo and its associated programs now link against a shared version of libsudo_util. The --disable-shared-libutil configure option may be used to force static linking if the --enable-static-sudoers option is also specified. The passwords in ldap.conf and ldap.secret may now be encoded in base64. Audit updates. SELinux role changes are now audited. For sudoedit, we now audit the actual editor being run, instead of just the sudoedit command. Fixed bugs in the man page post-processing that could cause portions of the manuals to be removed. Fixed a crash in the system_group plugin. Bug #653. Fixed sudoedit on platforms without a native version of the getprogname() function. Bug #654. Fixed compilation problems with some pre-C99 compilers. Fixed sudo's -C option which was broken in version 1.8.9. It is now possible to match an environment variable's value as well as its name using env_keep and env_check. This can be used to preserve bash functions which would otherwise be removed from the environment. New files created via sudoedit as a non-root user now have the proper group id. Bug #656. Sudoedit now works correctly in conjunction with sudo's SELinux RBAC support. Temporary files are now created with the proper security context. The sudo I/O logging plugin API has been updated. If a logging function returns an error, the command will be terminated and all of the plugin's logging functions will be disabled. If a logging function rejects the command's output it will no longer be displayed to the user's terminal. Fixed a compilation error on systems that lack openpty(), _getpty() and grantpt(). Bug #660. Fixed a hang when a sudoers source is listed more than once in a single sudoers nsswitch.conf entry. On AIX, shell scripts without a #! magic number are now passed to /usr/bin/sh, not /usr/bin/bsh. This is consistent with what the execvp() function on AIX does and matches historic sudo behavior. Bug #661. Fixed a cross-compilation problem building mksiglist and mksigname. Bug #662. Major changes between version 1.8.10p3 and 1.8.10p2: Fixed expansion of the %p escape in the prompt for "sudo -l" when rootpw, runaspw or targetpw is set. Bug #639. Fixed matching of uids and gids which was broken in version 1.8.9. Bug #640. PAM credential initialization has been re-enabled. It was unintentionally disabled by default in version 1.8.8. The way credentials are initialized has also been fixed. Bug #642. Fixed a descriptor leak on Linux when determing boot time. Sudo normally closes extra descriptors before running a command so the impact is limited. Bug #645. Fixed flushing of the last buffer of data when I/O logging is enabled. This bug, introduced in version 1.8.9, could cause incomplete command output on some systems. Bug #646. Major changes between version 1.8.10p2 and 1.8.10p1: Fixed a hang introduced in sudo 1.8.10 when timestamp_timeout is set to zero. Bug #638. Major changes between version 1.8.10p1 and 1.8.10: Fixed a bug introduced in sudo 1.8.10 that prevented the disabling of tty-based tickets. Fixed a bug with netgated commands in "sudo -l command" that could cause the command to be listed even when it was explicitly denied. This only affected list mode when a command was specified. Bug #636. Major changes between version 1.8.10 and 1.8.9p5: It is now possible to disable network interface probing in sudo.conf by changing the value of the probe_interfaces setting. When listing a user's privileges (sudo -l), the sudoers plugin will now prompt for the user's password even if the targetpw, rootpw or runaspw options are set. The sudoers plugin uses a new format for its time stamp files. Each user now has a single file which may contain multiple records when per-tty time stamps are in use (the default). The time stamps use a monotonic timer where available and are once again located in a directory under /var/run. The lecture status is now stored separately from the time stamps in a different directory. Bug #616. sudo's -K option will now remove all of the user's time stamps, not just the time stamp for the current terminal. The -k option can be used to only disable time stamps for the current terminal. If sudo was started in the background and needed to prompt for a password, it was not possible to suspend it at the password prompt. This now works properly. LDAP-based sudoers now uses a default search filter of (objectClass=sudoRole) for more efficient queries. The netgroup query has been modified to avoid falling below the minimum length for OpenLDAP substring indices. The new use_netgroups sudoers option can be used to explicitly enable or disable netgroups support. For LDAP-based sudoers, netgroup support requires an expensive substring match on the server. If netgroups are not needed, this option can be disabled to reduce the load on the LDAP server. Sudo is once again able to open the sudoers file when the group on sudoers doesn't match the expected value, so long as the file is not group writable. Sudo now installs an init.d script to clear the time stamp directory at boot time on AIX and HP-UX systems. These systems either lack /var/run or do not clear it on boot. The JSON format used by visudo -x now properly supports the negation operator. In addition, the Options object is now the same for both Defaults and Cmnd_Specs. Czech and Serbian translations for sudoers from translationproject.org. Catalan translation for sudo from translationproject.org. Major changes between version 1.8.9p5 and 1.8.9p4: Fixed a compilation error on AIX when LDAP support is enabled. Fixed parsing of the "umask" defaults setting in sudoers. Bug #632. Fixed a failed assertion when the "closefrom_override" defaults setting is enabled in sudoers and sudo's -C flag is used. Bug #633. Major changes between version 1.8.9p4 and 1.8.9p3: Fixed a bug where sudo could consume large amounts of CPU while the command was running when I/O logging is not enabled. Bug #631. Fixed a bug where sudo would exit with an error when the debug level is set to util@@debug or all@@debug and I/O logging is not enabled. The command would continue runnning after sudo exited. Major changes between version 1.8.9p3 and 1.8.9p2: Fixed a bug introduced in sudo 1.8.9 that prevented the tty name from being resolved properly on Linux systems. Bug #630. Major changes between version 1.8.9p2 and 1.8.9p1: Updated config.guess, config.sub and libtool to support the ppc64le architecture (IBM PowerPC Little Endian). Major changes between version 1.8.9p1 and 1.8.9: Fixed a problem with gcc 4.8's handling of bit fields that could lead to the noexec flag being enabled even when it was not explicitly set. Major changes between version 1.8.9 and 1.8.8: Reworked sudo's main event loop to use a simple event subsystem using poll(2) or select(2) as the back end. It is now possible to statically compile the sudoers plugin into the sudo binary without disabling shared library support. The sudo.conf file may still be used to configure other plugins. Sudo can now be compiled again with a C preprocessor that does not support variadic macros. Visudo can now export a sudoers file in JSON format using the new -x flag. The locale is now set correctly again for visudo and sudoreplay. The plugin API has been extended to allow the plugin to exclude specific file descriptors from the closefrom range. There is now a workaround for a Solaris-specific problem where NOEXEC was overriding traditional root DAC behavior. Add user netgroup filtering for SSSD. Previously, rules for a netgroup were applied to all even when they did not belong to the specified netgroup. On systems with BSD login classes, if the user specified a group (not a user) to run the command as, it was possible to specify a different login class even when the command was not run as the super user. The closefrom() emulation on Mac OS X now uses /dev/fd if possible. Fixed a bug where sudoedit would not update the original file from the temporary when PAM or I/O logging is not enabled. When recycling I/O logs, the log files are now truncated properly. Fixes bugs #617, #621, #622, #623, #624, #625, #626 Major changes between version 1.8.8 and 1.8.7: Removed a warning on PAM systems with stacked auth modules where the first module on the stack does not succeed. Sudo, sudoreplay and visudo now support GNU-style long options. The -h (--host) option may now be used to specify a host name. This is currently only used by the sudoers plugin in conjunction with the -l (--list) option. Program usage messages and manual SYNOPSIS sections have been simplified. Sudo's LDAP SASL support now works properly with Kerberos. Previously, the SASL library was unable to locate the user's credential cache. It is now possible to set the nproc resource limit to unlimited via pam_limits on Linux (bug #565). New pam_service and pam_login_service sudoers options that can be used to specify the PAM service name to use. New pam_session and pam_setcred sudoers options that can be used to disable PAM session and credential support. The sudoers plugin now properly supports UIDs and GIDs that are larger than 0x7fffffff on 32-bit platforms. Fixed a visudo bug introduced in sudo 1.8.7 where per-group Defaults entries would cause an internal error. If the tty_tickets sudoers option is enabled (the default), but there is no tty present, sudo will now use a ticket file based on the parent process ID. This makes it possible to support the normal timeout behavior for the session. Fixed a problem running commands that change their process group and then attempt to change the terminal settings when not running the command in a pseudo-terminal. Previously, the process would receive SIGTTOU since it was effectively a background process. Sudo will now grant the child the controlling tty and continue it when this happens. The closefrom_override sudoers option may now be used in a command-specified Defaults entry (bug #610). Sudo's BSM audit support now works on Solaris 11. Brazilian Portuguese translation for sudo and sudoers from translationproject.org. Czech translation for sudo from translationproject.org. French translation for sudo from translationproject.org. Sudo's noexec support on Mac OS X 10.4 and above now uses dynamic symbol interposition instead of setting DYLD_FORCE_FLAT_NAMESPACE=1 which causes issues with some programs. Fixed visudo's -q (--quiet) flag, broken in sudo 1.8.6. Root may no longer change its SELinux role without entering a password. Fixed a bug introduced in Sudo 1.8.7 where the indexes written to the I/O log timing file are two greater than they should be. Sudoreplay now contains a work-around to parse those files. In sudoreplay's list mode, the this qualifier in fromdate or todate expressions now behaves more sensibly. Previously, it would often match a date that was "one more" than expected. For example, "this week" now matches the current week instead of the following week. Major changes between version 1.8.7 and 1.8.6p8: The non-Unix group plugin is now supported when sudoers data is stored in LDAP. Sudo now uses a workaround for a locale bug on Solaris 11.0 that prevents setuid programs like sudo from fully using locales. User messages are now always displayed in the user's locale, even when the same message is being logged or mailed in a different locale. Log files created by sudo now explicitly have the group set to group ID 0 rather than relying on BSD group semantics (which may not be the default). A new exec_background sudoers option can be used to initially run the command without read access to the terminal when running a command in a pseudo-tty. If the command tries to read from the terminal it will be stopped by the kernel (via SIGTTIN or SIGTTOU) and sudo will immediately restart it as the forground process (if possible). This allows sudo to only pass terminal input to the program if the program actually is expecting it. Unfortunately, a few poorly-behaved programs (like "su" on most Linux systems) do not handle SIGTTIN and SIGTTOU properly. Sudo now uses an efficient group query to get all the groups for a user instead of iterating over every record in the group database on HP-UX and Solaris. Sudo now produces better error messages when there is an error in the sudo.conf file. Two new settings have been added to sudo.conf to give the admin better control of how group database queries are performed. The group_source specifies how the group list for a user will be determined. Legal values are static (use the kernel groups list), dynamic (perform a group database query) and adaptive (only perform a group database query if the kernel list is full). The max_groups setting specifies the maximum number of groups a user may belong to when performing a group database query. The sudo.conf file now supports line continuation by using a backslash as the last character on the line. There is now a standalone sudo.conf manual page. Sudo now stores its libexec files in a sudo subdirectory instead of in libexec itself. For backwards compatibility, if the plugin is not found in the default plugin directory, sudo will check the parent directory if the default directory ends in /sudo. The sudoers I/O logging plugin now logs the terminal size. A new sudoers option maxseq can be used to limit the number of I/O log entries that are stored. The system_group and group_file sudoers group provider plugins are now installed by default. The list output (sudo -l) output from the sudoers plugin is now less ambiguous when an entry includes different runas users. The long list output (sudo -ll) for file-based sudoers is now more consistent with the format of LDAP-based sudoers. A uid may now be used in the sudoRunAsUser attributes for LDAP sudoers. Minor plugin API change: the close and version functions are now optional. If the policy plugin does not provide a close function and the command is not being run in a new pseudo-tty, sudo may now execute the command directly instead of in a child process. A new sudoers option pam_session can be used to disable sudo's PAM session support. On HP-UX systems, sudo will now use the pstat() function to determine the tty instead of ttyname(). Turkish translation for sudo and sudoers from translationproject.org. Dutch translation for sudo and sudoers from translationproject.org. Tivoli Directory Server client libraries may now be used with HP-UX where libibmldap has a hidden dependency on libCsup. The sudoers plugin will now ignore invalid domain names when checking netgroup membership. Most Linux systems use the string "(none)" for the NIS-style domain name instead of an empty string. New support for specifying a SHA-2 digest along with the command in sudoers. Supported hash types are sha224, sha256, sha384 and sha512. See the description of Digest_Spec in the sudoers manual or the description of sudoCommand in the sudoers.ldap manual for details. The paths to ldap.conf and ldap.secret may now be specified as arguments to the sudoers plugin in the sudo.conf file. Fixed potential false positives in visudo's alias cycle detection. Fixed a problem where the time stamp file was being treated as out of date on Linux systems where the change time on the pseudo-tty device node can change after it is allocated. Sudo now only builds Position Independent Executables (PIE) by default on Linux systems and verifies that a trivial test program builds and runs. On Solaris 11.1 and higher, sudo binaries will now have the ASLR tag enabled if supported by the linker. Major changes between version 1.8.6p8 and 1.8.6p7: Terminal detection now works properly on 64-bit AIX kernels. This was broken by the removal of the ttyname() fallback in Sudo 1.8.6p6. Sudo is now able to map an AIX 64-bit device number to the corresponding device file in /dev. Sudo now checks for crypt() returning NULL when performing passwd-based authentication. Major changes between version 1.8.6p7 and 1.8.6p6: A time stamp file with the date set to the epoch by sudo -k is now completely ignored regardless of what the local clock is set to. Previously, if the local clock was set to a value between the epoch and the time stamp timeout value, a time stamp reset by sudo -k would be considered current. This is a potential security issue. The tty-specific time stamp file now includes the session ID of the sudo process that created it. If a process with the same tty but a different session ID runs sudo, the user will now be prompted for a password (assuming authentication is required for the command). This is a potential security issue. Major changes between version 1.8.6p6 and 1.8.6p5: On systems where the controlling tty can be determined via /proc or sysctl(), sudo will no longer fall back to using ttyname() if the process has no controlling tty. This prevents sudo from using a non-controlling tty for logging and time stamp purposes. This is a potential security issue. Major changes between version 1.8.6p5 and 1.8.6p4: Fixed a potential crash in visudo's alias cycle detection. Improved performance on Solaris when retrieving the group list for the target user. On systems with a large number of groups where the group database is not local (NIS, LDAP, AD), fetching the group list could take a minute or more. Major changes between version 1.8.6p4 and 1.8.6p3: The -fstack-protector is now used when linking visudo, sudoreplay and testsudoers. Avoid building PIE binaries on FreeBSD/ia64 as they don't run properly. Fixed a crash in visudo strict mode when an unknown Defaults setting is encountered. Do not inform the user that the command was not permitted by the policy if they do not successfully authenticate. This is a regression introduced in sudo 1.8.6. Allow sudo to be build with sss support without also including ldap support. Fix running commands that need the terminal in the background when I/O logging is enabled. E.g. sudo vi &. When the command is foregrounded, it will now resume properly. Major changes between version 1.8.6p3 and 1.8.6p2: Fixed post-processing of the man pages on systems with legacy versions of sed. Fixed sudoreplay -l on Linux systems with file systems that set DT_UNKNOWN in the d_type field of struct dirent. Major changes between version 1.8.6p2 and 1.8.6p1: Fixed suspending a command after it has already been resumed once when I/O logging (or use_pty) is not enabled. This was a regression introduced in version 1.8.6. Major changes between version 1.8.6p1 and 1.8.6: Fixed the setting of LOGNAME, USER and USERNAME variables in the command's environment when env_reset is enabled (the default). This was a regression introduced in version 1.8.6. Sudo now honors SUCCESS=return in /etc/nsswitch.conf. Major changes between version 1.8.6 and 1.8.5p3: Sudo is now built with the -fstack-protector flag if the the compiler supports it. Also, the -zrelro linker flag is used if supported. The --disable-hardening configure option can be used to build sudo without stack smashing protection. Sudo is now built as a Position Independent Executable (PIE) if supported by the compiler and linker. If the user is a member of the exempt group in sudoers, they will no longer be prompted for a password even if the -k flag is specified with the command. This makes sudo -k command consistent with the behavior one would get if the user ran sudo -k immediately before running the command. The sudoers file may now be a symbolic link. Previously, sudo would refuse to read sudoers unless it was a regular file. The sudoreplay command can now properly replay sessions where no tty was present. The sudoers plugin now takes advantage of symbol visibility controls when supported by the compiler or linker. As a result, only a small number of symbols are exported which significantly reduces the chances of a conflict with other shared objects. Improved support for the Tivoli Directory Server LDAP client libraries. This includes support for using LDAP over SSL (ldaps) as well as support for the BIND_TIMELIMIT, TLS_KEY and TLS_CIPHERS ldap.conf options. A new ldap.conf option, TLS_KEYPW can be used to specify a password to decrypt the key database. When constructing a time filter for use with LDAP sudoNotBefore and sudoNotAfter attributes, the current time now includes tenths of a second. This fixes a problem with timed entries on Active Directory. If a user fails to authenticate and the command would be rejected by sudoers, it is now logged with command not allowed instead of N incorrect password attempts. Likewise, the mail_no_perms sudoers option now takes precedence over mail_badpass The sudo manuals are now formatted using the mdoc macros. Versions using the legacy man macros are provided for systems that lack mdoc. New support for Solaris privilege sets. This makes it possible to specify fine-grained privileges in the sudoers file on Solaris 10 and above. A Runas_Spec that contains no Runas_Lists can be used to give a user the ability to run a command as themselves but with an expanded privilege set. Fixed a problem with the reboot and shutdown commands on some systems (such as HP-UX and BSD). On these systems, reboot sends all processes (except itself) SIGTERM. When sudo received SIGTERM, it would relay it to the reboot process, thus killing reboot before it had a chance to actually reboot the system. Support for using the System Security Services Daemon (SSSD) as a source of sudoers data. Slovenian translation for sudo and sudoers from translationproject.org. Visudo will now warn about unknown Defaults entries that are per-host, per-user, per-runas or per-command. Fixed a race condition that could cause sudo to receive SIGTTOU (and stop) when resuming a shell that was run via sudo when I/O logging (and use_pty) is not enabled. Sending SIGTSTP directly to the sudo process will now suspend the running command when I/O logging (and use_pty) is not enabled. Major changes between version 1.8.5p3 and 1.8.5p2: Fixed the loading of I/O plugins that conform to a plugin API version older than 1.2. Major changes between version 1.8.5p2 and 1.8.5p1: Fixed use of the SUDO_ASKPASS environment variable which was broken in Sudo 1.8.5. Fixed a problem reading the sudoers file when the file mode is more restrictive than the expected mode. For example, when the expected sudoers file mode is 0440 but the actual mode is 0400. Major changes between version 1.8.5p1 and 1.8.5: Fixed a bug that prevented files in an include directory from being evaluated. Major changes between version 1.8.5 and 1.8.4p5: When "noexec" is enabled, sudo_noexec.so will now be prepended to any existing LD_PRELOAD variable instead of replacing it. The sudo_noexec.so shared library now wraps the execvpe(), exect(), posix_spawn() and posix_spawnp() functions. The user/group/mode checks on sudoers files have been relaxed. As long as the file is owned by the sudoers uid, not world-writable and not writable by a group other than the sudoers gid, the file is considered OK. Note that visudo will still set the mode to the value specified at configure time. It is now possible to specify the sudoers path, uid, gid and file mode as options to the plugin in the sudo.conf file. Croatian, Galician, German, Lithuanian, Swedish and Vietnamese translations from translationproject.org. /etc/environment is no longer read directly on Linux systems when PAM is used. Sudo now merges the PAM environment into the user's environment which is typically set by the pam_env module. The initial evironment created when env_reset is in effect now includes the contents of /etc/environment on AIX systems and the "setenv" and "path" entries from /etc/login.conf on BSD systems. The plugin API has been extended in three ways. First, options specified in sudo.conf after the plugin pathname are passed to the plugin's open function. Second, sudo has limited support for hooks that can be used by plugins. Currently, the hooks are limited to environment handling functions. Third, the init_session policy plugin function is passed a pointer to the user environment which can be updated during session setup. The plugin API version has been incremented to version 1.2. See the sudo_plugin manual for more information. The policy plugin's init_session function is now called by the parent sudo process, not the child process that executes the command. This allows the PAM session to be open and closed in the same process, which some PAM modules require. Fixed parsing of "Path askpass" and "Path noexec" in sudo.conf, which was broken in version 1.8.4. On systems with an SVR4-style /proc file system, the /proc/pid/psinfo file is now uses to determine the controlling terminal, if possible. This allows tty-based tickets to work properly even when, e.g. standard input, output and error are redirected to /dev/null. The output of "sudoreplay -l" is now sorted by file name (or sequence number). Previously, entries were displayed in the order in which they were found on the file system. Sudo now behaves properly when I/O logging is enabled and the controlling terminal is revoked (e.g. the running sshd is killed). Previously, sudo may have exited without calling the I/O plugin's close function which can lead to an incomplete I/O log. Sudo can now detect when a user has logged out and back in again on Solaris 11, just like it can on Solaris 10. The built-in zlib included with Sudo has been upgraded to version 1.2.6. Setting the SSL parameter to start_tls in ldap.conf now works properly when using Mozilla-based SDKs that support the ldap_start_tls_s() function. The TLS_CHECKPEER parameter in ldap.conf now works when the Mozilla NSS crypto backend is used with OpenLDAP. A new group provider plugin, system_group, is included which performs group look ups by name using the system groups database. This can be used to restore the pre-1.7.3 sudo group lookup behavior. Major changes between version 1.8.4p5 and 1.8.4p4: Fixed a potential security issue in the matching of hosts against an IPv4 network specified in sudoers. The flaw may allow a user who is authorized to run commands on hosts belonging to one IPv4 network to run commands on a different host. Major changes between version 1.8.4p4 and 1.8.4p3: Fixed a bug introduced in Sudo 1.8.4 which prevented sudo -v from working. Major changes between version 1.8.4p3 and 1.8.4p2: Fixed a crash on FreeBSD when there is no tty present. When visudo is run with the -c (check) option, the sudoers file(s) owner and mode are now also checked unless the -f option was specified. Major changes between version 1.8.4p2 and 1.8.4p1: Fixed a bug introduced in Sudo 1.8.4 where insufficient space was allocated for group IDs in the LDAP filter. Fixed a bug introduced in Sudo 1.8.4 where the path to sudo.conf was /sudo.conf instead of etc/sudo.conf. Fixed a bug introduced in Sudo 1.8.4 which could cause a hang when I/O logging is enabled and input is from a pipe or file. Major changes between version 1.8.4p1 and 1.8.4: Fixed a bug introduced in sudo 1.8.4 that broke adding to or deleting from the env_keep, env_check and env_delete lists in sudoers on some platforms. Major changes between version 1.8.4 and 1.8.3p2: The -D flag in sudo has been replaced with a more general debugging framework that is configured in sudo.conf. Fixed a false positive in visudo strict mode when aliases are in use. Fixed a crash with sudo -i when a runas group was specified without a runas user. The line on which a syntax error is reported in the sudoers file is now more accurate. Previously it was often off by a line. Fixed a bug where stack garbage could be printed at the end of the lecture when the lecture_file option was enabled. make install now honors the LINGUAS environment variable. The #include and #includedir directives in sudoers now support relative paths. If the path is not fully qualified it is expected to be located in the same directory of the sudoers file that is including it. New Serbian and Spanish translations for sudo from translationproject.org. LDAP-based sudoers may now access by group ID in addition to group name. visudo will now fix the mode on the sudoers file even if no changes are made unless the -f option is specified. The use_loginclass sudoers option works properly again. On systems that use login.conf, sudo -i now sets environment variables based on login.conf. For LDAP-based sudoers, values in the search expression are now escaped as per RFC 4515. The plugin close function is now properly called when a login session is killed (as opposed to the actual command being killed). This can happen when an ssh session is disconnected or the terminal window is closed. The deprecated "noexec_file" sudoers option is no longer supported. Fixed a race condition when I/O logging is not enabled that could result in tty-generated signals (e.g. control-C) being received by the command twice. If none of the standard input, output or error are connected to a tty device, sudo will now check its parent's standard input, output or error for the tty name on systems with /proc and BSD systems that support the KERN_PROC_PID sysctl. This allows tty-based tickets to work properly even when, e.g. standard input, output and error are redirected to /dev/null. Added the --enable-kerb5-instance configure option to allow people using Kerberos V authentication to specify a custom instance so the principal name can be, e.g. "username/sudo" similar to how ksu uses "username/root". Fixed a bug where a pattern like /usr/* included /usr/bin/ in the results, which would be incorrectly be interpreted as if the sudoers file had specified a directory. visudo -c will now list any include files that were checked in addition to the main sudoers file when everything parses OK. Users that only have read-only access to the sudoers file may now run visudo -c. Previously, write permissions were required even though no writing is down in check-only mode. It is now possible to prevent the disabling of core dumps from within sudo itself by adding a line to the sudo.conf file like Set disable_coredump false. Major changes between version 1.8.3p2 and 1.8.3p1: Fixed a format string vulnerability when the sudo binary (or a symbolic link to the sudo binary) contains printf format escapes and the -D (debugging) flag is used. Major changes between version 1.8.3p1 and 1.8.3: Fixed a crash in the monitor process on Solaris when NOPASSWD was specified or when authentication was disabled. Fixed matching of a Runas_Alias in the group section of a Runas_Spec. Major changes between version 1.8.3 and 1.8.2: Fixed expansion of strftime() escape sequences in the log_dir sudoers setting. Esperanto, Italian and Japanese translations from translationproject.org. Sudo will now use PAM by default on AIX 6 and higher. Added --enable-werror configure option for gcc's -Werror flag. Visudo no longer assumes all editors support the +linenumber command line argument. It now uses a whitelist of editors known to support the option. Fixed matching of network addresses when a netmask is specified but the address is not the first one in the CIDR block. The configure script now check whether or not errno.h declares the errno variable. Previously, sudo would always declare errno itself for older systems that don't declare it in errno.h. The NOPASSWD tag is now honored for denied commands too, which matches historic sudo behavior (prior to sudo 1.7.0). Sudo now honors the DEREF setting in ldap.conf which controls how alias dereferencing is done during an LDAP search. A symbol conflict with the pam_ssh_agent_auth PAM module that would cause a crash been resolved. The inability to load a group provider plugin is no longer a fatal error. A potential crash in the utmp handling code has been fixed. Two PAM session issues have been resolved. In previous versions of sudo, the PAM session was opened as one user and closed as another. Additionally, if no authentication was performed, the PAM session would never be closed. Sudo will now work correctly with LDAP-based sudoers using TLS or SSL on Debian systems. The LOGNAME, USER and USERNAME environment variables are preserved correctly again in sudoedit mode. Major changes between version 1.8.2 and 1.8.1p2: Sudo, visudo, sudoreplay and the sudoers plug-in now have natural language support (NLS). Sudo will use gettext(), if available, to display translated messages. This can be disabled by passing configure the --disable-nls option. All translations are coordinated via The Translation Project, translationproject.org. Sudo 1.8.2 includes translations for Basque, Chinese (simplified), Danish, Finish, Polish, Russian and Ukranian. Plug-ins are now loaded with the RTLD_GLOBAL flag instead of RTLD_LOCAL. This fixes missing symbol problems in PAM modules on certain platforms, such as FreeBSD and SuSE Linux Enterprise. I/O logging is now supported for commands run in background mode (using sudo's -b flag). Group ownership of the sudoers file is now only enforced when the file mode on sudoers allows group readability or writability. Visudo now checks the contents of an alias and warns about cycles when the alias is expanded. If the user specifes a group via sudo's -g option that matches the target user's group in the password database, it is now allowed even if no groups are present in the Runas_Spec. The sudo Makefiles now have more complete dependencies which are automatically generated instead of being maintained manually. The use_pty sudoers option is now correctly passed back to the sudo front end. This was missing in previous versions of sudo 1.8 which prevented use_pty from being honored. sudo -i command now works correctly with the bash version 2.0 and higher. Previously, the .bash_profile would not be sourced prior to running the command unless bash was built with NON_INTERACTIVE_LOGIN_SHELLS defined. When matching groups in the sudoers file, sudo will now match based on the name of the group instead of the group ID. This can substantially reduce the number of group lookups for sudoers files that contain a large number of groups. Multi-factor authentication is now supported on AIX. Added support for non-RFC 4517 compliant LDAP servers that require that seconds be present in a timestamp, such as Tivoli Directory Server. If the group vector is to be preserved, the PATH search for the command is now done with the user's original group vector. For LDAP-based sudoers, the runas_default sudoOption now works properly in a sudoRole that contains a sudoCommand. Spaces in command line arguments for sudo -s and sudo -i are now escaped with a backslash when checking the security policy. Major changes between version 1.8.1p2 and 1.8.1p1: Two-character CIDR-style IPv4 netmasks are now matched correctly in the sudoers file. A build error with MIT Kerberos V has been resolved. A crash on HP-UX in the sudoers plugin when wildcards are present in the sudoers file has been resolved. Sudo now works correctly on Tru64 Unix again. Major changes between version 1.8.1p1 and 1.8.1: Fixed a problem on AIX where sudo was unable to set the final uid if the PAM module modified the effective uid. A non-existent includedir is now treated the same as an empty directory and not reported as an error. Removed extraneous parens in LDAP filter when sudoers_search_filter is enabled that can cause an LDAP search error. Fixed a make -j problem for make install Major changes between version 1.8.1 and 1.8.0: A new LDAP setting, sudoers_search_filter, has been added to ldap.conf. This setting can be used to restrict the set of records returned by the LDAP query. Based on changes from Matthew Thomas. White space is now permitted within a User_List when used in conjunction with a per-user Defaults definition. A group ID (%#gid) may now be specified in a User_List or Runas_List. Likewise, for non-Unix groups the syntax is %:#gid. Support for double-quoted words in the sudoers file has been fixed. The change in 1.7.5 for escaping the double quote character caused the double quoting to only be available at the beginning of an entry. The fix for resuming a suspended shell in 1.7.5 caused problems with resuming non-shells on Linux. Sudo will now save the process group ID of the program it is running on suspend and restore it when resuming, which fixes both problems. A bug that could result in corrupted output in "sudo -l" has been fixed. Sudo will now create an entry in the utmp (or utmpx) file when allocating a pseudo-tty (e.g. when logging I/O). The "set_utmp" and "utmp_runas" sudoers file options can be used to control this. Other policy plugins may use the "set_utmp" and "utmp_user" entries in the command_info list. The sudoers policy now stores the TSID field in the logs even when the "iolog_file" sudoers option is defined to a value other than %{sessid}. Previously, the TSID field was only included in the log file when the "iolog_file" option was set to its default value. The sudoreplay utility now supports arbitrary session IDs. Previously, it would only work with the base-36 session IDs that the sudoers plugin uses by default. Sudo now passes "run_shell=true" to the policy plugin in the settings list when sudo's -s command line option is specified. The sudoers policy plugin uses this to implement the "set_home" sudoers option which was missing from sudo 1.8.0. The "noexec" functionality has been moved out of the sudoers policy plugin and into the sudo front-end, which matches the behavior documented in the plugin writer's guide. As a result, the path to the noexec file is now specified in the sudo.conf file instead of the sudoers file. On Solaris 10, the PRIV_PROC_EXEC privilege is now used to implement the "noexec" feature. Previously, this was implemented via the LD_PRELOAD environment variable. The exit values for "sudo -l", "sudo -v" and "sudo -l command" have been fixed in the sudoers policy plugin. The sudoers policy plugin now passes the login class, if any, back to the sudo front-end. The sudoers policy plugin was not being linked with requisite libraries in certain configurations. Sudo now parses command line arguments before loading any plugins. This allows "sudo -V" or "sudo -h" to work even if there is a problem with sudo.conf Plugins are now linked with the static version of libgcc to allow the plugin to run on a system where no shared libgcc is installed, or where it is installed in a different location. Major changes between version 1.8.0 and 1.7.5: Sudo has been refactored to use a modular framework that can support third-party policy and I/O logging plugins. The default plugin is "sudoers" which provides the traditional sudo functionality. See the sudo_plugin manual for details on the plugin API and the sample in the plugins directory for a simple example. @ text @d1 1 a1 1 @@comment $NetBSD: PLIST,v 1.7 2014/07/28 20:07:42 jperkin Exp $ d37 53 @ 1.7 log @Darwin doesn't build sudo_noexec.so, patch from Sevan Janiyan. @ text @d1 1 a1 1 @@comment $NetBSD: PLIST,v 1.6 2010/09/21 03:05:27 taca Exp $ d5 7 a11 1 ${PLIST.noexec}libexec/sudo_noexec.so d15 1 d20 1 a28 3 share/doc/sudo/sample.pam share/doc/sudo/sample.sudoers share/doc/sudo/sample.syslog.conf d33 2 d36 1 @ 1.7.12.1 log @Pullup ticket #4904 - requested by taca security/sudo: security fix Revisions pulled up: - security/sudo/Makefile 1.147 - security/sudo/PLIST 1.8 - security/sudo/distinfo 1.84 - security/sudo/patches/patch-aa 1.31 - security/sudo/patches/patch-af 1.32 - security/sudo/patches/patch-ag 1.23 - security/sudo/patches/patch-logging.c deleted - security/sudo/patches/patch-plugins_sudoers_Makefile.in 1.1 - security/sudo/patches/patch-plugins_sudoers_logging.c 1.1 - security/sudo/patches/patch-src_Makefile.in 1.1 --- Module Name: pkgsrc Committed By: spz Date: Fri Jan 1 17:00:49 UTC 2016 Modified Files: pkgsrc/security/sudo: Makefile PLIST distinfo pkgsrc/security/sudo/patches: patch-aa patch-af patch-ag Added Files: pkgsrc/security/sudo/patches: patch-plugins_sudoers_Makefile.in patch-plugins_sudoers_logging.c patch-src_Makefile.in Removed Files: pkgsrc/security/sudo/patches: patch-logging.c Log Message: Update to 1.8.15, which fixes CVE-2015-5602, a symlink vulnerability in sudoedit. Note that it's a fairly large step and the package has only been tested on NetBSD and there may be further breakage. Testing on non-NetBSD would be appreciated. Upstream changelog: Major changes between version 1.8.15 and 1.8.14p3: Fixed a bug that prevented sudo from building outside the source tree on some platforms. Bug #708. Fixed the location of the sssd library in the RHEL/Centos packages. Bug #710. Fixed a build problem on systems that don't implicitly include sys/types.h from other header files. Bug #711. Fixed a problem on Linux using containers where sudo would ignore signals sent by a process in a different container. Sudo now refuses to run a command if the PAM session module returns an error. When editing files with sudoedit, symbolic links will no longer be followed by default. The old behavior can be restored by enabling the sudoedit_follow option in sudoers or on a per-command basis with the FOLLOW and NOFOLLOW tags. Bug #707. Fixed a bug introduced in version 1.8.14 that caused the last valid editor in the sudoers "editor" list to be used by visudo and sudoedit instead of the first. Bug #714. Fixed a bug in visudo that prevented the addition of a final newline to edited files without one. Fixed a bug decoding certain base64 digests in sudoers when the intermediate format included a '=' character. Individual records are now locked in the time stamp file instead of the entire file. This allows sudo to avoid prompting for a password multiple times on the same terminal when used in a pipeline. In other words, sudo cat foo | sudo grep bar now only prompts for the password once. Previously, both sudo processes would prompt for a password, often making it impossible to enter. Bug #705. Fixed a bug where sudo would fail to run commands as a non-root user on systems that lack both setresuid() and setreuid(). Bug #713. Fixed a bug introduced in sudo 1.8.14 that prevented visudo from re-editing the correct file when a syntax error was detected. Fixed a bug where sudo would not relay a SIGHUP signal to the command when the terminal is closed and the command is not run in its own pseudo-tty. Bug #719. If some, but not all, of the LOGNAME, USER or USERNAME environment variables have been preserved from the invoking user's environment, sudo will now use the preserved value to set the remaining variables instead of using the runas user. This ensures that if, for example, only LOGNAME is present in the env_keep list, that sudo will not set USER and USERNAME to the runas user. When the command sudo is running dies due to a signal, sudo will now send itself that same signal with the default signal handler installed instead of exiting. The bash shell appears to ignore some signals, e.g. SIGINT, unless the command being run is killed by that signal. This makes the behavior of commands run under sudo the same as without sudo when bash is the shell. Bug #722. Slovak translation for sudo from translationproject.org. Hungarian and Slovak translations for sudoers from translationproject.org. Previously, when env_reset was enabled (the default) and the -s option was not used, the SHELL environment variable was set to the shell of the invoking user. Now, when env_reset is enabled and the -s option is not used, SHELL is set based on the target user. Fixed challenge/response style BSD authentication. Added the sudoedit_checkdir Defaults option to prevent sudoedit from editing files located in a directory that is writable by the invoking user. Added the always_query_group_plugin Defaults option to control whether groups not found in the system group database are passed to the group plugin. Previously, unknown system groups were always passed to the group plugin. When creating a new file, sudoedit will now check that the file's parent directory exists before running the editor. Fixed the compiler stack protector test in configure for compilers that support -fstack-protector but don't actually have the ssp library available. Major changes between version 1.8.14p3 and 1.8.14p2: Fixed a bug introduced in sudo 1.8.14p2 that prevented sudo from working when no tty was present. Bug #706. Fixed tty detection on newer AIX systems where dev_t is 64-bit. Major changes between version 1.8.14p2 and 1.8.14p1: Fixed a bug introduced in sudo 1.8.14 that prevented the lecture file from being created. Bug #704. Major changes between version 1.8.14p1 and 1.8.14: Fixed a bug introduced in sudo 1.8.14 that prevented the sssd backend from working. Bug #703. Major changes between version 1.8.14 and 1.8.13: Log messages on Mac OS X now respect sudoers_locale when sudo is build with NLS support. The sudo manual pages now pass mandoc -Tlint with no warnings. Fixed a compilation problem on systems with the sig2str() function that do not define SIG2STR_MAX in signal.h. Worked around a compiler bug that resulted in unexpected behavior when returning an int from a function declared to return bool without an explicit cast. Worked around a bug in Mac OS X 10.10 BSD auditing where the au_preselect() fails for AUE_sudo events but succeeds for AUE_DARWIN_sudo. Fixed a hang on Linux systems with glibc when sudo is linked with jemalloc. When the user runs a command as a user ID that is not present in the password database via the -u flag, the command is now run with the group ID of the invoking user instead of group ID 0. Fixed a compilation problem on systems that don't pull in definitions of uid_t and gid_t without sys/types.h or unistd.h. Fixed a compilation problem on newer AIX systems which use a struct st_timespec for time stamps in struct stat that differs from struct timespec. Bug #702. The example directory is now configurable via --with-exampledir and defaults to DATAROOTDIR/examples/sudo on BSD systems. The /usr/lib/tmpfiles.d/sudo.conf file is now installed as part of "make install" when systemd is in use. Fixed a linker problem on some systems with libintl. Bug #690. Fixed compilation with compilers that don't support __func__ or __FUNCTION__. Sudo no longer needs to uses weak symbols to support localization in the warning functions. A registration function is used instead. Fixed a setresuid() failure in sudoers on Linux kernels where uid changes take the nproc resource limit into account. Fixed LDAP netgroup queries on AIX. Sudo will now display the custom prompt on Linux systems with PAM even if the "Password: " prompt is not localized by the PAM module. Bug #701. Double-quoted values in an LDAP sudoOption are now supported for consistency with file-based sudoers. Fixed a bug that prevented the btime entry in /proc/stat from being parsed on Linux. Major changes between version 1.8.13 and 1.8.12: The examples directory is now a subdirectory of the doc dir to conform to Debian guidelines. Bug #682. Fixed a compilation error for siglist.c and signame.c on some systems. Bug #686. Weak symbols are now used for sudo_warn_gettext() and sudo_warn_strerror() in libsudo_util to avoid link errors when -Wl,--no-undefined is used in LDFLAGS. The --disable-weak-symbols configure option can be used to disable the user of weak symbols. Fixed a bug in sudo's mkstemps() replacement function that prevented the file extension from being preserved in sudoedit. A new mail_all_cmnds sudoers flag will send mail when a user runs a command (or tries to). The behavior of the mail_always flag has been restored to always send mail when sudo is run. New MAIL and NOMAIL command tags have been added to toggle mail sending behavior on a per-command (or Cmnd_Alias) basis. Fixed matching of empty passwords when sudo is configured to use passwd (or shadow) file authentication on systems where the crypt() function returns NULL for invalid salts. On AIX, sudo now uses the value of the auth_type setting in /etc/security/login.cfg to determine whether to use LAM or PAM for user authentication. The all setting for listpw and verifypw now works correctly with LDAP and sssd sudoers. The sudo timestamp directory is now created at boot time on platforms that use systemd. Sudo will now restore the value of the SIGPIPE handler before executing the command. Sudo now uses struct timespec instead of struct timeval for time keeping when possible. If supported, sudoedit and visudo now use nanosecond granularity time stamps. Fixed a symbol name collision with systems that have their own SHA2 implementation. This fixes a problem where PAM could use the wrong SHA2 implementation on Solaris 10 systems configured to use SHA512 for passwords. The editor invoked by sudoedit once again uses an unmodified copy of the user's environment as per the documentation. This was inadvertantly changed in sudo 1.8.0. Bug #688. Major changes between version 1.8.12 and 1.8.11p2: The embedded copy of zlib has been upgraded to version 1.2.8 and is now installed as a shared library where supported. Debug settings for the sudo front end and sudoers plugin are now configured separately. Multiple sudo.conf Debug entries may now be specified per program (or plugin). The plugin API has been extended such that the path to the plugin that was loaded is now included in the settings array. This path can be used to register with the debugging subsystem. The debug_flags setting is now prefixed with a file name and may be specified multiple times if there is more than one matching Debug setting in sudo.conf. The sudoers regression tests now run with the locale set to C since some of the tests compare output that includes locale-specific messages. Bug #672. Fixed a bug where sudo would not run commands on Linux when compiled with audit support if audit is disabled. Bug #671. Added __BASH_FUNC< to the environment blacklist to match Apple's syntax for newer-style bash functions. The default password prompt now includes a trailing space after "Password:" for consistency with su(1) on most systems. Bug #663. Fixed a problem on DragonFly BSD where SIGCHLD could be ignored, preventing sudo from exiting. Bug #676. Visudo will now use the optional sudoers_file, sudoers_mode, sudoers_uid and sudoers_gid arguments if specified on the sudoers.so Plugin line in the sudo.conf file. Fixed a problem introduced in sudo 1.8.8 that prevented the full host name from being used when the fqdn sudoers option is used. Bug #678. French and Russian translations for sudoers from translationproject.org. Sudo now installs a handler for SIGCHLD signal handler immediately before stating the process that will execute the command (or start the monitor). The handler used to be installed earlier but this causes problems with poorly behaved PAM modules that install their own SIGCHLD signal handler and neglect to restore sudo's original handler. Bug #657. Removed a limit on the length of command line arguments expanded by a wild card using sudo's version of the fnmatch() function. This limit was introduced when sudo's version of fnmatch() was replaced in sudo 1.8.4. LDAP-based sudoers can now query an LDAP server for a user's netgroups directly. This is often much faster than fetching every sudoRole object containing a sudoUser that begins with a `+' prefix and checking whether the user is a member of any of the returned netgroups. The mail_always sudoers option no longer sends mail for sudo -l or sudo -v unless the user is unable to authenticate themselves. Fixed a crash when sudo is run with an empty argument vector. Fixed two potential crashes when sudo is run with very low resource limits. The TZ environment variable is now checked for safety instead of simply being copied to the environment of the command. This fixes a potential security issue. Major changes between version 1.8.11p2 and 1.8.11p1: Fixed a bug where dynamic shared objects loaded from a plugin could use the hooked version of getenv() but not the hooked versions of putenv(), setenv() or unsetenv(). This can cause problems for PAM modules that use those functions. Major changes between version 1.8.11p1 and 1.8.11: Fixed a compilation problem on some systems when the --disable-shared-libutil configure option was specified. The user can no longer interrupt the sleep after an incorrect password on PAM systems using pam_unix. Bug #666. Fixed a compilation problem on Linux systems that do not use PAM. Bug #667. "make install" will now work with the stock GNU autotools install-sh script. Bug #669. Fixed a crash with "sudo -i" when the current working directory does not exist. Bug #670. Fixed a potential crash in the debug subsystem when logging a message larger that 1024 bytes. Fixed a "make check" failure for ttyname when stdin is closed and stdout and stderr are redirected to a different tty. Bug #643. Added BASH_FUNC_* to environment blacklist to match newer-style bash functions. Major changes between version 1.8.11 and 1.8.10p3: The sudoers plugin no longer uses setjmp/longjmp to recover from fatal errors. All errors are now propagated to the caller via return codes. When running a command in the background, sudo will now forward SIGINFO to the command (if supported). Sudo will now use the system versions of the sha2 functions from libc or libmd if available. Visudo now works correctly on GNU Hurd. Bug #647. Fixed suspend and resume of curses programs on some system when the command is not being run in a pseudo-terminal. Bug #649. Fixed a crash with LDAP-based sudoers on some systems when Kerberos was enabled. Sudo now includes optional Solaris audit support. Catalan translation for sudoers from translationproject.org. Norwegian Bokmaal translation for sudo from translationproject.org. Greek translation for sudoers from translationproject.org The sudo source tree has been reorganized to more closely resemble that of other gettext-enabled packages. Sudo and its associated programs now link against a shared version of libsudo_util. The --disable-shared-libutil configure option may be used to force static linking if the --enable-static-sudoers option is also specified. The passwords in ldap.conf and ldap.secret may now be encoded in base64. Audit updates. SELinux role changes are now audited. For sudoedit, we now audit the actual editor being run, instead of just the sudoedit command. Fixed bugs in the man page post-processing that could cause portions of the manuals to be removed. Fixed a crash in the system_group plugin. Bug #653. Fixed sudoedit on platforms without a native version of the getprogname() function. Bug #654. Fixed compilation problems with some pre-C99 compilers. Fixed sudo's -C option which was broken in version 1.8.9. It is now possible to match an environment variable's value as well as its name using env_keep and env_check. This can be used to preserve bash functions which would otherwise be removed from the environment. New files created via sudoedit as a non-root user now have the proper group id. Bug #656. Sudoedit now works correctly in conjunction with sudo's SELinux RBAC support. Temporary files are now created with the proper security context. The sudo I/O logging plugin API has been updated. If a logging function returns an error, the command will be terminated and all of the plugin's logging functions will be disabled. If a logging function rejects the command's output it will no longer be displayed to the user's terminal. Fixed a compilation error on systems that lack openpty(), _getpty() and grantpt(). Bug #660. Fixed a hang when a sudoers source is listed more than once in a single sudoers nsswitch.conf entry. On AIX, shell scripts without a #! magic number are now passed to /usr/bin/sh, not /usr/bin/bsh. This is consistent with what the execvp() function on AIX does and matches historic sudo behavior. Bug #661. Fixed a cross-compilation problem building mksiglist and mksigname. Bug #662. Major changes between version 1.8.10p3 and 1.8.10p2: Fixed expansion of the %p escape in the prompt for "sudo -l" when rootpw, runaspw or targetpw is set. Bug #639. Fixed matching of uids and gids which was broken in version 1.8.9. Bug #640. PAM credential initialization has been re-enabled. It was unintentionally disabled by default in version 1.8.8. The way credentials are initialized has also been fixed. Bug #642. Fixed a descriptor leak on Linux when determing boot time. Sudo normally closes extra descriptors before running a command so the impact is limited. Bug #645. Fixed flushing of the last buffer of data when I/O logging is enabled. This bug, introduced in version 1.8.9, could cause incomplete command output on some systems. Bug #646. Major changes between version 1.8.10p2 and 1.8.10p1: Fixed a hang introduced in sudo 1.8.10 when timestamp_timeout is set to zero. Bug #638. Major changes between version 1.8.10p1 and 1.8.10: Fixed a bug introduced in sudo 1.8.10 that prevented the disabling of tty-based tickets. Fixed a bug with netgated commands in "sudo -l command" that could cause the command to be listed even when it was explicitly denied. This only affected list mode when a command was specified. Bug #636. Major changes between version 1.8.10 and 1.8.9p5: It is now possible to disable network interface probing in sudo.conf by changing the value of the probe_interfaces setting. When listing a user's privileges (sudo -l), the sudoers plugin will now prompt for the user's password even if the targetpw, rootpw or runaspw options are set. The sudoers plugin uses a new format for its time stamp files. Each user now has a single file which may contain multiple records when per-tty time stamps are in use (the default). The time stamps use a monotonic timer where available and are once again located in a directory under /var/run. The lecture status is now stored separately from the time stamps in a different directory. Bug #616. sudo's -K option will now remove all of the user's time stamps, not just the time stamp for the current terminal. The -k option can be used to only disable time stamps for the current terminal. If sudo was started in the background and needed to prompt for a password, it was not possible to suspend it at the password prompt. This now works properly. LDAP-based sudoers now uses a default search filter of (objectClass=sudoRole) for more efficient queries. The netgroup query has been modified to avoid falling below the minimum length for OpenLDAP substring indices. The new use_netgroups sudoers option can be used to explicitly enable or disable netgroups support. For LDAP-based sudoers, netgroup support requires an expensive substring match on the server. If netgroups are not needed, this option can be disabled to reduce the load on the LDAP server. Sudo is once again able to open the sudoers file when the group on sudoers doesn't match the expected value, so long as the file is not group writable. Sudo now installs an init.d script to clear the time stamp directory at boot time on AIX and HP-UX systems. These systems either lack /var/run or do not clear it on boot. The JSON format used by visudo -x now properly supports the negation operator. In addition, the Options object is now the same for both Defaults and Cmnd_Specs. Czech and Serbian translations for sudoers from translationproject.org. Catalan translation for sudo from translationproject.org. Major changes between version 1.8.9p5 and 1.8.9p4: Fixed a compilation error on AIX when LDAP support is enabled. Fixed parsing of the "umask" defaults setting in sudoers. Bug #632. Fixed a failed assertion when the "closefrom_override" defaults setting is enabled in sudoers and sudo's -C flag is used. Bug #633. Major changes between version 1.8.9p4 and 1.8.9p3: Fixed a bug where sudo could consume large amounts of CPU while the command was running when I/O logging is not enabled. Bug #631. Fixed a bug where sudo would exit with an error when the debug level is set to util@@debug or all@@debug and I/O logging is not enabled. The command would continue runnning after sudo exited. Major changes between version 1.8.9p3 and 1.8.9p2: Fixed a bug introduced in sudo 1.8.9 that prevented the tty name from being resolved properly on Linux systems. Bug #630. Major changes between version 1.8.9p2 and 1.8.9p1: Updated config.guess, config.sub and libtool to support the ppc64le architecture (IBM PowerPC Little Endian). Major changes between version 1.8.9p1 and 1.8.9: Fixed a problem with gcc 4.8's handling of bit fields that could lead to the noexec flag being enabled even when it was not explicitly set. Major changes between version 1.8.9 and 1.8.8: Reworked sudo's main event loop to use a simple event subsystem using poll(2) or select(2) as the back end. It is now possible to statically compile the sudoers plugin into the sudo binary without disabling shared library support. The sudo.conf file may still be used to configure other plugins. Sudo can now be compiled again with a C preprocessor that does not support variadic macros. Visudo can now export a sudoers file in JSON format using the new -x flag. The locale is now set correctly again for visudo and sudoreplay. The plugin API has been extended to allow the plugin to exclude specific file descriptors from the closefrom range. There is now a workaround for a Solaris-specific problem where NOEXEC was overriding traditional root DAC behavior. Add user netgroup filtering for SSSD. Previously, rules for a netgroup were applied to all even when they did not belong to the specified netgroup. On systems with BSD login classes, if the user specified a group (not a user) to run the command as, it was possible to specify a different login class even when the command was not run as the super user. The closefrom() emulation on Mac OS X now uses /dev/fd if possible. Fixed a bug where sudoedit would not update the original file from the temporary when PAM or I/O logging is not enabled. When recycling I/O logs, the log files are now truncated properly. Fixes bugs #617, #621, #622, #623, #624, #625, #626 Major changes between version 1.8.8 and 1.8.7: Removed a warning on PAM systems with stacked auth modules where the first module on the stack does not succeed. Sudo, sudoreplay and visudo now support GNU-style long options. The -h (--host) option may now be used to specify a host name. This is currently only used by the sudoers plugin in conjunction with the -l (--list) option. Program usage messages and manual SYNOPSIS sections have been simplified. Sudo's LDAP SASL support now works properly with Kerberos. Previously, the SASL library was unable to locate the user's credential cache. It is now possible to set the nproc resource limit to unlimited via pam_limits on Linux (bug #565). New pam_service and pam_login_service sudoers options that can be used to specify the PAM service name to use. New pam_session and pam_setcred sudoers options that can be used to disable PAM session and credential support. The sudoers plugin now properly supports UIDs and GIDs that are larger than 0x7fffffff on 32-bit platforms. Fixed a visudo bug introduced in sudo 1.8.7 where per-group Defaults entries would cause an internal error. If the tty_tickets sudoers option is enabled (the default), but there is no tty present, sudo will now use a ticket file based on the parent process ID. This makes it possible to support the normal timeout behavior for the session. Fixed a problem running commands that change their process group and then attempt to change the terminal settings when not running the command in a pseudo-terminal. Previously, the process would receive SIGTTOU since it was effectively a background process. Sudo will now grant the child the controlling tty and continue it when this happens. The closefrom_override sudoers option may now be used in a command-specified Defaults entry (bug #610). Sudo's BSM audit support now works on Solaris 11. Brazilian Portuguese translation for sudo and sudoers from translationproject.org. Czech translation for sudo from translationproject.org. French translation for sudo from translationproject.org. Sudo's noexec support on Mac OS X 10.4 and above now uses dynamic symbol interposition instead of setting DYLD_FORCE_FLAT_NAMESPACE=1 which causes issues with some programs. Fixed visudo's -q (--quiet) flag, broken in sudo 1.8.6. Root may no longer change its SELinux role without entering a password. Fixed a bug introduced in Sudo 1.8.7 where the indexes written to the I/O log timing file are two greater than they should be. Sudoreplay now contains a work-around to parse those files. In sudoreplay's list mode, the this qualifier in fromdate or todate expressions now behaves more sensibly. Previously, it would often match a date that was "one more" than expected. For example, "this week" now matches the current week instead of the following week. Major changes between version 1.8.7 and 1.8.6p8: The non-Unix group plugin is now supported when sudoers data is stored in LDAP. Sudo now uses a workaround for a locale bug on Solaris 11.0 that prevents setuid programs like sudo from fully using locales. User messages are now always displayed in the user's locale, even when the same message is being logged or mailed in a different locale. Log files created by sudo now explicitly have the group set to group ID 0 rather than relying on BSD group semantics (which may not be the default). A new exec_background sudoers option can be used to initially run the command without read access to the terminal when running a command in a pseudo-tty. If the command tries to read from the terminal it will be stopped by the kernel (via SIGTTIN or SIGTTOU) and sudo will immediately restart it as the forground process (if possible). This allows sudo to only pass terminal input to the program if the program actually is expecting it. Unfortunately, a few poorly-behaved programs (like "su" on most Linux systems) do not handle SIGTTIN and SIGTTOU properly. Sudo now uses an efficient group query to get all the groups for a user instead of iterating over every record in the group database on HP-UX and Solaris. Sudo now produces better error messages when there is an error in the sudo.conf file. Two new settings have been added to sudo.conf to give the admin better control of how group database queries are performed. The group_source specifies how the group list for a user will be determined. Legal values are static (use the kernel groups list), dynamic (perform a group database query) and adaptive (only perform a group database query if the kernel list is full). The max_groups setting specifies the maximum number of groups a user may belong to when performing a group database query. The sudo.conf file now supports line continuation by using a backslash as the last character on the line. There is now a standalone sudo.conf manual page. Sudo now stores its libexec files in a sudo subdirectory instead of in libexec itself. For backwards compatibility, if the plugin is not found in the default plugin directory, sudo will check the parent directory if the default directory ends in /sudo. The sudoers I/O logging plugin now logs the terminal size. A new sudoers option maxseq can be used to limit the number of I/O log entries that are stored. The system_group and group_file sudoers group provider plugins are now installed by default. The list output (sudo -l) output from the sudoers plugin is now less ambiguous when an entry includes different runas users. The long list output (sudo -ll) for file-based sudoers is now more consistent with the format of LDAP-based sudoers. A uid may now be used in the sudoRunAsUser attributes for LDAP sudoers. Minor plugin API change: the close and version functions are now optional. If the policy plugin does not provide a close function and the command is not being run in a new pseudo-tty, sudo may now execute the command directly instead of in a child process. A new sudoers option pam_session can be used to disable sudo's PAM session support. On HP-UX systems, sudo will now use the pstat() function to determine the tty instead of ttyname(). Turkish translation for sudo and sudoers from translationproject.org. Dutch translation for sudo and sudoers from translationproject.org. Tivoli Directory Server client libraries may now be used with HP-UX where libibmldap has a hidden dependency on libCsup. The sudoers plugin will now ignore invalid domain names when checking netgroup membership. Most Linux systems use the string "(none)" for the NIS-style domain name instead of an empty string. New support for specifying a SHA-2 digest along with the command in sudoers. Supported hash types are sha224, sha256, sha384 and sha512. See the description of Digest_Spec in the sudoers manual or the description of sudoCommand in the sudoers.ldap manual for details. The paths to ldap.conf and ldap.secret may now be specified as arguments to the sudoers plugin in the sudo.conf file. Fixed potential false positives in visudo's alias cycle detection. Fixed a problem where the time stamp file was being treated as out of date on Linux systems where the change time on the pseudo-tty device node can change after it is allocated. Sudo now only builds Position Independent Executables (PIE) by default on Linux systems and verifies that a trivial test program builds and runs. On Solaris 11.1 and higher, sudo binaries will now have the ASLR tag enabled if supported by the linker. Major changes between version 1.8.6p8 and 1.8.6p7: Terminal detection now works properly on 64-bit AIX kernels. This was broken by the removal of the ttyname() fallback in Sudo 1.8.6p6. Sudo is now able to map an AIX 64-bit device number to the corresponding device file in /dev. Sudo now checks for crypt() returning NULL when performing passwd-based authentication. Major changes between version 1.8.6p7 and 1.8.6p6: A time stamp file with the date set to the epoch by sudo -k is now completely ignored regardless of what the local clock is set to. Previously, if the local clock was set to a value between the epoch and the time stamp timeout value, a time stamp reset by sudo -k would be considered current. This is a potential security issue. The tty-specific time stamp file now includes the session ID of the sudo process that created it. If a process with the same tty but a different session ID runs sudo, the user will now be prompted for a password (assuming authentication is required for the command). This is a potential security issue. Major changes between version 1.8.6p6 and 1.8.6p5: On systems where the controlling tty can be determined via /proc or sysctl(), sudo will no longer fall back to using ttyname() if the process has no controlling tty. This prevents sudo from using a non-controlling tty for logging and time stamp purposes. This is a potential security issue. Major changes between version 1.8.6p5 and 1.8.6p4: Fixed a potential crash in visudo's alias cycle detection. Improved performance on Solaris when retrieving the group list for the target user. On systems with a large number of groups where the group database is not local (NIS, LDAP, AD), fetching the group list could take a minute or more. Major changes between version 1.8.6p4 and 1.8.6p3: The -fstack-protector is now used when linking visudo, sudoreplay and testsudoers. Avoid building PIE binaries on FreeBSD/ia64 as they don't run properly. Fixed a crash in visudo strict mode when an unknown Defaults setting is encountered. Do not inform the user that the command was not permitted by the policy if they do not successfully authenticate. This is a regression introduced in sudo 1.8.6. Allow sudo to be build with sss support without also including ldap support. Fix running commands that need the terminal in the background when I/O logging is enabled. E.g. sudo vi &. When the command is foregrounded, it will now resume properly. Major changes between version 1.8.6p3 and 1.8.6p2: Fixed post-processing of the man pages on systems with legacy versions of sed. Fixed sudoreplay -l on Linux systems with file systems that set DT_UNKNOWN in the d_type field of struct dirent. Major changes between version 1.8.6p2 and 1.8.6p1: Fixed suspending a command after it has already been resumed once when I/O logging (or use_pty) is not enabled. This was a regression introduced in version 1.8.6. Major changes between version 1.8.6p1 and 1.8.6: Fixed the setting of LOGNAME, USER and USERNAME variables in the command's environment when env_reset is enabled (the default). This was a regression introduced in version 1.8.6. Sudo now honors SUCCESS=return in /etc/nsswitch.conf. Major changes between version 1.8.6 and 1.8.5p3: Sudo is now built with the -fstack-protector flag if the the compiler supports it. Also, the -zrelro linker flag is used if supported. The --disable-hardening configure option can be used to build sudo without stack smashing protection. Sudo is now built as a Position Independent Executable (PIE) if supported by the compiler and linker. If the user is a member of the exempt group in sudoers, they will no longer be prompted for a password even if the -k flag is specified with the command. This makes sudo -k command consistent with the behavior one would get if the user ran sudo -k immediately before running the command. The sudoers file may now be a symbolic link. Previously, sudo would refuse to read sudoers unless it was a regular file. The sudoreplay command can now properly replay sessions where no tty was present. The sudoers plugin now takes advantage of symbol visibility controls when supported by the compiler or linker. As a result, only a small number of symbols are exported which significantly reduces the chances of a conflict with other shared objects. Improved support for the Tivoli Directory Server LDAP client libraries. This includes support for using LDAP over SSL (ldaps) as well as support for the BIND_TIMELIMIT, TLS_KEY and TLS_CIPHERS ldap.conf options. A new ldap.conf option, TLS_KEYPW can be used to specify a password to decrypt the key database. When constructing a time filter for use with LDAP sudoNotBefore and sudoNotAfter attributes, the current time now includes tenths of a second. This fixes a problem with timed entries on Active Directory. If a user fails to authenticate and the command would be rejected by sudoers, it is now logged with command not allowed instead of N incorrect password attempts. Likewise, the mail_no_perms sudoers option now takes precedence over mail_badpass The sudo manuals are now formatted using the mdoc macros. Versions using the legacy man macros are provided for systems that lack mdoc. New support for Solaris privilege sets. This makes it possible to specify fine-grained privileges in the sudoers file on Solaris 10 and above. A Runas_Spec that contains no Runas_Lists can be used to give a user the ability to run a command as themselves but with an expanded privilege set. Fixed a problem with the reboot and shutdown commands on some systems (such as HP-UX and BSD). On these systems, reboot sends all processes (except itself) SIGTERM. When sudo received SIGTERM, it would relay it to the reboot process, thus killing reboot before it had a chance to actually reboot the system. Support for using the System Security Services Daemon (SSSD) as a source of sudoers data. Slovenian translation for sudo and sudoers from translationproject.org. Visudo will now warn about unknown Defaults entries that are per-host, per-user, per-runas or per-command. Fixed a race condition that could cause sudo to receive SIGTTOU (and stop) when resuming a shell that was run via sudo when I/O logging (and use_pty) is not enabled. Sending SIGTSTP directly to the sudo process will now suspend the running command when I/O logging (and use_pty) is not enabled. Major changes between version 1.8.5p3 and 1.8.5p2: Fixed the loading of I/O plugins that conform to a plugin API version older than 1.2. Major changes between version 1.8.5p2 and 1.8.5p1: Fixed use of the SUDO_ASKPASS environment variable which was broken in Sudo 1.8.5. Fixed a problem reading the sudoers file when the file mode is more restrictive than the expected mode. For example, when the expected sudoers file mode is 0440 but the actual mode is 0400. Major changes between version 1.8.5p1 and 1.8.5: Fixed a bug that prevented files in an include directory from being evaluated. Major changes between version 1.8.5 and 1.8.4p5: When "noexec" is enabled, sudo_noexec.so will now be prepended to any existing LD_PRELOAD variable instead of replacing it. The sudo_noexec.so shared library now wraps the execvpe(), exect(), posix_spawn() and posix_spawnp() functions. The user/group/mode checks on sudoers files have been relaxed. As long as the file is owned by the sudoers uid, not world-writable and not writable by a group other than the sudoers gid, the file is considered OK. Note that visudo will still set the mode to the value specified at configure time. It is now possible to specify the sudoers path, uid, gid and file mode as options to the plugin in the sudo.conf file. Croatian, Galician, German, Lithuanian, Swedish and Vietnamese translations from translationproject.org. /etc/environment is no longer read directly on Linux systems when PAM is used. Sudo now merges the PAM environment into the user's environment which is typically set by the pam_env module. The initial evironment created when env_reset is in effect now includes the contents of /etc/environment on AIX systems and the "setenv" and "path" entries from /etc/login.conf on BSD systems. The plugin API has been extended in three ways. First, options specified in sudo.conf after the plugin pathname are passed to the plugin's open function. Second, sudo has limited support for hooks that can be used by plugins. Currently, the hooks are limited to environment handling functions. Third, the init_session policy plugin function is passed a pointer to the user environment which can be updated during session setup. The plugin API version has been incremented to version 1.2. See the sudo_plugin manual for more information. The policy plugin's init_session function is now called by the parent sudo process, not the child process that executes the command. This allows the PAM session to be open and closed in the same process, which some PAM modules require. Fixed parsing of "Path askpass" and "Path noexec" in sudo.conf, which was broken in version 1.8.4. On systems with an SVR4-style /proc file system, the /proc/pid/psinfo file is now uses to determine the controlling terminal, if possible. This allows tty-based tickets to work properly even when, e.g. standard input, output and error are redirected to /dev/null. The output of "sudoreplay -l" is now sorted by file name (or sequence number). Previously, entries were displayed in the order in which they were found on the file system. Sudo now behaves properly when I/O logging is enabled and the controlling terminal is revoked (e.g. the running sshd is killed). Previously, sudo may have exited without calling the I/O plugin's close function which can lead to an incomplete I/O log. Sudo can now detect when a user has logged out and back in again on Solaris 11, just like it can on Solaris 10. The built-in zlib included with Sudo has been upgraded to version 1.2.6. Setting the SSL parameter to start_tls in ldap.conf now works properly when using Mozilla-based SDKs that support the ldap_start_tls_s() function. The TLS_CHECKPEER parameter in ldap.conf now works when the Mozilla NSS crypto backend is used with OpenLDAP. A new group provider plugin, system_group, is included which performs group look ups by name using the system groups database. This can be used to restore the pre-1.7.3 sudo group lookup behavior. Major changes between version 1.8.4p5 and 1.8.4p4: Fixed a potential security issue in the matching of hosts against an IPv4 network specified in sudoers. The flaw may allow a user who is authorized to run commands on hosts belonging to one IPv4 network to run commands on a different host. Major changes between version 1.8.4p4 and 1.8.4p3: Fixed a bug introduced in Sudo 1.8.4 which prevented sudo -v from working. Major changes between version 1.8.4p3 and 1.8.4p2: Fixed a crash on FreeBSD when there is no tty present. When visudo is run with the -c (check) option, the sudoers file(s) owner and mode are now also checked unless the -f option was specified. Major changes between version 1.8.4p2 and 1.8.4p1: Fixed a bug introduced in Sudo 1.8.4 where insufficient space was allocated for group IDs in the LDAP filter. Fixed a bug introduced in Sudo 1.8.4 where the path to sudo.conf was /sudo.conf instead of etc/sudo.conf. Fixed a bug introduced in Sudo 1.8.4 which could cause a hang when I/O logging is enabled and input is from a pipe or file. Major changes between version 1.8.4p1 and 1.8.4: Fixed a bug introduced in sudo 1.8.4 that broke adding to or deleting from the env_keep, env_check and env_delete lists in sudoers on some platforms. Major changes between version 1.8.4 and 1.8.3p2: The -D flag in sudo has been replaced with a more general debugging framework that is configured in sudo.conf. Fixed a false positive in visudo strict mode when aliases are in use. Fixed a crash with sudo -i when a runas group was specified without a runas user. The line on which a syntax error is reported in the sudoers file is now more accurate. Previously it was often off by a line. Fixed a bug where stack garbage could be printed at the end of the lecture when the lecture_file option was enabled. make install now honors the LINGUAS environment variable. The #include and #includedir directives in sudoers now support relative paths. If the path is not fully qualified it is expected to be located in the same directory of the sudoers file that is including it. New Serbian and Spanish translations for sudo from translationproject.org. LDAP-based sudoers may now access by group ID in addition to group name. visudo will now fix the mode on the sudoers file even if no changes are made unless the -f option is specified. The use_loginclass sudoers option works properly again. On systems that use login.conf, sudo -i now sets environment variables based on login.conf. For LDAP-based sudoers, values in the search expression are now escaped as per RFC 4515. The plugin close function is now properly called when a login session is killed (as opposed to the actual command being killed). This can happen when an ssh session is disconnected or the terminal window is closed. The deprecated "noexec_file" sudoers option is no longer supported. Fixed a race condition when I/O logging is not enabled that could result in tty-generated signals (e.g. control-C) being received by the command twice. If none of the standard input, output or error are connected to a tty device, sudo will now check its parent's standard input, output or error for the tty name on systems with /proc and BSD systems that support the KERN_PROC_PID sysctl. This allows tty-based tickets to work properly even when, e.g. standard input, output and error are redirected to /dev/null. Added the --enable-kerb5-instance configure option to allow people using Kerberos V authentication to specify a custom instance so the principal name can be, e.g. "username/sudo" similar to how ksu uses "username/root". Fixed a bug where a pattern like /usr/* included /usr/bin/ in the results, which would be incorrectly be interpreted as if the sudoers file had specified a directory. visudo -c will now list any include files that were checked in addition to the main sudoers file when everything parses OK. Users that only have read-only access to the sudoers file may now run visudo -c. Previously, write permissions were required even though no writing is down in check-only mode. It is now possible to prevent the disabling of core dumps from within sudo itself by adding a line to the sudo.conf file like Set disable_coredump false. Major changes between version 1.8.3p2 and 1.8.3p1: Fixed a format string vulnerability when the sudo binary (or a symbolic link to the sudo binary) contains printf format escapes and the -D (debugging) flag is used. Major changes between version 1.8.3p1 and 1.8.3: Fixed a crash in the monitor process on Solaris when NOPASSWD was specified or when authentication was disabled. Fixed matching of a Runas_Alias in the group section of a Runas_Spec. Major changes between version 1.8.3 and 1.8.2: Fixed expansion of strftime() escape sequences in the log_dir sudoers setting. Esperanto, Italian and Japanese translations from translationproject.org. Sudo will now use PAM by default on AIX 6 and higher. Added --enable-werror configure option for gcc's -Werror flag. Visudo no longer assumes all editors support the +linenumber command line argument. It now uses a whitelist of editors known to support the option. Fixed matching of network addresses when a netmask is specified but the address is not the first one in the CIDR block. The configure script now check whether or not errno.h declares the errno variable. Previously, sudo would always declare errno itself for older systems that don't declare it in errno.h. The NOPASSWD tag is now honored for denied commands too, which matches historic sudo behavior (prior to sudo 1.7.0). Sudo now honors the DEREF setting in ldap.conf which controls how alias dereferencing is done during an LDAP search. A symbol conflict with the pam_ssh_agent_auth PAM module that would cause a crash been resolved. The inability to load a group provider plugin is no longer a fatal error. A potential crash in the utmp handling code has been fixed. Two PAM session issues have been resolved. In previous versions of sudo, the PAM session was opened as one user and closed as another. Additionally, if no authentication was performed, the PAM session would never be closed. Sudo will now work correctly with LDAP-based sudoers using TLS or SSL on Debian systems. The LOGNAME, USER and USERNAME environment variables are preserved correctly again in sudoedit mode. Major changes between version 1.8.2 and 1.8.1p2: Sudo, visudo, sudoreplay and the sudoers plug-in now have natural language support (NLS). Sudo will use gettext(), if available, to display translated messages. This can be disabled by passing configure the --disable-nls option. All translations are coordinated via The Translation Project, translationproject.org. Sudo 1.8.2 includes translations for Basque, Chinese (simplified), Danish, Finish, Polish, Russian and Ukranian. Plug-ins are now loaded with the RTLD_GLOBAL flag instead of RTLD_LOCAL. This fixes missing symbol problems in PAM modules on certain platforms, such as FreeBSD and SuSE Linux Enterprise. I/O logging is now supported for commands run in background mode (using sudo's -b flag). Group ownership of the sudoers file is now only enforced when the file mode on sudoers allows group readability or writability. Visudo now checks the contents of an alias and warns about cycles when the alias is expanded. If the user specifes a group via sudo's -g option that matches the target user's group in the password database, it is now allowed even if no groups are present in the Runas_Spec. The sudo Makefiles now have more complete dependencies which are automatically generated instead of being maintained manually. The use_pty sudoers option is now correctly passed back to the sudo front end. This was missing in previous versions of sudo 1.8 which prevented use_pty from being honored. sudo -i command now works correctly with the bash version 2.0 and higher. Previously, the .bash_profile would not be sourced prior to running the command unless bash was built with NON_INTERACTIVE_LOGIN_SHELLS defined. When matching groups in the sudoers file, sudo will now match based on the name of the group instead of the group ID. This can substantially reduce the number of group lookups for sudoers files that contain a large number of groups. Multi-factor authentication is now supported on AIX. Added support for non-RFC 4517 compliant LDAP servers that require that seconds be present in a timestamp, such as Tivoli Directory Server. If the group vector is to be preserved, the PATH search for the command is now done with the user's original group vector. For LDAP-based sudoers, the runas_default sudoOption now works properly in a sudoRole that contains a sudoCommand. Spaces in command line arguments for sudo -s and sudo -i are now escaped with a backslash when checking the security policy. Major changes between version 1.8.1p2 and 1.8.1p1: Two-character CIDR-style IPv4 netmasks are now matched correctly in the sudoers file. A build error with MIT Kerberos V has been resolved. A crash on HP-UX in the sudoers plugin when wildcards are present in the sudoers file has been resolved. Sudo now works correctly on Tru64 Unix again. Major changes between version 1.8.1p1 and 1.8.1: Fixed a problem on AIX where sudo was unable to set the final uid if the PAM module modified the effective uid. A non-existent includedir is now treated the same as an empty directory and not reported as an error. Removed extraneous parens in LDAP filter when sudoers_search_filter is enabled that can cause an LDAP search error. Fixed a make -j problem for make install Major changes between version 1.8.1 and 1.8.0: A new LDAP setting, sudoers_search_filter, has been added to ldap.conf. This setting can be used to restrict the set of records returned by the LDAP query. Based on changes from Matthew Thomas. White space is now permitted within a User_List when used in conjunction with a per-user Defaults definition. A group ID (%#gid) may now be specified in a User_List or Runas_List. Likewise, for non-Unix groups the syntax is %:#gid. Support for double-quoted words in the sudoers file has been fixed. The change in 1.7.5 for escaping the double quote character caused the double quoting to only be available at the beginning of an entry. The fix for resuming a suspended shell in 1.7.5 caused problems with resuming non-shells on Linux. Sudo will now save the process group ID of the program it is running on suspend and restore it when resuming, which fixes both problems. A bug that could result in corrupted output in "sudo -l" has been fixed. Sudo will now create an entry in the utmp (or utmpx) file when allocating a pseudo-tty (e.g. when logging I/O). The "set_utmp" and "utmp_runas" sudoers file options can be used to control this. Other policy plugins may use the "set_utmp" and "utmp_user" entries in the command_info list. The sudoers policy now stores the TSID field in the logs even when the "iolog_file" sudoers option is defined to a value other than %{sessid}. Previously, the TSID field was only included in the log file when the "iolog_file" option was set to its default value. The sudoreplay utility now supports arbitrary session IDs. Previously, it would only work with the base-36 session IDs that the sudoers plugin uses by default. Sudo now passes "run_shell=true" to the policy plugin in the settings list when sudo's -s command line option is specified. The sudoers policy plugin uses this to implement the "set_home" sudoers option which was missing from sudo 1.8.0. The "noexec" functionality has been moved out of the sudoers policy plugin and into the sudo front-end, which matches the behavior documented in the plugin writer's guide. As a result, the path to the noexec file is now specified in the sudo.conf file instead of the sudoers file. On Solaris 10, the PRIV_PROC_EXEC privilege is now used to implement the "noexec" feature. Previously, this was implemented via the LD_PRELOAD environment variable. The exit values for "sudo -l", "sudo -v" and "sudo -l command" have been fixed in the sudoers policy plugin. The sudoers policy plugin now passes the login class, if any, back to the sudo front-end. The sudoers policy plugin was not being linked with requisite libraries in certain configurations. Sudo now parses command line arguments before loading any plugins. This allows "sudo -V" or "sudo -h" to work even if there is a problem with sudo.conf Plugins are now linked with the static version of libgcc to allow the plugin to run on a system where no shared libgcc is installed, or where it is installed in a different location. Major changes between version 1.8.0 and 1.7.5: Sudo has been refactored to use a modular framework that can support third-party policy and I/O logging plugins. The default plugin is "sudoers" which provides the traditional sudo functionality. See the sudo_plugin manual for details on the plugin API and the sample in the plugins directory for a simple example. @ text @d1 1 a1 1 @@comment $NetBSD$ d5 1 a5 7 include/sudo_plugin.h lib/sudo/group_file.la lib/sudo/libsudo_util.la ${PLIST.noexec}lib/sudo/sudo_noexec.la lib/sudo/sudoers.la lib/sudo/system_group.la man/man5/sudo.conf.5 a8 1 man/man8/sudo_plugin.8 a12 1 share/doc/sudo/CONTRIBUTORS d21 3 a27 2 share/examples/sudo/pam.conf share/examples/sudo/sudo.conf a28 1 share/examples/sudo/syslog.conf @ 1.7.12.2 log @Pullup ticket #4905 - requested by taca security/sudo: build fix Revisions pulled up: - security/sudo/Makefile 1.148-1.149 - security/sudo/PLIST 1.9 - security/sudo/distinfo 1.85-1.86 - security/sudo/options.mk 1.19 - security/sudo/patches/patch-aa 1.32 --- Module Name: pkgsrc Committed By: adam Date: Tue Jan 5 17:05:00 UTC 2016 Modified Files: pkgsrc/security/sudo: Makefile distinfo Log Message: Fix building on OS X; cosmetic changes; fix distinfo --- Module Name: pkgsrc Committed By: adam Date: Sat Jan 9 11:22:12 UTC 2016 Modified Files: pkgsrc/security/sudo: Makefile PLIST distinfo options.mk pkgsrc/security/sudo/patches: patch-aa Log Message: Add nls as an option, but also fix builds where system gettext gets detected and used. @ text @a36 53 ${PLIST.nls}share/locale/ca/LC_MESSAGES/sudo.mo ${PLIST.nls}share/locale/ca/LC_MESSAGES/sudoers.mo ${PLIST.nls}share/locale/cs/LC_MESSAGES/sudo.mo ${PLIST.nls}share/locale/cs/LC_MESSAGES/sudoers.mo ${PLIST.nls}share/locale/da/LC_MESSAGES/sudo.mo ${PLIST.nls}share/locale/da/LC_MESSAGES/sudoers.mo ${PLIST.nls}share/locale/de/LC_MESSAGES/sudo.mo ${PLIST.nls}share/locale/de/LC_MESSAGES/sudoers.mo ${PLIST.nls}share/locale/el/LC_MESSAGES/sudoers.mo ${PLIST.nls}share/locale/eo/LC_MESSAGES/sudo.mo ${PLIST.nls}share/locale/eo/LC_MESSAGES/sudoers.mo ${PLIST.nls}share/locale/es/LC_MESSAGES/sudo.mo ${PLIST.nls}share/locale/eu/LC_MESSAGES/sudo.mo ${PLIST.nls}share/locale/eu/LC_MESSAGES/sudoers.mo ${PLIST.nls}share/locale/fi/LC_MESSAGES/sudo.mo ${PLIST.nls}share/locale/fi/LC_MESSAGES/sudoers.mo ${PLIST.nls}share/locale/fr/LC_MESSAGES/sudo.mo ${PLIST.nls}share/locale/fr/LC_MESSAGES/sudoers.mo ${PLIST.nls}share/locale/gl/LC_MESSAGES/sudo.mo ${PLIST.nls}share/locale/hr/LC_MESSAGES/sudo.mo ${PLIST.nls}share/locale/hr/LC_MESSAGES/sudoers.mo ${PLIST.nls}share/locale/hu/LC_MESSAGES/sudoers.mo ${PLIST.nls}share/locale/it/LC_MESSAGES/sudo.mo ${PLIST.nls}share/locale/it/LC_MESSAGES/sudoers.mo ${PLIST.nls}share/locale/ja/LC_MESSAGES/sudo.mo ${PLIST.nls}share/locale/ja/LC_MESSAGES/sudoers.mo ${PLIST.nls}share/locale/lt/LC_MESSAGES/sudoers.mo ${PLIST.nls}share/locale/nb/LC_MESSAGES/sudo.mo ${PLIST.nls}share/locale/nb/LC_MESSAGES/sudoers.mo ${PLIST.nls}share/locale/nl/LC_MESSAGES/sudo.mo ${PLIST.nls}share/locale/nl/LC_MESSAGES/sudoers.mo ${PLIST.nls}share/locale/pl/LC_MESSAGES/sudo.mo ${PLIST.nls}share/locale/pl/LC_MESSAGES/sudoers.mo ${PLIST.nls}share/locale/pt_BR/LC_MESSAGES/sudo.mo ${PLIST.nls}share/locale/pt_BR/LC_MESSAGES/sudoers.mo ${PLIST.nls}share/locale/ru/LC_MESSAGES/sudo.mo ${PLIST.nls}share/locale/ru/LC_MESSAGES/sudoers.mo ${PLIST.nls}share/locale/sk/LC_MESSAGES/sudo.mo ${PLIST.nls}share/locale/sk/LC_MESSAGES/sudoers.mo ${PLIST.nls}share/locale/sl/LC_MESSAGES/sudo.mo ${PLIST.nls}share/locale/sl/LC_MESSAGES/sudoers.mo ${PLIST.nls}share/locale/sr/LC_MESSAGES/sudo.mo ${PLIST.nls}share/locale/sr/LC_MESSAGES/sudoers.mo ${PLIST.nls}share/locale/sv/LC_MESSAGES/sudo.mo ${PLIST.nls}share/locale/sv/LC_MESSAGES/sudoers.mo ${PLIST.nls}share/locale/tr/LC_MESSAGES/sudo.mo ${PLIST.nls}share/locale/tr/LC_MESSAGES/sudoers.mo ${PLIST.nls}share/locale/uk/LC_MESSAGES/sudo.mo ${PLIST.nls}share/locale/uk/LC_MESSAGES/sudoers.mo ${PLIST.nls}share/locale/vi/LC_MESSAGES/sudo.mo ${PLIST.nls}share/locale/vi/LC_MESSAGES/sudoers.mo ${PLIST.nls}share/locale/zh_CN/LC_MESSAGES/sudo.mo ${PLIST.nls}share/locale/zh_CN/LC_MESSAGES/sudoers.mo @ 1.6 log @* Fix PLIST when "ldap" is enabled in PKG_OPTIONS. * Install README.LDAP when "ldap" is enabled in PKG_OPTIONS. * Fix build problem when "kerberos" is enabled in PKG_OPTIONS. Bump PKGREVISION since default PLIST has changed. @ text @d1 1 a1 1 @@comment $NetBSD: PLIST,v 1.5 2010/09/10 17:11:27 spz Exp $ d5 1 a5 1 libexec/sudo_noexec.so @ 1.5 log @updating to the latest and greatest (and less a bunch of security relevant bugs) version: Major changes between version 1.7.4p3 and 1.7.4p4: * A potential security issue has been fixed with respect to the handling of sudo's -g command line option when -u is also specified. The flaw may allow an attacker to run commands as a user that is not authorized by the sudoers file. * A bug has been fixed where "sudo -l" output was incomplete if multiple sudoers sources were defined in nsswitch.conf and there was an error querying one of the sources. * The log_input, log_output, and use_pty sudoers options now work correctly on AIX. Previously, sudo would hang if they were enabled. * Fixed "make install" when sudo is built in a directory other than the directory that holds the sources. * The runas_default sudoers setting now works properly in a per-command Defaults line. * Suspending and resuming the bash shell when PAM is in use now works properly. The SIGCONT signal was not being propagated to the child process. Major changes between version 1.7.4p2 and 1.7.4p3: * A bug has been fixed where duplicate HOME environment variables could be set when the env_reset setting was disabled and the always_set_home setting was enabled in sudoers. * The value of sysconfdir is now substituted into the path to the sudoers.d directory in the installed sudoers file. * Fixed compilation problems on Irix and other platforms. * If multiple PAM "auth" actions are specified and the user enters ^C at the password prompt, sudo will now abort any subsequent "auth" actions. Previously it was necessary to enter ^C once for each "auth" action. Major changes between version 1.7.4p1 and 1.7.4p2: * Fixed a bug where sudo could spin in a cpu loop waiting for the child process. * Packaging fixes for sudo.pp to better handle patchlevels. Major changes between version 1.7.4 and 1.7.4p1: * Fix a bug introduced in sudo 1.7.3 that prevented the -k and -K options from functioning when the tty_tickets sudoers option was enabled. * Sudo no longer prints a warning when the -k or -K options are specified and the ticket file does not exist. * Changes to the configure script to enable cross-compilation of Sudo. Major changes between version 1.7.3 and 1.7.4: * Sudoedit will now preserve the file extension in the name of the temporary file being edited. The extension is used by some editors (such as emacs) to choose the editing mode. * Time stamp files have moved from /var/run/sudo to either /var/db/sudo, /var/lib/sudo or /var/adm/sudo. The directories are checked for existence in that order. This prevents users from receiving the sudo lecture every time the system reboots. Time stamp files older than the boot time are ignored on systems where it is possible to determine this. * Ancillary documentation (README files, LICENSE, etc) is now installed in a sudo documentation directory. * Sudo now recognizes "tls_cacert" as an alias for "tls_cacertfile" in ldap.conf. * Defaults settings that are tied to a user, host or command may now include the negation operator. For example: Defaults:!millert lecture will match any user but millert. * The default PATH environment variable, used when no PATH variable exists, now includes /usr/sbin and /sbin. * Sudo now uses polypkg for cross-platform packing. * On Linux, sudo will now restore the nproc resource limit before executing a command, unless the limit appears to have been modified by pam_limits. This avoids a problem with bash scripts that open more than 32 descriptors on SuSE Linux, where sysconf(_SC_CHILD_MAX) will return -1 when RLIMIT_NPROC is set to RLIMIT_UNLIMITED (-1). * Visudo will now treat an unrecognized Defaults entry as a parse error (sudo will warn but still run). * The HOME and MAIL environment variables are now reset based on the target user's password database entry when the env_reset sudoers option is enabled (which is the case in the default configuration). Users wishing to preserve the original values should use a sudoers entry like: Defaults env_keep += HOME to preserve the old value of HOME and Defaults env_keep += MAIL to preserve the old value of MAIL. * The tty_tickets option is now on by default. * Fixed a problem in the restoration of the AIX authdb registry setting. * If PAM is in use, wait until the process has finished before closing the PAM session. * Fixed "sudo -i -u user" where user has no shell listed in the password database. * When logging I/O, sudo now handles pty read/write returning ENXIO, as seen on FreeBSD when the login session has been killed. * Sudo now performs I/O logging in the C locale. This avoids locale-related issues when parsing floating point numbers in the timing file. * Added support for Ubuntu-style admin flag dot files. Major changes between version 1.7.2p8 and 1.7.3: * Support for logging a command's input and output as well as the ability to replay sessions. For more information, see the documentation for the log_input and log_output Defaults options in the sudoers manual. Also see the sudoreplay manual for information on replaying I/O log sessions. * The use_pty sudoers option can be used to force a command to be run in a pseudo-pty, even when I/O logging is not enabled. * On some systems, sudo can now detect when a user has logged out and back in again when tty-based time stamps are in use. Supported systems include Solaris systems with the devices file system, Mac OS X, and Linux systems with the devpts filesystem (pseudo-ttys only). * On AIX systems, the registry setting in /etc/security/user is now taken into account when looking up users and groups. Sudo now applies the correct the user and group ids when running a command as a user whose account details come from a different source (e.g. LDAP or DCE vs. local files). * Support for multiple sudoers_base and uri entries in ldap.conf. When multiple entries are listed, sudo will try each one in the order in which they are specified. * Sudo's SELinux support should now function correctly when running commands as a non-root user and when one of stdin, stdout or stderr is not a terminal. * Sudo will now use the Linux audit system with configure with the --with-linux-audit flag. * Sudo now uses mbr_check_membership() on systems that support it to determine group membership. Currently, only Darwin (Mac OS X) supports this. * When the tty_tickets sudoers option is enabled but there is no terminal device, sudo will no longer use or create a tty-based ticket file. Previously, sudo would use a tty name of "unknown". As a consequence, if a user has no terminal device, sudo will now always prompt for a password. * The passwd_timeout and timestamp_timeout options may now be specified as floating point numbers for more granular timeout values. * Negating the fqdn option in sudoers now works correctly when sudo is configured with the --with-fqdn option. In previous versions of sudo the fqdn was set before sudoers was parsed. @ text @d1 1 a1 1 @@comment $NetBSD$ d18 1 a18 1 share/doc/sudo/README.LDAP d24 4 @ 1.4 log @Remove @@dirrm entries from PLISTs @ text @d1 1 a1 1 @@comment $NetBSD: PLIST,v 1.3 2009/02/05 13:48:12 taca Exp $ d4 1 d10 1 d13 4 d19 1 d21 3 @ 1.4.10.1 log @Pullup ticket #3220 - requested by spz security/sudo: security update Revisions pulled up: - security/sudo/Makefile 1.122-1.123 - security/sudo/PLIST 1.5 - security/sudo/distinfo 1.64-1.65 - security/sudo/patches/patch-aa 1.24 - security/sudo/patches/patch-af 1.24-1.25 - security/sudo/patches/patch-ag 1.15-1.16 --- Module Name: pkgsrc Committed By: taca Date: Mon Jul 5 03:08:10 UTC 2010 Modified Files: pkgsrc/security/sudo: Makefile distinfo pkgsrc/security/sudo/patches: patch-af patch-ag Log Message: Update sudo package to 1.7.2p8. Major changes between sudo 1.7.2p7 and 1.7.2p8: * Fixed a crash on AIX when LDAP support is in use. * Fixed problems with the QAS non-Unix group support --- Module Name: pkgsrc Committed By: spz Date: Fri Sep 10 17:11:27 UTC 2010 Modified Files: pkgsrc/security/sudo: Makefile PLIST distinfo pkgsrc/security/sudo/patches: patch-aa patch-af patch-ag Log Message: updating to the latest and greatest (and less a bunch of security relevant bugs) version: Major changes between version 1.7.4p3 and 1.7.4p4: * A potential security issue has been fixed with respect to the handling of sudo's -g command line option when -u is also specified. The flaw may allow an attacker to run commands as a user that is not authorized by the sudoers file. * A bug has been fixed where "sudo -l" output was incomplete if multiple sudoers sources were defined in nsswitch.conf and there was an error querying one of the sources. * The log_input, log_output, and use_pty sudoers options now work correctly on AIX. Previously, sudo would hang if they were enabled. * Fixed "make install" when sudo is built in a directory other than the directory that holds the sources. * The runas_default sudoers setting now works properly in a per-command Defaults line. * Suspending and resuming the bash shell when PAM is in use now works properly. The SIGCONT signal was not being propagated to the child process. Major changes between version 1.7.4p2 and 1.7.4p3: * A bug has been fixed where duplicate HOME environment variables could be set when the env_reset setting was disabled and the always_set_home setting was enabled in sudoers. * The value of sysconfdir is now substituted into the path to the sudoers.d directory in the installed sudoers file. * Fixed compilation problems on Irix and other platforms. * If multiple PAM "auth" actions are specified and the user enters ^C at the password prompt, sudo will now abort any subsequent "auth" actions. Previously it was necessary to enter ^C once for each "auth" action. Major changes between version 1.7.4p1 and 1.7.4p2: * Fixed a bug where sudo could spin in a cpu loop waiting for the child process. * Packaging fixes for sudo.pp to better handle patchlevels. Major changes between version 1.7.4 and 1.7.4p1: * Fix a bug introduced in sudo 1.7.3 that prevented the -k and -K options from functioning when the tty_tickets sudoers option was enabled. * Sudo no longer prints a warning when the -k or -K options are specified and the ticket file does not exist. * Changes to the configure script to enable cross-compilation of Sudo. Major changes between version 1.7.3 and 1.7.4: * Sudoedit will now preserve the file extension in the name of the temporary file being edited. The extension is used by some editors (such as emacs) to choose the editing mode. * Time stamp files have moved from /var/run/sudo to either /var/db/sudo, /var/lib/sudo or /var/adm/sudo. The directories are checked for existence in that order. This prevents users from receiving the sudo lecture every time the system reboots. Time stamp files older than the boot time are ignored on systems where it is possible to determine this. * Ancillary documentation (README files, LICENSE, etc) is now installed in a sudo documentation directory. * Sudo now recognizes "tls_cacert" as an alias for "tls_cacertfile" in ldap.conf. * Defaults settings that are tied to a user, host or command may now include the negation operator. For example: Defaults:!millert lecture will match any user but millert. * The default PATH environment variable, used when no PATH variable exists, now includes /usr/sbin and /sbin. * Sudo now uses polypkg for cross-platform packing. * On Linux, sudo will now restore the nproc resource limit before executing a command, unless the limit appears to have been modified by pam_limits. This avoids a problem with bash scripts that open more than 32 descriptors on SuSE Linux, where sysconf(_SC_CHILD_MAX) will return -1 when RLIMIT_NPROC is set to RLIMIT_UNLIMITED (-1). * Visudo will now treat an unrecognized Defaults entry as a parse error (sudo will warn but still run). * The HOME and MAIL environment variables are now reset based on the target user's password database entry when the env_reset sudoers option is enabled (which is the case in the default configuration). Users wishing to preserve the original values should use a sudoers entry like: Defaults env_keep += HOME to preserve the old value of HOME and Defaults env_keep += MAIL to preserve the old value of MAIL. * The tty_tickets option is now on by default. * Fixed a problem in the restoration of the AIX authdb registry setting. * If PAM is in use, wait until the process has finished before closing the PAM session. * Fixed "sudo -i -u user" where user has no shell listed in the password database. * When logging I/O, sudo now handles pty read/write returning ENXIO, as seen on FreeBSD when the login session has been killed. * Sudo now performs I/O logging in the C locale. This avoids locale-related issues when parsing floating point numbers in the timing file. * Added support for Ubuntu-style admin flag dot files. Major changes between version 1.7.2p8 and 1.7.3: * Support for logging a command's input and output as well as the ability to replay sessions. For more information, see the documentation for the log_input and log_output Defaults options in the sudoers manual. Also see the sudoreplay manual for information on replaying I/O log sessions. * The use_pty sudoers option can be used to force a command to be run in a pseudo-pty, even when I/O logging is not enabled. * On some systems, sudo can now detect when a user has logged out and back in again when tty-based time stamps are in use. Supported systems include Solaris systems with the devices file system, Mac OS X, and Linux systems with the devpts filesystem (pseudo-ttys only). * On AIX systems, the registry setting in /etc/security/user is now taken into account when looking up users and groups. Sudo now applies the correct the user and group ids when running a command as a user whose account details come from a different source (e.g. LDAP or DCE vs. local files). * Support for multiple sudoers_base and uri entries in ldap.conf. When multiple entries are listed, sudo will try each one in the order in which they are specified. * Sudo's SELinux support should now function correctly when running commands as a non-root user and when one of stdin, stdout or stderr is not a terminal. * Sudo will now use the Linux audit system with configure with the --with-linux-audit flag. * Sudo now uses mbr_check_membership() on systems that support it to determine group membership. Currently, only Darwin (Mac OS X) supports this. * When the tty_tickets sudoers option is enabled but there is no terminal device, sudo will no longer use or create a tty-based ticket file. Previously, sudo would use a tty name of "unknown". As a consequence, if a user has no terminal device, sudo will now always prompt for a password. * The passwd_timeout and timestamp_timeout options may now be specified as floating point numbers for more granular timeout values. * Negating the fqdn option in sudoers now works correctly when sudo is configured with the --with-fqdn option. In previous versions of sudo the fqdn was set before sudoers was parsed. @ text @d1 1 a1 1 @@comment $NetBSD$ a3 1 bin/sudoreplay a8 1 man/man8/sudoreplay.8 a10 4 share/doc/sudo/ChangeLog share/doc/sudo/HISTORY share/doc/sudo/LICENSE share/doc/sudo/NEWS a12 1 share/doc/sudo/TROUBLESHOOTING a13 3 share/doc/sudo/sample.pam share/doc/sudo/sample.sudoers share/doc/sudo/sample.syslog.conf @ 1.3 log @Update security/sudo package to 1.7.0. * pkgsrc change: relax restriction to kerberos package. What's new in Sudo 1.7.0? * Rewritten parser that converts sudoers into a set of data structures. This eliminates a number of ordering issues and makes it possible to apply sudoers Defaults entries before searching for the command. It also adds support for per-command Defaults specifications. * Sudoers now supports a #include facility to allow the inclusion of other sudoers-format files. * Sudo's -l (list) flag has been enhanced: o applicable Defaults options are now listed o a command argument can be specified for testing whether a user may run a specific command. o a new -U flag can be used in conjunction with "sudo -l" to allow root (or a user with "sudo ALL") list another user's privileges. * A new -g flag has been added to allow the user to specify a primary group to run the command as. The sudoers syntax has been extended to include a group section in the Runas specification. * A uid may now be used anywhere a username is valid. * The "secure_path" run-time Defaults option has been restored. * Password and group data is now cached for fast lookups. * The file descriptor at which sudo starts closing all open files is now configurable via sudoers and, optionally, the command line. * Visudo will now warn about aliases that are defined but not used. * The -i and -s command line flags now take an optional command to be run via the shell. Previously, the argument was passed to the shell as a script to run. * Improved LDAP support. SASL authentication may now be used in conjunction when connecting to an LDAP server. The krb5_ccname parameter in ldap.conf may be used to enable Kerberos. * Support for /etc/nsswitch.conf. LDAP users may now use nsswitch.conf to specify the sudoers order. E.g.: sudoers: ldap files to check LDAP, then /etc/sudoers. The default is "files", even when LDAP support is compiled in. This differs from sudo 1.6 where LDAP was always consulted first. * Support for /etc/environment on AIX and Linux. If sudo is run with the -i flag, the contents of /etc/environment are used to populate the new environment that is passed to the command being run. * If no terminal is available or if the new -A flag is specified, sudo will use a helper program to read the password if one is configured. Typically, this is a graphical password prompter such as ssh-askpass. * A new Defaults option, "mailfrom" that sets the value of the "From:" field in the warning/error mail. If unspecified, the login name of the invoking user is used. * A new Defaults option, "env_file" that refers to a file containing environment variables to be set in the command being run. * A new flag, -n, may be used to indicate that sudo should not prompt the user for a password and, instead, exit with an error if authentication is required. * If sudo needs to prompt for a password and it is unable to disable echo (and no askpass program is defined), it will refuse to run unless the "visiblepw" Defaults option has been specified. * Prior to version 1.7.0, hitting enter/return at the Password: prompt would exit sudo. In sudo 1.7.0 and beyond, this is treated as an empty password. To exit sudo, the user must press ^C or ^D at the prompt. * visudo will now check the sudoers file owner and mode in -c (check) mode when the -s (strict) flag is specified. @ text @d1 1 a1 1 @@comment $NetBSD: PLIST,v 1.2 2008/03/29 14:16:58 taca Exp $ a14 2 @@dirrm share/examples/sudo @@dirrm share/doc/sudo @ 1.2 log @Update sudo package to 1.6.9p15. 653) Fixed installation of sudo_noexec.so on AIX. 654) Updated libtool to version 1.5.26. 655) Fixed printing of default SELinux role and type in -V mode. 656) The HOME environment variable is once again preserved by default, as per the documentation. @ text @d1 1 a1 1 @@comment $NetBSD: PLIST,v 1.1 2007/07/04 20:37:50 jlam Exp $ d6 1 @ 1.2.12.1 log @Pullup ticket #2688 - requested by taca sudo: security update Revisions pulled up: - security/sudo/Makefile 1.114 - security/sudo/PLIST 1.3 - security/sudo/distinfo 1.57 - security/sudo/options.mk 1.16 - security/sudo/patches/patch-aa 1.20 - security/sudo/patches/patch-af 1.21 - security/sudo/patches/patch-ag 1.13 - security/sudo/patches/patch-ai delete --- Module Name: pkgsrc Committed By: taca Date: Thu Feb 5 13:48:12 UTC 2009 Modified Files: pkgsrc/security/sudo: Makefile PLIST distinfo options.mk pkgsrc/security/sudo/patches: patch-aa patch-af patch-ag Removed Files: pkgsrc/security/sudo/patches: patch-ai Log Message: Update security/sudo package to 1.7.0. * pkgsrc change: relax restriction to kerberos package. What's new in Sudo 1.7.0? * Rewritten parser that converts sudoers into a set of data structures. This eliminates a number of ordering issues and makes it possible to apply sudoers Defaults entries before searching for the command. It also adds support for per-command Defaults specifications. * Sudoers now supports a #include facility to allow the inclusion of other sudoers-format files. * Sudo's -l (list) flag has been enhanced: o applicable Defaults options are now listed o a command argument can be specified for testing whether a user may run a specific command. o a new -U flag can be used in conjunction with "sudo -l" to allow root (or a user with "sudo ALL") list another user's privileges. * A new -g flag has been added to allow the user to specify a primary group to run the command as. The sudoers syntax has been extended to include a group section in the Runas specification. * A uid may now be used anywhere a username is valid. * The "secure_path" run-time Defaults option has been restored. * Password and group data is now cached for fast lookups. * The file descriptor at which sudo starts closing all open files is now configurable via sudoers and, optionally, the command line. * Visudo will now warn about aliases that are defined but not used. * The -i and -s command line flags now take an optional command to be run via the shell. Previously, the argument was passed to the shell as a script to run. * Improved LDAP support. SASL authentication may now be used in conjunction when connecting to an LDAP server. The krb5_ccname parameter in ldap.conf may be used to enable Kerberos. * Support for /etc/nsswitch.conf. LDAP users may now use nsswitch.conf to specify the sudoers order. E.g.: sudoers: ldap files to check LDAP, then /etc/sudoers. The default is "files", even when LDAP support is compiled in. This differs from sudo 1.6 where LDAP was always consulted first. * Support for /etc/environment on AIX and Linux. If sudo is run with the -i flag, the contents of /etc/environment are used to populate the new environment that is passed to the command being run. * If no terminal is available or if the new -A flag is specified, sudo will use a helper program to read the password if one is configured. Typically, this is a graphical password prompter such as ssh-askpass. * A new Defaults option, "mailfrom" that sets the value of the "From:" field in the warning/error mail. If unspecified, the login name of the invoking user is used. * A new Defaults option, "env_file" that refers to a file containing environment variables to be set in the command being run. * A new flag, -n, may be used to indicate that sudo should not prompt the user for a password and, instead, exit with an error if authentication is required. * If sudo needs to prompt for a password and it is unable to disable echo (and no askpass program is defined), it will refuse to run unless the "visiblepw" Defaults option has been specified. * Prior to version 1.7.0, hitting enter/return at the Password: prompt would exit sudo. In sudo 1.7.0 and beyond, this is treated as an empty password. To exit sudo, the user must press ^C or ^D at the prompt. * visudo will now check the sudoers file owner and mode in -c (check) mode when the -s (strict) flag is specified. @ text @d1 1 a1 1 @@comment $NetBSD$ a5 1 ${PLIST.ldap}man/man5/sudoers.ldap.5 @ 1.1 log @pkgsrc basically follows the BSD man page hierarchy. Install the su and visudo manpages in man/man1, and the sudoers manpage in man/man5. Remove the platform-specific PLISTs that only differed in the location of the man pages. Bump the PKGREVISION to 5. @ text @d1 1 a1 1 @@comment $NetBSD$ d4 1 a4 1 libexec/sudo_noexec.la @