src/usr.bin/sudo/INSTALL - annotate

Return to INSTALL CVS log

Up to [local] / src / usr.bin / sudo

Annotation of src/usr.bin/sudo/INSTALL, Revision 1.17

1.16 millert 1: Installation instructions for Sudo 1.6.9
1.3 millert 2: ========================================
1.1 millert 3:
4: Sudo uses a `configure' script to probe the capabilities and type
5: of the system in question. In this release, `configure' takes many
6: more options than it did before. Please read this document fully
7: before configuring and building sudo. You may also wish to read the
8: file INSTALL.configure which explains more about the `configure' script.
9:
10: Simple sudo installation
11: ========================
12:
13: For most systems and configurations it is possible simply to:
14:
15: 0) If you are upgrading from a previous version of sudo
16: please read the info in the UPGRADE file before proceeding.
17:
18: 1) If you previously ran `configure' on a different host
19: you will probably want to do a `make distclean' to remove
20: the old `config.cache' file. Otherwise, `configure'
21: will complain and refuse to run. Alternately, one can
22: simply `rm config.cache'.
23:
24: 2) Read the `OS dependent notes' section for any particular
25: "gotchas" relating to your operating system.
26:
27: 3) `cd' to the source or build directory and type `./configure'
28: to generate a Makefile and config.h file suitable for
29: building sudo. Before you actually run configure you
30: should read the `Available configure options' section
31: to see if there are any special options you may want
1.7 millert 32: or need.
1.1 millert 33:
34: 4) Edit the configure-generated Makefile if you wish to
1.16 millert 35: change any of the default paths (alternatively, you could
1.1 millert 36: have changed the paths via options to `configure'.
37:
38: 5) Type `make' to compile sudo. If you are building sudo
39: in a separate build tree (apart from the sudo source)
40: GNU make will probably be required. If `configure' did
41: its job properly (and you have a supported configuration)
42: there won't be any problems. If this doesn't work, take
43: a look at the files TROUBLESHOOTING and PORTING for tips
44: on what might have gone wrong. Please mail us if you have a
45: fix or if you are unable to come up with a fix (address at EOF).
46:
47: 6) Type `make install' (as root) to install sudo, visudo, the
48: man pages, and a skeleton sudoers file. Note that the install
49: will not overwrite an existing sudoers file. You can also
50: install various pieces the package via the install-binaries,
51: install-man, and install-sudoers make targets.
52:
53: 7) Edit the sudoers file with `visudo' as necessary for your
54: site. You will probably want to refer the sample.sudoers
55: file and sudoers man page included with the sudo package.
56:
57: 8) If you want to use syslogd(8) to do the logging, you'll need
58: to update your /etc/syslog.conf file. See the sample.syslog.conf
59: file included in the distribution for an example.
60:
61: Available configure options
62: ===========================
63:
64: This section describes flags accepted by the sudo's `configure' script.
65: Defaults are listed in brackets after the description.
66:
67: Configuration:
68: --cache-file=FILE
69: Cache test results in FILE
70:
1.9 millert 71: --config-cache, -C
72: Alias for `--cache-file=config.cache'
73:
74: --help, -h
1.1 millert 75: Print the usage/help info
76:
1.9 millert 77: --no-create, -n
1.1 millert 78: Do not create output files
79:
1.9 millert 80: --quiet, --silent, -q
1.1 millert 81: Do not print `checking...' messages
82:
83: Directory and file names:
84: --prefix=PREFIX
85: Install architecture-independent files in PREFIX This really only
86: applies to man pages. [/usr/local]
87:
88: --exec-prefix=EPREFIX
89: Install architecture-dependent files in EPREFIX This includes the
90: sudo and visudo executables. [same as prefix]
91:
92: --bindir=DIR
93: Install `sudo' in DIR [EPREFIX/bin]
94:
95: --sbindir=DIR
96: Install `visudo' in DIR [EPREFIX/sbin]
97:
98: --sysconfdir=DIR
99: Install `sudoers' file in DIR [/etc]
100:
101: --mandir=DIR
102: Install man pages in DIR [PREFIX/man]
103:
104: --srcdir=DIR
105: Find the sources in DIR [configure dir or ..]
106:
107: Special features/options:
1.12 millert 108: --with-CC=PATH
1.1 millert 109: Specifies path to C compiler you wish to use.
110:
1.12 millert 111: --with-incpath=DIR
1.16 millert 112: Adds the specified directory (or directories) to CPPFLAGS
113: so configure and the compiler will look there for include
114: files. Multiple directories may be specified as long as
115: they are space separated.
1.1 millert 116: Eg: --with-incpath="/usr/local/include /opt/include"
117:
1.12 millert 118: --with-libpath=DIR
1.16 millert 119: Adds the specified directory (or directories) to LDFLAGS
120: so configure and the compiler will look there for libraries.
121: Multiple directories may be specified as with --with-incpath.
1.14 millert 122:
123: --with-rpath
124: Tells configure to use -Rpath in addition to -Lpath when
125: passing library paths to the loader. This option is on
126: by default for Solaris and SVR4.
127:
128: --with-blibpath[=PATH]
1.16 millert 129: Tells configure to construct a -blibpath argument to the
130: loader. If a PATH is specified, it will be used as the
131: base. Otherwise, "/usr/lib:/lib:/usr/local/lib" will be
132: used for gcc and "/usr/lib:/lib" for non-gcc. Additional
133: library paths will be appended as needed by configure.
1.14 millert 134: This option is only valid for AIX where it is on by default.
1.12 millert 135:
136: --with-libraries=LIBRARY
1.16 millert 137: Adds the specified library (or libaries) to SUDO_LIBS and
138: and VISUDO_LIBS so sudo will link against them. If the
139: library doesn't start with `-l' or end in `.a' or `.o' a
140: `-l' will be prepended to it. Multiple libraries may be
141: specified as long as they are space separated.
1.1 millert 142:
143: --with-csops
144: Add CSOps standard options. You probably aren't interested in this.
145:
1.14 millert 146: --with-skey[=DIR]
1.16 millert 147: Enable S/Key OTP (One Time Password) support. If specified,
148: DIR should contain include and lib directories with skey.h
149: and libskey.a respectively.
1.14 millert 150:
151: --with-opie[=DIR]
152: Enable NRL OPIE OTP (One Time Password) support. If specified,
153: DIR should contain include and lib directories with opie.h
154: and libopie.a respectively.
1.1 millert 155:
1.12 millert 156: --with-SecurID[=DIR]
1.1 millert 157: Enable SecurID support. If specified, DIR is directory containing
158: sdiclient.a, sdi_athd.h, sdconf.h, and sdacmvls.h.
159:
1.12 millert 160: --with-fwtk[=DIR]
1.1 millert 161: Enable TIS Firewall Toolkit (FWTK) 'authsrv' support. If specified,
162: DIR is the base directory containing the compiled FWTK package
163: (or at least the library and header files).
164:
1.14 millert 165: --with-kerb4[=DIR]
1.16 millert 166: Enable Kerberos IV support. If specified, DIR is the base
167: directory containing the Kerberos IV include and lib dirs.
168: This uses Kerberos passphrases for authentication but does
169: not use the Kerberos cookie scheme.
1.14 millert 170:
171: --with-kerb5[=DIR]
1.16 millert 172: Enable Kerberos V support. If specified, DIR is the base
173: directory containing the Kerberos V include and lib dirs.
174: This This uses Kerberos passphrases for authentication but
175: does not use the Kerberos cookie scheme. Will not work for
176: Kerberos V older than version 1.1.
1.1 millert 177:
1.15 millert 178: --with-ldap[=DIR]
179: Enable LDAP support. If specified, DIR is the base directory
180: containing the LDAP include and lib directories. Please see
181: README.LDAP for more information.
182:
1.16 millert 183: --with-ldap-conf-file=filename
1.15 millert 184: Path to LDAP configuration file. If specified, sudo reads
185: this file instead of /etc/ldap.conf to locate the LDAP server.
186:
1.16 millert 187: --with-ldap-secret-file=filename
188: Path to LDAP secret password file. If specified, sudo uses
189: this file instead of /etc/ldap.secret to read the secret password
190: when rootbinddn is specified in the ldap config file.
191:
192: --with-aixauth
1.1 millert 193: Enable support for the AIX 4.x general authentication function.
194: This will use the authentication scheme specified for the user
1.16 millert 195: on the machine. It is on by default for AIX systems that
196: support it.
1.1 millert 197:
198: --with-pam
1.16 millert 199: Enable PAM support. This is on by default for Darwin, FreeBSD,
200: Linux, Solaris and HP-UX (version 11 and higher).
201:
202: NOTE: on RedHat Linux and Fedora you *must* have an /etc/pam.d/sudo
203: file installed. You may either use the sample.pam file included with
1.15 millert 204: sudo or use /etc/pam.d/su as a reference. The sample.pam file
205: included with sudo may or may not work with other Linux distributions.
206: On Solaris and HP-UX 11 systems you should check (and understand)
207: the contents of /etc/pam.conf. Do a "man pam.conf" for more
208: information and consider using the "debug" option, if available,
209: with your PAM libraries in /etc/pam.conf to obtain syslog output
210: for debugging purposes.
1.1 millert 211:
212: --with-AFS
1.13 millert 213: Enable AFS support with Kerberos authentication. Should work under
1.1 millert 214: AFS 3.3. If your AFS doesn't have -laudit you should be able to
215: link without it.
216:
217: --with-DCE
1.15 millert 218: Enable DCE support for systems without PAM. Known to work on
219: HP-UX 9.X, 10.X, and 11.0; other systems may require source
220: code and/or `configure' changes. On systems with PAM support
221: (such as HP-UX 11.0 and higher, Solaris, FreeBSD and Linux), the
222: DCE PAM module (usually libpam_dce) should be used instead.
1.1 millert 223:
1.5 millert 224: --with-logincap
1.16 millert 225: This adds support for login classes specified in /etc/login.conf.
226: It is enabled by default on BSD/OS, Darwin, FreeBSD, OpenBSD and
227: NetBSD (where available). By default, a login class is not applied
228: unless the 'use_loginclass' option is defined in sudoers or the user
229: specifies a class on the command line.
230:
231: --with-project
232: Enable support for Solaris project resource limits.
233: This option is only available on Solaris 9 and above.
1.6 millert 234:
235: --with-bsdauth
1.16 millert 236: Enable support for BSD authentication. This is the default
237: for BSD/OS and OpenBSD systems that support it.
238: It is not possible to mix BSD authentication with other
239: authentication methods (and there really should be no need
240: to do so). Note that only the newer BSD authentication API
241: is supported. If you don't have /usr/include/bsd_auth.h
242: then you cannot use this.
1.10 millert 243:
1.15 millert 244: --with-noexec[=PATH]
1.16 millert 245: Enable support for the "noexec" functionality which prevents
246: a dynamically-linked program being run by sudo from executing
247: another program (think shell escapes). Please see the
248: "PREVENTING SHELL ESCAPES" section in the sudoers man page
249: for details. If specified, PATH should be a fully qualified
250: pathname, e.g. /usr/local/libexec/sudo_noexec.so. If PATH
251: is "no", noexec support will not be compiled in. The default
252: is to compile noexec support if libtool supports building
253: shared objects on your OS.
1.15 millert 254:
1.10 millert 255: --disable-root-mailer
1.16 millert 256: By default sudo will run the mailer as root when tattling
257: on a user so as to prevent that user from killing the mailer.
258: With this option, sudo will run the mailer as the invoking
259: user which some people consider to be safer.
1.11 millert 260:
261: --disable-setreuid
1.16 millert 262: Disable use of the setreuid() function for operating systems
263: where it is broken. Mac OS X has setreuid() but it doesn't
264: really work.
1.5 millert 265:
1.13 millert 266: --disable-setresuid
1.16 millert 267: Disable use of the setresuid() function for operating systems
268: where it is broken (none currently known).
1.13 millert 269:
1.1 millert 270: --disable-sia
1.16 millert 271: Disable SIA support. This is the "Security Integration
272: Architecture" on Digital UNIX. If you disable SIA sudo will
273: use its own authentication routines.
1.1 millert 274:
275: --disable-shadow
1.16 millert 276: Disable shadow password support. Normally, sudo will compile
277: in shadow password support and use a shadow password if it
278: exists.
1.12 millert 279:
280: --with-sudoers-mode=MODE
1.16 millert 281: File mode for the sudoers file (octal). Note that if you
282: wish to NFS-mount the sudoers file this must be group
283: readable. Also note that this is actually set in the
284: Makefile. The default mode is 0440.
1.12 millert 285:
286: --with-sudoers-uid=UID
1.16 millert 287: User id that "owns" the sudoers file. Note that this is
288: the numeric id, *not* the symbolic name. Also note that
289: this is actually set in the Makefile. The default is 0.
1.12 millert 290:
291: --with-sudoers-gid=GID
1.16 millert 292: Group id that "owns" the sudoers file. Note that this is
293: the numeric id, *not* the symbolic name. Also note that
294: this is actually set in the Makefile. The default is 0.
1.1 millert 295:
296: --without-interfaces
1.16 millert 297: This option keeps sudo from trying to glean the ip address
298: from each attached ethernet interface. It is only useful
299: on a machine where sudo's interface reading support does
300: not work, which may be the case on some SysV-based OS's
301: using STREAMS.
1.1 millert 302:
303: --without-passwd
1.16 millert 304: This option excludes authentication via the passwd (or
305: shadow) file. It should only be used when another, alternative,
306: authentication scheme is in use.
1.1 millert 307:
308: --with-otp-only
1.16 millert 309: This option is now just an alias for --without-passwd.
1.13 millert 310:
311: --with-stow
1.16 millert 312: Properly handle GNU stow packaging. The sudoers file will
313: physically live in ${prefix}/etc and /etc/sudoers will be
314: a symbolic link.
1.1 millert 315:
1.4 millert 316: The following options are also configurable at runtime:
317:
1.1 millert 318: --with-long-otp-prompt
1.16 millert 319: When validating with a One Time Password scheme (S/Key or
320: OPIE), a two-line prompt is used to make it easier to cut
321: and paste the challenge to a local window. It's not as
322: pretty as the default but some people find it more convenient.
1.1 millert 323:
324: --with-logging=TYPE
1.16 millert 325: How you want to do your logging. You may choose "syslog",
326: "file", or "both". Setting this to "syslog" is nice because
327: you can keep all of your sudo logs in one place (see the
328: sample.syslog.conf file). The default is "syslog".
1.1 millert 329:
330: --with-logfac=FACILITY
1.16 millert 331: Determines which syslog facility to log to. This requires
332: a 4.3BSD or later version of syslog. You can still set
333: this for ancient syslogs but it will have no effect. The
334: following facilities are supported: authpriv (if your OS
335: supports it), auth, daemon, user, local0, local1, local2,
336: local3, local4, local5, local6, and local7.
1.1 millert 337:
338: --with-goodpri=PRIORITY
1.16 millert 339: Determines which syslog priority to log successfully
340: authenticated commands. The following priorities are
341: supported: alert, crit, debug, emerg, err, info, notice,
342: and warning.
1.1 millert 343:
344: --with-badpri=PRIORITY
1.16 millert 345: Determines which syslog priority to log unauthenticated
346: commands and errors. The following priorities are supported:
347: alert, crit, debug, emerg, err, info, notice, and warning.
1.12 millert 348:
349: --with-logpath=PATH
1.16 millert 350: Override the default location of the sudo log file and use
351: "path" instead. By default will use /var/log/sudo.log if
352: there is a /var/log dir, falling back to /var/adm/sudo.log
353: or /usr/adm/sudo.log if not.
1.1 millert 354:
1.12 millert 355: --with-loglen=NUMBER
1.1 millert 356: Number of characters per line for the file log. This is only used if
357: you are to "file" or "both". This value is used to decide when to wrap
358: lines for nicer log files. The default is 80. Setting this to 0
359: will disable the wrapping.
360:
361: --with-ignore-dot
362: If set, sudo will ignore '.' or '' (current dir) in $PATH.
363: The $PATH itself is not modified.
364:
1.12 millert 365: --with-mailto=USER|MAIL_ALIAS
366: User (or mail alias) that mail from sudo is sent to.
367: This should go to a sysadmin at your site. The default is "root".
1.1 millert 368:
1.12 millert 369: --with-mailsubject="SUBJECT OF MAIL"
1.1 millert 370: Subject of the mail sent to the "mailto" user. The token "%h"
371: will expand to the hostname of the machine.
372: Default is "*** SECURITY information for %h ***".
373:
374: --without-mail-if-no-user
1.4 millert 375: Normally, sudo will mail to the "alertmail" user if the user invoking
1.1 millert 376: sudo is not in the sudoers file. This option disables that behavior.
377:
378: --with-mail-if-no-host
379: Send mail to the "alermail" user if the user exists in the sudoers
380: file, but is not allowed to run commands on the current host.
381:
382: --with-mail-if-noperms
383: Send mail to the "alermail" user if the user is allowed to use sudo but
384: the command they are trying is not listed in their sudoers file entry.
385:
1.12 millert 386: --with-passprompt="PASSWORD PROMPT"
1.1 millert 387: Default prompt to use when asking for a password; can be overridden
388: via the -p option and the SUDO_PROMPT environment variable. Supports
1.17 ! millert 389: the "%H", "%h", "%U" and "%u" escapes as documented in the sudo
! 390: manual page. The default value is "Password:".
1.1 millert 391:
1.12 millert 392: --with-badpass-message="BAD PASSWORD MESSAGE"
1.1 millert 393: Message that is displayed if a user enters an incorrect password.
394: The default is "Sorry, try again." unless insults are turned on.
395:
396: --with-fqdn
1.16 millert 397: Define this if you want to put fully qualified hostnames in the sudoers
1.1 millert 398: file. Ie: instead of myhost you would use myhost.mydomain.edu. You may
399: still use the short form if you wish (and even mix the two). Beware
400: that turning FQDN on requires sudo to make DNS lookups which may make
401: sudo unusable if your DNS is totally hosed. Also note that you must
402: use the host's official name as DNS knows it. That is, you may not use
403: a host alias (CNAME entry) due to performance issues and the fact that
404: there is no way to get all aliases from DNS.
405:
1.12 millert 406: --with-timedir=PATH
1.1 millert 407: Override the default location of the sudo timestamp directory and
408: use "path" instead.
409:
1.12 millert 410: --with-sendmail=PATH
1.1 millert 411: Override configure's guess as to the location of sendmail.
412:
413: --without-sendmail
414: Do not use sendmail to mail messages to the "mailto" user.
415: Use only if don't run sendmail or the equivalent.
416:
1.12 millert 417: --with-umask=MASK
1.1 millert 418: Umask to use when running the root command. The default is 0022.
419:
420: --without-umask
421: Preserves the umask of the user invoking sudo.
422:
1.12 millert 423: --with-runas-default=USER
1.1 millert 424: The default user to run commands as if the -u flag is not specified
425: on the command line. This defaults to "root".
426:
1.12 millert 427: --with-exempt=GROUP
1.1 millert 428: Users in the specified group don't need to enter a password when
429: running sudo. This may be useful for sites that don't want their
430: "core" sysadmins to have to enter a password but where Jr. sysadmins
431: need to. You should probably use NOPASSWD in sudoers instead.
432:
1.12 millert 433: --with-passwd-tries=NUMBER
1.1 millert 434: Number of tries a user gets to enter his/her password before sudo logs
435: the failure and exits. The default is 3.
436:
1.12 millert 437: --with-timeout=NUMBER
1.1 millert 438: Number of minutes that can elapse before sudo will ask for a passwd
439: again. The default is 5, set this to 0 to always prompt for a password.
440:
1.12 millert 441: --with-password-timeout=NUMBER
1.1 millert 442: Number of minutes before the sudo password prompt times out.
443: The default is 5, set this to 0 for no password timeout.
444:
445: --with-tty-tickets
1.4 millert 446: This makes sudo use a different ticket file for each user/tty combo.
447: Ie: instead of the ticket path being "username" it is "username/tty".
1.1 millert 448: This is useful for "shared" accounts like "operator". Note that this
449: means that there will be more files in the timestamp dir. This is not
450: a problem if your system has a cron job to remove of files from /tmp
451: (or wherever you specified the timestamp dir to be).
452:
453: --with-insults
454: Define this if you want to be insulted for typing an incorrect password
455: just like the original sudo(8). This is off by default.
456:
457: --with-all-insults
1.7 millert 458: Include all the insult sets listed below. You must either specify
459: --with-insults or enable insults in the sudoers file for this to
460: have any effect.
1.1 millert 461:
462: --with-classic-insults
463: Uses insults from sudo "classic." If you just specify --with-insults
464: you will get the classic and CSOps insults. This is on by default if
465: --with-insults is given.
466:
467: --with-csops-insults
468: Insults the user with an extra set of insults (some quotes, some
469: original) from a sysadmin group at CU (CSOps). You must specify
470: --with-insults as well for this to have any effect. This is on by
471: default if --with-insults is given.
472:
473: --with-hal-insults
474: Uses 2001-like insults when an incorrect password is entered.
1.7 millert 475: You must either specify --with-insults or enable insults in the
476: sudoers file for this to have any effect.
1.1 millert 477:
478: --with-goons-insults
479: Insults the user with lines from the "Goon Show" when an incorrect
1.7 millert 480: password is entered. You must either specify --with-insults or
481: enable insults in the sudoers file for this to have any effect.
1.1 millert 482:
1.15 millert 483: --with-pc-insults
484: Replace politically incorrect insults with less objectionable ones.
485:
1.12 millert 486: --with-secure-path[=PATH]
1.1 millert 487: Path used for every command run from sudo(8). If you don't trust the
488: people running sudo to have a sane PATH environment variable you may
489: want to use this. Another use is if you want to have the "root path"
490: be separate from the "user path." You will need to customize the path
491: for your site. NOTE: this is not applied to users in the group
492: specified by --with-exemptgroup. If you do not specify a path,
493: "/bin:/usr/ucb:/usr/bin:/usr/sbin:/sbin:/usr/etc:/etc" is used.
494:
495: --without-lecture
496: Don't print the lecture the first time a user runs sudo.
497:
1.12 millert 498: --with-editor=PATH
1.15 millert 499: Specify the default editor path for use by visudo. This may be a
500: single pathname or a colon-separated list of editors. In the latter
501: case, visudo will choose the editor that matches the user's VISUAL
502: or EDITOR environment variables or the first editor in the list that
503: exists. The default is the path to vi on your system.
1.5 millert 504:
505: --with-env-editor
1.15 millert 506: Makes visudo consult the VISUAL and EDITOR environment variables before
1.7 millert 507: falling back on the default editor list (as specified by --with-editor).
508: Note that this may create a security hole as it allows the user to
509: run any arbitrary command as root without logging. A safer alternative
1.15 millert 510: is to use a colon-separated list of editors with the --with-editor
511: option. visudo will then only use the VISUAL or EDITOR variables
512: if they match a value specified via --with-editor.
1.5 millert 513:
1.1 millert 514: --disable-authentication
1.16 millert 515: By default, sudo requires the user to authenticate via a
516: password or similar means. This options causes sudo to
517: *not* require authentication. It is possible to turn
518: authentication back on in sudoers via the PASSWD attribute.
1.1 millert 519:
520: --disable-root-sudo
521: Don't let root run sudo. This can be used to prevent people from
522: "chaining" sudo commands to get a root shell by doing something
523: like "sudo sudo /bin/sh".
524:
525: --enable-log-host
526: Log the hostname in the log file.
1.3 millert 527:
528: --enable-noargs-shell
529: If sudo is invoked with no arguments it acts as if the "-s" flag had
530: been given. That is, it runs a shell as root (the shell is determined
531: by the SHELL environment variable, falling back on the shell listed
532: in the invoking user's /etc/passwd entry).
1.1 millert 533:
534: --enable-shell-sets-home
535: If sudo is invoked with the "-s" flag the HOME environment variable
536: will be set to the home directory of the target user (which is root
537: unless the "-u" option is used). This option effectively makes the
538: "-s" flag imply "-H".
539:
540: --disable-path-info
541: Normally, sudo will tell the user when a command could not be found
542: in their $PATH. Some sites may wish to disable this as it could
543: be used to gather information on the location of executables that
544: the normal user does not have access to. The disadvantage is that
545: if the executable is simply not in the user's path, sudo will tell
546: the user that they are not allowed to run it, which can be confusing.
547:
548: Shadow password and C2 support
549: ==============================
550:
551: Shadow passwords (also included with most C2 security packages) are
552: supported on most major platforms for which they exist. The
553: `configure' script will attempt to determine if your system can use
554: shadow passwords and include support for them if so. Shadow password
555: support is now compiled in by default (it doesn't hurt anything if you
556: don't have them configured). To disable the shadow password support,
557: use the --disable-shadow option to configure.
558:
559: Shadow passwords are known to work on the following platforms:
560:
561: SunOS 4.x
562: Solaris 2.x
563: HP-UX >= 9.x
564: Ultrix 4.x
565: Digital UNIX
566: IRIX >= 5.x
567: AIX >= 3.2.x
568: ConvexOS with C2 security (not tested recently)
569: Linux
570: SCO >= 3.2.2
571: Pyramid DC/OSx
572: UnixWare
573: SVR4 (and variants using standard SVR4 shadow passwords)
574: 4.4BSD based systems (including OpenBSD, NetBSD, FreeBSD, and BSD/OS)
575: OS's using SecureWare's C2 security.
576:
577: OS dependent notes
578: ==================
579:
580: OpenBSD < 2.2 and NetBSD < 1.2.1:
1.15 millert 581: The fdesc file system has a bug wrt /dev/tty handling that
1.1 millert 582: causes sudo to hang at the password prompt. The workaround
583: is to run configure with --with-password-timeout=0
584:
585: Solaris 2.x:
586: You need to have a C compiler in order to build sudo.
587: Since Solaris 2.x does not come with one by default this
588: means that you either need to have purchased the unbundled Sun
589: C compiler or have a copy of the GNU C compiler (gcc).
590: The SunSoft Catalyst CD should contain gcc binaries for
591: Solaris. You can also get them from various places on the
592: net, including http://www.sunfreeware.com/
593: NOTE: sudo will *not* build with the sun C compiler in BSD
1.16 millert 594: compatibility mode (/usr/ucb/cc). Sudo is designed to
595: compile with the standard C compiler (or gcc) and will
596: not build correctly with /usr/ucb/cc. You can use the
597: `--with-CC' option to point `configure' to the non-ucb
598: compiler if it is not the first cc in your path. Some
599: sites link /usr/ucb/cc to gcc; configure will not notice
600: this an still refuse to use /usr/ucb/cc, so make sure gcc
601: is also in your path if your site is setup this way.
1.1 millert 602: Also: Many versions of Solaris come with a broken syslogd.
603: If you have having problems with sudo logging you should
604: make sure you have the latest syslogd patch installed.
605: This is a problem for Solaris 2.4 and 2.5 at least.
606:
607: AIX 3.2.x:
608: I've had various problems with the AIX C compiler producing
609: incorrect code when the -O flag was used. When optimization
610: is not used, the problems go away. Gcc does not appear
611: to have this problem.
612:
613: Also, the AIX 3.2.x lex will not work with sudo's parse.lex.
614: This should not be a problem as sudo comes shipped with
615: a pre-generated lex.yy.c (created by flex). If you want
616: to modify the lex tokenizer, make sure you grab a copy of
617: flex from ftp.ee.lbl.gov (also available on most GNU mirrors)
618: and sudo will use that instead.
619:
620: Ultrix 4.x:
621: Ultrix still ships with the 4.2BSD syslog(3) which does not
622: allow things like logging different facilities to different
623: files, redirecting logs to a single loghost and other niceties.
624: You may want to just grab and install:
625: ftp://gatekeeper.dec.com/pub/DEC/jtkohl-syslog-complete.tar.Z
626: (available via anonymous ftp) which is a port if the 4.3BSD
627: syslog/syslogd that is backwards compatible with the Ultrix version.
628: I recommend it highly. If you do not do this you probably want
629: to run configure with --with-logging=file
630:
631: Digital UNIX:
632: By default, sudo will use SIA (Security Integration Architecture)
1.16 millert 633: to validate a user. If you want to use an alternative authentication
1.1 millert 634: method that does not go through SIA, you need to use the
635: --disable-sia option to configure. If you use gcc to compile
636: you will get warnings when building interfaces.c. These are
637: harmless but if they really bug you, you can edit
638: /usr/include/net/if.h around line 123, right after the comment:
639: /* forward decls for C++ */
640: change the line:
641: #ifdef __cplusplus
642: to:
643: #if defined(__cplusplus) || defined(__GNUC__)
644: If you don't like the idea of editing the system header file
645: you can just make a copy in gcc's private include tree and
646: edit that.
647:
648: Linux:
1.16 millert 649: PAM and LDAP headers are not installed by default on most Linux
650: systems. You will need to install the "pav-dev" package if
651: /usr/include/security/pam_appl.h is not present on your system.
652: If you wish to build with LDAP support you will also need the
653: openldap-devel package.
654:
1.1 millert 655: Versions of glibc 2.x previous to 2.0.7 have a broken lsearch().
656: You will need to either upgrade to glibc-2.0.7 or use sudo's
657: version of lsearch(). To use sudo's lsearch(), comment out
658: the "#define HAVE_LSEARCH 1" line in config.h and add lsearch.o
659: to the LIBOBJS line in the Makefile.
660:
1.9 millert 661: If you are using a Linux kernel older than 2.4 it is not possible
662: to access the sudoers file via NFS. This is due to a bug in
663: the Linux client-side NFS implementation that has since been
664: fixed. There is a workaround on the sudo ftp site, linux_nfs.patch,
665: if you need to NFS-mount sudoers on older Linux kernels.
1.11 millert 666:
1.1 millert 667: Mac OS X:
668: It has been reported that for sudo to work on Mac OS X it must
669: either be built with the --with-password-timeout=0 option or the
670: password timeout must be disabled in the Defaults line in the
671: sudoers file. If sudo just hangs when you try to enter a password,
672: you need to disable the password timeout (Note: this is not a bug
673: in sudo).
674:
675: SCO ODT:
676: You'll probably need libcrypt_i.a available via anonymous ftp
677: from sosco.sco.com. The necessary files are /SLS/lng225b.Z
678: and /SLS/lng225b.ltr.Z.
1.5 millert 679:
680: Dynix:
681: Some people have experienced problems building sudo with gcc
682: on Dynix. If you experience problems compiling sudo using gcc
683: on Dynix, try using the native compiler (cc). You can do so
684: by removing the config.cache file and then re-running configure
685: with the --with-CC=cc option.
1.15 millert 686:
687: HP-UX:
688: The default C compiler shipped with HP-UX does not support creating
689: position independent code and so is unable to support sudo's "noexec"
690: functionality. You must use either the HP ANSI C compiler or gcc for
691: noexec to work. Binary packages of gcc are available from
692: http://hpux.connect.org.uk/ and http://hpux.cs.utah.edu/.
1.16 millert 693:
694: SunOS 4.x:
695: The /bin/sh shipped with SunOS blows up while running configure.
696: You can work around this by installalling bash or zsh. If you
697: have bash or zsh in your path, configure will use it instead
698: automatically.