1 What's new in Sudo 1.8.1p2?
3 * Two-character CIDR-style IPv4 netmasks are now matched correctly
6 * A build error with MIT Kerberos V has been resolved.
8 * A crash on HP-UX in the sudoers plugin when wildcards are
9 present in the sudoers file has been resolved.
11 * Sudo now works correctly on Tru64 Unix again.
13 What's new in Sudo 1.8.1p1?
15 * Fixed a problem on AIX where sudo was unable to set the final
16 uid if the PAM module modified the effective uid.
18 * A non-existent includedir is now treated the same as an empty
19 directory and not reported as an error.
21 * Removed extraneous parens in LDAP filter when sudoers_search_filter
22 is enabled that can cause an LDAP search error.
24 * Fixed a "make -j" problem for "make install".
26 What's new in Sudo 1.8.1?
28 * A new LDAP setting, sudoers_search_filter, has been added to
29 ldap.conf. This setting can be used to restrict the set of
30 records returned by the LDAP query. Based on changes from Matthew
33 * White space is now permitted within a User_List when used in
34 conjunction with a per-user Defaults definition.
36 * A group ID (%#gid) may now be specified in a User_List or Runas_List.
37 Likewise, for non-Unix groups the syntax is %:#gid.
39 * Support for double-quoted words in the sudoers file has been fixed.
40 The change in 1.7.5 for escaping the double quote character
41 caused the double quoting to only be available at the beginning
44 * The fix for resuming a suspended shell in 1.7.5 caused problems
45 with resuming non-shells on Linux. Sudo will now save the process
46 group ID of the program it is running on suspend and restore it
47 when resuming, which fixes both problems.
49 * A bug that could result in corrupted output in "sudo -l" has been
52 * Sudo will now create an entry in the utmp (or utmpx) file when
53 allocating a pseudo-tty (e.g. when logging I/O). The "set_utmp"
54 and "utmp_runas" sudoers file options can be used to control this.
55 Other policy plugins may use the "set_utmp" and "utmp_user"
56 entries in the command_info list.
58 * The sudoers policy now stores the TSID field in the logs
59 even when the "iolog_file" sudoers option is defined to a value
60 other than %{sessid}. Previously, the TSID field was only
61 included in the log file when the "iolog_file" option was set
64 * The sudoreplay utility now supports arbitrary session IDs.
65 Previously, it would only work with the base-36 session IDs
66 that the sudoers plugin uses by default.
68 * Sudo now passes "run_shell=true" to the policy plugin in the
69 settings list when sudo's -s command line option is specified.
70 The sudoers policy plugin uses this to implement the "set_home"
71 sudoers option which was missing from sudo 1.8.0.
73 * The "noexec" functionality has been moved out of the sudoers
74 policy plugin and into the sudo front-end, which matches the
75 behavior documented in the plugin writer's guide. As a result,
76 the path to the noexec file is now specified in the sudo.conf
77 file instead of the sudoers file.
79 * On Solaris 10, the PRIV_PROC_EXEC privilege is now used to
80 implement the "noexec" feature. Previously, this was implemented
81 via the LD_PRELOAD environment variable.
83 * The exit values for "sudo -l", "sudo -v" and "sudo -l command"
84 have been fixed in the sudoers policy plugin.
86 * The sudoers policy plugin now passes the login class, if any,
87 back to the sudo front-end.
89 * The sudoers policy plugin was not being linked with requisite
90 libraries in certain configurations.
92 * Sudo now parses command line arguments before loading any plugins.
93 This allows "sudo -V" or "sudo -h" to work even if there is a problem
96 * Plugins are now linked with the static version of libgcc to allow
97 the plugin to run on a system where no shared libgcc is installed,
98 or where it is installed in a different location.
100 What's new in Sudo 1.8.0?
102 * Sudo has been refactored to use a modular framework that can
103 support third-party policy and I/O logging plugins. The default
104 plugin is "sudoers" which provides the traditional sudo functionality.
105 See the sudo_plugin manual for details on the plugin API and the
106 sample in the plugins directory for a simple example.
108 What's new in Sudo 1.7.5?
110 * When using visudo in check mode, a file named "-" may be used to
111 check sudoers data on the standard input.
113 * Sudo now only fetches shadow password entries when using the
114 password database directly for authentication.
116 * Password and group entries are now cached using the same key
117 that was used to look them up. This fixes a problem when looking
118 up entries by name if the name in the retrieved entry does not
119 match the name used to look it up. This may happen on some systems
120 that do case insensitive lookups or that truncate long names.
122 * GCC will no longer display warnings on glibc systems that use
123 the warn_unused_result attribute for write(2) and other system calls.
125 * If a PAM account management module denies access, sudo now prints
126 a more useful error message and stops trying to validate the user.
128 * Fixed a potential hang on idle systems when the sudo-run process
131 * Sudo now includes a copy of zlib that will be used on systems
132 that do not have zlib installed.
134 * The --with-umask-override configure flag has been added to enable
135 the "umask_override" sudoers Defaults option at build time.
137 * Sudo now unblocks all signals on startup to avoid problems caused
138 by the parent process changing the default signal mask.
140 * LDAP Sudoers entries may now specify a time period for which
141 the entry is valid. This requires an updated sudoers schema
142 that includes the sudoNotBefore and sudoNotAfter attributes.
143 Support for timed entries must be explicitly enabled in the
144 ldap.conf file. Based on changes from Andreas Mueller.
146 * LDAP Sudoers entries may now specify a sudoOrder attribute that
147 determines the order in which matching entries are applied. The
148 last matching entry is used, just like file-based sudoers. This
149 requires an updated sudoers schema that includes the sudoOrder
150 attribute. Based on changes from Andreas Mueller.
152 * When run as sudoedit, or when given the -e flag, sudo now treats
153 command line arguments as pathnames. This means that slashes
154 in the sudoers file entry must explicitly match slashes in
155 the command line arguments. As a result, and entry such as:
156 user ALL = sudoedit /etc/*
157 will allow editing of /etc/motd but not /etc/security/default.
159 * NETWORK_TIMEOUT is now an alias for BIND_TIMELIMIT in ldap.conf for
160 compatibility with OpenLDAP configuration files.
162 * The LDAP API TIMEOUT parameter is now honored in ldap.conf.
164 * The I/O log directory may now be specified in the sudoers file.
166 * Sudo will no longer refuse to run if the sudoers file is writable
169 * Sudo now performs command line escaping for "sudo -s" and "sudo -i"
170 after validating the command so the sudoers entries do not need
171 to include the backslashes.
173 * Logging and email sending are now done in the locale specified
174 by the "sudoers_locale" setting ("C" by default). Email send by
175 sudo now includes MIME headers when "sudoers_locale" is not "C".
177 * The configure script has a new option, --disable-env-reset, to
178 allow one to change the default for the sudoers Default setting
179 "env_reset" at compile time.
181 * When logging "sudo -l command", sudo will now prepend "list "
182 to the command in the log line to distinguish between an
183 actual command invocation in the logs.
185 * Double-quoted group and user names may now include escaped double
186 quotes as part of the name. Previously this was a parse error.
188 * Sudo once again restores the state of the signal handlers it
189 modifies before executing the command. This allows sudo to be
190 used with the nohup command.
192 * Resuming a suspended shell now works properly when I/O logging
193 is not enabled (the I/O logging case was already correct).
195 What's new in Sudo 1.7.4p6?
197 * A bug has been fixed in the I/O logging support that could cause
198 visual artifacts in full-screen programs such as text editors.
200 What's new in Sudo 1.7.4p5?
202 * A bug has been fixed that would allow a command to be run without the
203 user entering a password when sudo's -g flag is used without the -u flag.
205 * If user has no supplementary groups, sudo will now fall back on checking
206 the group file explicitly, which restores historic sudo behavior.
208 * A crash has been fixed when sudo's -g flag is used without the -u flag
209 and the sudoers file contains an entry with no runas user or group listed.
211 * A crash has been fixed when the Solaris project support is enabled
212 and sudo's -g flag is used without the -u flag.
214 * Sudo no longer exits with an error when support for auditing is
215 compiled in but auditing is not enabled.
217 * Fixed a bug introduced in sudo 1.7.3 where the ticket file was not
218 being honored when the "targetpw" sudoers Defaults option was enabled.
220 * The LOG_INPUT and LOG_OUTPUT tags in sudoers are now parsed correctly.
222 * A crash has been fixed in "sudo -l" when sudo is built with auditing
223 support and the user is not allowed to run any commands on the host.
225 What's new in Sudo 1.7.4p4?
227 * A potential security issue has been fixed with respect to the handling
228 of sudo's -g command line option when -u is also specified. The flaw
229 may allow an attacker to run commands as a user that is not authorized
232 * A bug has been fixed where "sudo -l" output was incomplete if multiple
233 sudoers sources were defined in nsswitch.conf and there was an error
234 querying one of the sources.
236 * The log_input, log_output, and use_pty sudoers options now work correctly
237 on AIX. Previously, sudo would hang if they were enabled.
239 * The "make install" target now works correctly when sudo is built in a
240 directory other than the source directory.
242 * The "runas_default" sudoers setting now works properly in a per-command
245 * Suspending and resuming the bash shell when PAM is in use now works
246 correctly. The SIGCONT signal was not propagated to the child process.
248 What's new in Sudo 1.7.4p3?
250 * A bug has been fixed where duplicate HOME environment variables could be
251 present when the env_reset setting was disabled and the always_set_home
252 setting was enabled in sudoers.
254 * The value of sysconfdir is now substituted into the path to the sudoers.d
255 directory in the installed sudoers file.
257 * Compilation problems on IRIX and other platforms have been fixed.
259 * If multiple PAM "auth" actions are specified and the user enters ^C at
260 the password prompt, sudo will no longer prompt for a password for any
261 subsequent "auth" actions. Previously it was necessary to enter ^C for
264 What's new in Sudo 1.7.4p2?
266 * A bug where sudo could spin in a busy loop waiting for the child process
269 What's new in Sudo 1.7.4p1?
271 * A bug introduced in sudo 1.7.3 that prevented the -k and -K options from
272 functioning when the tty_tickets sudoers option is enabled has been fixed.
274 * Sudo no longer prints a warning when the -k or -K options are specified
275 and the ticket file does not exist.
277 * It is now easier to cross-compile sudo.
279 What's new in Sudo 1.7.4?
281 * Sudoedit will now preserve the file extension in the name of the
282 temporary file being edited. The extension is used by some
283 editors (such as emacs) to choose the editing mode.
285 * Time stamp files have moved from /var/run/sudo to either /var/db/sudo,
286 /var/lib/sudo or /var/adm/sudo. The directories are checked for
287 existence in that order. This prevents users from receiving the
288 sudo lecture every time the system reboots. Time stamp files older
289 than the boot time are ignored on systems where it is possible to
292 * The tty_tickets sudoers option is now enabled by default.
294 * Ancillary documentation (README files, LICENSE, etc) is now installed
295 in a sudo documentation directory.
297 * Sudo now recognizes "tls_cacert" as an alias for "tls_cacertfile"
300 * Defaults settings that are tied to a user, host or command may
301 now include the negation operator. For example:
302 Defaults:!millert lecture
303 will match any user but millert.
305 * The default PATH environment variable, used when no PATH variable
306 exists, now includes /usr/sbin and /sbin.
308 * Sudo now uses polypkg (http://rc.quest.com/topics/polypkg/)
309 for cross-platform packing.
311 * On Linux, sudo will now restore the nproc resource limit before
312 executing a command, unless the limit appears to have been modified
313 by pam_limits. This avoids a problem with bash scripts that open
314 more than 32 descriptors on SuSE Linux, where sysconf(_SC_CHILD_MAX)
315 will return -1 when RLIMIT_NPROC is set to RLIMIT_UNLIMITED (-1).
317 * The HOME and MAIL environment variables are now reset based on the
318 target user's password database entry when the env_reset sudoers option
319 is enabled (which is the case in the default configuration). Users
320 wishing to preserve the original values should use a sudoers entry like:
321 Defaults env_keep += HOME
322 to preserve the old value of HOME and
323 Defaults env_keep += MAIL
324 to preserve the old value of MAIL.
326 * Fixed a problem in the restoration of the AIX authdb registry setting.
328 * Sudo will now fork(2) and wait until the command has completed before
329 calling pam_close_session().
331 * The default syslog facility is now "authpriv" if the operating system
332 supports it, else "auth".
334 What's new in Sudo 1.7.3?
336 * Support for logging I/O for the command being run.
337 For more information, see the documentation for the "log_input"
338 and "log_output" Defaults options in the sudoers manual. Also
339 see the sudoreplay manual for how to replay I/O log sessions.
341 * The use_pty sudoers option can be used to force a command to be
342 run in a pseudo-pty, even when I/O logging is not enabled.
344 * On some systems, sudo can now detect when a user has logged out
345 and back in again when tty-based time stamps are in use. Supported
346 systems include Solaris systems with the devices file system,
347 Mac OS X, and Linux systems with the devpts filesystem (pseudo-ttys
350 * On AIX systems, the registry setting in /etc/security/user is
351 now taken into account when looking up users and groups. Sudo
352 now applies the correct the user and group ids when running a
353 command as a user whose account details come from a different
354 source (e.g. LDAP or DCE vs. local files).
356 * Support for multiple 'sudoers_base' and 'uri' entries in ldap.conf.
357 When multiple entries are listed, sudo will try each one in the
358 order in which they are specified.
360 * Sudo's SELinux support should now function correctly when running
361 commands as a non-root user and when one of stdin, stdout or stderr
364 * Sudo will now use the Linux audit system with configure with
365 the --with-linux-audit flag.
367 * Sudo now uses mbr_check_membership() on systems that support it
368 to determine group membership. Currently, only Darwin (Mac OS X)
371 * When the tty_tickets sudoers option is enabled but there is no
372 terminal device, sudo will no longer use or create a tty-based
373 ticket file. Previously, sudo would use a tty name of "unknown".
374 As a consequence, if a user has no terminal device, sudo will
375 now always prompt for a password.
377 * The passwd_timeout and timestamp_timeout options may now be
378 specified as floating point numbers for more granular timeout
381 * Negating the fqdn option in sudoers now works correctly when sudo
382 is configured with the --with-fqdn option. In previous versions
383 of sudo the fqdn was set before sudoers was parsed.
385 What's new in Sudo 1.7.2?
387 * A new #includedir directive is available in sudoers. This can be
388 used to implement an /etc/sudo.d directory. Files in an includedir
389 are not edited by visudo unless they contain a syntax error.
391 * The -g option did not work properly when only setting the group
392 (and not the user). Also, in -l mode the wrong user was displayed
393 for sudoers entries where only the group was allowed to be set.
395 * Fixed a problem with the alias checking in visudo which
396 could prevent visudo from exiting.
398 * Sudo will now correctly parse the shell-style /etc/environment
399 file format used by pam_env on Linux.
401 * When doing password and group database lookups, sudo will only
402 cache an entry by name or by id, depending on how the entry was
403 looked up. Previously, sudo would cache by both name and id
404 from a single lookup, but this breaks sites that have multiple
405 password or group database names that map to the same uid or
408 * User and group names in sudoers may now be enclosed in double
409 quotes to avoid having to escape special characters.
411 * BSM audit fixes when changing to a non-root uid.
413 * Experimental non-Unix group support. Currently only works with
414 Quest Authorization Services and allows Active Directory groups
417 * For Netscape/Mozilla-derived LDAP SDKs the certificate and key
418 paths may be specified as a directory or a file. However, version
419 5.0 of the SDK only appears to support using a directory (despite
420 documentation to the contrary). If SSL client initialization
421 fails and the certificate or key paths look like they could be
422 default file name, strip off the last path element and try again.
424 * A setenv() compatibility fix for Linux systems, where a NULL
425 value is treated the same as an empty string and the variable
426 name is checked against the NULL pointer.
428 What's new in Sudo 1.7.1?
430 * A new Defaults option "pwfeedback" will cause sudo to provide visual
431 feedback when the user is entering a password.
433 * A new Defaults option "fast_glob" will cause sudo to use the fnmatch()
434 function for file name globbing instead of glob(). When this option
435 is enabled, sudo will not check the file system when expanding wildcards.
436 This is faster but a side effect is that relative paths with wildcard
439 * New BSM audit support for systems that support it such as FreeBSD
442 * The file name specified with the #include directive may now include
443 a %h escape which is expanded to the short form of hostname.
445 * The -k flag may now be specified along with a command, causing the
446 user's timestamp file to be ignored.
448 * New support for Tivoli-based LDAP START_TLS, present in AIX.
450 * New support for /etc/netsvc.conf on AIX.
452 * The unused alias checks in visudo now handle the case of an alias
453 referring to another alias.
455 What's new in Sudo 1.7.0?
457 * Rewritten parser that converts sudoers into a set of data structures.
458 This eliminates a number of ordering issues and makes it possible to
459 apply sudoers Defaults entries before searching for the command.
460 It also adds support for per-command Defaults specifications.
462 * Sudoers now supports a #include facility to allow the inclusion of other
463 sudoers-format files.
465 * Sudo's -l (list) flag has been enhanced:
466 o applicable Defaults options are now listed
467 o a command argument can be specified for testing whether a user
468 may run a specific command.
469 o a new -U flag can be used in conjunction with "sudo -l" to allow
470 root (or a user with "sudo ALL") list another user's privileges.
472 * A new -g flag has been added to allow the user to specify a
473 primary group to run the command as. The sudoers syntax has been
474 extended to include a group section in the Runas specification.
476 * A uid may now be used anywhere a username is valid.
478 * The "secure_path" run-time Defaults option has been restored.
480 * Password and group data is now cached for fast lookups.
482 * The file descriptor at which sudo starts closing all open files is now
483 configurable via sudoers and, optionally, the command line.
485 * Visudo will now warn about aliases that are defined but not used.
487 * The -i and -s command line flags now take an optional command
488 to be run via the shell. Previously, the argument was passed
489 to the shell as a script to run.
491 * Improved LDAP support. SASL authentication may now be used in
492 conjunction when connecting to an LDAP server. The krb5_ccname
493 parameter in ldap.conf may be used to enable Kerberos.
495 * Support for /etc/nsswitch.conf. LDAP users may now use nsswitch.conf
496 to specify the sudoers order. E.g.:
498 to check LDAP, then /etc/sudoers. The default is "files", even
499 when LDAP support is compiled in. This differs from sudo 1.6
500 where LDAP was always consulted first.
502 * Support for /etc/environment on AIX and Linux. If sudo is run
503 with the -i flag, the contents of /etc/environment are used to
504 populate the new environment that is passed to the command being
507 * If no terminal is available or if the new -A flag is specified,
508 sudo will use a helper program to read the password if one is
509 configured. Typically, this is a graphical password prompter
512 * A new Defaults option, "mailfrom" that sets the value of the
513 "From:" field in the warning/error mail. If unspecified, the
514 login name of the invoking user is used.
516 * A new Defaults option, "env_file" that refers to a file containing
517 environment variables to be set in the command being run.
519 * A new flag, -n, may be used to indicate that sudo should not
520 prompt the user for a password and, instead, exit with an error
521 if authentication is required.
523 * If sudo needs to prompt for a password and it is unable to disable
524 echo (and no askpass program is defined), it will refuse to run
525 unless the "visiblepw" Defaults option has been specified.
527 * Prior to version 1.7.0, hitting enter/return at the Password: prompt
528 would exit sudo. In sudo 1.7.0 and beyond, this is treated as
529 an empty password. To exit sudo, the user must press ^C or ^D
532 * visudo will now check the sudoers file owner and mode in -c (check)
533 mode when the -s (strict) flag is specified.
535 * A new Defaults option "umask_override" will cause sudo to set the
536 umask specified in sudoers even if it is more permissive than the
537 invoking user's umask.