4 SUDOERS.LDAP(4) MAINTENANCE COMMANDS SUDOERS.LDAP(4)
8 sudoers.ldap - sudo LDAP configuration
10 D
\bDE
\bES
\bSC
\bCR
\bRI
\bIP
\bPT
\bTI
\bIO
\bON
\bN
11 In addition to the standard _
\bs_
\bu_
\bd_
\bo_
\be_
\br_
\bs file, s
\bsu
\bud
\bdo
\bo may be configured via
12 LAP. This can be especially useful for synchronizing _
\bs_
\bu_
\bd_
\bo_
\be_
\br_
\bs in a
13 large, distributed environment.
15 Using LDAP for _
\bs_
\bu_
\bd_
\bo_
\be_
\br_
\bs has several benefits:
17 +
\bo s
\bsu
\bud
\bdo
\bo no longer needs to read _
\bs_
\bu_
\bd_
\bo_
\be_
\br_
\bs in its entirety. When LDAP is
18 used, there are only two or three LDAP queries per invocation.
19 This makes it especially fast and particularly usable in LDAP
22 +
\bo s
\bsu
\bud
\bdo
\bo no longer exits if there is a typo in _
\bs_
\bu_
\bd_
\bo_
\be_
\br_
\bs. It is not
23 possible to load LDAP data into the server that does not conform to
24 the sudoers schema, so proper syntax is guaranteed. It is still
25 possible to have typos in a user or host name, but this will not
26 prevent s
\bsu
\bud
\bdo
\bo from running.
28 +
\bo It is possible to specify per-entry options that override the
29 global default options. _
\b/_
\be_
\bt_
\bc_
\b/_
\bs_
\bu_
\bd_
\bo_
\be_
\br_
\bs only supports default options
30 and limited options associated with user/host/commands/aliases.
31 The syntax is complicated and can be difficult for users to
32 understand. Placing the options directly in the entry is more
35 +
\bo The v
\bvi
\bis
\bsu
\bud
\bdo
\bo program is no longer needed. v
\bvi
\bis
\bsu
\bud
\bdo
\bo provides locking
36 and syntax checking of the _
\b/_
\be_
\bt_
\bc_
\b/_
\bs_
\bu_
\bd_
\bo_
\be_
\br_
\bs file. Since LDAP updates
37 are atomic, locking is no longer necessary. Because syntax is
38 checked when the data is inserted into LDAP, there is no need for a
39 specialized tool to check syntax.
41 Another major difference between LDAP and file-based _
\bs_
\bu_
\bd_
\bo_
\be_
\br_
\bs is that in
42 LDAP, s
\bsu
\bud
\bdo
\bo-specific Aliases are not supported.
44 For the most part, there is really no need for s
\bsu
\bud
\bdo
\bo-specific Aliases.
45 Unix groups or user netgroups can be used in place of User_Aliases and
46 RunasAliases. Host netgroups can be used in place of HostAliases.
47 Since Unix groups and netgroups can also be stored in LDAP there is no
48 real need for s
\bsu
\bud
\bdo
\bo-specific aliases.
50 Cmnd_Aliases are not really required either since it is possible to
51 have multiple users listed in a sudoRole. Instead of defining a
52 Cmnd_Alias that is referenced by multiple users, one can create a
53 sudoRole that contains the commands and assign multiple users to it.
55 S
\bSU
\bUD
\bDO
\bOe
\ber
\brs
\bs L
\bLD
\bDA
\bAP
\bP c
\bco
\bon
\bnt
\bta
\bai
\bin
\bne
\ber
\br
56 The _
\bs_
\bu_
\bd_
\bo_
\be_
\br_
\bs configuration is contained in the ou=SUDOers LDAP
59 Sudo first looks for the cn=default entry in the SUDOers container. If
60 found, the multi-valued sudoOption attribute is parsed in the same
64 1.7.2p6 March 3, 2010 1
70 SUDOERS.LDAP(4) MAINTENANCE COMMANDS SUDOERS.LDAP(4)
73 manner as a global Defaults line in _
\b/_
\be_
\bt_
\bc_
\b/_
\bs_
\bu_
\bd_
\bo_
\be_
\br_
\bs. In the following
74 example, the SSH_AUTH_SOCK variable will be preserved in the
75 environment for all users.
77 dn: cn=defaults,ou=SUDOers,dc=example,dc=com
81 description: Default sudoOption's go here
82 sudoOption: env_keep+=SSH_AUTH_SOCK
84 The equivalent of a sudoer in LDAP is a sudoRole. It consists of the
87 s
\bsu
\bud
\bdo
\boU
\bUs
\bse
\ber
\br
88 A user name, uid (prefixed with '#'), Unix group (prefixed with a
89 '%') or user netgroup (prefixed with a '+').
91 s
\bsu
\bud
\bdo
\boH
\bHo
\bos
\bst
\bt
92 A host name, IP address, IP network, or host netgroup (prefixed
93 with a '+'). The special value ALL will match any host.
95 s
\bsu
\bud
\bdo
\boC
\bCo
\bom
\bmm
\bma
\ban
\bnd
\bd
96 A Unix command with optional command line arguments, potentially
97 including globbing characters (aka wild cards). The special value
98 ALL will match any command. If a command is prefixed with an
99 exclamation point '!', the user will be prohibited from running
102 s
\bsu
\bud
\bdo
\boO
\bOp
\bpt
\bti
\bio
\bon
\bn
103 Identical in function to the global options described above, but
104 specific to the sudoRole in which it resides.
106 s
\bsu
\bud
\bdo
\boR
\bRu
\bun
\bnA
\bAs
\bsU
\bUs
\bse
\ber
\br
107 A user name or uid (prefixed with '#') that commands may be run as
108 or a Unix group (prefixed with a '%') or user netgroup (prefixed
109 with a '+') that contains a list of users that commands may be run
110 as. The special value ALL will match any user.
112 s
\bsu
\bud
\bdo
\boR
\bRu
\bun
\bnA
\bAs
\bsG
\bGr
\bro
\bou
\bup
\bp
113 A Unix group or gid (prefixed with '#') that commands may be run
114 as. The special value ALL will match any group.
116 Each component listed above should contain a single value, but there
117 may be multiple instances of each component type. A sudoRole must
118 contain at least one sudoUser, sudoHost and sudoCommand.
120 The following example allows users in group wheel to run any command on
121 any host via s
\bsu
\bud
\bdo
\bo:
130 1.7.2p6 March 3, 2010 2
136 SUDOERS.LDAP(4) MAINTENANCE COMMANDS SUDOERS.LDAP(4)
139 dn: cn=%wheel,ou=SUDOers,dc=example,dc=com
141 objectClass: sudoRole
147 A
\bAn
\bna
\bat
\bto
\bom
\bmy
\by o
\bof
\bf L
\bLD
\bDA
\bAP
\bP s
\bsu
\bud
\bdo
\boe
\ber
\brs
\bs l
\blo
\boo
\bok
\bku
\bup
\bp
148 When looking up a sudoer using LDAP there are only two or three LDAP
149 queries per invocation. The first query is to parse the global
150 options. The second is to match against the user's name and the groups
151 that the user belongs to. (The special ALL tag is matched in this
152 query too.) If no match is returned for the user's name and groups, a
153 third query returns all entries containing user netgroups and checks to
154 see if the user belongs to any of them.
156 D
\bDi
\bif
\bff
\bfe
\ber
\bre
\ben
\bnc
\bce
\bes
\bs b
\bbe
\bet
\btw
\bwe
\bee
\ben
\bn L
\bLD
\bDA
\bAP
\bP a
\ban
\bnd
\bd n
\bno
\bon
\bn-
\b-L
\bLD
\bDA
\bAP
\bP s
\bsu
\bud
\bdo
\boe
\ber
\brs
\bs
157 There are some subtle differences in the way sudoers is handled once in
158 LDAP. Probably the biggest is that according to the RFC, LDAP ordering
159 is arbitrary and you cannot expect that Attributes and Entries are
160 returned in any specific order. If there are conflicting command rules
161 on an entry, the negative takes precedence. This is called paranoid
162 behavior (not necessarily the most specific match).
167 # Allow all commands except shell
168 johnny ALL=(root) ALL,!/bin/sh
169 # Always allows all commands because ALL is matched last
170 puddles ALL=(root) !/bin/sh,ALL
172 # LDAP equivalent of johnny
173 # Allows all commands except shell
174 dn: cn=role1,ou=Sudoers,dc=my-domain,dc=com
175 objectClass: sudoRole
181 sudoCommand: !/bin/sh
183 # LDAP equivalent of puddles
184 # Notice that even though ALL comes last, it still behaves like
185 # role1 since the LDAP code assumes the more paranoid configuration
186 dn: cn=role2,ou=Sudoers,dc=my-domain,dc=com
187 objectClass: sudoRole
192 sudoCommand: !/bin/sh
196 1.7.2p6 March 3, 2010 3
202 SUDOERS.LDAP(4) MAINTENANCE COMMANDS SUDOERS.LDAP(4)
207 Another difference is that negations on the Host, User or Runas are
208 currently ignorred. For example, the following attributes do not
209 behave the way one might expect.
211 # does not match all but joe
212 # rather, does not match anyone
215 # does not match all but joe
216 # rather, matches everyone including Joe
220 # does not match all but web01
221 # rather, matches all hosts including web01
225 S
\bSu
\bud
\bdo
\boe
\ber
\brs
\bs S
\bSc
\bch
\bhe
\bem
\bma
\ba
226 In order to use s
\bsu
\bud
\bdo
\bo's LDAP support, the s
\bsu
\bud
\bdo
\bo schema must be installed
227 on your LDAP server. In addition, be sure to index the 'sudoUser'
230 Three versions of the schema: one for OpenLDAP servers
231 (_
\bs_
\bc_
\bh_
\be_
\bm_
\ba_
\b._
\bO_
\bp_
\be_
\bn_
\bL_
\bD_
\bA_
\bP), one for Netscape-derived servers (_
\bs_
\bc_
\bh_
\be_
\bm_
\ba_
\b._
\bi_
\bP_
\bl_
\ba_
\bn_
\be_
\bt),
232 and one for Microsoft Active Directory (_
\bs_
\bc_
\bh_
\be_
\bm_
\ba_
\b._
\bA_
\bc_
\bt_
\bi_
\bv_
\be_
\bD_
\bi_
\br_
\be_
\bc_
\bt_
\bo_
\br_
\by) may be
233 found in the s
\bsu
\bud
\bdo
\bo distribution.
235 The schema for s
\bsu
\bud
\bdo
\bo in OpenLDAP form is included in the EXAMPLES
238 C
\bCo
\bon
\bnf
\bfi
\big
\bgu
\bur
\bri
\bin
\bng
\bg l
\bld
\bda
\bap
\bp.
\b.c
\bco
\bon
\bnf
\bf
239 Sudo reads the _
\b/_
\be_
\bt_
\bc_
\b/_
\bl_
\bd_
\ba_
\bp_
\b._
\bc_
\bo_
\bn_
\bf file for LDAP-specific configuration.
240 Typically, this file is shared amongst different LDAP-aware clients.
241 As such, most of the settings are not s
\bsu
\bud
\bdo
\bo-specific. Note that s
\bsu
\bud
\bdo
\bo
242 parses _
\b/_
\be_
\bt_
\bc_
\b/_
\bl_
\bd_
\ba_
\bp_
\b._
\bc_
\bo_
\bn_
\bf itself and may support options that differ from
243 those described in the _
\bl_
\bd_
\ba_
\bp_
\b._
\bc_
\bo_
\bn_
\bf(4) manual.
245 Also note that on systems using the OpenLDAP libraries, default values
246 specified in _
\b/_
\be_
\bt_
\bc_
\b/_
\bo_
\bp_
\be_
\bn_
\bl_
\bd_
\ba_
\bp_
\b/_
\bl_
\bd_
\ba_
\bp_
\b._
\bc_
\bo_
\bn_
\bf or the user's _
\b._
\bl_
\bd_
\ba_
\bp_
\br_
\bc files are
249 Only those options explicitly listed in _
\b/_
\be_
\bt_
\bc_
\b/_
\bl_
\bd_
\ba_
\bp_
\b._
\bc_
\bo_
\bn_
\bf that are
250 supported by s
\bsu
\bud
\bdo
\bo are honored. Configuration options are listed below
251 in upper case but are parsed in a case-independent manner.
253 U
\bUR
\bRI
\bI ldap[s]://[hostname[:port]] ...
254 Specifies a whitespace-delimited list of one or more URIs
255 describing the LDAP server(s) to connect to. The _
\bp_
\br_
\bo_
\bt_
\bo_
\bc_
\bo_
\bl may be
256 either l
\bld
\bda
\bap
\bp or l
\bld
\bda
\bap
\bps
\bs, the latter being for servers that support TLS
257 (SSL) encryption. If no _
\bp_
\bo_
\br_
\bt is specified, the default is port 389
258 for ldap:// or port 636 for ldaps://. If no _
\bh_
\bo_
\bs_
\bt_
\bn_
\ba_
\bm_
\be is specified,
262 1.7.2p6 March 3, 2010 4
268 SUDOERS.LDAP(4) MAINTENANCE COMMANDS SUDOERS.LDAP(4)
271 s
\bsu
\bud
\bdo
\bo will connect to l
\blo
\boc
\bca
\bal
\blh
\bho
\bos
\bst
\bt. Only systems using the OpenSSL
272 libraries support the mixing of ldap:// and ldaps:// URIs. The
273 Netscape-derived libraries used on most commercial versions of Unix
274 are only capable of supporting one or the other.
276 H
\bHO
\bOS
\bST
\bT name[:port] ...
277 If no U
\bUR
\bRI
\bI is specified, the H
\bHO
\bOS
\bST
\bT parameter specifies a whitespace-
278 delimited list of LDAP servers to connect to. Each host may
279 include an optional _
\bp_
\bo_
\br_
\bt separated by a colon (':'). The H
\bHO
\bOS
\bST
\bT
280 parameter is deprecated in favor of the U
\bUR
\bRI
\bI specification and is
281 included for backwards compatibility.
283 P
\bPO
\bOR
\bRT
\bT port_number
284 If no U
\bUR
\bRI
\bI is specified, the P
\bPO
\bOR
\bRT
\bT parameter specifies the default
285 port to connect to on the LDAP server if a H
\bHO
\bOS
\bST
\bT parameter does not
286 specify the port itself. If no P
\bPO
\bOR
\bRT
\bT parameter is used, the default
287 is port 389 for LDAP and port 636 for LDAP over TLS (SSL). The
288 P
\bPO
\bOR
\bRT
\bT parameter is deprecated in favor of the U
\bUR
\bRI
\bI specification and
289 is included for backwards compatibility.
291 B
\bBI
\bIN
\bND
\bD_
\b_T
\bTI
\bIM
\bME
\bEL
\bLI
\bIM
\bMI
\bIT
\bT seconds
292 The B
\bBI
\bIN
\bND
\bD_
\b_T
\bTI
\bIM
\bME
\bEL
\bLI
\bIM
\bMI
\bIT
\bT parameter specifies the amount of time, in
293 seconds, to wait while trying to connect to an LDAP server. If
294 multiple U
\bUR
\bRI
\bIs or H
\bHO
\bOS
\bST
\bTs are specified, this is the amount of time to
295 wait before trying the next one in the list.
297 T
\bTI
\bIM
\bME
\bEL
\bLI
\bIM
\bMI
\bIT
\bT seconds
298 The T
\bTI
\bIM
\bME
\bEL
\bLI
\bIM
\bMI
\bIT
\bT parameter specifies the amount of time, in seconds,
299 to wait for a response to an LDAP query.
301 S
\bSU
\bUD
\bDO
\bOE
\bER
\bRS
\bS_
\b_B
\bBA
\bAS
\bSE
\bE base
302 The base DN to use when performing s
\bsu
\bud
\bdo
\bo LDAP queries. Typically
303 this is of the form ou=SUDOers,dc=example,dc=com for the domain
306 S
\bSU
\bUD
\bDO
\bOE
\bER
\bRS
\bS_
\b_D
\bDE
\bEB
\bBU
\bUG
\bG debug_level
307 This sets the debug level for s
\bsu
\bud
\bdo
\bo LDAP queries. Debugging
308 information is printed to the standard error. A value of 1 results
309 in a moderate amount of debugging information. A value of 2 shows
310 the results of the matches themselves. This parameter should not
311 be set in a production environment as the extra information is
312 likely to confuse users.
314 B
\bBI
\bIN
\bND
\bDD
\bDN
\bN DN
315 The B
\bBI
\bIN
\bND
\bDD
\bDN
\bN parameter specifies the identity, in the form of a
316 Distinguished Name (DN), to use when performing LDAP operations.
317 If not specified, LDAP operations are performed with an anonymous
318 identity. By default, most LDAP servers will allow anonymous
321 B
\bBI
\bIN
\bND
\bDP
\bPW
\bW secret
322 The B
\bBI
\bIN
\bND
\bDP
\bPW
\bW parameter specifies the password to use when performing
323 LDAP operations. This is typically used in conjunction with the
324 B
\bBI
\bIN
\bND
\bDD
\bDN
\bN parameter.
328 1.7.2p6 March 3, 2010 5
334 SUDOERS.LDAP(4) MAINTENANCE COMMANDS SUDOERS.LDAP(4)
337 R
\bRO
\bOO
\bOT
\bTB
\bBI
\bIN
\bND
\bDD
\bDN
\bN DN
338 The R
\bRO
\bOO
\bOT
\bTB
\bBI
\bIN
\bND
\bDD
\bDN
\bN parameter specifies the identity, in the form of a
339 Distinguished Name (DN), to use when performing privileged LDAP
340 operations, such as _
\bs_
\bu_
\bd_
\bo_
\be_
\br_
\bs queries. The password corresponding to
341 the identity should be stored in _
\b/_
\be_
\bt_
\bc_
\b/_
\bl_
\bd_
\ba_
\bp_
\b._
\bs_
\be_
\bc_
\br_
\be_
\bt. If not
342 specified, the B
\bBI
\bIN
\bND
\bDD
\bDN
\bN identity is used (if any).
344 L
\bLD
\bDA
\bAP
\bP_
\b_V
\bVE
\bER
\bRS
\bSI
\bIO
\bON
\bN number
345 The version of the LDAP protocol to use when connecting to the
346 server. The default value is protocol version 3.
348 S
\bSS
\bSL
\bL on/true/yes/off/false/no
349 If the S
\bSS
\bSL
\bL parameter is set to on, true or yes, TLS (SSL)
350 encryption is always used when communicating with the LDAP server.
351 Typically, this involves connecting to the server on port 636
354 S
\bSS
\bSL
\bL start_tls
355 If the S
\bSS
\bSL
\bL parameter is set to start_tls, the LDAP server
356 connection is initiated normally and TLS encryption is begun before
357 the bind credentials are sent. This has the advantage of not
358 requiring a dedicated port for encrypted communications. This
359 parameter is only supported by LDAP servers that honor the
360 start_tls extension, such as the OpenLDAP server.
362 T
\bTL
\bLS
\bS_
\b_C
\bCH
\bHE
\bEC
\bCK
\bKP
\bPE
\bEE
\bER
\bR on/true/yes/off/false/no
363 If enabled, T
\bTL
\bLS
\bS_
\b_C
\bCH
\bHE
\bEC
\bCK
\bKP
\bPE
\bEE
\bER
\bR will cause the LDAP server's TLS
364 certificated to be verified. If the server's TLS certificate
365 cannot be verified (usually because it is signed by an unknown
366 certificate authority), s
\bsu
\bud
\bdo
\bo will be unable to connect to it. If
367 T
\bTL
\bLS
\bS_
\b_C
\bCH
\bHE
\bEC
\bCK
\bKP
\bPE
\bEE
\bER
\bR is disabled, no check is made.
369 T
\bTL
\bLS
\bS_
\b_C
\bCA
\bAC
\bCE
\bER
\bRT
\bTF
\bFI
\bIL
\bLE
\bE file name
370 The path to a certificate authority bundle which contains the
371 certificates for all the Certificate Authorities the client knows
372 to be valid, e.g. _
\b/_
\be_
\bt_
\bc_
\b/_
\bs_
\bs_
\bl_
\b/_
\bc_
\ba_
\b-_
\bb_
\bu_
\bn_
\bd_
\bl_
\be_
\b._
\bp_
\be_
\bm. This option is only
373 supported by the OpenLDAP libraries.
375 T
\bTL
\bLS
\bS_
\b_C
\bCA
\bAC
\bCE
\bER
\bRT
\bTD
\bDI
\bIR
\bR directory
376 Similar to T
\bTL
\bLS
\bS_
\b_C
\bCA
\bAC
\bCE
\bER
\bRT
\bTF
\bFI
\bIL
\bLE
\bE but instead of a file, it is a directory
377 containing individual Certificate Authority certificates, e.g.
378 _
\b/_
\be_
\bt_
\bc_
\b/_
\bs_
\bs_
\bl_
\b/_
\bc_
\be_
\br_
\bt_
\bs. The directory specified by T
\bTL
\bLS
\bS_
\b_C
\bCA
\bAC
\bCE
\bER
\bRT
\bTD
\bDI
\bIR
\bR is
379 checked after T
\bTL
\bLS
\bS_
\b_C
\bCA
\bAC
\bCE
\bER
\bRT
\bTF
\bFI
\bIL
\bLE
\bE. This option is only supported by the
382 T
\bTL
\bLS
\bS_
\b_C
\bCE
\bER
\bRT
\bT file name
383 The path to a file containing the client certificate which can be
384 used to authenticate the client to the LDAP server. The
385 certificate type depends on the LDAP libraries used.
388 tls_cert /etc/ssl/client_cert.pem
394 1.7.2p6 March 3, 2010 6
400 SUDOERS.LDAP(4) MAINTENANCE COMMANDS SUDOERS.LDAP(4)
403 tls_cert /var/ldap/cert7.db
405 When using Netscape-derived libraries, this file may also contain
406 Certificate Authority certificates.
408 T
\bTL
\bLS
\bS_
\b_K
\bKE
\bEY
\bY file name
409 The path to a file containing the private key which matches the
410 certificate specified by T
\bTL
\bLS
\bS_
\b_C
\bCE
\bER
\bRT
\bT. The private key must not be
411 password-protected. The key type depends on the LDAP libraries
415 tls_key /etc/ssl/client_key.pem
418 tls_key /var/ldap/key3.db
420 T
\bTL
\bLS
\bS_
\b_R
\bRA
\bAN
\bND
\bDF
\bFI
\bIL
\bLE
\bE file name
421 The T
\bTL
\bLS
\bS_
\b_R
\bRA
\bAN
\bND
\bDF
\bFI
\bIL
\bLE
\bE parameter specifies the path to an entropy source
422 for systems that lack a random device. It is generally used in
423 conjunction with _
\bp_
\br_
\bn_
\bg_
\bd or _
\be_
\bg_
\bd. This option is only supported by
424 the OpenLDAP libraries.
426 T
\bTL
\bLS
\bS_
\b_C
\bCI
\bIP
\bPH
\bHE
\bER
\bRS
\bS cipher list
427 The T
\bTL
\bLS
\bS_
\b_C
\bCI
\bIP
\bPH
\bHE
\bER
\bRS
\bS parameter allows the administer to restrict which
428 encryption algorithms may be used for TLS (SSL) connections. See
429 the OpenSSL manual for a list of valid ciphers. This option is
430 only supported by the OpenLDAP libraries.
432 U
\bUS
\bSE
\bE_
\b_S
\bSA
\bAS
\bSL
\bL on/true/yes/off/false/no
433 Enable U
\bUS
\bSE
\bE_
\b_S
\bSA
\bAS
\bSL
\bL for LDAP servers that support SASL authentication.
435 S
\bSA
\bAS
\bSL
\bL_
\b_A
\bAU
\bUT
\bTH
\bH_
\b_I
\bID
\bD identity
436 The SASL user name to use when connecting to the LDAP server. By
437 default, s
\bsu
\bud
\bdo
\bo will use an anonymous connection.
439 R
\bRO
\bOO
\bOT
\bTU
\bUS
\bSE
\bE_
\b_S
\bSA
\bAS
\bSL
\bL on/true/yes/off/false/no
440 Enable R
\bRO
\bOO
\bOT
\bTU
\bUS
\bSE
\bE_
\b_S
\bSA
\bAS
\bSL
\bL to enable SASL authentication when connecting
441 to an LDAP server from a privileged process, such as s
\bsu
\bud
\bdo
\bo.
443 R
\bRO
\bOO
\bOT
\bTS
\bSA
\bAS
\bSL
\bL_
\b_A
\bAU
\bUT
\bTH
\bH_
\b_I
\bID
\bD identity
444 The SASL user name to use when R
\bRO
\bOO
\bOT
\bTU
\bUS
\bSE
\bE_
\b_S
\bSA
\bAS
\bSL
\bL is enabled.
446 S
\bSA
\bAS
\bSL
\bL_
\b_S
\bSE
\bEC
\bCP
\bPR
\bRO
\bOP
\bPS
\bS none/properties
447 SASL security properties or _
\bn_
\bo_
\bn_
\be for no properties. See the SASL
448 programmer's manual for details.
450 K
\bKR
\bRB
\bB5
\b5_
\b_C
\bCC
\bCN
\bNA
\bAM
\bME
\bE file name
451 The path to the Kerberos 5 credential cache to use when
452 authenticating with the remote server.
454 See the ldap.conf entry in the EXAMPLES section.
460 1.7.2p6 March 3, 2010 7
466 SUDOERS.LDAP(4) MAINTENANCE COMMANDS SUDOERS.LDAP(4)
469 C
\bCo
\bon
\bnf
\bfi
\big
\bgu
\bur
\bri
\bin
\bng
\bg n
\bns
\bss
\bsw
\bwi
\bit
\btc
\bch
\bh.
\b.c
\bco
\bon
\bnf
\bf
470 Unless it is disabled at build time, s
\bsu
\bud
\bdo
\bo consults the Name Service
471 Switch file, _
\b/_
\be_
\bt_
\bc_
\b/_
\bn_
\bs_
\bs_
\bw_
\bi_
\bt_
\bc_
\bh_
\b._
\bc_
\bo_
\bn_
\bf, to specify the _
\bs_
\bu_
\bd_
\bo_
\be_
\br_
\bs search order.
472 Sudo looks for a line beginning with sudoers: and uses this to
473 determine the search order. Note that s
\bsu
\bud
\bdo
\bo does not stop searching
474 after the first match and later matches take precedence over earlier
477 The following sources are recognized:
479 files read sudoers from F</etc/sudoers>
480 ldap read sudoers from LDAP
482 In addition, the entry [NOTFOUND=return] will short-circuit the search
483 if the user was not found in the preceding source.
485 To consult LDAP first followed by the local sudoers file (if it
490 The local _
\bs_
\bu_
\bd_
\bo_
\be_
\br_
\bs file can be ignored completely by using:
494 If the _
\b/_
\be_
\bt_
\bc_
\b/_
\bn_
\bs_
\bs_
\bw_
\bi_
\bt_
\bc_
\bh_
\b._
\bc_
\bo_
\bn_
\bf file is not present or there is no sudoers
495 line, the following default is assumed:
499 Note that _
\b/_
\be_
\bt_
\bc_
\b/_
\bn_
\bs_
\bs_
\bw_
\bi_
\bt_
\bc_
\bh_
\b._
\bc_
\bo_
\bn_
\bf is supported even when the underlying
500 operating system does not use an nsswitch.conf file.
502 C
\bCo
\bon
\bnf
\bfi
\big
\bgu
\bur
\bri
\bin
\bng
\bg n
\bne
\bet
\bts
\bsv
\bvc
\bc.
\b.c
\bco
\bon
\bnf
\bf
503 On AIX systems, the _
\b/_
\be_
\bt_
\bc_
\b/_
\bn_
\be_
\bt_
\bs_
\bv_
\bc_
\b._
\bc_
\bo_
\bn_
\bf file is consulted instead of
504 _
\b/_
\be_
\bt_
\bc_
\b/_
\bn_
\bs_
\bs_
\bw_
\bi_
\bt_
\bc_
\bh_
\b._
\bc_
\bo_
\bn_
\bf. s
\bsu
\bud
\bdo
\bo simply treats _
\bn_
\be_
\bt_
\bs_
\bv_
\bc_
\b._
\bc_
\bo_
\bn_
\bf as a variant of
505 _
\bn_
\bs_
\bs_
\bw_
\bi_
\bt_
\bc_
\bh_
\b._
\bc_
\bo_
\bn_
\bf; information in the previous section unrelated to the
506 file format itself still applies.
508 To consult LDAP first followed by the local sudoers file (if it
511 sudoers = ldap, files
513 The local _
\bs_
\bu_
\bd_
\bo_
\be_
\br_
\bs file can be ignored completely by using:
517 To treat LDAP as authoratative and only use the local sudoers file if
518 the user is not present in LDAP, use:
520 sudoers = ldap = auth, files
522 Note that in the above example, the auth qualfier only affects user
526 1.7.2p6 March 3, 2010 8
532 SUDOERS.LDAP(4) MAINTENANCE COMMANDS SUDOERS.LDAP(4)
535 lookups; both LDAP and _
\bs_
\bu_
\bd_
\bo_
\be_
\br_
\bs will be queried for Defaults entries.
537 If the _
\b/_
\be_
\bt_
\bc_
\b/_
\bn_
\be_
\bt_
\bs_
\bv_
\bc_
\b._
\bc_
\bo_
\bn_
\bf file is not present or there is no sudoers
538 line, the following default is assumed:
543 _
\b/_
\be_
\bt_
\bc_
\b/_
\bl_
\bd_
\ba_
\bp_
\b._
\bc_
\bo_
\bn_
\bf LDAP configuration file
545 _
\b/_
\be_
\bt_
\bc_
\b/_
\bn_
\bs_
\bs_
\bw_
\bi_
\bt_
\bc_
\bh_
\b._
\bc_
\bo_
\bn_
\bf determines sudoers source order
547 _
\b/_
\be_
\bt_
\bc_
\b/_
\bn_
\be_
\bt_
\bs_
\bv_
\bc_
\b._
\bc_
\bo_
\bn_
\bf determines sudoers source order on AIX
549 E
\bEX
\bXA
\bAM
\bMP
\bPL
\bLE
\bES
\bS
550 E
\bEx
\bxa
\bam
\bmp
\bpl
\ble
\be l
\bld
\bda
\bap
\bp.
\b.c
\bco
\bon
\bnf
\bf
551 # Either specify one or more URIs or one or more host:port pairs.
552 # If neither is specified sudo will default to localhost, port 389.
555 #host ldapserver1 ldapserver2:390
557 # Default port if host is specified without one, defaults to 389.
560 # URI will override the host and port settings.
561 uri ldap://ldapserver
562 #uri ldaps://secureldapserver
563 #uri ldaps://secureldapserver ldap://ldapserver
565 # The amount of time, in seconds, to wait while trying to connect to
569 # The amount of time, in seconds, to wait while performing an LDAP query.
572 # must be set or sudo will ignore LDAP
573 sudoers_base ou=SUDOers,dc=example,dc=com
575 # verbose sudoers matching from ldap
578 # optional proxy credentials
579 #binddn <who to search as>
581 #rootbinddn <who to search as, uses /etc/ldap.secret for bindpw>
583 # LDAP protocol version, defaults to 3
586 # Define if you want to use an encrypted LDAP connection.
587 # Typically, you must also set the port to 636 (ldaps).
592 1.7.2p6 March 3, 2010 9
598 SUDOERS.LDAP(4) MAINTENANCE COMMANDS SUDOERS.LDAP(4)
602 # Define if you want to use port 389 and switch to
603 # encryption before the bind credentials are sent.
604 # Only supported by LDAP servers that support the start_tls
605 # extension such as OpenLDAP.
608 # Additional TLS options follow that allow tweaking of the
609 # SSL/TLS connection.
611 #tls_checkpeer yes # verify server SSL certificate
612 #tls_checkpeer no # ignore server SSL certificate
614 # If you enable tls_checkpeer, specify either tls_cacertfile
615 # or tls_cacertdir. Only supported when using OpenLDAP.
617 #tls_cacertfile /etc/certs/trusted_signers.pem
618 #tls_cacertdir /etc/certs
620 # For systems that don't have /dev/random
621 # use this along with PRNGD or EGD.pl to seed the
622 # random number pool to generate cryptographic session keys.
623 # Only supported when using OpenLDAP.
625 #tls_randfile /etc/egd-pool
627 # You may restrict which ciphers are used. Consult your SSL
628 # documentation for which options go here.
629 # Only supported when using OpenLDAP.
631 #tls_ciphers <cipher-list>
633 # Sudo can provide a client certificate when communicating to
636 # * Enable both lines at the same time.
637 # * Do not password protect the key file.
638 # * Ensure the keyfile is only readable by root.
641 #tls_cert /etc/certs/client_cert.pem
642 #tls_key /etc/certs/client_key.pem
644 # For SunONE or iPlanet LDAP, tls_cert and tls_key may specify either
645 # a directory, in which case the files in the directory must have the
646 # default names (e.g. cert8.db and key4.db), or the path to the cert
647 # and key files themselves. However, a bug in version 5.0 of the LDAP
648 # SDK will prevent specific file names from working. For this reason
649 # it is suggested that tls_cert and tls_key be set to a directory,
652 # The certificate database specified by tls_cert may contain CA certs
653 # and/or the client's cert. If the client's cert is included, tls_key
654 # should be specified as well.
658 1.7.2p6 March 3, 2010 10
664 SUDOERS.LDAP(4) MAINTENANCE COMMANDS SUDOERS.LDAP(4)
667 # For backward compatibility, "sslpath" may be used in place of tls_cert.
671 # If using SASL authentication for LDAP (OpenSSL)
673 # sasl_auth_id <SASL username>
675 # rootsasl_auth_id <SASL username for root access>
677 # krb5_ccname /etc/.ldapcache
679 S
\bSu
\bud
\bdo
\bo s
\bsc
\bch
\bhe
\bem
\bma
\ba f
\bfo
\bor
\br O
\bOp
\bpe
\ben
\bnL
\bLD
\bDA
\bAP
\bP
680 The following schema is in OpenLDAP format. Simply copy it to the
681 schema directory (e.g. _
\b/_
\be_
\bt_
\bc_
\b/_
\bo_
\bp_
\be_
\bn_
\bl_
\bd_
\ba_
\bp_
\b/_
\bs_
\bc_
\bh_
\be_
\bm_
\ba), add the proper include
682 line in slapd.conf and restart s
\bsl
\bla
\bap
\bpd
\bd.
684 attributetype ( 1.3.6.1.4.1.15953.9.1.1
686 DESC 'User(s) who may run sudo'
687 EQUALITY caseExactIA5Match
688 SUBSTR caseExactIA5SubstringsMatch
689 SYNTAX 1.3.6.1.4.1.1466.115.121.1.26 )
691 attributetype ( 1.3.6.1.4.1.15953.9.1.2
693 DESC 'Host(s) who may run sudo'
694 EQUALITY caseExactIA5Match
695 SUBSTR caseExactIA5SubstringsMatch
696 SYNTAX 1.3.6.1.4.1.1466.115.121.1.26 )
698 attributetype ( 1.3.6.1.4.1.15953.9.1.3
700 DESC 'Command(s) to be executed by sudo'
701 EQUALITY caseExactIA5Match
702 SYNTAX 1.3.6.1.4.1.1466.115.121.1.26 )
704 attributetype ( 1.3.6.1.4.1.15953.9.1.4
706 DESC 'User(s) impersonated by sudo'
707 EQUALITY caseExactIA5Match
708 SYNTAX 1.3.6.1.4.1.1466.115.121.1.26 )
710 attributetype ( 1.3.6.1.4.1.15953.9.1.5
712 DESC 'Options(s) followed by sudo'
713 EQUALITY caseExactIA5Match
714 SYNTAX 1.3.6.1.4.1.1466.115.121.1.26 )
716 attributetype ( 1.3.6.1.4.1.15953.9.1.6
718 DESC 'User(s) impersonated by sudo'
719 EQUALITY caseExactIA5Match
720 SYNTAX 1.3.6.1.4.1.1466.115.121.1.26 )
724 1.7.2p6 March 3, 2010 11
730 SUDOERS.LDAP(4) MAINTENANCE COMMANDS SUDOERS.LDAP(4)
734 attributetype ( 1.3.6.1.4.1.15953.9.1.7
735 NAME 'sudoRunAsGroup'
736 DESC 'Group(s) impersonated by sudo'
737 EQUALITY caseExactIA5Match
738 SYNTAX 1.3.6.1.4.1.1466.115.121.1.26 )
740 objectclass ( 1.3.6.1.4.1.15953.9.2.1 NAME 'sudoRole' SUP top STRUCTURAL
741 DESC 'Sudoer Entries'
743 MAY ( sudoUser $ sudoHost $ sudoCommand $ sudoRunAs $ sudoRunAsUser $
744 sudoRunAsGroup $ sudoOption $ description )
747 S
\bSE
\bEE
\bE A
\bAL
\bLS
\bSO
\bO
748 _
\bl_
\bd_
\ba_
\bp_
\b._
\bc_
\bo_
\bn_
\bf(4), _
\bs_
\bu_
\bd_
\bo_
\be_
\br_
\bs(5)
750 C
\bCA
\bAV
\bVE
\bEA
\bAT
\bTS
\bS
751 The way that _
\bs_
\bu_
\bd_
\bo_
\be_
\br_
\bs is parsed differs between Note that there are
752 differences in the way that LDAP-based _
\bs_
\bu_
\bd_
\bo_
\be_
\br_
\bs is parsed compared to
753 file-based _
\bs_
\bu_
\bd_
\bo_
\be_
\br_
\bs. See the "Differences between LDAP and non-LDAP
754 sudoers" section for more information.
757 If you feel you have found a bug in s
\bsu
\bud
\bdo
\bo, please submit a bug report at
758 http://www.sudo.ws/sudo/bugs/
760 S
\bSU
\bUP
\bPP
\bPO
\bOR
\bRT
\bT
761 Limited free support is available via the sudo-users mailing list, see
762 http://www.sudo.ws/mailman/listinfo/sudo-users to subscribe or search
765 D
\bDI
\bIS
\bSC
\bCL
\bLA
\bAI
\bIM
\bME
\bER
\bR
766 s
\bsu
\bud
\bdo
\bo is provided ``AS IS'' and any express or implied warranties,
767 including, but not limited to, the implied warranties of
768 merchantability and fitness for a particular purpose are disclaimed.
769 See the LICENSE file distributed with s
\bsu
\bud
\bdo
\bo or
770 http://www.sudo.ws/sudo/license.html for complete details.
790 1.7.2p6 March 3, 2010 12