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

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