1 What's new in Sudo 1.8.5p2?
3 * Fixed use of the SUDO_ASKPASS environment variable which was
6 * Fixed a problem reading the sudoers file when the file mode is
7 more restrictive than the expected mode. For example, when the
8 expected sudoers file mode is 0440 but the actual mode is 0400.
10 What's new in Sudo 1.8.5p1?
12 * Fixed a bug that prevented files in an include directory from
15 What's new in Sudo 1.8.5?
17 * When "noexec" is enabled, sudo_noexec.so will now be prepended
18 to any existing LD_PRELOAD variable instead of replacing it.
20 * The sudo_noexec.so shared library now wraps the execvpe(),
21 exect(), posix_spawn() and posix_spawnp() functions.
23 * The user/group/mode checks on sudoers files have been relaxed.
24 As long as the file is owned by the sudoers uid, not world-writable
25 and not writable by a group other than the sudoers gid, the file
26 is considered OK. Note that visudo will still set the mode to
27 the value specified at configure time.
29 * It is now possible to specify the sudoers path, uid, gid and
30 file mode as options to the plugin in the sudo.conf file.
32 * Croatian, Galician, German, Lithuanian, Swedish and Vietnamese
33 translations from translationproject.org.
35 * /etc/environment is no longer read directly on Linux systems
36 when PAM is used. Sudo now merges the PAM environment into the
37 user's environment which is typically set by the pam_env module.
39 * The initial evironment created when env_reset is in effect now
40 includes the contents of /etc/environment on AIX systems and the
41 "setenv" and "path" entries from /etc/login.conf on BSD systems.
43 * The plugin API has been extended in three ways. First, options
44 specified in sudo.conf after the plugin pathname are passed to
45 the plugin's open function. Second, sudo has limited support
46 for hooks that can be used by plugins. Currently, the hooks are
47 limited to environment handling functions. Third, the init_session
48 policy plugin function is passed a pointer to the user environment
49 which can be updated during session setup. The plugin API version
50 has been incremented to version 1.2. See the sudo_plugin manual
53 * The policy plugin's init_session function is now called by the
54 parent sudo process, not the child process that executes the
55 command. This allows the PAM session to be open and closed in
56 the same process, which some PAM modules require.
58 * Fixed parsing of "Path askpass" and "Path noexec" in sudo.conf,
59 which was broken in version 1.8.4.
61 * On systems with an SVR4-style /proc file system, the /proc/pid/psinfo
62 file is now uses to determine the controlling terminal, if possible.
63 This allows tty-based tickets to work properly even when, e.g.
64 standard input, output and error are redirected to /dev/null.
66 * The output of "sudoreplay -l" is now sorted by file name (or
67 sequence number). Previously, entries were displayed in the
68 order in which they were found on the file system.
70 * Sudo now behaves properly when I/O logging is enabled and the
71 controlling terminal is revoked (e.g. the running sshd is killed).
72 Previously, sudo may have exited without calling the I/O plugin's
73 close function which can lead to an incomplete I/O log.
75 * Sudo can now detect when a user has logged out and back in again
76 on Solaris 11, just like it can on Solaris 10.
78 * The built-in zlib included with Sudo has been upgraded to version
81 * Setting the SSL parameter to start_tls in ldap.conf now works
82 properly when using Mozilla-based SDKs that support the
83 ldap_start_tls_s() function.
85 * The TLS_CHECKPEER parameter in ldap.conf now works when the
86 Mozilla NSS crypto backend is used with OpenLDAP.
88 * A new group provider plugin, system_group, is included which
89 performs group look ups by name using the system groups database.
90 This can be used to restore the pre-1.7.3 sudo group lookup
93 What's new in Sudo 1.8.4p5?
95 * Fixed a bug when matching against an IP address with an associated
96 netmask in the sudoers file. In certain circumstances, this
97 could allow users to run commands on hosts they are not authorized
100 What's new in Sudo 1.8.4p4?
102 * Fixed a bug introduced in Sudo 1.8.4 which prevented "sudo -v"
105 What's new in Sudo 1.8.4p3?
107 * Fixed a crash on FreeBSD when no tty is present.
109 * Fixed a bug introduced in Sudo 1.8.4 that allowed users to
110 specify environment variables to set on the command line without
111 having sudo "ALL" permissions or the "SETENV" tag.
113 * When visudo is run with the -c (check) option, the sudoers
114 file(s) owner and mode are now also checked unless the -f option
117 What's new in Sudo 1.8.4p2?
119 * Fixed a bug introduced in Sudo 1.8.4 where insufficient space
120 was allocated for group IDs in the LDAP filter.
122 * Fixed a bug introduced in Sudo 1.8.4 where the path to sudo.conf
123 was "/sudo.conf" instead of "/etc/sudo.conf".
125 * Fixed a bug introduced in Sudo 1.8.4 which could cause a hang
126 when I/O logging is enabled and input is from a pipe or file.
128 What's new in Sudo 1.8.4p1?
130 * Fixed a bug introduced in sudo 1.8.4 that broke adding to or
131 deleting from the env_keep, env_check and env_delete lists in
132 sudoers on some platforms.
134 What's new in Sudo 1.8.4?
136 * The -D flag in sudo has been replaced with a more general debugging
137 framework that is configured in sudo.conf.
139 * Fixed a false positive in visudo strict mode when aliases are
142 * Fixed a crash with "sudo -i" when a runas group was specified
143 without a runas user.
145 * The line on which a syntax error is reported in the sudoers file
146 is now more accurate. Previously it was often off by a line.
148 * Fixed a bug where stack garbage could be printed at the end of
149 the lecture when the "lecture_file" option was enabled.
151 * "make install" now honors the LINGUAS environment variable.
153 * The #include and #includedir directives in sudoers now support
154 relative paths. If the path is not fully qualified it is expected
155 to be located in the same directory of the sudoers file that is
158 * Serbian and Spanish translations for sudo from translationproject.org.
160 * LDAP-based sudoers may now access by group ID in addition to
163 * visudo will now fix the mode on the sudoers file even if no changes
164 are made unless the -f option is specified.
166 * The "use_loginclass" sudoers option works properly again.
168 * On systems that use login.conf, "sudo -i" now sets environment
169 variables based on login.conf.
171 * For LDAP-based sudoers, values in the search expression are now
172 escaped as per RFC 4515.
174 * The plugin close function is now properly called when a login
175 session is killed (as opposed to the actual command being killed).
176 This can happen when an ssh session is disconnected or the
177 terminal window is closed.
179 * The deprecated "noexec_file" sudoers option is no longer supported.
181 * Fixed a race condition when I/O logging is not enabled that could
182 result in tty-generated signals (e.g. control-C) being received
183 by the command twice.
185 * If none of the standard input, output or error are connected to
186 a tty device, sudo will now check its parent's standard input,
187 output or error for the tty name on systems with /proc and BSD
188 systems that support the KERN_PROC_PID sysctl. This allows
189 tty-based tickets to work properly even when, e.g. standard
190 input, output and error are redirected to /dev/null.
192 * Added the --enable-kerb5-instance configure option to allow
193 people using Kerberos V authentication to specify a custom
194 instance so the principal name can be, e.g. "username/sudo"
195 similar to how ksu uses "username/root".
197 * Fixed a bug where a pattern like "/usr/*" included /usr/bin/ in
198 the results, which would be incorrectly be interpreted as if the
199 sudoers file had specified a directory.
201 * "visudo -c" will now list any include files that were checked
202 in addition to the main sudoers file when everything parses OK.
204 * Users that only have read-only access to the sudoers file may
205 now run "visudo -c". Previously, write permissions were required
206 even though no writing is down in check-only mode.
208 * It is now possible to prevent the disabling of core dumps from
209 within sudo itself by adding a line to the sudo.conf file like
210 "Set disable_coredump false".
212 What's new in Sudo 1.8.3p2?
214 * Fixed a format string vulnerability when the sudo binary (or a
215 symbolic link to the sudo binary) contains printf format escapes
216 and the -D (debugging) flag is used.
218 What's new in Sudo 1.8.3p1?
220 * Fixed a crash in the monitor process on Solaris when NOPASSWD
221 was specified or when authentication was disabled.
223 * Fixed matching of a Runas_Alias in the group section of a
226 What's new in Sudo 1.8.3?
228 * Fixed expansion of strftime() escape sequences in the "log_dir"
231 * Esperanto, Italian and Japanese translations from translationproject.org.
233 * Sudo will now use PAM by default on AIX 6 and higher.
235 * Added --enable-werror configure option for gcc's -Werror flag.
237 * Visudo no longer assumes all editors support the +linenumber
238 command line argument. It now uses a whitelist of editors known
239 to support the option.
241 * Fixed matching of network addresses when a netmask is specified
242 but the address is not the first one in the CIDR block.
244 * The configure script now check whether or not errno.h declares
245 the errno variable. Previously, sudo would always declare errno
246 itself for older systems that don't declare it in errno.h.
248 * The NOPASSWD tag is now honored for denied commands too, which
249 matches historic sudo behavior (prior to sudo 1.7.0).
251 * Sudo now honors the "DEREF" setting in ldap.conf which controls
252 how alias dereferencing is done during an LDAP search.
254 * A symbol conflict with the pam_ssh_agent_auth PAM module that
255 would cause a crash been resolved.
257 * The inability to load a group provider plugin is no longer
260 * A potential crash in the utmp handling code has been fixed.
262 * Two PAM session issues have been resolved. In previous versions
263 of sudo, the PAM session was opened as one user and closed as
264 another. Additionally, if no authentication was performed, the
265 PAM session would never be closed.
267 * Sudo will now work correctly with LDAP-based sudoers using TLS
268 or SSL on Debian systems.
270 * The LOGNAME, USER and USERNAME environment variables are preserved
271 correctly again in sudoedit mode.
273 What's new in Sudo 1.8.2?
275 * Sudo, visudo, sudoreplay and the sudoers plug-in now have natural
276 language support (NLS). This can be disabled by passing configure
277 the --disable-nls option. Sudo will use gettext(), if available,
278 to display translated messages. All translations are coordinated
279 via The Translation Project, http://translationproject.org/.
281 * Plug-ins are now loaded with the RTLD_GLOBAL flag instead of
282 RTLD_LOCAL. This fixes missing symbol problems in PAM modules
283 on certain platforms, such as FreeBSD and SuSE Linux Enterprise.
285 * I/O logging is now supported for commands run in background mode
286 (using sudo's -b flag).
288 * Group ownership of the sudoers file is now only enforced when
289 the file mode on sudoers allows group readability or writability.
291 * Visudo now checks the contents of an alias and warns about cycles
292 when the alias is expanded.
294 * If the user specifies a group via sudo's -g option that matches
295 the target user's group in the password database, it is now
296 allowed even if no groups are present in the Runas_Spec.
298 * The sudo Makefiles now have more complete dependencies which are
299 automatically generated instead of being maintained manually.
301 * The "use_pty" sudoers option is now correctly passed back to the
302 sudo front end. This was missing in previous versions of sudo
303 1.8 which prevented "use_pty" from being honored.
305 * "sudo -i command" now works correctly with the bash version
306 2.0 and higher. Previously, the .bash_profile would not be
307 sourced prior to running the command unless bash was built with
308 NON_INTERACTIVE_LOGIN_SHELLS defined.
310 * When matching groups in the sudoers file, sudo will now match
311 based on the name of the group instead of the group ID. This can
312 substantially reduce the number of group lookups for sudoers
313 files that contain a large number of groups.
315 * Multi-factor authentication is now supported on AIX.
317 * Added support for non-RFC 4517 compliant LDAP servers that require
318 that seconds be present in a timestamp, such as Tivoli Directory Server.
320 * If the group vector is to be preserved, the PATH search for the
321 command is now done with the user's original group vector.
323 * For LDAP-based sudoers, the "runas_default" sudoOption now works
324 properly in a sudoRole that contains a sudoCommand.
326 * Spaces in command line arguments for "sudo -s" and "sudo -i" are
327 now escaped with a backslash when checking the security policy.
329 What's new in Sudo 1.8.1p2?
331 * Two-character CIDR-style IPv4 netmasks are now matched correctly
334 * A build error with MIT Kerberos V has been resolved.
336 * A crash on HP-UX in the sudoers plugin when wildcards are
337 present in the sudoers file has been resolved.
339 * Sudo now works correctly on Tru64 Unix again.
341 What's new in Sudo 1.8.1p1?
343 * Fixed a problem on AIX where sudo was unable to set the final
344 uid if the PAM module modified the effective uid.
346 * A non-existent includedir is now treated the same as an empty
347 directory and not reported as an error.
349 * Removed extraneous parens in LDAP filter when sudoers_search_filter
350 is enabled that can cause an LDAP search error.
352 * Fixed a "make -j" problem for "make install".
354 What's new in Sudo 1.8.1?
356 * A new LDAP setting, sudoers_search_filter, has been added to
357 ldap.conf. This setting can be used to restrict the set of
358 records returned by the LDAP query. Based on changes from Matthew
361 * White space is now permitted within a User_List when used in
362 conjunction with a per-user Defaults definition.
364 * A group ID (%#gid) may now be specified in a User_List or Runas_List.
365 Likewise, for non-Unix groups the syntax is %:#gid.
367 * Support for double-quoted words in the sudoers file has been fixed.
368 The change in 1.7.5 for escaping the double quote character
369 caused the double quoting to only be available at the beginning
372 * The fix for resuming a suspended shell in 1.7.5 caused problems
373 with resuming non-shells on Linux. Sudo will now save the process
374 group ID of the program it is running on suspend and restore it
375 when resuming, which fixes both problems.
377 * A bug that could result in corrupted output in "sudo -l" has been
380 * Sudo will now create an entry in the utmp (or utmpx) file when
381 allocating a pseudo-tty (e.g. when logging I/O). The "set_utmp"
382 and "utmp_runas" sudoers file options can be used to control this.
383 Other policy plugins may use the "set_utmp" and "utmp_user"
384 entries in the command_info list.
386 * The sudoers policy now stores the TSID field in the logs
387 even when the "iolog_file" sudoers option is defined to a value
388 other than %{sessid}. Previously, the TSID field was only
389 included in the log file when the "iolog_file" option was set
390 to its default value.
392 * The sudoreplay utility now supports arbitrary session IDs.
393 Previously, it would only work with the base-36 session IDs
394 that the sudoers plugin uses by default.
396 * Sudo now passes "run_shell=true" to the policy plugin in the
397 settings list when sudo's -s command line option is specified.
398 The sudoers policy plugin uses this to implement the "set_home"
399 sudoers option which was missing from sudo 1.8.0.
401 * The "noexec" functionality has been moved out of the sudoers
402 policy plugin and into the sudo front-end, which matches the
403 behavior documented in the plugin writer's guide. As a result,
404 the path to the noexec file is now specified in the sudo.conf
405 file instead of the sudoers file.
407 * On Solaris 10, the PRIV_PROC_EXEC privilege is now used to
408 implement the "noexec" feature. Previously, this was implemented
409 via the LD_PRELOAD environment variable.
411 * The exit values for "sudo -l", "sudo -v" and "sudo -l command"
412 have been fixed in the sudoers policy plugin.
414 * The sudoers policy plugin now passes the login class, if any,
415 back to the sudo front-end.
417 * The sudoers policy plugin was not being linked with requisite
418 libraries in certain configurations.
420 * Sudo now parses command line arguments before loading any plugins.
421 This allows "sudo -V" or "sudo -h" to work even if there is a problem
424 * Plugins are now linked with the static version of libgcc to allow
425 the plugin to run on a system where no shared libgcc is installed,
426 or where it is installed in a different location.
428 What's new in Sudo 1.8.0?
430 * Sudo has been refactored to use a modular framework that can
431 support third-party policy and I/O logging plugins. The default
432 plugin is "sudoers" which provides the traditional sudo functionality.
433 See the sudo_plugin manual for details on the plugin API and the
434 sample in the plugins directory for a simple example.
436 What's new in Sudo 1.7.5?
438 * When using visudo in check mode, a file named "-" may be used to
439 check sudoers data on the standard input.
441 * Sudo now only fetches shadow password entries when using the
442 password database directly for authentication.
444 * Password and group entries are now cached using the same key
445 that was used to look them up. This fixes a problem when looking
446 up entries by name if the name in the retrieved entry does not
447 match the name used to look it up. This may happen on some systems
448 that do case insensitive lookups or that truncate long names.
450 * GCC will no longer display warnings on glibc systems that use
451 the warn_unused_result attribute for write(2) and other system calls.
453 * If a PAM account management module denies access, sudo now prints
454 a more useful error message and stops trying to validate the user.
456 * Fixed a potential hang on idle systems when the sudo-run process
459 * Sudo now includes a copy of zlib that will be used on systems
460 that do not have zlib installed.
462 * The --with-umask-override configure flag has been added to enable
463 the "umask_override" sudoers Defaults option at build time.
465 * Sudo now unblocks all signals on startup to avoid problems caused
466 by the parent process changing the default signal mask.
468 * LDAP Sudoers entries may now specify a time period for which
469 the entry is valid. This requires an updated sudoers schema
470 that includes the sudoNotBefore and sudoNotAfter attributes.
471 Support for timed entries must be explicitly enabled in the
472 ldap.conf file. Based on changes from Andreas Mueller.
474 * LDAP Sudoers entries may now specify a sudoOrder attribute that
475 determines the order in which matching entries are applied. The
476 last matching entry is used, just like file-based sudoers. This
477 requires an updated sudoers schema that includes the sudoOrder
478 attribute. Based on changes from Andreas Mueller.
480 * When run as sudoedit, or when given the -e flag, sudo now treats
481 command line arguments as pathnames. This means that slashes
482 in the sudoers file entry must explicitly match slashes in
483 the command line arguments. As a result, and entry such as:
484 user ALL = sudoedit /etc/*
485 will allow editing of /etc/motd but not /etc/security/default.
487 * NETWORK_TIMEOUT is now an alias for BIND_TIMELIMIT in ldap.conf for
488 compatibility with OpenLDAP configuration files.
490 * The LDAP API TIMEOUT parameter is now honored in ldap.conf.
492 * The I/O log directory may now be specified in the sudoers file.
494 * Sudo will no longer refuse to run if the sudoers file is writable
497 * Sudo now performs command line escaping for "sudo -s" and "sudo -i"
498 after validating the command so the sudoers entries do not need
499 to include the backslashes.
501 * Logging and email sending are now done in the locale specified
502 by the "sudoers_locale" setting ("C" by default). Email send by
503 sudo now includes MIME headers when "sudoers_locale" is not "C".
505 * The configure script has a new option, --disable-env-reset, to
506 allow one to change the default for the sudoers Default setting
507 "env_reset" at compile time.
509 * When logging "sudo -l command", sudo will now prepend "list "
510 to the command in the log line to distinguish between an
511 actual command invocation in the logs.
513 * Double-quoted group and user names may now include escaped double
514 quotes as part of the name. Previously this was a parse error.
516 * Sudo once again restores the state of the signal handlers it
517 modifies before executing the command. This allows sudo to be
518 used with the nohup command.
520 * Resuming a suspended shell now works properly when I/O logging
521 is not enabled (the I/O logging case was already correct).
523 What's new in Sudo 1.7.4p6?
525 * A bug has been fixed in the I/O logging support that could cause
526 visual artifacts in full-screen programs such as text editors.
528 What's new in Sudo 1.7.4p5?
530 * A bug has been fixed that would allow a command to be run without the
531 user entering a password when sudo's -g flag is used without the -u flag.
533 * If user has no supplementary groups, sudo will now fall back on checking
534 the group file explicitly, which restores historic sudo behavior.
536 * A crash has been fixed when sudo's -g flag is used without the -u flag
537 and the sudoers file contains an entry with no runas user or group listed.
539 * A crash has been fixed when the Solaris project support is enabled
540 and sudo's -g flag is used without the -u flag.
542 * Sudo no longer exits with an error when support for auditing is
543 compiled in but auditing is not enabled.
545 * Fixed a bug introduced in sudo 1.7.3 where the ticket file was not
546 being honored when the "targetpw" sudoers Defaults option was enabled.
548 * The LOG_INPUT and LOG_OUTPUT tags in sudoers are now parsed correctly.
550 * A crash has been fixed in "sudo -l" when sudo is built with auditing
551 support and the user is not allowed to run any commands on the host.
553 What's new in Sudo 1.7.4p4?
555 * A potential security issue has been fixed with respect to the handling
556 of sudo's -g command line option when -u is also specified. The flaw
557 may allow an attacker to run commands as a user that is not authorized
560 * A bug has been fixed where "sudo -l" output was incomplete if multiple
561 sudoers sources were defined in nsswitch.conf and there was an error
562 querying one of the sources.
564 * The log_input, log_output, and use_pty sudoers options now work correctly
565 on AIX. Previously, sudo would hang if they were enabled.
567 * The "make install" target now works correctly when sudo is built in a
568 directory other than the source directory.
570 * The "runas_default" sudoers setting now works properly in a per-command
573 * Suspending and resuming the bash shell when PAM is in use now works
574 correctly. The SIGCONT signal was not propagated to the child process.
576 What's new in Sudo 1.7.4p3?
578 * A bug has been fixed where duplicate HOME environment variables could be
579 present when the env_reset setting was disabled and the always_set_home
580 setting was enabled in sudoers.
582 * The value of sysconfdir is now substituted into the path to the sudoers.d
583 directory in the installed sudoers file.
585 * Compilation problems on IRIX and other platforms have been fixed.
587 * If multiple PAM "auth" actions are specified and the user enters ^C at
588 the password prompt, sudo will no longer prompt for a password for any
589 subsequent "auth" actions. Previously it was necessary to enter ^C for
592 What's new in Sudo 1.7.4p2?
594 * A bug where sudo could spin in a busy loop waiting for the child process
597 What's new in Sudo 1.7.4p1?
599 * A bug introduced in sudo 1.7.3 that prevented the -k and -K options from
600 functioning when the tty_tickets sudoers option is enabled has been fixed.
602 * Sudo no longer prints a warning when the -k or -K options are specified
603 and the ticket file does not exist.
605 * It is now easier to cross-compile sudo.
607 What's new in Sudo 1.7.4?
609 * Sudoedit will now preserve the file extension in the name of the
610 temporary file being edited. The extension is used by some
611 editors (such as emacs) to choose the editing mode.
613 * Time stamp files have moved from /var/run/sudo to either /var/db/sudo,
614 /var/lib/sudo or /var/adm/sudo. The directories are checked for
615 existence in that order. This prevents users from receiving the
616 sudo lecture every time the system reboots. Time stamp files older
617 than the boot time are ignored on systems where it is possible to
620 * The tty_tickets sudoers option is now enabled by default.
622 * Ancillary documentation (README files, LICENSE, etc) is now installed
623 in a sudo documentation directory.
625 * Sudo now recognizes "tls_cacert" as an alias for "tls_cacertfile"
628 * Defaults settings that are tied to a user, host or command may
629 now include the negation operator. For example:
630 Defaults:!millert lecture
631 will match any user but millert.
633 * The default PATH environment variable, used when no PATH variable
634 exists, now includes /usr/sbin and /sbin.
636 * Sudo now uses polypkg (http://rc.quest.com/topics/polypkg/)
637 for cross-platform packing.
639 * On Linux, sudo will now restore the nproc resource limit before
640 executing a command, unless the limit appears to have been modified
641 by pam_limits. This avoids a problem with bash scripts that open
642 more than 32 descriptors on SuSE Linux, where sysconf(_SC_CHILD_MAX)
643 will return -1 when RLIMIT_NPROC is set to RLIMIT_UNLIMITED (-1).
645 * The HOME and MAIL environment variables are now reset based on the
646 target user's password database entry when the env_reset sudoers option
647 is enabled (which is the case in the default configuration). Users
648 wishing to preserve the original values should use a sudoers entry like:
649 Defaults env_keep += HOME
650 to preserve the old value of HOME and
651 Defaults env_keep += MAIL
652 to preserve the old value of MAIL.
654 * Fixed a problem in the restoration of the AIX authdb registry setting.
656 * Sudo will now fork(2) and wait until the command has completed before
657 calling pam_close_session().
659 * The default syslog facility is now "authpriv" if the operating system
660 supports it, else "auth".
662 What's new in Sudo 1.7.3?
664 * Support for logging I/O for the command being run.
665 For more information, see the documentation for the "log_input"
666 and "log_output" Defaults options in the sudoers manual. Also
667 see the sudoreplay manual for how to replay I/O log sessions.
669 * The use_pty sudoers option can be used to force a command to be
670 run in a pseudo-pty, even when I/O logging is not enabled.
672 * On some systems, sudo can now detect when a user has logged out
673 and back in again when tty-based time stamps are in use. Supported
674 systems include Solaris systems with the devices file system,
675 Mac OS X, and Linux systems with the devpts filesystem (pseudo-ttys
678 * On AIX systems, the registry setting in /etc/security/user is
679 now taken into account when looking up users and groups. Sudo
680 now applies the correct the user and group ids when running a
681 command as a user whose account details come from a different
682 source (e.g. LDAP or DCE vs. local files).
684 * Support for multiple 'sudoers_base' and 'uri' entries in ldap.conf.
685 When multiple entries are listed, sudo will try each one in the
686 order in which they are specified.
688 * Sudo's SELinux support should now function correctly when running
689 commands as a non-root user and when one of stdin, stdout or stderr
692 * Sudo will now use the Linux audit system with configure with
693 the --with-linux-audit flag.
695 * Sudo now uses mbr_check_membership() on systems that support it
696 to determine group membership. Currently, only Darwin (Mac OS X)
699 * When the tty_tickets sudoers option is enabled but there is no
700 terminal device, sudo will no longer use or create a tty-based
701 ticket file. Previously, sudo would use a tty name of "unknown".
702 As a consequence, if a user has no terminal device, sudo will
703 now always prompt for a password.
705 * The passwd_timeout and timestamp_timeout options may now be
706 specified as floating point numbers for more granular timeout
709 * Negating the fqdn option in sudoers now works correctly when sudo
710 is configured with the --with-fqdn option. In previous versions
711 of sudo the fqdn was set before sudoers was parsed.
713 What's new in Sudo 1.7.2?
715 * A new #includedir directive is available in sudoers. This can be
716 used to implement an /etc/sudo.d directory. Files in an includedir
717 are not edited by visudo unless they contain a syntax error.
719 * The -g option did not work properly when only setting the group
720 (and not the user). Also, in -l mode the wrong user was displayed
721 for sudoers entries where only the group was allowed to be set.
723 * Fixed a problem with the alias checking in visudo which
724 could prevent visudo from exiting.
726 * Sudo will now correctly parse the shell-style /etc/environment
727 file format used by pam_env on Linux.
729 * When doing password and group database lookups, sudo will only
730 cache an entry by name or by id, depending on how the entry was
731 looked up. Previously, sudo would cache by both name and id
732 from a single lookup, but this breaks sites that have multiple
733 password or group database names that map to the same uid or
736 * User and group names in sudoers may now be enclosed in double
737 quotes to avoid having to escape special characters.
739 * BSM audit fixes when changing to a non-root uid.
741 * Experimental non-Unix group support. Currently only works with
742 Quest Authorization Services and allows Active Directory groups
745 * For Netscape/Mozilla-derived LDAP SDKs the certificate and key
746 paths may be specified as a directory or a file. However, version
747 5.0 of the SDK only appears to support using a directory (despite
748 documentation to the contrary). If SSL client initialization
749 fails and the certificate or key paths look like they could be
750 default file name, strip off the last path element and try again.
752 * A setenv() compatibility fix for Linux systems, where a NULL
753 value is treated the same as an empty string and the variable
754 name is checked against the NULL pointer.
756 What's new in Sudo 1.7.1?
758 * A new Defaults option "pwfeedback" will cause sudo to provide visual
759 feedback when the user is entering a password.
761 * A new Defaults option "fast_glob" will cause sudo to use the fnmatch()
762 function for file name globbing instead of glob(). When this option
763 is enabled, sudo will not check the file system when expanding wildcards.
764 This is faster but a side effect is that relative paths with wildcard
767 * New BSM audit support for systems that support it such as FreeBSD
770 * The file name specified with the #include directive may now include
771 a %h escape which is expanded to the short form of hostname.
773 * The -k flag may now be specified along with a command, causing the
774 user's timestamp file to be ignored.
776 * New support for Tivoli-based LDAP START_TLS, present in AIX.
778 * New support for /etc/netsvc.conf on AIX.
780 * The unused alias checks in visudo now handle the case of an alias
781 referring to another alias.
783 What's new in Sudo 1.7.0?
785 * Rewritten parser that converts sudoers into a set of data structures.
786 This eliminates a number of ordering issues and makes it possible to
787 apply sudoers Defaults entries before searching for the command.
788 It also adds support for per-command Defaults specifications.
790 * Sudoers now supports a #include facility to allow the inclusion of other
791 sudoers-format files.
793 * Sudo's -l (list) flag has been enhanced:
794 o applicable Defaults options are now listed
795 o a command argument can be specified for testing whether a user
796 may run a specific command.
797 o a new -U flag can be used in conjunction with "sudo -l" to allow
798 root (or a user with "sudo ALL") list another user's privileges.
800 * A new -g flag has been added to allow the user to specify a
801 primary group to run the command as. The sudoers syntax has been
802 extended to include a group section in the Runas specification.
804 * A uid may now be used anywhere a username is valid.
806 * The "secure_path" run-time Defaults option has been restored.
808 * Password and group data is now cached for fast lookups.
810 * The file descriptor at which sudo starts closing all open files is now
811 configurable via sudoers and, optionally, the command line.
813 * Visudo will now warn about aliases that are defined but not used.
815 * The -i and -s command line flags now take an optional command
816 to be run via the shell. Previously, the argument was passed
817 to the shell as a script to run.
819 * Improved LDAP support. SASL authentication may now be used in
820 conjunction when connecting to an LDAP server. The krb5_ccname
821 parameter in ldap.conf may be used to enable Kerberos.
823 * Support for /etc/nsswitch.conf. LDAP users may now use nsswitch.conf
824 to specify the sudoers order. E.g.:
826 to check LDAP, then /etc/sudoers. The default is "files", even
827 when LDAP support is compiled in. This differs from sudo 1.6
828 where LDAP was always consulted first.
830 * Support for /etc/environment on AIX and Linux. If sudo is run
831 with the -i flag, the contents of /etc/environment are used to
832 populate the new environment that is passed to the command being
835 * If no terminal is available or if the new -A flag is specified,
836 sudo will use a helper program to read the password if one is
837 configured. Typically, this is a graphical password prompter
840 * A new Defaults option, "mailfrom" that sets the value of the
841 "From:" field in the warning/error mail. If unspecified, the
842 login name of the invoking user is used.
844 * A new Defaults option, "env_file" that refers to a file containing
845 environment variables to be set in the command being run.
847 * A new flag, -n, may be used to indicate that sudo should not
848 prompt the user for a password and, instead, exit with an error
849 if authentication is required.
851 * If sudo needs to prompt for a password and it is unable to disable
852 echo (and no askpass program is defined), it will refuse to run
853 unless the "visiblepw" Defaults option has been specified.
855 * Prior to version 1.7.0, hitting enter/return at the Password: prompt
856 would exit sudo. In sudo 1.7.0 and beyond, this is treated as
857 an empty password. To exit sudo, the user must press ^C or ^D
860 * visudo will now check the sudoers file owner and mode in -c (check)
861 mode when the -s (strict) flag is specified.
863 * A new Defaults option "umask_override" will cause sudo to set the
864 umask specified in sudoers even if it is more permissive than the
865 invoking user's umask.