sudo 1.9.3p1 released

--===============4476501124627937741==
Content-Type: multipart/signed; protocol="application/pgp-signature";
  micalg=pgp-; boundary="34879_Wed_Sep_23_19_37_20_MDT_2020"

--34879_Wed_Sep_23_19_37_20_MDT_2020
Content-Type: text/plain; charset=us-ascii

Sudo version 1.9.3, patchlevel 1 is now available.  This patch
release fixes a few small issues found in sudo 1.9.3.

Source:
    https://www.sudo.ws/dist/sudo-1.9.3p1.tar.gz
    ftp://ftp.sudo.ws/pub/sudo/sudo-1.9.3p1.tar.gz

SHA256 checksum:
    dcb9de53e45e1c39042074b847f5e0d8ae1890725dd6a9d9101a81569e6eb49e
MD5 checksum:
    8f230d0f8994f0b21b109370d1fbcf45

Binary packages:
    https://www.sudo.ws/download.html#binary

For a list of download mirror sites, see:
    https://www.sudo.ws/download_mirrors.html

Sudo web site:
    https://www.sudo.ws/

Sudo web site mirrors:
    https://www.sudo.ws/mirrors.html

Major changes between sudo 1.9.3 and 1.9.3p1

 * Fixed a regression introduced in sudo 1.9.3 where the configure
   script would not detect the crypt(3) function if it was present
   in the C library, not an additional library.

 * Fixed a regression introduced in sudo 1.8.23 with shadow passwd
   file authentication on OpenBSD.  BSD authentication was not
   affected.

 * Sudo now logs when a user-specified command-line option is
   rejected by a sudoers rule.  Previously, these conditions were
   written to the audit log, but the default sudo log file.  Affected
   command line arguments include -C (--close-from), -D (--chdir),
   -R (--chroot), -g (--group) and -u (--user).

Major changes between sudo 1.9.2 and 1.9.3

 * sudoedit will now prompt the user before overwriting an existing
   file with one that is zero-length after editing.  Bug #922.

 * Fixed building the Python plugin on systems with a compiler that
   doesn't support symbol hiding.

 * Sudo now uses a linker script to hide symbols even when the
   compiler has native symbol hiding support.  This should make it
   easier to detect omissions in the symbol exports file, regardless
   of the platform.

 * Fixed the libssl dependency in Debian packages for older releases
   that use libssl1.0.0.

 * Sudo and visudo now provide more detailed messages when a syntax
   error is detected in sudoers.  The offending line and token are
   now displayed.  If the parser was generated by GNU bison,
   additional information about what token was expected is also
   displayed.  Bug #841.

 * Sudoers rules must now end in either a newline or the end-of-file.
   Previously, it was possible to have multiple rules on a single
   line, separated by white space.  The use of an end-of-line
   terminator makes it possible to display accurate error messages.

 * Sudo no longer refuses to run if a syntax error in the sudoers
   file is encountered.  The entry with the syntax error will be
   discarded and sudo will continue to parse the file.  This makes
   recovery from a syntax error less painful on systems where sudo
   is the primary method of superuser access.  The historic behavior
   can be restored by add "error_recovery=false" to the sudoers
   plugin's optional arguments in sudo.conf.  Bug #618.

 * Fixed the sample_approval plugin's symbol exports file for systems
   where the compiler doesn't support symbol hiding.

 * Fixed a regression introduced in sudo 1.9.1 where arguments to
   the "sudoers_policy" plugin in sudo.conf were not being applied.
   The sudoers file is now parsed by the "sudoers_audit" plugin,
   which is loaded implicitly when "sudoers_policy" is listed in
   sudo.conf.  Starting with sudo 1.9.3, if there are plugin arguments
   for "sudoers_policy" but "sudoers_audit" is not listed, those
   arguments will be applied to "sudoers_audit" instead.

 * The user's resource limits are now passed to sudo plugins in
   the user_info[] list.  A plugin cannot determine the limits
   itself because sudo changes the limits while it runs to prevent
   resource starvation.

 * It is now possible to set the working directory or change the
   root directory on a per-command basis using the CWD and CHROOT
   options.  There are also new Defaults settings, runchroot and
   runcwd, that can be used to set the working directory or root
   directory on a more global basis.

 * New -D (--chdir) and -R (--chroot) command line options can be
   used to set the working directory or root directory if the sudoers
   file allows it.  This functionality is not enabled by default
   and must be explicitly enabled in the sudoers file.

--34879_Wed_Sep_23_19_37_20_MDT_2020
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----

iQIcBAEBCAAGBQJfa/hQAAoJEKn0wCHOpHD7ThUP/AmFMPZ0nyHIb6TOVpIsj9yO
NakM0KigXNqHX7UpADp8g98ctCce0C1nB4V2xxOENwsbzQ3Jfqm62SIjn60x2JvW
X3sF6kYkAxE5hCleL2ySu813jyudnosWTRiJ9Z1gNJI63PNvqS+0mkskIvJxq05X
MT69za1zpMX06OrXAjp9bqAc/1AQEbV5lJHXgGqyxqmLqQVxssgJFcfL7HGwSAGC
JGjRz6qvZ3xvhkK73A/UHdsuqGQph+YzA+qE4BIr1fnHa9fB75hyvjTEhRf2a50s
ByJTm/l/Clx7Iu7Uq8WrSPTRMVixIs30Ibpw9J220xb74d/upUg2jNy+YTYgTvDR
mkSlmWa21UZLGbBhdhyynUDl0+dUa533qKkhxOMB1FkqQj9bPQBmKfyABvkAPAj4
ho0O4gsRXQKLdhmUpYC+MO4DHDqVP19s7j2Ptwvj70GGRv6DTtuKMEWfIguA4dcA
BjUzjXy4ow0F7ExANo0MALJ6EtIkbmIHVlQIrrP8a+VeCHubbCmQ2HCMHCuiskkw
aJzCy+asL370QEXMKwqVwkxZ/lT4vYye+FupfnN7SELp38620BmqgxgJYbTVv1EH
Ku8DMLUWqoFK19DXXixVXF3mCz52n9DTBlpiewKPQ/MKj4+XYEm1ujcRcCj5y4np
fJYPeCrEm50vw+OLdvRY
=Tzau
-----END PGP SIGNATURE-----

--34879_Wed_Sep_23_19_37_20_MDT_2020--


--===============4476501124627937741==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

____________________________________________________________
sudo-announce mailing list <[email protected]>
For list information, options, or to unsubscribe, visit:
https://www.sudo.ws/mailman/listinfo/sudo-announce

--===============4476501124627937741==--