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