1 Installation instructions for Sudo 1.7
2 ======================================
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.
10 Simple sudo installation
11 ========================
13 For most systems and configurations it is possible simply to:
15 0) If you are upgrading from a previous version of sudo
16 please read the info in the UPGRADE file before proceeding.
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'.
24 2) Read the `OS dependent notes' section for any particular
25 "gotchas" relating to your operating system.
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
34 4) Edit the configure-generated Makefile if you wish to
35 change any of the default paths (alternatively, you could
36 have changed the paths via options to `configure'.
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).
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.
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.
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.
61 Available configure options
62 ===========================
64 This section describes flags accepted by the sudo's `configure' script.
65 Defaults are listed in brackets after the description.
69 Cache test results in FILE
72 Alias for `--cache-file=config.cache'
75 Print the usage/help info
78 Do not create output files
81 Do not print `checking...' messages
83 Directory and file names:
85 Install architecture-independent files in PREFIX This really only
86 applies to man pages. [/usr/local]
89 Install architecture-dependent files in EPREFIX This includes the
90 sudo and visudo executables. [same as prefix]
93 Install `sudo' in DIR [EPREFIX/bin]
96 Install `visudo' in DIR [EPREFIX/sbin]
99 Install `sudoers' file in DIR [/etc]
102 Install man pages in DIR [PREFIX/man]
105 Find the sources in DIR [configure dir or ..]
107 Special features/options:
109 Specifies path to C compiler you wish to use.
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.
116 Eg: --with-incpath="/usr/local/include /opt/include"
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.
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.
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.
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.
144 Add CSOps standard options. You probably aren't interested in this.
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.
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.
157 Enable SecurID support. If specified, DIR is directory containing
158 sdiclient.a, sdi_athd.h, sdconf.h, and sdacmvls.h.
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).
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.
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.
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.
183 --with-ldap-conf-file=filename
184 Path to LDAP configuration file. If specified, sudo reads
185 this file instead of /etc/ldap.conf to locate the LDAP server.
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.
192 --with-nsswitch[=filename]
193 Path to nsswitch.conf or "no" to disable nsswitch support.
194 If specified, sudo uses this file instead of /etc/nsswitch.conf.
195 If nsswitch is disabled but LDAP is enabled, sudo will check
196 LDAP first, then the sudoers file.
198 --with-netsvc[=filename]
199 Path to netsvc.conf or "no" to disable netsvc.conf support.
200 If specified, sudo uses this file instead of /etc/netsvc.conf
204 Enable support for the AIX 4.x general authentication function.
205 This will use the authentication scheme specified for the user
206 on the machine. It is on by default for AIX systems that
210 Enable PAM support. This is on by default for Darwin, FreeBSD,
211 Linux, Solaris and HP-UX (version 11 and higher).
213 NOTE: on RedHat Linux and Fedora you *must* have an /etc/pam.d/sudo
214 file install. You may either use the sample.pam file included with
215 sudo or use /etc/pam.d/su as a reference. The sample.pam file
216 included with sudo may or may not work with other Linux distributions.
217 On Solaris and HP-UX 11 systems you should check (and understand)
218 the contents of /etc/pam.conf. Do a "man pam.conf" for more
219 information and consider using the "debug" option, if available,
220 with your PAM libraries in /etc/pam.conf to obtain syslog output
221 for debugging purposes.
224 Enable AFS support with Kerberos authentication. Should work under
225 AFS 3.3. If your AFS doesn't have -laudit you should be able to
229 Enable DCE support for systems without PAM. Known to work on
230 HP-UX 9.X, 10.X, and 11.0; other systems may require source
231 code and/or `configure' changes. On systems with PAM support
232 (such as HP-UX 11.0 and higher, Solaris, FreeBSD and Linux), the
233 DCE PAM module (usually libpam_dce) should be used instead.
236 This adds support for login classes specified in /etc/login.conf.
237 It is enabled by default on BSD/OS, Darwin, FreeBSD, OpenBSD and
238 NetBSD (where available). By default, a login class is not applied
239 unless the 'use_loginclass' option is defined in sudoers or the user
240 specifies a class on the command line.
243 Enable support for BSD authentication. This is the default
244 for BSD/OS and OpenBSD systems that support it.
245 It is not possible to mix BSD authentication with other
246 authentication methods (and there really should be no need
247 to do so). Note that only the newer BSD authentication API
248 is supported. If you don't have /usr/include/bsd_auth.h
249 then you cannot use this.
252 Enable support for Solaris project resource limits.
253 This option is only available on Solaris 9 and above.
256 Enable support for the "noexec" functionality which prevents
257 a dynamically-linked program being run by sudo from executing
258 another program (think shell escapes). Please see the
259 "PREVENTING SHELL ESCAPES" section in the sudoers man page
260 for details. If specified, PATH should be a fully qualified
261 pathname, e.g. /usr/local/libexec/sudo_noexec.so. If PATH
262 is "no", noexec support will not be compiled in. The default
263 is to compile noexec support if libtool supports building
264 shared objects on your OS.
266 --disable-pam-session
267 Disable sudo's PAM session support. This may be needed on
268 older PAM implementations or on operating systems where
269 opening a PAM session changes the utmp or wtmp files. If
270 PAM session support is disabled, resource limits may not
271 be updatedin for command being run.
273 --disable-root-mailer
274 By default sudo will run the mailer as root when tattling
275 on a user so as to prevent that user from killing the mailer.
276 With this option, sudo will run the mailer as the invoking
277 user which some people consider to be safer.
280 Disable use of the setreuid() function for operating systems
281 where it is broken. Mac OS X has setreuid() but it doesn't
285 Disable use of the setresuid() function for operating systems
286 where it is broken (none currently known).
289 Disable SIA support. This is the "Security Integration
290 Architecture" on Digital UNIX. If you disable SIA sudo will
291 use its own authentication routines.
294 Disable shadow password support. Normally, sudo will compile
295 in shadow password support and use a shadow password if it
298 --with-sudoers-mode=MODE
299 File mode for the sudoers file (octal). Note that if you
300 wish to NFS-mount the sudoers file this must be group
301 readable. Also note that this is actually set in the
302 Makefile. The default mode is 0440.
304 --with-sudoers-uid=UID
305 User id that "owns" the sudoers file. Note that this is
306 the numeric id, *not* the symbolic name. Also note that
307 this is actually set in the Makefile. The default is 0.
309 --with-sudoers-gid=GID
310 Group id that "owns" the sudoers file. Note that this is
311 the numeric id, *not* the symbolic name. Also note that
312 this is actually set in the Makefile. The default is 0.
315 This option keeps sudo from trying to glean the ip address
316 from each attached ethernet interface. It is only useful
317 on a machine where sudo's interface reading support does
318 not work, which may be the case on some SysV-based OS's
322 This option excludes authentication via the passwd (or
323 shadow) file. It should only be used when another, alternative,
324 authentication scheme is in use.
327 This option is now just an alias for --without-passwd.
330 Properly handle GNU stow packaging. The sudoers file will
331 physically live in ${prefix}/etc and /etc/sudoers will be
335 Enable support for role based access control (RBAC) on
336 systems that support SELinux.
339 Enable non-Unix group support using Quest Authentication
340 Services. If NAME is specified, it should be the name of
341 the shared library providing QAS support (libvas.so by default).
343 --with-libvas-rpath=[PATH]
344 The path to search when loading libvas.so (or an alternate
345 name as specified by --with-libvas). This option only has
346 an effect when --with-libvas is specified.
348 The following options are also configurable at runtime:
350 --with-long-otp-prompt
351 When validating with a One Time Password scheme (S/Key or
352 OPIE), a two-line prompt is used to make it easier to cut
353 and paste the challenge to a local window. It's not as
354 pretty as the default but some people find it more convenient.
357 How you want to do your logging. You may choose "syslog",
358 "file", or "both". Setting this to "syslog" is nice because
359 you can keep all of your sudo logs in one place (see the
360 sample.syslog.conf file). The default is "syslog".
362 --with-logfac=FACILITY
363 Determines which syslog facility to log to. This requires
364 a 4.3BSD or later version of syslog. You can still set
365 this for ancient syslogs but it will have no effect. The
366 following facilities are supported: authpriv (if your OS
367 supports it), auth, daemon, user, local0, local1, local2,
368 local3, local4, local5, local6, and local7.
370 --with-goodpri=PRIORITY
371 Determines which syslog priority to log successfully
372 authenticated commands. The following priorities are
373 supported: alert, crit, debug, emerg, err, info, notice,
376 --with-badpri=PRIORITY
377 Determines which syslog priority to log unauthenticated
378 commands and errors. The following priorities are supported:
379 alert, crit, debug, emerg, err, info, notice, and warning.
382 Override the default location of the sudo log file and use
383 "path" instead. By default will use /var/log/sudo.log if
384 there is a /var/log dir, falling back to /var/adm/sudo.log
385 or /usr/adm/sudo.log if not.
388 Number of characters per line for the file log. This is only used if
389 you are to "file" or "both". This value is used to decide when to wrap
390 lines for nicer log files. The default is 80. Setting this to 0
391 will disable the wrapping.
394 If set, sudo will ignore '.' or '' (current dir) in $PATH.
395 The $PATH itself is not modified.
397 --with-mailto=USER|MAIL_ALIAS
398 User (or mail alias) that mail from sudo is sent to.
399 This should go to a sysadmin at your site. The default is "root".
401 --with-mailsubject="SUBJECT OF MAIL"
402 Subject of the mail sent to the "mailto" user. The token "%h"
403 will expand to the hostname of the machine.
404 Default is "*** SECURITY information for %h ***".
406 --without-mail-if-no-user
407 Normally, sudo will mail to the "alertmail" user if the user invoking
408 sudo is not in the sudoers file. This option disables that behavior.
410 --with-mail-if-no-host
411 Send mail to the "alermail" user if the user exists in the sudoers
412 file, but is not allowed to run commands on the current host.
414 --with-mail-if-noperms
415 Send mail to the "alermail" user if the user is allowed to use sudo but
416 the command they are trying is not listed in their sudoers file entry.
418 --with-passprompt="PASSWORD PROMPT"
419 Default prompt to use when asking for a password; can be overridden
420 via the -p option and the SUDO_PROMPT environment variable. Supports
421 the "%H", "%h", "%U" and "%u" escapes as documented in the sudo
422 manual page. The default value is "Password:".
424 --with-badpass-message="BAD PASSWORD MESSAGE"
425 Message that is displayed if a user enters an incorrect password.
426 The default is "Sorry, try again." unless insults are turned on.
429 Define this if you want to put fully qualified hostnames in the sudoers
430 file. Ie: instead of myhost you would use myhost.mydomain.edu. You may
431 still use the short form if you wish (and even mix the two). Beware
432 that turning FQDN on requires sudo to make DNS lookups which may make
433 sudo unusable if your DNS is totally hosed. Also note that you must
434 use the host's official name as DNS knows it. That is, you may not use
435 a host alias (CNAME entry) due to performance issues and the fact that
436 there is no way to get all aliases from DNS.
439 Override the default location of the sudo timestamp directory and
443 Override configure's guess as to the location of sendmail.
446 Do not use sendmail to mail messages to the "mailto" user.
447 Use only if don't run sendmail or the equivalent.
450 Umask to use when running the root command. The default is 0022.
453 Preserves the umask of the user invoking sudo.
455 --with-runas-default=USER
456 The default user to run commands as if the -u flag is not specified
457 on the command line. This defaults to "root".
460 Users in the specified group don't need to enter a password when
461 running sudo. This may be useful for sites that don't want their
462 "core" sysadmins to have to enter a password but where Jr. sysadmins
463 need to. You should probably use NOPASSWD in sudoers instead.
465 --with-passwd-tries=NUMBER
466 Number of tries a user gets to enter his/her password before sudo logs
467 the failure and exits. The default is 3.
469 --with-timeout=NUMBER
470 Number of minutes that can elapse before sudo will ask for a passwd
471 again. The default is 5, set this to 0 to always prompt for a password.
473 --with-password-timeout=NUMBER
474 Number of minutes before the sudo password prompt times out.
475 The default is 5, set this to 0 for no password timeout.
478 This makes sudo use a different ticket file for each user/tty combo.
479 Ie: instead of the ticket path being "username" it is "username/tty".
480 This is useful for "shared" accounts like "operator". Note that this
481 means that there will be more files in the timestamp dir. This is not
482 a problem if your system has a cron job to remove of files from /tmp
483 (or wherever you specified the timestamp dir to be).
486 Define this if you want to be insulted for typing an incorrect password
487 just like the original sudo(8). This is off by default.
490 Include all the insult sets listed below. You must either specify
491 --with-insults or enable insults in the sudoers file for this to
494 --with-classic-insults
495 Uses insults from sudo "classic." If you just specify --with-insults
496 you will get the classic and CSOps insults. This is on by default if
497 --with-insults is given.
500 Insults the user with an extra set of insults (some quotes, some
501 original) from a sysadmin group at CU (CSOps). You must specify
502 --with-insults as well for this to have any effect. This is on by
503 default if --with-insults is given.
506 Uses 2001-like insults when an incorrect password is entered.
507 You must either specify --with-insults or enable insults in the
508 sudoers file for this to have any effect.
511 Insults the user with lines from the "Goon Show" when an incorrect
512 password is entered. You must either specify --with-insults or
513 enable insults in the sudoers file for this to have any effect.
516 Replace politically incorrect insults with less objectionable ones.
518 --with-secure-path[=PATH]
519 Path used for every command run from sudo(8). If you don't trust the
520 people running sudo to have a sane PATH environment variable you may
521 want to use this. Another use is if you want to have the "root path"
522 be separate from the "user path." You will need to customize the path
523 for your site. NOTE: this is not applied to users in the group
524 specified by --with-exemptgroup. If you do not specify a path,
525 "/bin:/usr/ucb:/usr/bin:/usr/sbin:/sbin:/usr/etc:/etc" is used.
528 Don't print the lecture the first time a user runs sudo.
531 Specify the default editor path for use by visudo. This may be a
532 single pathname or a colon-separated list of editors. In the latter
533 case, visudo will choose the editor that matches the user's VISUAL
534 or EDITOR environment variables or the first editor in the list that
535 exists. The default is the path to vi on your system.
538 Makes visudo consult the VISUAL and EDITOR environment variables before
539 falling back on the default editor list (as specified by --with-editor).
540 Note that this may create a security hole as it allows the user to
541 run any arbitrary command as root without logging. A safer alternative
542 is to use a colon-separated list of editors with the --with-editor
543 option. visudo will then only use the VISUAL or EDITOR variables
544 if they match a value specified via --with-editor.
547 Set PATH as the "askpass" program to use when no tty is
548 available. Typically, this is a graphical password prompter,
549 similar to the one used by ssh. The program must take a
550 prompt as an argument and print the received password to
553 --disable-authentication
554 By default, sudo requires the user to authenticate via a
555 password or similar means. This options causes sudo to
556 *not* require authentication. It is possible to turn
557 authentication back on in sudoers via the PASSWD attribute.
560 Don't let root run sudo. This can be used to prevent people from
561 "chaining" sudo commands to get a root shell by doing something
562 like "sudo sudo /bin/sh".
564 --enable-gss-krb5-ccache-name
565 Use the gss_krb5_ccache_name() function to set the Kerberos
566 V credential cache file name. By default, sudo will use
567 the KRB5CCNAME environment variable to set this. While
568 gss_krb5_ccache_name() provides a better API to do this it
569 is not supported by all Kerberos V and SASL combinations.
572 Log the hostname in the log file.
574 --enable-noargs-shell
575 If sudo is invoked with no arguments it acts as if the "-s" flag had
576 been given. That is, it runs a shell as root (the shell is determined
577 by the SHELL environment variable, falling back on the shell listed
578 in the invoking user's /etc/passwd entry).
580 --enable-shell-sets-home
581 If sudo is invoked with the "-s" flag the HOME environment variable
582 will be set to the home directory of the target user (which is root
583 unless the "-u" option is used). This option effectively makes the
584 "-s" flag imply "-H".
587 Normally, sudo will tell the user when a command could not be found
588 in their $PATH. Some sites may wish to disable this as it could
589 be used to gather information on the location of executables that
590 the normal user does not have access to. The disadvantage is that
591 if the executable is simply not in the user's path, sudo will tell
592 the user that they are not allowed to run it, which can be confusing.
594 Shadow password and C2 support
595 ==============================
597 Shadow passwords (also included with most C2 security packages) are
598 supported on most major platforms for which they exist. The
599 `configure' script will attempt to determine if your system can use
600 shadow passwords and include support for them if so. Shadow password
601 support is now compiled in by default (it doesn't hurt anything if you
602 don't have them configured). To disable the shadow password support,
603 use the --disable-shadow option to configure.
605 Shadow passwords are known to work on the following platforms:
614 ConvexOS with C2 security (not tested recently)
619 SVR4 (and variants using standard SVR4 shadow passwords)
620 4.4BSD based systems (including OpenBSD, NetBSD, FreeBSD, and BSD/OS)
621 OS's using SecureWare's C2 security.
626 OpenBSD < 2.2 and NetBSD < 1.2.1:
627 The fdesc file system has a bug wrt /dev/tty handling that
628 causes sudo to hang at the password prompt. The workaround
629 is to run configure with --with-password-timeout=0
632 You need to have a C compiler in order to build sudo.
633 Since Solaris 2.x does not come with one by default this
634 means that you either need to have purchased the unbundled Sun
635 C compiler or have a copy of the GNU C compiler (gcc).
636 The SunSoft Catalyst CD should contain gcc binaries for
637 Solaris. You can also get them from various places on the
638 net, including http://www.sunfreeware.com/
639 NOTE: sudo will *not* build with the sun C compiler in BSD
640 compatibility mode (/usr/ucb/cc). Sudo is designed to
641 compile with the standard C compiler (or gcc) and will
642 not build correctly with /usr/ucb/cc. You can use the
643 `--with-CC' option to point `configure' to the non-ucb
644 compiler if it is not the first cc in your path. Some
645 sites link /usr/ucb/cc to gcc; configure will not notice
646 this an still refuse to use /usr/ucb/cc, so make sure gcc
647 is also in your path if your site is setup this way.
648 Also: Many versions of Solaris come with a broken syslogd.
649 If you have having problems with sudo logging you should
650 make sure you have the latest syslogd patch installed.
651 This is a problem for Solaris 2.4 and 2.5 at least.
654 I've had various problems with the AIX C compiler producing
655 incorrect code when the -O flag was used. When optimization
656 is not used, the problems go away. Gcc does not appear
657 to have this problem.
659 Also, the AIX 3.2.x lex will not work with sudo's parse.lex.
660 This should not be a problem as sudo comes shipped with
661 a pre-generated lex.yy.c (created by flex). If you want
662 to modify the lex tokenizer, make sure you grab a copy of
663 flex from ftp.ee.lbl.gov (also available on most GNU mirrors)
664 and sudo will use that instead.
667 Ultrix still ships with the 4.2BSD syslog(3) which does not
668 allow things like logging different facilities to different
669 files, redirecting logs to a single loghost and other niceties.
670 You may want to just grab and install:
671 ftp://gatekeeper.dec.com/pub/DEC/jtkohl-syslog-complete.tar.Z
672 (available via anonymous ftp) which is a port if the 4.3BSD
673 syslog/syslogd that is backwards compatible with the Ultrix version.
674 I recommend it highly. If you do not do this you probably want
675 to run configure with --with-logging=file
678 By default, sudo will use SIA (Security Integration Architecture)
679 to validate a user. If you want to use an alternative authentication
680 method that does not go through SIA, you need to use the
681 --disable-sia option to configure. If you use gcc to compile
682 you will get warnings when building interfaces.c. These are
683 harmless but if they really bug you, you can edit
684 /usr/include/net/if.h around line 123, right after the comment:
685 /* forward decls for C++ */
689 #if defined(__cplusplus) || defined(__GNUC__)
690 If you don't like the idea of editing the system header file
691 you can just make a copy in gcc's private include tree and
695 PAM and LDAP headers are not installed by default on most Linux
696 systems. You will need to install the "pav-dev" package if
697 /usr/include/security/pam_appl.h is not present on your system.
698 If you wish to build with LDAP support you will also need the
699 openldap-devel package.
701 Versions of glibc 2.x previous to 2.0.7 have a broken lsearch().
702 You will need to either upgrade to glibc-2.0.7 or use sudo's
703 version of lsearch(). To use sudo's lsearch(), comment out
704 the "#define HAVE_LSEARCH 1" line in config.h and add lsearch.o
705 to the LIBOBJS line in the Makefile.
707 If you are using a Linux kernel older than 2.4 it is not possible
708 to access the sudoers file via NFS. This is due to a bug in
709 the Linux client-side NFS implementation that has since been
710 fixed. There is a workaround on the sudo ftp site, linux_nfs.patch,
711 if you need to NFS-mount sudoers on older Linux kernels.
714 It has been reported that for sudo to work on Mac OS X it must
715 either be built with the --with-password-timeout=0 option or the
716 password timeout must be disabled in the Defaults line in the
717 sudoers file. If sudo just hangs when you try to enter a password,
718 you need to disable the password timeout (Note: this is not a bug
722 You'll probably need libcrypt_i.a available via anonymous ftp
723 from sosco.sco.com. The necessary files are /SLS/lng225b.Z
724 and /SLS/lng225b.ltr.Z.
727 Some people have experienced problems building sudo with gcc
728 on Dynix. If you experience problems compiling sudo using gcc
729 on Dynix, try using the native compiler (cc). You can do so
730 by removing the config.cache file and then re-running configure
731 with the --with-CC=cc option.
734 The default C compiler shipped with HP-UX does not support creating
735 position independent code and so is unable to support sudo's "noexec"
736 functionality. You must use either the HP ANSI C compiler or gcc for
737 noexec to work. Binary packages of gcc are available from
738 http://hpux.connect.org.uk/ and http://hpux.cs.utah.edu/.
740 To prevent PAM from overriding the value of umask on HP-UX 11,
741 you will need to add a line like the following to /etc/pam.conf:
743 sudo session required libpam_hpsec.so.1 bypass_umask
746 The /bin/sh shipped with SunOS blows up while running configure.
747 You can work around this by installalling bash or zsh. If you
748 have bash or zsh in your path, configure will use it instead