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

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