From: Todd C. Miller Date: Mon, 24 Sep 2018 12:09:07 +0000 (-0600) Subject: Changes in 1.8.26 (so far). X-Git-Tag: SUDO_1_8_26^2~74 X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=4c4f44621fab07e2623b8dc0c518d2b8fbc45eb8;p=sudo Changes in 1.8.26 (so far). --- diff --git a/NEWS b/NEWS index 67cfed686..f32c0a350 100644 --- a/NEWS +++ b/NEWS @@ -1,3 +1,17 @@ +What's new in Sudo 1.8.26 + + * Fixed a bug in cvtsudoers when converting to JSON format when + alias expansion is enabled. Bug #853. + + * 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. + What's new in Sudo 1.8.25p1 * Fixed a bug introduced in sudo 1.8.25 that caused a crash on diff --git a/doc/UPGRADE b/doc/UPGRADE index 30444fdb1..1b787c132 100644 --- a/doc/UPGRADE +++ b/doc/UPGRADE @@ -1,6 +1,20 @@ Notes on upgrading from an older release ======================================== +o Upgrading from a version prior to 1.8.26: + + Starting with version 1.8.26, 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 still sets the LOGNAME, USER and, on AIX systems, LOGIN + environment variables. + + Handling of the LOGNAME, USER (and on AIX, LOGIN) environment + variables has changed slightly in version 1.8.26. Sudo now + treats those variables as a single unit. This means that if + one variable is preserved or removed from the environment using + env_keep, env_check or env_delete, the others are too. + o Upgrading from a version prior to 1.8.23: In sudo 1.8.23 the "sudoers2ldif" script and the "visudo -x"