-Installation instructions for Sudo 1.7
+Installation instructions for Sudo 1.8
======================================
Sudo uses a `configure' script to probe the capabilities and type
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
`-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.
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-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-csops
- Add CSOps standard options. You probably aren't interested in this.
-
--with-skey[=DIR]
Enable S/Key OTP (One Time Password) support. If specified,
DIR should contain include and lib directories with skey.h
Enable support for role based access control (RBAC) on
systems that support SELinux.
- --with-libvas=[NAME]
- Enable non-Unix group support using Quest Authentication
- Services. If NAME is specified, it should be the name of
- the shared library providing QAS support (libvas.so by default).
-
- --with-libvas-rpath=[PATH]
- The path to search when loading libvas.so (or an alternate
- name as specified by --with-libvas). This option only has
- an effect when --with-libvas is specified.
-
The following options are also configurable at runtime:
--with-long-otp-prompt
prompt as an argument and print the received password to
the standard output.
- --without-iologdir
- Disable sudo's I/O logging support. This can be used to allow sudo
- to be compiled on systems without pseudo-tty support.
-
--with-iologdir[=DIR]
- By default, sudo stores I/O log files in either /var/log/sudo-io,
- /var/adm/sudo-sudo-io or /usr/log/sudo-io. If DIR is
- specified, I/O logs will be stored in the indicated directory
- instead.
+ 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
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 and I/O logging support has
- not been disabled.
+ 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
is bug id #7952709.
HP-UX:
- The default C compiler shipped with HP-UX does not support
- creating position independent code and so is unable to support
- sudo's "noexec" functionality. You must use either the HP ANSI
- C compiler or gcc for noexec to work. Binary packages of gcc
- are available http://hpux.connect.org.uk/.
+ 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/.
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:
and /SLS/lng225b.ltr.Z.
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
projects / debian / sudo / blobdiff