2 Copyright (c) 1994-1996,1998-2004 Todd C. Miller <Todd.Miller@courtesan.com>
4 Permission to use, copy, modify, and distribute this software for any
5 purpose with or without fee is hereby granted, provided that the above
6 copyright notice and this permission notice appear in all copies.
8 THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES
9 WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF
10 MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR
11 ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES
12 WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN
13 ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF
14 OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.
15 ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
17 Sponsored in part by the Defense Advanced Research Projects
18 Agency (DARPA) and Air Force Research Laboratory, Air Force
19 Materiel Command, USAF, under agreement number F39502-99-1-0512.
21 $Sudo: sudoers.pod,v 1.96 2004/09/06 20:45:27 millert Exp $
26 sudoers - list of which users may execute what
30 The I<sudoers> file is composed of two types of entries: aliases
31 (basically variables) and user specifications (which specify who
34 When multiple entries match for a user, they are applied in order.
35 Where there are conflicting values, the last match is used (which
36 is not necessarily the most specific match).
38 The I<sudoers> grammar will be described below in Extended Backus-Naur
39 Form (EBNF). Don't despair if you don't know what EBNF is; it is
40 fairly simple, and the definitions below are annotated.
42 =head2 Quick guide to EBNF
44 EBNF is a concise and exact way of describing the grammar of a language.
45 Each EBNF definition is made up of I<production rules>. E.g.,
47 symbol ::= definition | alternate1 | alternate2 ...
49 Each I<production rule> references others and thus makes up a
50 grammar for the language. EBNF also contains the following
51 operators, which many readers will recognize from regular
52 expressions. Do not, however, confuse them with "wildcard"
53 characters, which have different meanings.
59 Means that the preceding symbol (or group of symbols) is optional.
60 That is, it may appear once or not at all.
64 Means that the preceding symbol (or group of symbols) may appear
69 Means that the preceding symbol (or group of symbols) may appear
74 Parentheses may be used to group symbols together. For clarity,
75 we will use single quotes ('') to designate what is a verbatim character
76 string (as opposed to a symbol name).
80 There are four kinds of aliases: C<User_Alias>, C<Runas_Alias>,
81 C<Host_Alias> and C<Cmnd_Alias>.
83 Alias ::= 'User_Alias' User_Alias (':' User_Alias)* |
84 'Runas_Alias' Runas_Alias (':' Runas_Alias)* |
85 'Host_Alias' Host_Alias (':' Host_Alias)* |
86 'Cmnd_Alias' Cmnd_Alias (':' Cmnd_Alias)*
88 User_Alias ::= NAME '=' User_List
90 Runas_Alias ::= NAME '=' Runas_List
92 Host_Alias ::= NAME '=' Host_List
94 Cmnd_Alias ::= NAME '=' Cmnd_List
96 NAME ::= [A-Z]([a-z][A-Z][0-9]_)*
98 Each I<alias> definition is of the form
100 Alias_Type NAME = item1, item2, ...
102 where I<Alias_Type> is one of C<User_Alias>, C<Runas_Alias>, C<Host_Alias>,
103 or C<Cmnd_Alias>. A C<NAME> is a string of uppercase letters, numbers,
104 and underscore characters ('_'). A C<NAME> B<must> start with an
105 uppercase letter. It is possible to put several alias definitions
106 of the same type on a single line, joined by a colon (':'). E.g.,
108 Alias_Type NAME = item1, item2, item3 : NAME = item4, item5
110 The definitions of what constitutes a valid I<alias> member follow.
115 User ::= '!'* username |
120 A C<User_List> is made up of one or more usernames, system groups
121 (prefixed with '%'), netgroups (prefixed with '+') and other aliases.
122 Each list item may be prefixed with one or more '!' operators.
123 An odd number of '!' operators negate the value of the item; an even
124 number just cancel each other out.
126 Runas_List ::= Runas_User |
127 Runas_User ',' Runas_List
129 Runas_User ::= '!'* username |
135 A C<Runas_List> is similar to a C<User_List> except that it can
136 also contain uids (prefixed with '#') and instead of C<User_Alias>es
137 it can contain C<Runas_Alias>es. Note that usernames and groups
138 are matched as strings. In other words, two users (groups) with
139 the same uid (gid) are considered to be distinct. If you wish to
140 match all usernames with the same uid (e.g. root and toor), you
141 can use a uid instead (#0 in the example given).
146 Host ::= '!'* hostname |
148 '!'* network(/netmask)? |
152 A C<Host_List> is made up of one or more hostnames, IP addresses,
153 network numbers, netgroups (prefixed with '+') and other aliases.
154 Again, the value of an item may be negated with the '!' operator.
155 If you do not specify a netmask with a network number, the netmask
156 of the host's ethernet interface(s) will be used when matching.
157 The netmask may be specified either in dotted quad notation (e.g.
158 255.255.255.0) or CIDR notation (number of bits, e.g. 24). A hostname
159 may include shell-style wildcards (see the L<Wildcards> section below),
160 but unless the C<hostname> command on your machine returns the fully
161 qualified hostname, you'll need to use the I<fqdn> option for wildcards
167 commandname ::= filename |
171 Cmnd ::= '!'* commandname |
176 A C<Cmnd_List> is a list of one or more commandnames, directories, and other
177 aliases. A commandname is a fully qualified filename which may include
178 shell-style wildcards (see the L<Wildcards> section below). A simple
179 filename allows the user to run the command with any arguments he/she
180 wishes. However, you may also specify command line arguments (including
181 wildcards). Alternately, you can specify C<""> to indicate that the command
182 may only be run B<without> command line arguments. A directory is a
183 fully qualified pathname ending in a '/'. When you specify a directory
184 in a C<Cmnd_List>, the user will be able to run any file within that directory
185 (but not in any subdirectories therein).
187 If a C<Cmnd> has associated command line arguments, then the arguments
188 in the C<Cmnd> must match exactly those given by the user on the command line
189 (or match the wildcards if there are any). Note that the following
190 characters must be escaped with a '\' if they are used in command
191 arguments: ',', ':', '=', '\'. The special command C<"sudoedit">
192 is used to permit a user to run B<sudo> with the B<-e> flag (or
193 as B<sudoedit>). It may take command line arguments just as
194 a normal command does.
198 Certain configuration options may be changed from their default
199 values at runtime via one or more C<Default_Entry> lines. These
200 may affect all users on any host, all users on a specific host, a
201 specific user, or commands being run as a specific user.
203 Default_Type ::= 'Defaults' |
204 'Defaults' '@' Host |
205 'Defaults' ':' User |
206 'Defaults' '>' RunasUser
208 Default_Entry ::= Default_Type Parameter_List
210 Parameter_List ::= Parameter |
211 Parameter ',' Parameter_List
213 Parameter ::= Parameter '=' Value |
214 Parameter '+=' Value |
215 Parameter '-=' Value |
218 Parameters may be B<flags>, B<integer> values, B<strings>, or B<lists>.
219 Flags are implicitly boolean and can be turned off via the '!'
220 operator. Some integer, string and list parameters may also be
221 used in a boolean context to disable them. Values may be enclosed
222 in double quotes (C<">) when they contain multiple words. Special
223 characters may be escaped with a backslash (C<\>).
225 Lists have two additional assignment operators, C<+=> and C<-=>.
226 These operators are used to add to and delete from a list respectively.
227 It is not an error to use the C<-=> operator to remove an element
228 that does not exist in a list.
234 =item long_otp_prompt
236 When validating with a One Time Password scheme (B<S/Key> or B<OPIE>),
237 a two-line prompt is used to make it easier to cut and paste the
238 challenge to a local window. It's not as pretty as the default but
239 some people find it more convenient. This flag is I<@long_otp_prompt@>
244 If set, B<sudo> will ignore '.' or '' (current dir) in the C<PATH>
245 environment variable; the C<PATH> itself is not modified. This
246 flag is I<@ignore_dot@> by default. Currently, while it is possible
247 to set I<ignore_dot> in I<sudoers>, its value is not used. This option
248 should be considered read-only (it will be fixed in a future version
253 Send mail to the I<mailto> user every time a users runs B<sudo>.
254 This flag is I<off> by default.
258 Send mail to the I<mailto> user if the user running sudo does not
259 enter the correct password. This flag is I<off> by default.
263 If set, mail will be sent to the I<mailto> user if the invoking
264 user is not in the I<sudoers> file. This flag is I<@mail_no_user@>
269 If set, mail will be sent to the I<mailto> user if the invoking
270 user exists in the I<sudoers> file, but is not allowed to run
271 commands on the current host. This flag is I<@mail_no_host@> by default.
275 If set, mail will be sent to the I<mailto> user if the invoking
276 user is allowed to use B<sudo> but the command they are trying is not
277 listed in their I<sudoers> file entry or is explicitly denied.
278 This flag is I<@mail_no_perms@> by default.
282 If set, users must authenticate on a per-tty basis. Normally,
283 B<sudo> uses a directory in the ticket dir with the same name as
284 the user running it. With this flag enabled, B<sudo> will use a
285 file named for the tty the user is logged in on in that directory.
286 This flag is I<@tty_tickets@> by default.
290 If set, users must authenticate themselves via a password (or other
291 means of authentication) before they may run commands. This default
292 may be overridden via the C<PASSWD> and C<NOPASSWD> tags.
293 This flag is I<on> by default.
297 If set, root is allowed to run B<sudo> too. Disabling this prevents users
298 from "chaining" B<sudo> commands to get a root shell by doing something
299 like C<"sudo sudo /bin/sh">. Note, however, that turning off I<root_sudo>
300 will also prevent root and from running B<sudoedit>.
301 Disabling I<root_sudo> provides no real additional security; it
302 exists purely for historical reasons.
303 This flag is I<@root_sudo@> by default.
307 If set, the hostname will be logged in the (non-syslog) B<sudo> log file.
308 This flag is I<off> by default.
312 If set, the four-digit year will be logged in the (non-syslog) B<sudo> log file.
313 This flag is I<off> by default.
317 If set and B<sudo> is invoked with no arguments it acts as if the
318 B<-s> flag had been given. That is, it runs a shell as root (the
319 shell is determined by the C<SHELL> environment variable if it is
320 set, falling back on the shell listed in the invoking user's
321 /etc/passwd entry if not). This flag is I<off> by default.
325 If set and B<sudo> is invoked with the B<-s> flag the C<HOME>
326 environment variable will be set to the home directory of the target
327 user (which is root unless the B<-u> option is used). This effectively
328 makes the B<-s> flag imply B<-H>. This flag is I<off> by default.
330 =item always_set_home
332 If set, B<sudo> will set the C<HOME> environment variable to the home
333 directory of the target user (which is root unless the B<-u> option is used).
334 This effectively means that the B<-H> flag is always implied.
335 This flag is I<off> by default.
339 Normally, B<sudo> will tell the user when a command could not be
340 found in their C<PATH> environment variable. Some sites may wish
341 to disable this as it could be used to gather information on the
342 location of executables that the normal user does not have access
343 to. The disadvantage is that if the executable is simply not in
344 the user's C<PATH>, B<sudo> will tell the user that they are not
345 allowed to run it, which can be confusing. This flag is I<off> by
348 =item preserve_groups
350 By default B<sudo> will initialize the group vector to the list of
351 groups the target user is in. When I<preserve_groups> is set, the
352 user's existing group vector is left unaltered. The real and
353 effective group IDs, however, are still set to match the target
354 user. This flag is I<off> by default.
358 Set this flag if you want to put fully qualified hostnames in the
359 I<sudoers> file. I.e., instead of myhost you would use myhost.mydomain.edu.
360 You may still use the short form if you wish (and even mix the two).
361 Beware that turning on I<fqdn> requires B<sudo> to make DNS lookups
362 which may make B<sudo> unusable if DNS stops working (for example
363 if the machine is not plugged into the network). Also note that
364 you must use the host's official name as DNS knows it. That is,
365 you may not use a host alias (C<CNAME> entry) due to performance
366 issues and the fact that there is no way to get all aliases from
367 DNS. If your machine's hostname (as returned by the C<hostname>
368 command) is already fully qualified you shouldn't need to set
369 I<fqdn>. This flag is I<@fqdn@> by default.
373 If set, B<sudo> will insult users when they enter an incorrect
374 password. This flag is I<@insults@> by default.
378 If set, B<sudo> will only run when the user is logged in to a real
379 tty. This will disallow things like C<"rsh somehost sudo ls"> since
380 L<rsh(1)> does not allocate a tty. Because it is not possible to turn
381 off echo when there is no tty present, some sites may with to set
382 this flag to prevent a user from entering a visible password. This
383 flag is I<off> by default.
387 If set, B<visudo> will use the value of the EDITOR or VISUAL
388 environment variables before falling back on the default editor list.
389 Note that this may create a security hole as it allows the user to
390 run any arbitrary command as root without logging. A safer alternative
391 is to place a colon-separated list of editors in the C<editor>
392 variable. B<visudo> will then only use the EDITOR or VISUAL if
393 they match a value specified in C<editor>. This flag is C<@env_editor@> by
398 If set, B<sudo> will prompt for the root password instead of the password
399 of the invoking user. This flag is I<off> by default.
403 If set, B<sudo> will prompt for the password of the user defined by the
404 I<runas_default> option (defaults to C<@runas_default@>) instead of the
405 password of the invoking user. This flag is I<off> by default.
409 If set, B<sudo> will prompt for the password of the user specified by
410 the B<-u> flag (defaults to C<root>) instead of the password of the
411 invoking user. Note that this precludes the use of a uid not listed
412 in the passwd database as an argument to the B<-u> flag.
413 This flag is I<off> by default.
417 Normally, B<sudo> will set the C<LOGNAME> and C<USER> environment variables
418 to the name of the target user (usually root unless the B<-u> flag is given).
419 However, since some programs (including the RCS revision control system)
420 use C<LOGNAME> to determine the real identity of the user, it may be desirable
421 to change this behavior. This can be done by negating the set_logname option.
425 Normally, when B<sudo> executes a command the real and effective
426 UIDs are set to the target user (root by default). This option
427 changes that behavior such that the real UID is left as the invoking
428 user's UID. In other words, this makes B<sudo> act as a setuid
429 wrapper. This can be useful on systems that disable some potentially
430 dangerous functionality when a program is run setuid. Note, however,
431 that this means that sudo will run with the real uid of the invoking
432 user which may allow that user to kill B<sudo> before it can log a
433 failure, depending on how your OS defines the interaction between
434 signals and setuid processes.
438 If set, B<sudo> will reset the environment to only contain the
439 following variables: C<HOME>, C<LOGNAME>, C<PATH>, C<SHELL>, C<TERM>,
440 and C<USER> (in addition to the C<SUDO_*> variables).
441 Of these, only C<TERM> is copied unaltered from the old environment.
442 The other variables are set to default values (possibly modified
443 by the value of the I<set_logname> option). If B<sudo> was compiled
444 with the C<SECURE_PATH> option, its value will be used for the C<PATH>
445 environment variable.
446 Other variables may be preserved with the I<env_keep> option.
450 If set, B<sudo> will apply the defaults specified for the target user's
451 login class if one exists. Only available if B<sudo> is configured with
452 the --with-logincap option. This flag is I<off> by default.
456 If set, all commands run via sudo will behave as if the C<NOEXEC>
457 tag has been set, unless overridden by a C<EXEC> tag. See the
458 description of I<NOEXEC and EXEC> below as well as the L<PREVENTING SHELL
459 ESCAPES> section at the end of this manual. This flag is I<off> by default.
461 =item ignore_local_sudoers
463 If set via LDAP, parsing of @sysconfdir@/sudoers will be skipped.
464 This is intended for an Enterprises that wish to prevent the usage of local
465 sudoers files so that only LDAP is used. This thwarts the efforts of
466 rogue operators who would attempt to add roles to @sysconfdir@/sudoers.
467 When this option is present, @sysconfdir@/sudoers does not even need to exist.
468 Since this options tells sudo how to behave when no specific LDAP entries
469 have been matched, this sudoOption is only meaningful for the cn=defaults
470 section. This flag is I<off> by default.
480 The number of tries a user gets to enter his/her password before
481 B<sudo> logs the failure and exits. The default is C<@passwd_tries@>.
485 B<Integers that can be used in a boolean context>:
491 Number of characters per line for the file log. This value is used
492 to decide when to wrap lines for nicer log files. This has no
493 effect on the syslog log file, only the file log. The default is
494 C<@loglen@> (use 0 or negate the option to disable word wrap).
496 =item timestamp_timeout
498 Number of minutes that can elapse before B<sudo> will ask for a
499 passwd again. The default is C<@timeout@>. Set this to C<0> to always
500 prompt for a password.
501 If set to a value less than C<0> the user's timestamp will never
502 expire. This can be used to allow users to create or delete their
503 own timestamps via C<sudo -v> and C<sudo -k> respectively.
507 Number of minutes before the B<sudo> password prompt times out.
508 The default is C<@password_timeout@>, set this to C<0> for no password timeout.
512 Umask to use when running the command. Negate this option or set
513 it to 0777 to preserve the user's umask. The default is C<@sudo_umask@>.
523 Subject of the mail sent to the I<mailto> user. The escape C<%h>
524 will expand to the hostname of the machine.
525 Default is C<@mailsub@>.
527 =item badpass_message
529 Message that is displayed if a user enters an incorrect password.
530 The default is C<@badpass_message@> unless insults are enabled.
534 The directory in which B<sudo> stores its timestamp files.
535 The default is F<@timedir@>.
539 The owner of the timestamp directory and the timestamps stored therein.
540 The default is C<root>.
544 The default prompt to use when asking for a password; can be overridden
545 via the B<-p> option or the C<SUDO_PROMPT> environment variable.
546 The following percent (`C<%>') escapes are supported:
552 expanded to the invoking user's login name
556 expanded to the login name of the user the command will
557 be run as (defaults to root)
561 expanded to the local hostname without the domain name
565 expanded to the local hostname including the domain name
566 (on if the machine's hostname is fully qualified or the I<fqdn>
571 two consecutive C<%> characters are collaped into a single C<%> character
575 The default value is C<@passprompt@>.
579 The default user to run commands as if the B<-u> flag is not specified
580 on the command line. This defaults to C<@runas_default@>.
581 Note that if I<runas_default> is set it B<must> occur before
582 any C<Runas_Alias> specifications.
586 Syslog priority to use when user authenticates successfully.
587 Defaults to C<@goodpri@>.
591 Syslog priority to use when user authenticates unsuccessfully.
592 Defaults to C<@badpri@>.
596 A colon (':') separated list of editors allowed to be used with
597 B<visudo>. B<visudo> will choose the editor that matches the user's
598 USER environment variable if possible, or the first editor in the
599 list that exists and is executable. The default is the path to vi
604 Path to a shared library containing dummy versions of the execv(),
605 execve() and fexecve() library functions that just return an error.
606 This is used to implement the I<noexec> functionality on systems that
607 support C<LD_PRELOAD> or its equivalent. Defaults to F<@noexec_file@>.
611 B<Strings that can be used in a boolean context>:
617 This option controls when a short lecture will be printed along with
618 the password prompt. It has the following possible values:
624 Never lecture the user.
628 Only lecture the user the first time they run B<sudo>.
632 Always lecture the user.
636 If no value is specified, a value of I<once> is implied.
637 Negating the option results in a value of I<never> being used.
638 The default value is I<@lecture@>.
642 Path to a file containing an alternate sudo lecture that will
643 be used in place of the standard lecture if the named file exists.
647 Path to the B<sudo> log file (not the syslog log file). Setting a path
648 turns on logging to a file; negating this option turns it off.
652 Syslog facility if syslog is being used for logging (negate to
653 disable syslog logging). Defaults to C<@logfac@>.
657 Path to mail program used to send warning mail.
658 Defaults to the path to sendmail found at configure time.
662 Flags to use when invoking mailer. Defaults to B<-t>.
666 Address to send warning and error mail to. The address should
667 be enclosed in double quotes (C<">) to protect against sudo
668 interpreting the C<@> sign. Defaults to C<@mailto@>.
672 Users in this group are exempt from password and PATH requirements. This
673 option is turned on for Debian.
677 This option controls when a password will be required when a user runs
678 B<sudo> with the B<-v> flag. It has the following possible values:
684 All the user's I<sudoers> entries for the current host must have
685 the C<NOPASSWD> flag set to avoid entering a password.
689 At least one of the user's I<sudoers> entries for the current host
690 must have the C<NOPASSWD> flag set to avoid entering a password.
694 The user need never enter a password to use the B<-v> flag.
698 The user must always enter a password to use the B<-v> flag.
702 If no value is specified, a value of I<all> is implied.
703 Negating the option results in a value of I<never> being used.
704 The default value is I<all>.
708 This option controls when a password will be required when a
709 user runs B<sudo> with the B<-l> flag. It has the following possible values:
715 All the user's I<sudoers> entries for the current host must have
716 the C<NOPASSWD> flag set to avoid entering a password.
720 At least one of the user's I<sudoers> entries for the current host
721 must have the C<NOPASSWD> flag set to avoid entering a password.
725 The user need never enter a password to use the B<-l> flag.
729 The user must always enter a password to use the B<-l> flag.
733 If no value is specified, a value of I<any> is implied.
734 Negating the option results in a value of I<never> being used.
735 The default value is I<any>.
739 B<Lists that can be used in a boolean context>:
745 Environment variables to be removed from the user's environment if
746 the variable's value contains C<%> or C</> characters. This can
747 be used to guard against printf-style format vulnerabilities in
748 poorly-written programs. The argument may be a double-quoted,
749 space-separated list or a single value without double-quotes. The
750 list can be replaced, added to, deleted from, or disabled by using
751 the C<=>, C<+=>, C<-=>, and C<!> operators respectively. The default
752 list of environment variables to check is printed when B<sudo> is
753 run by root with the I<-V> option.
757 Environment variables to be removed from the user's environment.
758 The argument may be a double-quoted, space-separated list or a
759 single value without double-quotes. The list can be replaced, added
760 to, deleted from, or disabled by using the C<=>, C<+=>, C<-=>, and
761 C<!> operators respectively. The default list of environment
762 variables to remove is printed when B<sudo> is run by root with the
763 I<-V> option. Note that many operating systems will remove potentially
764 dangerous variables from the environment of any setuid process (such
769 Environment variables to be preserved in the user's environment
770 when the I<env_reset> option is in effect. This allows fine-grained
771 control over the environment B<sudo>-spawned processes will receive.
772 The argument may be a double-quoted, space-separated list or a
773 single value without double-quotes. The list can be replaced, added
774 to, deleted from, or disabled by using the C<=>, C<+=>, C<-=>, and
775 C<!> operators respectively. This list has no default members.
779 When logging via L<syslog(3)>, B<sudo> accepts the following values
780 for the syslog facility (the value of the B<syslog> Parameter):
781 B<authpriv> (if your OS supports it), B<auth>, B<daemon>, B<user>,
782 B<local0>, B<local1>, B<local2>, B<local3>, B<local4>, B<local5>,
783 B<local6>, and B<local7>. The following syslog priorities are
784 supported: B<alert>, B<crit>, B<debug>, B<emerg>, B<err>, B<info>,
785 B<notice>, and B<warning>.
787 =head2 User Specification
789 User_Spec ::= User_List Host_List '=' Cmnd_Spec_List \
790 (':' Host_List '=' Cmnd_Spec_List)*
792 Cmnd_Spec_List ::= Cmnd_Spec |
793 Cmnd_Spec ',' Cmnd_Spec_List
795 Cmnd_Spec ::= Runas_Spec? Tag_Spec* Cmnd
797 Runas_Spec ::= '(' Runas_List ')'
799 Tag_Spec ::= ('NOPASSWD:' | 'PASSWD:' | 'NOEXEC:' | 'EXEC:')
801 A B<user specification> determines which commands a user may run
802 (and as what user) on specified hosts. By default, commands are
803 run as B<root>, but this can be changed on a per-command basis.
805 Let's break that down into its constituent parts:
809 A C<Runas_Spec> is simply a C<Runas_List> (as defined above)
810 enclosed in a set of parentheses. If you do not specify a
811 C<Runas_Spec> in the user specification, a default C<Runas_Spec>
812 of B<root> will be used. A C<Runas_Spec> sets the default for
813 commands that follow it. What this means is that for the entry:
815 dgb boulder = (operator) /bin/ls, /bin/kill, /usr/bin/lprm
817 The user B<dgb> may run F</bin/ls>, F</bin/kill>, and
818 F</usr/bin/lprm> -- but only as B<operator>. E.g.,
820 $ sudo -u operator /bin/ls.
822 It is also possible to override a C<Runas_Spec> later on in an
823 entry. If we modify the entry like so:
825 dgb boulder = (operator) /bin/ls, (root) /bin/kill, /usr/bin/lprm
827 Then user B<dgb> is now allowed to run F</bin/ls> as B<operator>,
828 but F</bin/kill> and F</usr/bin/lprm> as B<root>.
832 A command may have zero or more tags associated with it. There are
833 four possible tag values, C<NOPASSWD>, C<PASSWD>, C<NOEXEC>, C<EXEC>.
834 Once a tag is set on a C<Cmnd>, subsequent C<Cmnd>s in the
835 C<Cmnd_Spec_List>, inherit the tag unless it is overridden by the
836 opposite tag (ie: C<PASSWD> overrides C<NOPASSWD> and C<EXEC>
837 overrides C<NOEXEC>).
839 =head3 NOPASSWD and PASSWD
841 By default, B<sudo> requires that a user authenticate him or herself
842 before running a command. This behavior can be modified via the
843 C<NOPASSWD> tag. Like a C<Runas_Spec>, the C<NOPASSWD> tag sets
844 a default for the commands that follow it in the C<Cmnd_Spec_List>.
845 Conversely, the C<PASSWD> tag can be used to reverse things.
848 ray rushmore = NOPASSWD: /bin/kill, /bin/ls, /usr/bin/lprm
850 would allow the user B<ray> to run F</bin/kill>, F</bin/ls>, and
851 F</usr/bin/lprm> as root on the machine rushmore as B<root> without
852 authenticating himself. If we only want B<ray> to be able to
853 run F</bin/kill> without a password the entry would be:
855 ray rushmore = NOPASSWD: /bin/kill, PASSWD: /bin/ls, /usr/bin/lprm
857 Note, however, that the C<PASSWD> tag has no effect on users who are
858 in the group specified by the exempt_group option.
860 By default, if the C<NOPASSWD> tag is applied to any of the entries
861 for a user on the current host, he or she will be able to run
862 C<sudo -l> without a password. Additionally, a user may only run
863 C<sudo -v> without a password if the C<NOPASSWD> tag is present
864 for all a user's entries that pertain to the current host.
865 This behavior may be overridden via the verifypw and listpw options.
867 =head3 NOEXEC and EXEC
869 If sudo has been compiled with I<noexec> support and the underlying
870 operating system support it, the C<NOEXEC> tag can be used to prevent
871 a dynamically-linked executable from running further commands itself.
873 In the following example, user B<aaron> may run F</usr/bin/more>
874 and F</usr/bin/vi> but shell escapes will be disabled.
876 aaron shanty = NOEXEC: /usr/bin/more, /usr/bin/vi
878 See the L<PREVENTING SHELL ESCAPES> section below for more details
879 on how I<noexec> works and whether or not it will work on your system.
883 B<sudo> allows shell-style I<wildcards> (aka meta or glob characters)
884 to be used in pathnames as well as command line arguments in the
885 I<sudoers> file. Wildcard matching is done via the B<POSIX>
886 L<fnmatch(3)> routine. Note that these are I<not> regular expressions.
892 Matches any set of zero or more characters.
896 Matches any single character.
900 Matches any character in the specified range.
904 Matches any character B<not> in the specified range.
908 For any character "x", evaluates to "x". This is used to
909 escape special characters such as: "*", "?", "[", and "}".
913 Note that a forward slash ('/') will B<not> be matched by
914 wildcards used in the pathname. When matching the command
915 line arguments, however, a slash B<does> get matched by
916 wildcards. This is to make a path like:
920 match F</usr/bin/who> but not F</usr/bin/X11/xterm>.
922 WARNING: a pathname with wildcards will B<not> match a user command
923 that consists of a relative path. In other words, given the
924 following I<sudoers> entry:
926 billy workstation = /usr/bin/*
928 user billy will be able to run any command in /usr/bin as root, such
929 as F</usr/bin/w>. The following two command will be allowed (the first
930 assumes that F</usr/bin> is in the user's path):
935 However, this will not:
940 For this reason you should only B<grant> access to commands using
941 wildcards and never B<restrict> access using them. This limitation
942 will be removed in a future version of B<sudo>.
944 =head2 Exceptions to wildcard rules
946 The following exceptions apply to the above rules:
952 If the empty string C<""> is the only command line argument in the
953 I<sudoers> entry it means that command is not allowed to be run
954 with B<any> arguments.
958 =head2 Other special characters and reserved words
960 The pound sign ('#') is used to indicate a comment (unless it
961 occurs in the context of a user name and is followed by one or
962 more digits, in which case it is treated as a uid). Both the
963 comment character and any text after it, up to the end of the line,
966 The reserved word B<ALL> is a built-in I<alias> that always causes
967 a match to succeed. It can be used wherever one might otherwise
968 use a C<Cmnd_Alias>, C<User_Alias>, C<Runas_Alias>, or C<Host_Alias>.
969 You should not try to define your own I<alias> called B<ALL> as the
970 built-in alias will be used in preference to your own. Please note
971 that using B<ALL> can be dangerous since in a command context, it
972 allows the user to run B<any> command on the system.
974 An exclamation point ('!') can be used as a logical I<not> operator
975 both in an I<alias> and in front of a C<Cmnd>. This allows one to
976 exclude certain values. Note, however, that using a C<!> in
977 conjunction with the built-in C<ALL> alias to allow a user to
978 run "all but a few" commands rarely works as intended (see SECURITY
981 Long lines can be continued with a backslash ('\') as the last
982 character on the line.
984 Whitespace between elements in a list as well as special syntactic
985 characters in a I<User Specification> ('=', ':', '(', ')') is optional.
987 The following characters must be escaped with a backslash ('\') when
988 used as part of a word (e.g. a username or hostname):
989 '@', '!', '=', ':', ',', '(', ')', '\'.
993 @sysconfdir@/sudoers List of who can run what
994 /etc/group Local groups file
995 /etc/netgroup List of network groups
999 Since the I<sudoers> file is parsed in a single pass, order is
1000 important. In general, you should structure I<sudoers> such that
1001 the C<Host_Alias>, C<User_Alias>, and C<Cmnd_Alias> specifications
1002 come first, followed by any C<Default_Entry> lines, and finally the
1003 C<Runas_Alias> and user specifications. The basic rule of thumb
1004 is you cannot reference an Alias that has not already been defined.
1006 Below are example I<sudoers> entries. Admittedly, some of
1007 these are a bit contrived. First, we define our I<aliases>:
1009 # User alias specification
1010 User_Alias FULLTIMERS = millert, mikef, dowdy
1011 User_Alias PARTTIMERS = bostley, jwfox, crawl
1012 User_Alias WEBMASTERS = will, wendy, wim
1014 # Runas alias specification
1015 Runas_Alias OP = root, operator
1016 Runas_Alias DB = oracle, sybase
1018 # Host alias specification
1019 Host_Alias SPARC = bigtime, eclipse, moet, anchor :\
1020 SGI = grolsch, dandelion, black :\
1021 ALPHA = widget, thalamus, foobar :\
1022 HPPA = boa, nag, python
1023 Host_Alias CUNETS = 128.138.0.0/255.255.0.0
1024 Host_Alias CSNETS = 128.138.243.0, 128.138.204.0/24, 128.138.242.0
1025 Host_Alias SERVERS = master, mail, www, ns
1026 Host_Alias CDROM = orion, perseus, hercules
1028 # Cmnd alias specification
1029 Cmnd_Alias DUMPS = /usr/bin/mt, /usr/sbin/dump, /usr/sbin/rdump,\
1030 /usr/sbin/restore, /usr/sbin/rrestore
1031 Cmnd_Alias KILL = /usr/bin/kill
1032 Cmnd_Alias PRINTING = /usr/sbin/lpc, /usr/bin/lprm
1033 Cmnd_Alias SHUTDOWN = /usr/sbin/shutdown
1034 Cmnd_Alias HALT = /usr/sbin/halt
1035 Cmnd_Alias REBOOT = /usr/sbin/reboot
1036 Cmnd_Alias SHELLS = /usr/bin/sh, /usr/bin/csh, /usr/bin/ksh, \
1037 /usr/local/bin/tcsh, /usr/bin/rsh, \
1039 Cmnd_Alias SU = /usr/bin/su
1041 Here we override some of the compiled in default values. We want
1042 B<sudo> to log via L<syslog(3)> using the I<auth> facility in all
1043 cases. We don't want to subject the full time staff to the B<sudo>
1044 lecture, user B<millert> need not give a password, and we don't
1045 want to reset the C<LOGNAME> or C<USER> environment variables when
1046 running commands as root. Additionally, on the machines in the
1047 I<SERVERS> C<Host_Alias>, we keep an additional local log file and
1048 make sure we log the year in each log line since the log entries
1049 will be kept around for several years.
1051 # Override built-in defaults
1052 Defaults syslog=auth
1053 Defaults>root !set_logname
1054 Defaults:FULLTIMERS !lecture
1055 Defaults:millert !authenticate
1056 Defaults@SERVERS log_year, logfile=/var/log/sudo.log
1058 The I<User specification> is the part that actually determines who may
1061 root ALL = (ALL) ALL
1062 %wheel ALL = (ALL) ALL
1064 We let B<root> and any user in group B<wheel> run any command on any
1067 FULLTIMERS ALL = NOPASSWD: ALL
1069 Full time sysadmins (B<millert>, B<mikef>, and B<dowdy>) may run any
1070 command on any host without authenticating themselves.
1072 PARTTIMERS ALL = ALL
1074 Part time sysadmins (B<bostley>, B<jwfox>, and B<crawl>) may run any
1075 command on any host but they must authenticate themselves first
1076 (since the entry lacks the C<NOPASSWD> tag).
1080 The user B<jack> may run any command on the machines in the I<CSNETS> alias
1081 (the networks C<128.138.243.0>, C<128.138.204.0>, and C<128.138.242.0>).
1082 Of those networks, only C<128.138.204.0> has an explicit netmask (in
1083 CIDR notation) indicating it is a class C network. For the other
1084 networks in I<CSNETS>, the local machine's netmask will be used
1089 The user B<lisa> may run any command on any host in the I<CUNETS> alias
1090 (the class B network C<128.138.0.0>).
1092 operator ALL = DUMPS, KILL, SHUTDOWN, HALT, REBOOT, PRINTING,\
1093 sudoedit /etc/printcap, /usr/oper/bin/
1095 The B<operator> user may run commands limited to simple maintenance.
1096 Here, those are commands related to backups, killing processes, the
1097 printing system, shutting down the system, and any commands in the
1098 directory F</usr/oper/bin/>.
1100 joe ALL = /usr/bin/su operator
1102 The user B<joe> may only L<su(1)> to operator.
1104 pete HPPA = /usr/bin/passwd [A-z]*, !/usr/bin/passwd root
1106 The user B<pete> is allowed to change anyone's password except for
1107 root on the I<HPPA> machines. Note that this assumes L<passwd(1)>
1108 does not take multiple usernames on the command line.
1110 bob SPARC = (OP) ALL : SGI = (OP) ALL
1112 The user B<bob> may run anything on the I<SPARC> and I<SGI> machines
1113 as any user listed in the I<OP> C<Runas_Alias> (B<root> and B<operator>).
1117 The user B<jim> may run any command on machines in the I<biglab> netgroup.
1118 B<Sudo> knows that "biglab" is a netgroup due to the '+' prefix.
1120 +secretaries ALL = PRINTING, /usr/bin/adduser, /usr/bin/rmuser
1122 Users in the B<secretaries> netgroup need to help manage the printers
1123 as well as add and remove users, so they are allowed to run those
1124 commands on all machines.
1126 fred ALL = (DB) NOPASSWD: ALL
1128 The user B<fred> can run commands as any user in the I<DB> C<Runas_Alias>
1129 (B<oracle> or B<sybase>) without giving a password.
1131 john ALPHA = /usr/bin/su [!-]*, !/usr/bin/su *root*
1133 On the I<ALPHA> machines, user B<john> may su to anyone except root
1134 but he is not allowed to give L<su(1)> any flags.
1136 jen ALL, !SERVERS = ALL
1138 The user B<jen> may run any command on any machine except for those
1139 in the I<SERVERS> C<Host_Alias> (master, mail, www and ns).
1141 jill SERVERS = /usr/bin/, !SU, !SHELLS
1143 For any machine in the I<SERVERS> C<Host_Alias>, B<jill> may run
1144 any commands in the directory /usr/bin/ except for those commands
1145 belonging to the I<SU> and I<SHELLS> C<Cmnd_Aliases>.
1147 steve CSNETS = (operator) /usr/local/op_commands/
1149 The user B<steve> may run any command in the directory /usr/local/op_commands/
1150 but only as user operator.
1152 matt valkyrie = KILL
1154 On his personal workstation, valkyrie, B<matt> needs to be able to
1155 kill hung processes.
1157 WEBMASTERS www = (www) ALL, (root) /usr/bin/su www
1159 On the host www, any user in the I<WEBMASTERS> C<User_Alias> (will,
1160 wendy, and wim), may run any command as user www (which owns the
1161 web pages) or simply L<su(1)> to www.
1163 ALL CDROM = NOPASSWD: /sbin/umount /CDROM,\
1164 /sbin/mount -o nosuid\,nodev /dev/cd0a /CDROM
1166 Any user may mount or unmount a CD-ROM on the machines in the CDROM
1167 C<Host_Alias> (orion, perseus, hercules) without entering a password.
1168 This is a bit tedious for users to type, so it is a prime candidate
1169 for encapsulating in a shell script.
1171 =head1 SECURITY NOTES
1173 It is generally not effective to "subtract" commands from C<ALL>
1174 using the '!' operator. A user can trivially circumvent this
1175 by copying the desired command to a different name and then
1176 executing that. For example:
1178 bill ALL = ALL, !SU, !SHELLS
1180 Doesn't really prevent B<bill> from running the commands listed in
1181 I<SU> or I<SHELLS> since he can simply copy those commands to a
1182 different name, or use a shell escape from an editor or other
1183 program. Therefore, these kind of restrictions should be considered
1184 advisory at best (and reinforced by policy).
1186 =head1 PREVENTING SHELL ESCAPES
1188 Once B<sudo> executes a program, that program is free to do whatever
1189 it pleases, including run other programs. This can be a security
1190 issue since it is not uncommon for a program to allow shell escapes,
1191 which lets a user bypass B<sudo>'s restrictions. Common programs
1192 that permit shell escapes include shells (obviously), editors,
1193 paginators, mail and terminal programs.
1195 Many systems that support shared libraries have the ability to
1196 override default library functions by pointing an environment
1197 variable (usually C<LD_PRELOAD>) to an alternate shared library.
1198 On such systems, B<sudo>'s I<noexec> functionality can be used to
1199 prevent a program run by sudo from executing any other programs.
1200 Note, however, that this applies only to native dynamically-linked
1201 executables. Statically-linked executables and foreign executables
1202 running under binary emulation are not affected.
1204 To tell whether or not B<sudo> supports I<noexec>, you can run
1205 the following as root:
1207 sudo -V | grep "dummy exec"
1209 If the resulting output contains a line that begins with:
1211 File containing dummy exec functions:
1213 then B<sudo> may be able to replace the exec family of functions
1214 in the standard library with its own that simply return an error.
1215 Unfortunately, there is no foolproof way to know whether or not
1216 I<noexec> will work at compile-time. I<Noexec> should work on
1217 SunOS, Solaris, *BSD, Linux, IRIX, Tru64 UNIX, MacOS X, and HP-UX
1218 11.x. It is known B<not> to work on AIX and UnixWare. I<Noexec>
1219 is expected to work on most operating systems that support the
1220 C<LD_PRELOAD> environment variable. Check your operating system's
1221 manual pages for the dynamic linker (usually ld.so, ld.so.1, dyld,
1222 dld.sl, rld, or loader) to see if C<LD_PRELOAD> is supported.
1224 To enable I<noexec> for a command, use the C<NOEXEC> tag as documented
1225 in the User Specification section above. Here is that example again:
1227 aaron shanty = NOEXEC: /usr/bin/more, /usr/bin/vi
1229 This allows user B<aaron> to run F</usr/bin/more> and F</usr/bin/vi>
1230 with I<noexec> enabled. This will prevent those two commands from
1231 executing other commands (such as a shell). If you are unsure
1232 whether or not your system is capable of supporting I<noexec> you
1233 can always just try it out and see if it works.
1235 Note that disabling shell escapes is not a panacea. Programs running
1236 as root are still capable of many potentially hazardous operations
1237 (such as changing or overwriting files) that could lead to unintended
1238 privilege escalation. In the specific case of an editor, a safer
1239 approach is to give the user permission to run B<sudoedit>.
1243 L<rsh(1)>, L<su(1)>, L<fnmatch(3)>, L<sudo(@mansectsu@)>, L<visudo(@mansectsu@)>
1247 The I<sudoers> file should B<always> be edited by the B<visudo>
1248 command which locks the file and does grammatical checking. It is
1249 imperative that I<sudoers> be free of syntax errors since B<sudo>
1250 will not run with a syntactically incorrect I<sudoers> file.
1252 When using netgroups of machines (as opposed to users), if you
1253 store fully qualified hostnames in the netgroup (as is usually the
1254 case), you either need to have the machine's hostname be fully qualified
1255 as returned by the C<hostname> command or use the I<fqdn> option in
1260 If you feel you have found a bug in B<sudo>, please submit a bug report
1261 at http://www.sudo.ws/sudo/bugs/
1265 Commercial support is available for B<sudo>, see
1266 http://www.sudo.ws/sudo/support.html for details.
1268 Limited free support is available via the sudo-users mailing list,
1269 see http://www.sudo.ws/mailman/listinfo/sudo-users to subscribe or
1270 search the archives.
1274 B<Sudo> is provided ``AS IS'' and any express or implied warranties,
1275 including, but not limited to, the implied warranties of merchantability
1276 and fitness for a particular purpose are disclaimed. See the LICENSE
1277 file distributed with B<sudo> or http://www.sudo.ws/sudo/license.html
1278 for complete details.