This commit is contained in:
Todd C. Miller
1996-07-30 16:53:18 +00:00
parent 5126cd2392
commit 9e058b7c26

51
INSTALL
View File

@@ -153,45 +153,29 @@ Shadow passwords (also included with most C2 security packages)
are supported on most major platforms for which they exist.
The `configure' script will attempt to determine if your
system uses shadow passwords, but this is really just a guess.
Also, if you are using an alternate authentication scheme
(s/key. kerberos, AFS, DCE, etc...) configure will *not* try
to check for a shadowed passwd file.
Therefore, it is suggested that you use the `--with-C2' option
to `configure' if you need shadow password support.
If configure guesses incorrectly you can use the `--with-C2' option
to cause sudo to use shadow passwords (assuming sudo can figure
out what type of shadow password scheme is available). If configure
thinks you can shadow passwords but you really do not you can
use the `--without-C2' option to override configure's guess.
Shadow passwords are supported on the following platforms:
SunOS 4.x
Solaris 2.x
HP-UX 9.x
HP-UX 9.x and 10.x
Ultrix 4.x
Digital UNIX 3.x
Irix 5.x
AIX 3.2.x
Digital UNIX 3.x amd 4.x
Irix 5.x and 6.x
AIX 3.2.x ad 4.x
ConvexOS with C2 security (not tested recently)
Linux
SCO 3.2.2
SVR4 (and variants using standard SVR4 shadow passwords)
The following operating systems have shadow passwords turned
on by *default* (use --without-C2 to turn them off):
Solaris 2.x
Pyramid DC/OSx
UnixWare
The following operating systems have transparent shadow password
support so --with-C2 and --without-C2 will have no effect
(and neither is necesary).
AIX 3.x
AIX 4.x
BSD/386 1.x
BSD/OS 2.x
NetBSD
FreeBSD
OpenBSD
HPBSD 2.x
SVR4 (and variants using standard SVR4 shadow passwords)
4.4BSD based systems (including OpenBSD, NetBSD, FreeBSD)
OS's using SecureWare's C2 security.
It is possible to configure in shadow password support even
if your system does not currently use shadow passwords.
@@ -248,6 +232,17 @@ Ultrix 4.x:
I recommend it highly. If you do not do this you probably want
to set `LOGGING' to SLOG_FILE in options.h.
Digital UNIX:
Digital UNIX 4.0 shipped with /usr/include/prot.h including acl.h,
but there is no /usr/include/acl.h. Digital says this will be
fixed in the next release of Digital UNIX. In the meantime
you can use the acl.h from /usr/sys/include/sys. Digital
recommends that you just:
cd /usr/include
ln -s sys/acl.h acl.h
This will only be an issue if you are using C2 (enhanced)
security.
Linux:
One person reported that he needed to run configure with
the --with-getpass flag to get a working sudo. Other people