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.14

1.13 millert 1: Installation instructions for Sudo 1.6.7
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
35: change any of the default paths (alternately you could
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
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.14 ! 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.
! 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]
! 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.
! 134: This option is only valid for AIX where it is on by default.
1.12 millert 135:
136: --with-libraries=LIBRARY
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]
! 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.
! 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]
! 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.
! 170:
! 171: --with-kerb5[=DIR]
! 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:
178: --with-authenticate
179: Enable support for the AIX 4.x general authentication function.
180: This will use the authentication scheme specified for the user
181: on the machine.
182:
183: --with-pam
1.4 millert 184: Enable PAM support. Tested on:
185: Redhat Linux 5.x, 6.0, and 6.1
186: Solaris 2.6 and 7
187: HP-UX 11.0
188: NOTE: on RedHat Linux you *must* install an /etc/pam.d/sudo file.
189: You may either use the sample.pam file included with sudo or use
190: /etc/pam.d/su as a reference. On Solaris and HP-UX 11 systems
191: you should check (and understand) the contents of /etc/pam.conf.
192: Do a "man pam.conf" for more information and consider using the
193: "debug" option, if available, with your PAM libraries in
194: /etc/pam.conf to obtain syslog output for debugging purposes.
1.1 millert 195:
196: --with-AFS
1.13 millert 197: Enable AFS support with Kerberos authentication. Should work under
1.1 millert 198: AFS 3.3. If your AFS doesn't have -laudit you should be able to
199: link without it.
200:
201: --with-DCE
1.4 millert 202: Enable DCE support. Known to work on HP-UX 9.X, 10.X, and 11.0.
203: The use of PAM is recommended for HP-UX 11.X systems, since PAM is
204: fully implemented (this is not true for 10.20 and earlier versions).
205: Check to see that your 11.X (or other) system uses DCE via PAM by
206: looking at /etc/pam.conf to see if "libpam_dce" libraries are
207: referenced there. Other platforms may require source code and/or
208: `configure' changes; you should check to see if your platform can
209: access DCE via PAM before using this option.
1.1 millert 210:
1.5 millert 211: --with-logincap
1.6 millert 212: Enable support for BSD login classes where available (OS-dependent).
213: This adds support for the login classes specified in /etc/login.conf.
1.5 millert 214: By default, a login class is not applied unless the 'use_loginclass'
215: option is defined in sudoers or the user specifies a class on the
1.6 millert 216: command line.
217:
218: --with-bsdauth
1.9 millert 219: Enable support for BSD authentication on BSD/OS and OpenBSD.
1.12 millert 220: This option implies --with-logincap. It is not possible
221: to mix BSD authentication with other authentication methods
222: (and there really should be no need to do so). Note that
223: only the newer BSD authentication API is supported. If you
224: don't have /usr/include/bsd_auth.h then you cannot use this.
1.10 millert 225:
226: --disable-root-mailer
227: By default sudo will run the mailer as root when tattling
228: on a user so as to prevent that user from killing the mailer.
229: With this option, sudo will run the mailer as the invoking
230: user which some people consider to be safer.
1.9 millert 231:
232: --disable-saved-ids
1.12 millert 233: Disable use of POSIX saved IDs. Normally, sudo will try
234: to use POSIX saved IDs if they are supported. However,
235: some implementations are broken.
1.11 millert 236:
237: --disable-setreuid
1.12 millert 238: Disable use of the setreuid() function for operating systems
239: where it is broken. 4.4BSD has setreuid() but it doesn't
240: really work.
1.5 millert 241:
1.13 millert 242: --disable-setresuid
243: Disable use of the setresuid() function for operating systems
244: where it is broken (none currently known).
245:
1.1 millert 246: --disable-sia
1.12 millert 247: Disable SIA support. This is the "Security Integration
248: Architecture" on Digital UNIX. If you disable SIA sudo will
249: use its own authentication routines.
1.1 millert 250:
251: --disable-shadow
1.12 millert 252: Disable shadow password support. Normally, sudo will compile
253: in shadow password support and use a shadow password if it
254: exists.
255:
256: --with-sudoers-mode=MODE
257: File mode for the sudoers file (octal). Note that if you
258: wish to NFS-mount the sudoers file this must be group
259: readable. Also note that this is actually set in the
260: Makefile. The default mode is 0440.
261:
262: --with-sudoers-uid=UID
263: User id that "owns" the sudoers file. Note that this is
264: the numeric id, *not* the symbolic name. Also note that
265: this is actually set in the Makefile. The default is 0.
266:
267: --with-sudoers-gid=GID
268: Group id that "owns" the sudoers file. Note that this is
269: the numeric id, *not* the symbolic name. Also note that
270: this is actually set in the Makefile. The default is 0.
1.1 millert 271:
272: --with-execv
273: Use execv() to exec the command instead of execvp(). I can't think of
274: a reason to actually do this since execvp() is passed a fully qualified
275: pathname but someone might thoroughly distrust execvp(). Note that if
276: you define this you lose the ability to exec scripts that are missing
277: the '#!/bin/sh' cookie (like /bin/kill on SunOS and /etc/fastboot on
278: 4.3BSD). This is off by default.
279:
280: --without-interfaces
1.12 millert 281: This option keeps sudo from trying to glean the ip address
282: from each attached ethernet interface. It is only useful
283: on a machine where sudo's interface reading support does
284: not work, which may be the case on some SysV-based OS's
285: using STREAMS.
1.1 millert 286:
287: --without-passwd
1.12 millert 288: This option excludes authentication via the passwd (or
289: shadow) file. It should only be used when another, alternate,
290: authentication scheme is in use.
1.1 millert 291:
292: --with-otp-only
1.12 millert 293: This option is now just an alias for --without-passwd.
1.13 millert 294:
295: --with-stow
296: Properly handle GNU stow packaging. The sudoers file will
297: physically live in ${prefix}/etc and /etc/sudoers will be
298: a symbolic link.
1.1 millert 299:
1.4 millert 300: The following options are also configurable at runtime:
301:
1.1 millert 302: --with-long-otp-prompt
1.12 millert 303: When validating with a One Time Password scheme (S/Key or
304: OPIE), a two-line prompt is used to make it easier to cut
305: and paste the challenge to a local window. It's not as
306: pretty as the default but some people find it more convenient.
1.1 millert 307:
308: --with-logging=TYPE
1.12 millert 309: How you want to do your logging. You may choose "syslog",
310: "file", or "both". Setting this to "syslog" is nice because
311: you can keep all of your sudo logs in one place (see the
312: sample.syslog.conf file). The default is "syslog".
1.1 millert 313:
314: --with-logfac=FACILITY
1.12 millert 315: Determines which syslog facility to log to. This requires
316: a 4.3BSD or later version of syslog. You can still set
317: this for ancient syslogs but it will have no effect. The
318: following facilities are supported: authpriv (if your OS
319: supports it), auth, daemon, user, local0, local1, local2,
320: local3, local4, local5, local6, and local7.
1.1 millert 321:
322: --with-goodpri=PRIORITY
1.12 millert 323: Determines which syslog priority to log successfully
324: authenticated commands. The following priorities are
325: supported: alert, crit, debug, emerg, err, info, notice,
326: and warning.
1.1 millert 327:
328: --with-badpri=PRIORITY
1.12 millert 329: Determines which syslog priority to log unauthenticated
330: commands and errors. The following priorities are supported:
331: alert, crit, debug, emerg, err, info, notice, and warning.
332:
333: --with-logpath=PATH
334: Override the default location of the sudo log file and use
335: "path" instead. By default will use /var/log/sudo.log if
336: there is a /var/log dir, falling back to /var/adm/sudo.log
337: or /usr/adm/sudo.log if not.
1.1 millert 338:
1.12 millert 339: --with-loglen=NUMBER
1.1 millert 340: Number of characters per line for the file log. This is only used if
341: you are to "file" or "both". This value is used to decide when to wrap
342: lines for nicer log files. The default is 80. Setting this to 0
343: will disable the wrapping.
344:
345: --with-ignore-dot
346: If set, sudo will ignore '.' or '' (current dir) in $PATH.
347: The $PATH itself is not modified.
348:
1.12 millert 349: --with-mailto=USER|MAIL_ALIAS
350: User (or mail alias) that mail from sudo is sent to.
351: This should go to a sysadmin at your site. The default is "root".
1.1 millert 352:
1.12 millert 353: --with-mailsubject="SUBJECT OF MAIL"
1.1 millert 354: Subject of the mail sent to the "mailto" user. The token "%h"
355: will expand to the hostname of the machine.
356: Default is "*** SECURITY information for %h ***".
357:
358: --without-mail-if-no-user
1.4 millert 359: Normally, sudo will mail to the "alertmail" user if the user invoking
1.1 millert 360: sudo is not in the sudoers file. This option disables that behavior.
361:
362: --with-mail-if-no-host
363: Send mail to the "alermail" user if the user exists in the sudoers
364: file, but is not allowed to run commands on the current host.
365:
366: --with-mail-if-noperms
367: Send mail to the "alermail" user if the user is allowed to use sudo but
368: the command they are trying is not listed in their sudoers file entry.
369:
1.12 millert 370: --with-passprompt="PASSWORD PROMPT"
1.1 millert 371: Default prompt to use when asking for a password; can be overridden
372: via the -p option and the SUDO_PROMPT environment variable. Supports
373: two escapes: "%u" expands to the user's login name and "%h" expands
374: to the local hostname. Default is "Password:".
375:
1.12 millert 376: --with-badpass-message="BAD PASSWORD MESSAGE"
1.1 millert 377: Message that is displayed if a user enters an incorrect password.
378: The default is "Sorry, try again." unless insults are turned on.
379:
380: --with-fqdn
381: Define this if you want to put fully qualified hostnames in the sudoers
382: file. Ie: instead of myhost you would use myhost.mydomain.edu. You may
383: still use the short form if you wish (and even mix the two). Beware
384: that turning FQDN on requires sudo to make DNS lookups which may make
385: sudo unusable if your DNS is totally hosed. Also note that you must
386: use the host's official name as DNS knows it. That is, you may not use
387: a host alias (CNAME entry) due to performance issues and the fact that
388: there is no way to get all aliases from DNS.
389:
1.12 millert 390: --with-timedir=PATH
1.1 millert 391: Override the default location of the sudo timestamp directory and
392: use "path" instead.
393:
1.12 millert 394: --with-sendmail=PATH
1.1 millert 395: Override configure's guess as to the location of sendmail.
396:
397: --without-sendmail
398: Do not use sendmail to mail messages to the "mailto" user.
399: Use only if don't run sendmail or the equivalent.
400:
1.12 millert 401: --with-umask=MASK
1.1 millert 402: Umask to use when running the root command. The default is 0022.
403:
404: --without-umask
405: Preserves the umask of the user invoking sudo.
406:
1.12 millert 407: --with-runas-default=USER
1.1 millert 408: The default user to run commands as if the -u flag is not specified
409: on the command line. This defaults to "root".
410:
1.12 millert 411: --with-exempt=GROUP
1.1 millert 412: Users in the specified group don't need to enter a password when
413: running sudo. This may be useful for sites that don't want their
414: "core" sysadmins to have to enter a password but where Jr. sysadmins
415: need to. You should probably use NOPASSWD in sudoers instead.
416:
1.12 millert 417: --with-passwd-tries=NUMBER
1.1 millert 418: Number of tries a user gets to enter his/her password before sudo logs
419: the failure and exits. The default is 3.
420:
1.12 millert 421: --with-timeout=NUMBER
1.1 millert 422: Number of minutes that can elapse before sudo will ask for a passwd
423: again. The default is 5, set this to 0 to always prompt for a password.
424:
1.12 millert 425: --with-password-timeout=NUMBER
1.1 millert 426: Number of minutes before the sudo password prompt times out.
427: The default is 5, set this to 0 for no password timeout.
428:
429: --with-tty-tickets
1.4 millert 430: This makes sudo use a different ticket file for each user/tty combo.
431: Ie: instead of the ticket path being "username" it is "username/tty".
1.1 millert 432: This is useful for "shared" accounts like "operator". Note that this
433: means that there will be more files in the timestamp dir. This is not
434: a problem if your system has a cron job to remove of files from /tmp
435: (or wherever you specified the timestamp dir to be).
436:
437: --with-insults
438: Define this if you want to be insulted for typing an incorrect password
439: just like the original sudo(8). This is off by default.
440:
441: --with-all-insults
1.7 millert 442: Include all the insult sets listed below. You must either specify
443: --with-insults or enable insults in the sudoers file for this to
444: have any effect.
1.1 millert 445:
446: --with-classic-insults
447: Uses insults from sudo "classic." If you just specify --with-insults
448: you will get the classic and CSOps insults. This is on by default if
449: --with-insults is given.
450:
451: --with-csops-insults
452: Insults the user with an extra set of insults (some quotes, some
453: original) from a sysadmin group at CU (CSOps). You must specify
454: --with-insults as well for this to have any effect. This is on by
455: default if --with-insults is given.
456:
457: --with-hal-insults
458: Uses 2001-like insults when an incorrect password is entered.
1.7 millert 459: You must either specify --with-insults or enable insults in the
460: sudoers file for this to have any effect.
1.1 millert 461:
462: --with-goons-insults
463: Insults the user with lines from the "Goon Show" when an incorrect
1.7 millert 464: password is entered. You must either specify --with-insults or
465: enable insults in the sudoers file for this to have any effect.
1.1 millert 466:
1.12 millert 467: --with-secure-path[=PATH]
1.1 millert 468: Path used for every command run from sudo(8). If you don't trust the
469: people running sudo to have a sane PATH environment variable you may
470: want to use this. Another use is if you want to have the "root path"
471: be separate from the "user path." You will need to customize the path
472: for your site. NOTE: this is not applied to users in the group
473: specified by --with-exemptgroup. If you do not specify a path,
474: "/bin:/usr/ucb:/usr/bin:/usr/sbin:/sbin:/usr/etc:/etc" is used.
475:
476: --without-lecture
477: Don't print the lecture the first time a user runs sudo.
478:
1.12 millert 479: --with-editor=PATH
1.7 millert 480: Specify the default editor path for use by visudo. This may be
481: a single pathname or a colon-separated list of editors. In
482: the latter case, visudo will choose the editor that matches
483: the user's USER environment variable or the first editor in
484: the list that exists. The default is the path to vi on your system.
1.5 millert 485:
486: --with-env-editor
487: Makes visudo consult the EDITOR and VISUAL environment variables before
1.7 millert 488: falling back on the default editor list (as specified by --with-editor).
489: Note that this may create a security hole as it allows the user to
490: run any arbitrary command as root without logging. A safer alternative
491: is to use a colon-separated list of editors with the --with-env-editor
492: option. visudo will then only use the EDITOR or VISUAL if they match
493: a value specified via --with-editor.
1.5 millert 494:
1.1 millert 495: --disable-authentication
496: By default, sudo requires the user to authenticate via a
497: password or similar means. This options causes sudo to
498: *not* require authentication. It is possible to turn
499: authentication back on in sudoers via the PASSWD attribute.
500:
501: --disable-root-sudo
502: Don't let root run sudo. This can be used to prevent people from
503: "chaining" sudo commands to get a root shell by doing something
504: like "sudo sudo /bin/sh".
505:
506: --enable-log-host
507: Log the hostname in the log file.
1.3 millert 508:
509: --enable-noargs-shell
510: If sudo is invoked with no arguments it acts as if the "-s" flag had
511: been given. That is, it runs a shell as root (the shell is determined
512: by the SHELL environment variable, falling back on the shell listed
513: in the invoking user's /etc/passwd entry).
1.1 millert 514:
515: --enable-shell-sets-home
516: If sudo is invoked with the "-s" flag the HOME environment variable
517: will be set to the home directory of the target user (which is root
518: unless the "-u" option is used). This option effectively makes the
519: "-s" flag imply "-H".
520:
521: --disable-path-info
522: Normally, sudo will tell the user when a command could not be found
523: in their $PATH. Some sites may wish to disable this as it could
524: be used to gather information on the location of executables that
525: the normal user does not have access to. The disadvantage is that
526: if the executable is simply not in the user's path, sudo will tell
527: the user that they are not allowed to run it, which can be confusing.
528:
529: Shadow password and C2 support
530: ==============================
531:
532: Shadow passwords (also included with most C2 security packages) are
533: supported on most major platforms for which they exist. The
534: `configure' script will attempt to determine if your system can use
535: shadow passwords and include support for them if so. Shadow password
536: support is now compiled in by default (it doesn't hurt anything if you
537: don't have them configured). To disable the shadow password support,
538: use the --disable-shadow option to configure.
539:
540: Shadow passwords are known to work on the following platforms:
541:
542: SunOS 4.x
543: Solaris 2.x
544: HP-UX >= 9.x
545: Ultrix 4.x
546: Digital UNIX
547: IRIX >= 5.x
548: AIX >= 3.2.x
549: ConvexOS with C2 security (not tested recently)
550: Linux
551: SCO >= 3.2.2
552: Pyramid DC/OSx
553: UnixWare
554: SVR4 (and variants using standard SVR4 shadow passwords)
555: 4.4BSD based systems (including OpenBSD, NetBSD, FreeBSD, and BSD/OS)
556: OS's using SecureWare's C2 security.
557:
558: OS dependent notes
559: ==================
560:
561: OpenBSD < 2.2 and NetBSD < 1.2.1:
562: The fdesc filesystem has a bug wrt /dev/tty handling that
563: causes sudo to hang at the password prompt. The workaround
564: is to run configure with --with-password-timeout=0
565:
566: Solaris 2.x:
567: You need to have a C compiler in order to build sudo.
568: Since Solaris 2.x does not come with one by default this
569: means that you either need to have purchased the unbundled Sun
570: C compiler or have a copy of the GNU C compiler (gcc).
571: The SunSoft Catalyst CD should contain gcc binaries for
572: Solaris. You can also get them from various places on the
573: net, including http://www.sunfreeware.com/
574: NOTE: sudo will *not* build with the sun C compiler in BSD
575: compatibility mode (/usr/ucb/cc). Sudo is designed to
576: compile with the standard C compiler (or gcc) and will
577: not build correctly with /usr/ucb/cc. You can use the
578: `--with-CC' option to point `configure' to the non-ucb
579: compiler if it is not the first cc in your path. Some
580: sites link /usr/ucb/cc to gcc; configure will not notice
581: this an still refuse to use /usr/ucb/cc, so make sure gcc
582: is also in your path if your site is setup this way.
583: Also: Many versions of Solaris come with a broken syslogd.
584: If you have having problems with sudo logging you should
585: make sure you have the latest syslogd patch installed.
586: This is a problem for Solaris 2.4 and 2.5 at least.
587:
588: AIX 3.2.x:
589: I've had various problems with the AIX C compiler producing
590: incorrect code when the -O flag was used. When optimization
591: is not used, the problems go away. Gcc does not appear
592: to have this problem.
593:
594: Also, the AIX 3.2.x lex will not work with sudo's parse.lex.
595: This should not be a problem as sudo comes shipped with
596: a pre-generated lex.yy.c (created by flex). If you want
597: to modify the lex tokenizer, make sure you grab a copy of
598: flex from ftp.ee.lbl.gov (also available on most GNU mirrors)
599: and sudo will use that instead.
600:
601: Ultrix 4.x:
602: Ultrix still ships with the 4.2BSD syslog(3) which does not
603: allow things like logging different facilities to different
604: files, redirecting logs to a single loghost and other niceties.
605: You may want to just grab and install:
606: ftp://gatekeeper.dec.com/pub/DEC/jtkohl-syslog-complete.tar.Z
607: (available via anonymous ftp) which is a port if the 4.3BSD
608: syslog/syslogd that is backwards compatible with the Ultrix version.
609: I recommend it highly. If you do not do this you probably want
610: to run configure with --with-logging=file
611:
612: Digital UNIX:
613: By default, sudo will use SIA (Security Integration Architecture)
614: to validate a user. If you want to use an alternate authentication
615: method that does not go through SIA, you need to use the
616: --disable-sia option to configure. If you use gcc to compile
617: you will get warnings when building interfaces.c. These are
618: harmless but if they really bug you, you can edit
619: /usr/include/net/if.h around line 123, right after the comment:
620: /* forward decls for C++ */
621: change the line:
622: #ifdef __cplusplus
623: to:
624: #if defined(__cplusplus) || defined(__GNUC__)
625: If you don't like the idea of editing the system header file
626: you can just make a copy in gcc's private include tree and
627: edit that.
628:
629: Linux:
630: NOTE: Reportedly, Linux's execvp(3) doesn't always execute
631: scripts that lack the "#!/some/shell" header correctly.
632: The workaround is to give all your scripts a proper
633: header.
634: Versions of glibc 2.x previous to 2.0.7 have a broken lsearch().
635: You will need to either upgrade to glibc-2.0.7 or use sudo's
636: version of lsearch(). To use sudo's lsearch(), comment out
637: the "#define HAVE_LSEARCH 1" line in config.h and add lsearch.o
638: to the LIBOBJS line in the Makefile.
639:
1.9 millert 640: If you are using a Linux kernel older than 2.4 it is not possible
641: to access the sudoers file via NFS. This is due to a bug in
642: the Linux client-side NFS implementation that has since been
643: fixed. There is a workaround on the sudo ftp site, linux_nfs.patch,
644: if you need to NFS-mount sudoers on older Linux kernels.
1.11 millert 645:
646: Linux kernels 2.2.16-2.2.19 appear to have broken POSIX saved
647: ID support. You must run configure with the --disable-saved-ids
648: flag to get a working sudo.
1.1 millert 649:
650: Mac OS X:
651: It has been reported that for sudo to work on Mac OS X it must
652: either be built with the --with-password-timeout=0 option or the
653: password timeout must be disabled in the Defaults line in the
654: sudoers file. If sudo just hangs when you try to enter a password,
655: you need to disable the password timeout (Note: this is not a bug
656: in sudo).
657:
658: SCO ODT:
659: You'll probably need libcrypt_i.a available via anonymous ftp
660: from sosco.sco.com. The necessary files are /SLS/lng225b.Z
661: and /SLS/lng225b.ltr.Z.
1.5 millert 662:
663: Dynix:
664: Some people have experienced problems building sudo with gcc
665: on Dynix. If you experience problems compiling sudo using gcc
666: on Dynix, try using the native compiler (cc). You can do so
667: by removing the config.cache file and then re-running configure
668: with the --with-CC=cc option.