[sudo-workers] sudo 1.8.1rc3 and 1.7.6rc3 released

Wed Apr 6 20:19:16 EDT 2011

A new release candidate for sudo versions 1.8.1 and 1.7.6 is now
available.  Unless a major issue is found, the GA release of sudo
1.8.1 will occur at the end of the week.

Source:
    http://www.sudo.ws/sudo/dist/beta/sudo-1.8.1rc3.tar.gz
    ftp://ftp.sudo.ws/pub/sudo/beta/sudo-1.8.1rc3.tar.gz
    http://www.sudo.ws/sudo/dist/beta/sudo-1.7.6rc3.tar.gz
    ftp://ftp.sudo.ws/pub/sudo/beta/sudo-1.7.6rc3.tar.gz

Binary packages:
    http://www.sudo.ws/sudo/dist/beta/packages/index.html

Major changes between sudo 1.8.1rc1 and 1.8.1rc3:

 * 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.

 * Fixed the fnmatch and glob regress tests on non-BSD systems.

 * Fixed and documented the --with-plugindir configure option.

 * If there is an error making one of the subdirectories, make
   will now exit with an error instead of continuing.

 * Fixed shell warnings when --without-skey, --without-opie,
   --without-kerb4, --without-kerb5 or --without-SecurID were specified.

 * Sudoers and visudo versions now include the sudoers grammar version.

 * LDFLAGS is now honored in the plugin Makefile.in files.

Major changes between sudo 1.8.1b4 and 1.8.1rc1:

 * Fixed a bug introduced in sudo 1.8.1b2 on systems without a
   native isblank() function that prevented Defaults lines from
   parsing correctly.

Major changes between sudo 1.8.1b3 and 1.8.1b4:

 * The %#gid syntax is now fully functional and documented.

 * Fixed a build problem on HP-UX.

 * If there is an existing sudoers file, verify that it parses
   properly before installing sudo via "make install".    

 * The testsudoers utility now supports runas groups and has
   more useful return values.

 * Fixed a crash when unrecognized escapes were used in an iolog     
   file or dir.

 * Removed redundant AIX-specified code when setting resource limits.

Major changes between sudo 1.8.1b2 and 1.8.1b3:

 * The sudoers parser now treats a newline in the middle of a double
   quoted string as an error unless a line continuation character
   was used.  Previously, the text between the double quote and the
   newline was discarded.

 * Fixed a potential crash when a non-regular file (e.g. a directory)
   is present in an includedir.

 * When the -V flag is specified, the main sudo version is
   now printed even if the policy plugin cannot be initialized.

 * A uid or gid is now allowed in per-user and per-runas Defaults
   entries.

 * The sudoers parser now returns an error when an empty string
   is found where a word was expected.

 * Fixed printing of "ALL" in an Alias in testsudoers.

Major changes between sudo 1.8.0 and 1.8.1b2:

 * 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.

 * 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.

Major changes between sudo 1.7.6rc1 and 1.7.6rc3:

 * Fixed shell warnings when --without-skey, --without-opie,
   --without-kerb4, --without-kerb5 or --without-SecurID were specified.

Major changes between sudo 1.7.6b3 and 1.7.6rc1:

 * Fixed a bug introduced in sudo 1.8.1b2 on systems without
   a native isblank() function that prevented Defaults lines
   from parsing correctly.

Major changes between sudo 1.7.6b2 and 1.7.6b3:

 * The sudoers parser now treats a newline in the middle of a double
   quoted string as an error unless a line continuation character was used.
   Previously, the text between the double quote and the newline was
   discarded.