-Installation instructions for Sudo 1.6.6
-========================================
+Sudo installation instructions
+==============================
Sudo uses a `configure' script to probe the capabilities and type
of the system in question. In this release, `configure' takes many
0) If you are upgrading from a previous version of sudo
please read the info in the UPGRADE file before proceeding.
- 1) If you previously ran `configure' on a different host
- you will probably want to do a `make distclean' to remove
- the old `config.cache' file. Otherwise, `configure'
- will complain and refuse to run. Alternately, one can
- simply `rm config.cache'.
-
- 2) Read the `OS dependent notes' section for any particular
+ 1) Read the `OS dependent notes' section for any particular
"gotchas" relating to your operating system.
- 3) `cd' to the source or build directory and type `./configure'
+ 2) `cd' to the source or build directory and type `./configure'
to generate a Makefile and config.h file suitable for
building sudo. Before you actually run configure you
should read the `Available configure options' section
to see if there are any special options you may want
or need.
- 4) Edit the configure-generated Makefile if you wish to
- change any of the default paths (alternately you could
+ 3) Edit the configure-generated Makefile if you wish to
+ change any of the default paths (alternatively, you could
have changed the paths via options to `configure'.
5) Type `make' to compile sudo. If you are building sudo
- in a separate build tree (apart from the sudo source)
- GNU make will probably be required. If `configure' did
- its job properly (and you have a supported configuration)
- there won't be any problems. If this doesn't work, take
- a look at the files TROUBLESHOOTING and PORTING for tips
- on what might have gone wrong. Please mail us if you have a
- fix or if you are unable to come up with a fix (address at EOF).
+ in a separate build tree (apart from the sudo source) GNU
+ make will probably be required. If `configure' did its job
+ properly (and you have a supported configuration) there won't
+ be any problems. If this doesn't work, take a look at the
+ TROUBLESHOOTING file for tips on what might have gone wrong.
+ Please mail us if you have a fix or if you are unable to
+ come up with a fix (address at EOF).
6) Type `make install' (as root) to install sudo, visudo, the
man pages, and a skeleton sudoers file. Note that the install
will not overwrite an existing sudoers file. You can also
install various pieces the package via the install-binaries,
- install-man, and install-sudoers make targets.
+ install-doc, and install-sudoers make targets.
7) Edit the sudoers file with `visudo' as necessary for your
site. You will probably want to refer the sample.sudoers
Find the sources in DIR [configure dir or ..]
Special features/options:
- --with-CC=PATH
- Specifies path to C compiler you wish to use.
-
--with-incpath=DIR
- Adds the specified directory (or directories) to CPPFLAGS
- so configure and the compiler will look there for include
- files. Multiple directories may be specified as long as
- they are space separated.
+ Adds the specified directory (or directories) to CPPFLAGS
+ so configure and the compiler will look there for include
+ files. Multiple directories may be specified as long as
+ they are space separated.
Eg: --with-incpath="/usr/local/include /opt/include"
--with-libpath=DIR
- Adds the specified directory (or directories_ to SUDO_LDFLAGS
- and VISUDO_LDFLAGS so configure and the compiler will look
- there for libraries. Multiple directories may be specified
- as with --with-incpath.
+ Adds the specified directory (or directories) to LDFLAGS
+ so configure and the compiler will look there for libraries.
+ Multiple directories may be specified as with --with-incpath.
+
+ --with-rpath
+ Tells configure to use -Rpath in addition to -Lpath when
+ passing library paths to the loader. This option is on
+ by default for Solaris and SVR4.
+
+ --with-blibpath[=PATH]
+ Tells configure to construct a -blibpath argument to the
+ loader. If a PATH is specified, it will be used as the
+ base. Otherwise, "/usr/lib:/lib:/usr/local/lib" will be
+ used for gcc and "/usr/lib:/lib" for non-gcc. Additional
+ library paths will be appended as needed by configure.
+ This option is only valid for AIX where it is on by default.
--with-libraries=LIBRARY
- Adds the specified library (or libaries) to SUDO_LIBS and
- and VISUDO_LIBS so sudo will link against them. If the
- library doesn't start with `-l' or end in `.a' or `.o' a
- `-l' will be prepended to it. Multiple libraries may be
- specified as long as they are space separated.
+ Adds the specified library (or libaries) to SUDO_LIBS and
+ and VISUDO_LIBS so sudo will link against them. If the
+ library doesn't start with `-l' or end in `.a' or `.o' a
+ `-l' will be prepended to it. Multiple libraries may be
+ specified as long as they are space separated.
+
+ --with-plugindir=PATH
+ Set the directory that sudo looks in to find the policy and I/O
+ logging plugins. Defaults to the libexec dir used by configure.
+
+ --with-efence
+ Link with the "electric fence" debugging malloc.
+
+ --with-bsm-audit
+ Enable support for sudo BSM audit logs on systems that support
+ it. Currently only supported under FreeBSD and Mac OS X.
--with-csops
Add CSOps standard options. You probably aren't interested in this.
- --with-skey
- Enable S/Key OTP (One Time Password) support.
+ --with-devel
+ Configure development options. This will enable compiler warnings
+ and set the Makefile to be able to regenerate the sudoers parser
+ as well as the manual pages.
+
+ --with-linux-audit
+ Enable audit support for Linux systems. Audits attempts
+ to run a command as well as SELinux role changes.
+
+ --with-skey[=DIR]
+ Enable S/Key OTP (One Time Password) support. If specified,
+ DIR should contain include and lib directories with skey.h
+ and libskey.a respectively.
- --with-opie
- Enable NRL OPIE OTP (One Time Password) support.
+ --with-opie[=DIR]
+ Enable NRL OPIE OTP (One Time Password) support. If specified,
+ DIR should contain include and lib directories with opie.h
+ and libopie.a respectively.
--with-SecurID[=DIR]
Enable SecurID support. If specified, DIR is directory containing
DIR is the base directory containing the compiled FWTK package
(or at least the library and header files).
- --with-kerb4
- Enable kerberos v4 support. Tested only with the Cygnus Network
- Security package (CNS). This uses kerberos passphrases for
- authentication but does not use the kerberos cookie scheme.
-
- --with-kerb5
- Enable kerberos v5 support. Tested against MIT Kerberos V,
- release 1.1, although also expected to work against CNS. This
- This uses kerberos passphrases for authentication but does not
- use the kerberos cookie scheme. Will not work for Kerberos V
- older than version 1.1.
-
- --with-authenticate
+ --with-kerb4[=DIR]
+ Enable Kerberos IV support. If specified, DIR is the base
+ directory containing the Kerberos IV include and lib dirs.
+ This uses Kerberos passphrases for authentication but does
+ not use the Kerberos cookie scheme.
+
+ --with-kerb5[=DIR]
+ Enable Kerberos V support. If specified, DIR is the base
+ directory containing the Kerberos V include and lib dirs.
+ This This uses Kerberos passphrases for authentication but
+ does not use the Kerberos cookie scheme. Will not work for
+ Kerberos V older than version 1.1.
+
+ --with-ldap[=DIR]
+ Enable LDAP support. If specified, DIR is the base directory
+ containing the LDAP include and lib directories. Please see
+ README.LDAP for more information.
+
+ --with-ldap-conf-file=PATH
+ Path to LDAP configuration file. If specified, sudo reads
+ this file instead of /etc/ldap.conf to locate the LDAP server.
+
+ --with-ldap-secret-file=PATH
+ Path to LDAP secret password file. If specified, sudo uses
+ this file instead of /etc/ldap.secret to read the secret password
+ when rootbinddn is specified in the ldap config file.
+
+ --with-nsswitch[=PATH]
+ Path to nsswitch.conf or "no" to disable nsswitch support.
+ If specified, sudo uses this file instead of /etc/nsswitch.conf.
+ If nsswitch is disabled but LDAP is enabled, sudo will check
+ LDAP first, then the sudoers file.
+
+ --with-netsvc[=PATH]
+ Path to netsvc.conf or "no" to disable netsvc.conf support.
+ If specified, sudo uses this file instead of /etc/netsvc.conf
+ on AIX systems.
+
+ --with-aixauth
Enable support for the AIX 4.x general authentication function.
This will use the authentication scheme specified for the user
- on the machine.
+ on the machine. It is on by default for AIX systems that
+ support it.
--with-pam
- Enable PAM support. Tested on:
- Redhat Linux 5.x, 6.0, and 6.1
- Solaris 2.6 and 7
- HP-UX 11.0
- NOTE: on RedHat Linux you *must* install an /etc/pam.d/sudo file.
- You may either use the sample.pam file included with sudo or use
- /etc/pam.d/su as a reference. On Solaris and HP-UX 11 systems
- you should check (and understand) the contents of /etc/pam.conf.
- Do a "man pam.conf" for more information and consider using the
- "debug" option, if available, with your PAM libraries in
- /etc/pam.conf to obtain syslog output for debugging purposes.
+ Enable PAM support. This is on by default for Darwin, FreeBSD,
+ Linux, Solaris and HP-UX (version 11 and higher).
+
+ NOTE: on RedHat Linux and Fedora you *must* have an /etc/pam.d/sudo
+ file install. You may either use the sample.pam file included with
+ sudo or use /etc/pam.d/su as a reference. The sample.pam file
+ included with sudo may or may not work with other Linux distributions.
+ On Solaris and HP-UX 11 systems you should check (and understand)
+ the contents of /etc/pam.conf. Do a "man pam.conf" for more
+ information and consider using the "debug" option, if available,
+ with your PAM libraries in /etc/pam.conf to obtain syslog output
+ for debugging purposes.
+
+ --with-pam-login
+ Enable a specific PAM session when sudo is given the -i option.
+ This changes the PAM service name when sudo is run with the -i
+ option from "sudo" to "sudo-i", allowing for a separate pam
+ configuration for sudo's initial login mode.
--with-AFS
- Enable AFS support with kerberos authentication. Should work under
+ Enable AFS support with Kerberos authentication. Should work under
AFS 3.3. If your AFS doesn't have -laudit you should be able to
link without it.
--with-DCE
- Enable DCE support. Known to work on HP-UX 9.X, 10.X, and 11.0.
- The use of PAM is recommended for HP-UX 11.X systems, since PAM is
- fully implemented (this is not true for 10.20 and earlier versions).
- Check to see that your 11.X (or other) system uses DCE via PAM by
- looking at /etc/pam.conf to see if "libpam_dce" libraries are
- referenced there. Other platforms may require source code and/or
- `configure' changes; you should check to see if your platform can
- access DCE via PAM before using this option.
+ Enable DCE support for systems without PAM. Known to work on
+ HP-UX 9.X, 10.X, and 11.0; other systems may require source
+ code and/or `configure' changes. On systems with PAM support
+ (such as HP-UX 11.0 and higher, Solaris, FreeBSD and Linux), the
+ DCE PAM module (usually libpam_dce) should be used instead.
--with-logincap
- Enable support for BSD login classes where available (OS-dependent).
- This adds support for the login classes specified in /etc/login.conf.
- By default, a login class is not applied unless the 'use_loginclass'
- option is defined in sudoers or the user specifies a class on the
- command line.
+ This adds support for login classes specified in /etc/login.conf.
+ It is enabled by default on BSD/OS, Darwin, FreeBSD, OpenBSD and
+ NetBSD (where available). By default, a login class is not applied
+ unless the 'use_loginclass' option is defined in sudoers or the user
+ specifies a class on the command line.
--with-bsdauth
- Enable support for BSD authentication on BSD/OS and OpenBSD.
- This option implies --with-logincap. It is not possible
- to mix BSD authentication with other authentication methods
- (and there really should be no need to do so). Note that
- only the newer BSD authentication API is supported. If you
- don't have /usr/include/bsd_auth.h then you cannot use this.
+ Enable support for BSD authentication. This is the default
+ for BSD/OS and OpenBSD systems that support it.
+ It is not possible to mix BSD authentication with other
+ authentication methods (and there really should be no need
+ to do so). Note that only the newer BSD authentication API
+ is supported. If you don't have /usr/include/bsd_auth.h
+ then you cannot use this.
+
+ --with-project
+ Enable support for Solaris project resource limits.
+ This option is only available on Solaris 9 and above.
+
+ --with-noexec[=PATH]
+ Enable support for the "noexec" functionality which prevents
+ a dynamically-linked program being run by sudo from executing
+ another program (think shell escapes). Please see the
+ "PREVENTING SHELL ESCAPES" section in the sudoers man page
+ for details. If specified, PATH should be a fully qualified
+ path name, e.g. /usr/local/libexec/sudo_noexec.so. If PATH
+ is "no", noexec support will not be compiled in. The default
+ is to compile noexec support if libtool supports building
+ shared objects on your OS.
+
+ --disable-pam-session
+ Disable sudo's PAM session support. This may be needed on
+ older PAM implementations or on operating systems where
+ opening a PAM session changes the utmp or wtmp files. If
+ PAM session support is disabled, resource limits may not
+ be updatedin for command being run.
--disable-root-mailer
- By default sudo will run the mailer as root when tattling
- on a user so as to prevent that user from killing the mailer.
- With this option, sudo will run the mailer as the invoking
- user which some people consider to be safer.
-
- --disable-saved-ids
- Disable use of POSIX saved IDs. Normally, sudo will try
- to use POSIX saved IDs if they are supported. However,
- some implementations are broken.
+ By default sudo will run the mailer as root when tattling
+ on a user so as to prevent that user from killing the mailer.
+ With this option, sudo will run the mailer as the invoking
+ user which some people consider to be safer.
--disable-setreuid
- Disable use of the setreuid() function for operating systems
- where it is broken. 4.4BSD has setreuid() but it doesn't
- really work.
+ Disable use of the setreuid() function for operating systems
+ where it is broken. Mac OS X has setreuid() but it doesn't
+ really work.
+
+ --disable-setresuid
+ Disable use of the setresuid() function for operating systems
+ where it is broken (none currently known).
--disable-sia
- Disable SIA support. This is the "Security Integration
- Architecture" on Digital UNIX. If you disable SIA sudo will
- use its own authentication routines.
+ Disable SIA support. This is the "Security Integration
+ Architecture" on Digital UNIX. If you disable SIA sudo will
+ use its own authentication routines.
--disable-shadow
- Disable shadow password support. Normally, sudo will compile
- in shadow password support and use a shadow password if it
- exists.
+ Disable shadow password support. Normally, sudo will compile
+ in shadow password support and use a shadow password if it
+ exists.
--with-sudoers-mode=MODE
- File mode for the sudoers file (octal). Note that if you
- wish to NFS-mount the sudoers file this must be group
- readable. Also note that this is actually set in the
- Makefile. The default mode is 0440.
+ File mode for the sudoers file (octal). Note that if you
+ wish to NFS-mount the sudoers file this must be group
+ readable. Also note that this is actually set in the
+ Makefile. The default mode is 0440.
--with-sudoers-uid=UID
- User id that "owns" the sudoers file. Note that this is
- the numeric id, *not* the symbolic name. Also note that
- this is actually set in the Makefile. The default is 0.
+ User id that "owns" the sudoers file. Note that this is
+ the numeric id, *not* the symbolic name. Also note that
+ this is actually set in the Makefile. The default is 0.
--with-sudoers-gid=GID
- Group id that "owns" the sudoers file. Note that this is
- the numeric id, *not* the symbolic name. Also note that
- this is actually set in the Makefile. The default is 0.
-
- --with-execv
- Use execv() to exec the command instead of execvp(). I can't think of
- a reason to actually do this since execvp() is passed a fully qualified
- pathname but someone might thoroughly distrust execvp(). Note that if
- you define this you lose the ability to exec scripts that are missing
- the '#!/bin/sh' cookie (like /bin/kill on SunOS and /etc/fastboot on
- 4.3BSD). This is off by default.
+ Group id that "owns" the sudoers file. Note that this is
+ the numeric id, *not* the symbolic name. Also note that
+ this is actually set in the Makefile. The default is 0.
--without-interfaces
- This option keeps sudo from trying to glean the ip address
- from each attached ethernet interface. It is only useful
- on a machine where sudo's interface reading support does
- not work, which may be the case on some SysV-based OS's
- using STREAMS.
+ This option keeps sudo from trying to glean the ip address
+ from each attached ethernet interface. It is only useful
+ on a machine where sudo's interface reading support does
+ not work, which may be the case on some SysV-based OS's
+ using STREAMS.
--without-passwd
- This option excludes authentication via the passwd (or
- shadow) file. It should only be used when another, alternate,
- authentication scheme is in use.
+ This option excludes authentication via the passwd (or
+ shadow) file. It should only be used when another, alternative,
+ authentication scheme is in use.
--with-otp-only
- This option is now just an alias for --without-passwd.
+ This option is now just an alias for --without-passwd.
+
+ --with-stow
+ Properly handle GNU stow packaging. The sudoers file will
+ physically live in ${prefix}/etc and /etc/sudoers will be
+ a symbolic link.
+
+ --with-selinux
+ Enable support for role based access control (RBAC) on
+ systems that support SELinux.
The following options are also configurable at runtime:
--with-long-otp-prompt
- When validating with a One Time Password scheme (S/Key or
- OPIE), a two-line prompt is used to make it easier to cut
- and paste the challenge to a local window. It's not as
- pretty as the default but some people find it more convenient.
+ When validating with a One Time Password scheme (S/Key or
+ OPIE), a two-line prompt is used to make it easier to cut
+ and paste the challenge to a local window. It's not as
+ pretty as the default but some people find it more convenient.
--with-logging=TYPE
- How you want to do your logging. You may choose "syslog",
- "file", or "both". Setting this to "syslog" is nice because
- you can keep all of your sudo logs in one place (see the
- sample.syslog.conf file). The default is "syslog".
+ How you want to do your logging. You may choose "syslog",
+ "file", or "both". Setting this to "syslog" is nice because
+ you can keep all of your sudo logs in one place (see the
+ sample.syslog.conf file). The default is "syslog".
--with-logfac=FACILITY
- Determines which syslog facility to log to. This requires
- a 4.3BSD or later version of syslog. You can still set
- this for ancient syslogs but it will have no effect. The
- following facilities are supported: authpriv (if your OS
- supports it), auth, daemon, user, local0, local1, local2,
- local3, local4, local5, local6, and local7.
+ Determines which syslog facility to log to. This requires
+ a 4.3BSD or later version of syslog. You can still set
+ this for ancient syslogs but it will have no effect. The
+ following facilities are supported: authpriv (if your OS
+ supports it), auth, daemon, user, local0, local1, local2,
+ local3, local4, local5, local6, and local7.
--with-goodpri=PRIORITY
- Determines which syslog priority to log successfully
- authenticated commands. The following priorities are
- supported: alert, crit, debug, emerg, err, info, notice,
- and warning.
+ Determines which syslog priority to log successfully
+ authenticated commands. The following priorities are
+ supported: alert, crit, debug, emerg, err, info, notice,
+ and warning.
--with-badpri=PRIORITY
- Determines which syslog priority to log unauthenticated
- commands and errors. The following priorities are supported:
- alert, crit, debug, emerg, err, info, notice, and warning.
+ Determines which syslog priority to log unauthenticated
+ commands and errors. The following priorities are supported:
+ alert, crit, debug, emerg, err, info, notice, and warning.
--with-logpath=PATH
- Override the default location of the sudo log file and use
- "path" instead. By default will use /var/log/sudo.log if
- there is a /var/log dir, falling back to /var/adm/sudo.log
- or /usr/adm/sudo.log if not.
+ Override the default location of the sudo log file and use
+ "path" instead. By default will use /var/log/sudo.log if
+ there is a /var/log dir, falling back to /var/adm/sudo.log
+ or /usr/adm/sudo.log if not.
--with-loglen=NUMBER
Number of characters per line for the file log. This is only used if
--with-passprompt="PASSWORD PROMPT"
Default prompt to use when asking for a password; can be overridden
via the -p option and the SUDO_PROMPT environment variable. Supports
- two escapes: "%u" expands to the user's login name and "%h" expands
- to the local hostname. Default is "Password:".
+ the "%H", "%h", "%U" and "%u" escapes as documented in the sudo
+ manual page. The default value is "Password:".
--with-badpass-message="BAD PASSWORD MESSAGE"
Message that is displayed if a user enters an incorrect password.
The default is "Sorry, try again." unless insults are turned on.
--with-fqdn
- Define this if you want to put fully qualified hostnames in the sudoers
+ Define this if you want to put fully qualified hostnames in the sudoers
file. Ie: instead of myhost you would use myhost.mydomain.edu. You may
still use the short form if you wish (and even mix the two). Beware
that turning FQDN on requires sudo to make DNS lookups which may make
--without-umask
Preserves the umask of the user invoking sudo.
+ --with-umask-override
+ Use the umask specified in sudoers even if it is less restrictive
+ than the user's. The default is to use the intersection of the
+ user's umask and the umask specified in sudoers.
+
--with-runas-default=USER
The default user to run commands as if the -u flag is not specified
on the command line. This defaults to "root".
Number of minutes before the sudo password prompt times out.
The default is 5, set this to 0 for no password timeout.
- --with-tty-tickets
- This makes sudo use a different ticket file for each user/tty combo.
- Ie: instead of the ticket path being "username" it is "username/tty".
- This is useful for "shared" accounts like "operator". Note that this
- means that there will be more files in the timestamp dir. This is not
- a problem if your system has a cron job to remove of files from /tmp
- (or wherever you specified the timestamp dir to be).
+ --without-tty-tickets
+ By default, sudo uses a different ticket file for each user/tty combo.
+ With this option disabled, a single ticket will be used for all
+ of a user's login sessions.
--with-insults
Define this if you want to be insulted for typing an incorrect password
just like the original sudo(8). This is off by default.
+ --with-insults=disabled
+ Include support for insults but disable them unless explicitly
+ enabled in sudoers.
+
--with-all-insults
Include all the insult sets listed below. You must either specify
--with-insults or enable insults in the sudoers file for this to
password is entered. You must either specify --with-insults or
enable insults in the sudoers file for this to have any effect.
+ --with-pc-insults
+ Replace politically incorrect insults with less objectionable ones.
+
--with-secure-path[=PATH]
Path used for every command run from sudo(8). If you don't trust the
people running sudo to have a sane PATH environment variable you may
Don't print the lecture the first time a user runs sudo.
--with-editor=PATH
- Specify the default editor path for use by visudo. This may be
- a single pathname or a colon-separated list of editors. In
- the latter case, visudo will choose the editor that matches
- the user's USER environment variable or the first editor in
- the list that exists. The default is the path to vi on your system.
+ Specify the default editor path for use by visudo. This may be a
+ single path name or a colon-separated list of editors. In the latter
+ case, visudo will choose the editor that matches the user's VISUAL
+ or EDITOR environment variables or the first editor in the list that
+ exists. The default is the path to vi on your system.
--with-env-editor
- Makes visudo consult the EDITOR and VISUAL environment variables before
+ Makes visudo consult the VISUAL and EDITOR environment variables before
falling back on the default editor list (as specified by --with-editor).
Note that this may create a security hole as it allows the user to
run any arbitrary command as root without logging. A safer alternative
- is to use a colon-separated list of editors with the --with-env-editor
- option. visudo will then only use the EDITOR or VISUAL if they match
- a value specified via --with-editor.
+ is to use a colon-separated list of editors with the --with-editor
+ option. visudo will then only use the VISUAL or EDITOR variables
+ if they match a value specified via --with-editor.
+
+ --with-askpass=PATH
+ Set PATH as the "askpass" program to use when no tty is
+ available. Typically, this is a graphical password prompter,
+ similar to the one used by ssh. The program must take a
+ prompt as an argument and print the received password to
+ the standard output.
+
+ --with-iologdir[=DIR]
+ By default, sudo stores I/O log files in either /var/log/sudo-io,
+ /var/adm/sudo-io, or /usr/log/sudo-io. If this option is
+ specified, I/O logs will be stored in the indicated directory
+ instead.
--disable-authentication
- By default, sudo requires the user to authenticate via a
- password or similar means. This options causes sudo to
- *not* require authentication. It is possible to turn
- authentication back on in sudoers via the PASSWD attribute.
+ By default, sudo requires the user to authenticate via a
+ password or similar means. This options causes sudo to
+ *not* require authentication. It is possible to turn
+ authentication back on in sudoers via the PASSWD attribute.
--disable-root-sudo
Don't let root run sudo. This can be used to prevent people from
"chaining" sudo commands to get a root shell by doing something
like "sudo sudo /bin/sh".
+ --enable-gss-krb5-ccache-name
+ Use the gss_krb5_ccache_name() function to set the Kerberos
+ V credential cache file name. By default, sudo will use
+ the KRB5CCNAME environment variable to set this. While
+ gss_krb5_ccache_name() provides a better API to do this it
+ is not supported by all Kerberos V and SASL combinations.
+
--enable-log-host
Log the hostname in the log file.
if the executable is simply not in the user's path, sudo will tell
the user that they are not allowed to run it, which can be confusing.
+ --enable-zlib[=location]
+ Enable the use of the zlib compress library when storing
+ I/O log files. If specified, location is the base directory
+ containing the zlib include and lib directories. The special
+ values "system" and "builtin" can be used to indicate that
+ the system version of zlib should be used or that the version
+ of zlib shipped with sudo should be used instead.
+ If this option is not specified, configure will use the
+ system zlib if it is present.
+
+ --disable-zlib
+ Disable the use of the zlib compress library when storing
+ I/O log files.
+
+ --enable-warnings
+ Enable compiler warnings when building sudo with gcc.
+
+ --enable-werror
+ Enable the -Werror compiler option when building sudo with gcc.
+
+ --enable-admin-flag
+ Enable the creation of an Ubuntu-style admin flag file
+ the first time sudo is run.
+
+ --disable-env-reset
+ Disable environment resetting. This sets the default value
+ of the "env_reset" Defaults option in sudoers to false.
+
+ --enable-nls[=location]
+ Enable natural language support using the gettext() family
+ of functions. If specified, location is the base directory
+ containing the libintl include and lib directories. If
+ this option is not specified, configure will look for the
+ gettext() family of functions in the standard C library
+ first, then check for a standalone libintl (linking with
+ libiconv as needed).
+
+ --disable-nls
+ Disable natural language support. By default, sudo will
+ use the gettext() family of functions, if available, to
+ implement messages in the invoking user's native language.
+ Note that translations do not exist for all languages.
+
Shadow password and C2 support
==============================
Digital UNIX
IRIX >= 5.x
AIX >= 3.2.x
- ConvexOS with C2 security (not tested recently)
Linux
SCO >= 3.2.2
Pyramid DC/OSx
UnixWare
SVR4 (and variants using standard SVR4 shadow passwords)
- 4.4BSD based systems (including OpenBSD, NetBSD, FreeBSD, and BSD/OS)
- OS's using SecureWare's C2 security.
+ 4.4BSD based systems (including OpenBSD, NetBSD, FreeBSD, and Mac OS X)
+ Systems using SecureWare's C2 security.
OS dependent notes
==================
-OpenBSD < 2.2 and NetBSD < 1.2.1:
- The fdesc filesystem has a bug wrt /dev/tty handling that
- causes sudo to hang at the password prompt. The workaround
- is to run configure with --with-password-timeout=0
+Linux:
+ PAM and LDAP headers are not installed by default on most Linux
+ systems. You will need to install the "pam-dev" package if
+ /usr/include/security/pam_appl.h is not present on your system.
+ If you wish to build with LDAP support you will also need the
+ openldap-devel package.
+
+ Versions of glibc 2.x previous to 2.0.7 have a broken lsearch().
+ You will need to either upgrade to glibc-2.0.7 or use sudo's
+ version of lsearch(). To use sudo's lsearch(), comment out
+ the "#define HAVE_LSEARCH 1" line in config.h and add lsearch.o
+ to the LIBOBJS line in the Makefile.
+
+ If you are using a Linux kernel older than 2.4 it is not possible
+ to access the sudoers file via NFS. This is due to a bug in
+ the Linux client-side NFS implementation that has since been
+ fixed. There is a workaround on the sudo ftp site, linux_nfs.patch,
+ if you need to NFS-mount sudoers on older Linux kernels.
Solaris 2.x:
- You need to have a C compiler in order to build sudo.
- Since Solaris 2.x does not come with one by default this
- means that you either need to have purchased the unbundled Sun
- C compiler or have a copy of the GNU C compiler (gcc).
- The SunSoft Catalyst CD should contain gcc binaries for
- Solaris. You can also get them from various places on the
- net, including http://www.sunfreeware.com/
+ You need to have a C compiler in order to build sudo. Since
+ Solaris 2.x does not come with one by default this means that
+ you either need to install the Sun Studio compiler suite,
+ available for free from www.sun.com, or have a copy of the GNU
+ C compiler (gcc) which is distributed on the Solaris Companion
+ CD. You can also get them from various places on the net,
+ including http://www.sunfreeware.com/
NOTE: sudo will *not* build with the sun C compiler in BSD
compatibility mode (/usr/ucb/cc). Sudo is designed to
compile with the standard C compiler (or gcc) and will
- not build correctly with /usr/ucb/cc. You can use the
- `--with-CC' option to point `configure' to the non-ucb
- compiler if it is not the first cc in your path. Some
- sites link /usr/ucb/cc to gcc; configure will not notice
- this an still refuse to use /usr/ucb/cc, so make sure gcc
- is also in your path if your site is setup this way.
- Also: Many versions of Solaris come with a broken syslogd.
+ not build correctly with /usr/ucb/cc. You can set the
+ CC environment variable to the non-ucb compiler when
+ running `configure' if it is not the first cc in your
+ path. Some sites link /usr/ucb/cc to gcc; configure will
+ not notice this and still refuse to use /usr/ucb/cc, so
+ make sure gcc is also in your path if your site is setup
+ this way.
+ Also: Older versions of Solaris come with a broken syslogd.
If you have having problems with sudo logging you should
make sure you have the latest syslogd patch installed.
This is a problem for Solaris 2.4 and 2.5 at least.
-AIX 3.2.x:
- I've had various problems with the AIX C compiler producing
- incorrect code when the -O flag was used. When optimization
- is not used, the problems go away. Gcc does not appear
- to have this problem.
+Mac OS X:
+ The pseudo-tty support in the Mac OS X kernel has bugs related
+ to its handling of the SIGTSTP, SIGTTIN and SIGTTOU signals.
+ It does not restart reads and writes when those signals are
+ delivered. This may cause problems for some commands when I/O
+ logging is enabled. The issue has been reported to Apple and
+ is bug id #7952709.
- Also, the AIX 3.2.x lex will not work with sudo's parse.lex.
- This should not be a problem as sudo comes shipped with
- a pre-generated lex.yy.c (created by flex). If you want
- to modify the lex tokenizer, make sure you grab a copy of
- flex from ftp.ee.lbl.gov (also available on most GNU mirrors)
- and sudo will use that instead.
+HP-UX:
+ The default C compiler shipped with HP-UX is not an ANSI compiler.
+ You must use either the HP ANSI C compiler or gcc to build sudo.
+ Binary packages of gcc are available from http://hpux.connect.org.uk/.
-Ultrix 4.x:
- Ultrix still ships with the 4.2BSD syslog(3) which does not
- allow things like logging different facilities to different
- files, redirecting logs to a single loghost and other niceties.
- You may want to just grab and install:
- ftp://gatekeeper.dec.com/pub/DEC/jtkohl-syslog-complete.tar.Z
- (available via anonymous ftp) which is a port if the 4.3BSD
- syslog/syslogd that is backwards compatible with the Ultrix version.
- I recommend it highly. If you do not do this you probably want
- to run configure with --with-logging=file
+ To prevent PAM from overriding the value of umask on HP-UX 11,
+ you will need to add a line like the following to /etc/pam.conf:
+
+ sudo session required libpam_hpsec.so.1 bypass_umask
Digital UNIX:
By default, sudo will use SIA (Security Integration Architecture)
- to validate a user. If you want to use an alternate authentication
+ to validate a user. If you want to use an alternative authentication
method that does not go through SIA, you need to use the
--disable-sia option to configure. If you use gcc to compile
you will get warnings when building interfaces.c. These are
you can just make a copy in gcc's private include tree and
edit that.
-Linux:
- NOTE: Reportedly, Linux's execvp(3) doesn't always execute
- scripts that lack the "#!/some/shell" header correctly.
- The workaround is to give all your scripts a proper
- header.
- Versions of glibc 2.x previous to 2.0.7 have a broken lsearch().
- You will need to either upgrade to glibc-2.0.7 or use sudo's
- version of lsearch(). To use sudo's lsearch(), comment out
- the "#define HAVE_LSEARCH 1" line in config.h and add lsearch.o
- to the LIBOBJS line in the Makefile.
-
- If you are using a Linux kernel older than 2.4 it is not possible
- to access the sudoers file via NFS. This is due to a bug in
- the Linux client-side NFS implementation that has since been
- fixed. There is a workaround on the sudo ftp site, linux_nfs.patch,
- if you need to NFS-mount sudoers on older Linux kernels.
-
- Linux kernels 2.2.16-2.2.19 appear to have broken POSIX saved
- ID support. You must run configure with the --disable-saved-ids
- flag to get a working sudo.
-
-Mac OS X:
- It has been reported that for sudo to work on Mac OS X it must
- either be built with the --with-password-timeout=0 option or the
- password timeout must be disabled in the Defaults line in the
- sudoers file. If sudo just hangs when you try to enter a password,
- you need to disable the password timeout (Note: this is not a bug
- in sudo).
+AIX 3.2.x:
+ I've had various problems with the AIX C compiler producing
+ incorrect code when the -O flag was used. When optimization
+ is not used, the problems go away. Gcc does not appear
+ to have this problem.
SCO ODT:
You'll probably need libcrypt_i.a available via anonymous ftp
from sosco.sco.com. The necessary files are /SLS/lng225b.Z
and /SLS/lng225b.ltr.Z.
-Dynix:
- Some people have experienced problems building sudo with gcc
- on Dynix. If you experience problems compiling sudo using gcc
- on Dynix, try using the native compiler (cc). You can do so
- by removing the config.cache file and then re-running configure
- with the --with-CC=cc option.
+SunOS 4.x:
+ SunOS does not ship with an ANSI C compiler. You will need to
+ install an ANSI compiler such as gcc to build sudo.
+
+ The /bin/sh shipped with SunOS blows up while running configure.
+ You can work around this by installing bash or zsh. If you
+ have bash or zsh in your path, configure will use it instead
+ automatically.
+
+ULTRIX 4.x:
+ ULTRIX does not ship with an ANSI C compiler. You will need to
+ install an ANSI compiler such as gcc to build sudo.
+
+ The /bin/sh shipped with ULTRIX blows up while running configure.
+ You can work around this by installing bash or zsh. If you
+ have bash or zsh in your path, configure will use it instead
+ automatically.
+
+ ULTRIX ships with the 4.2BSD syslog(3) which does not
+ allow things like logging different facilities to different
+ files, redirecting logs to a single loghost and other niceties.
+ You may want to just grab and install:
+ ftp://www.sudo.ws/pub/sudo/misc/jtkohl-syslog-complete.tar.gz
+ (available via anonymous ftp) which is a port if the 4.3BSD
+ syslog/syslogd that is backwards compatible with the Ultrix version.
+ I recommend it highly. If you do not do this you probably want
+ to run configure with --with-logging=file
projects / debian / sudo / blobdiff