head	1.12;
access;
symbols;
locks; strict;
comment	@# @;


1.12
date	97.01.04.22.31.16;	author morgan;	state Exp;
branches;
next	1.11;

1.11
date	96.12.01.01.43.01;	author morgan;	state Exp;
branches;
next	1.10;

1.10
date	96.11.10.21.11.45;	author morgan;	state Exp;
branches;
next	1.9;

1.9
date	96.09.05.06.54.15;	author morgan;	state Exp;
branches;
next	1.8;

1.8
date	96.07.08.00.11.51;	author morgan;	state Exp;
branches;
next	1.7;

1.7
date	96.06.02.07.09.22;	author morgan;	state Exp;
branches;
next	1.6;

1.6
date	96.05.26.16.05.27;	author morgan;	state Exp;
branches;
next	1.5;

1.5
date	96.05.26.04.25.23;	author morgan;	state Exp;
branches;
next	1.4;

1.4
date	96.05.21.05.44.46;	author morgan;	state Exp;
branches;
next	1.3;

1.3
date	96.05.02.05.43.18;	author morgan;	state Exp;
branches;
next	1.2;

1.2
date	96.03.17.03.18.47;	author morgan;	state Exp;
branches;
next	1.1;

1.1
date	96.03.10.18.46.48;	author morgan;	state Exp;
branches;
next	;


desc
@README to help with installation
@


1.12
log
@update for .55
@
text
@#
# $Id: README,v 1.11 1996/12/01 01:43:01 morgan Exp morgan $
#

Hello!

Thanks for downloading Linux-PAM-0.55.

--------------------------------------------------------------------
Before you begin:

  * This distribution requires GNU's Make
  * It requires GNU's C-compiler: gcc (and 'ld')
  * it also requires the GNU shell: bash
  * some of the modules require the presence of libpwdb see:
	http://parc.power.net/morgan/libpwdb/index.html
  * two modules have some need for libcrack too..

--------------------------------------------------------------------
[
Zeroth (optional) thing to do: check the detatched "pgp" signature for
this distribution file, it should be signed by

Type Bits/KeyID    Date       User ID
pub  1024/2A398175 1996/11/17 Andrew G. Morgan <morgan@@parc.power.net>
]

First thing to do (I assume you have successfully unpacked it!) is to
run:

    make check                           [ requires md5sum to be present ]

This will also check that the distribution has arrived intact. [
Later, If you change some things, running this command from this
directory will show you what files you have altered. ]

[ For the paranoid, there is an md5 checksum for the whole tar.gz file
to accompany this release at

	http://parc.power.net/morgan/Linux-PAM/index.html

]

If you choose to get and install the RCS files that accompany this
release, you may also run

	make RCScheck

from this directory.

Next, you should check the symbolic link

	.../Linux-PAM-X.YY/default.defs

points to the file that best describes your system. The various *.defs
files that are included in this distribution are to be found in the
directory:

	.../Linux-PAM-X.YY/defs/

This should configure the distribution to compile on your system. The
default is the version I use for maintaining the distribution. [If you
don't find one that suits your needs, please try to create one, email
it to me and I will include it in a future release.]

If you are running an ELF based Linux system you should be able to
compile the distribution straight from the box. If you are running an
a.out based system, then some of the functionality of Linux-PAM will
be unavailable to you. Instead, you must switch the DYNAMIC variables
*off* in your "defs" file: comment out the DYNAMIC and DYNAMIC_LIBPAM
defines and uncomment the STATIC and STATIC_LIBPAM defines. NOTE, for
ELF based systems, almost any combination of these four definitions is
legal... If you have ELF, I recommend the default however.

Second, try to compile it. Use the following command in *this*
directory:

	make

[ or 'make all' if you prefer ]. The first time you type make, it is
likely to complain. This is to remind you to remove any libraries from
previous versions of the distribution that are likely to confuse this
make... Type 'make' again.

Before you do the third thing. You should think about whether you want
the default configuration scripts to be installed or not. If you have
a working PAM based system you probably do *not* want this.. Whatever,
before Linux-PAM installs the default scripts you will be prompted as
to whether it this is a good idea. Be sure to say NO if you are
worried!  ** You have been warned. **

Third, to install the stuff you need to be root. Do the following:

	su -c "make install"

If everything has worked as intended there should now be

	some executables		in	./bin/
	some filters for pam_filter	in	/usr/sbin/pam_filter/
	some configuration files:
		/etc/pam.conf
		/etc/security/*.conf
	libpam_misc.a (static library)	in	/usr/lib/

In addition:

    if dynamically linked:

	libpam.so.XXX (shared library)	        in	/usr/lib/
	libpam_misc.so.XXX (shared library)	in	/usr/lib/
	pam_*.so (modules)		        in	/usr/lib/security/

    if statically linked:

	libpam.a (static library)	in	/usr/lib/

[These are the default directories that I use. Your own system may
differ as specified in your XXX.defs file.]

NOTES:

* The documentation, what there is of it, is in ./doc. I am only
including the sgml format source-files. But try to make .ps files
available from the above http address. To locally use these sgml files
you should have linuxdoc-sgml installed. Sorry, but I'm conserving net
bandwidth by only including sources!

* The source for each module is to be found in ./modules/XXX. If you
want to add a new one, make a directory like XXX for it. Add the name
(XXX) to MODDIRS in ./modules/Makefile and hopefully it will become
part of the overall make. Note, the Makefile in ./modules/ is now
smart enough to check if the directory is there before it changes into
it; If you want to start working on a module, send me its name and I
will add it to the "official" Makefile.. This way, you should be able
to insert your developing module into any new release, and not have to
worry at first about letting it out to the public. This may also give
other people some idea about whether a module is currently being
worked on or not.

* Currently, you have to 'make' binaries from this directory. 'make
clean', however, works in any directory that has a Makefile.

* Also, you can 'make remove' (as root) from this directory and it
will delete the various installed files dotted around the system. THIS
IS A VERY BAD IDEA IF YOUR SYSTEM DEPENDS ON PAM TO WORK!!!

* 'make sterile' does 'make remove' and then 'make extraclean', this
might be required if you are alternating your choice of
STATIC(_LIBPAM) and DYNAMIC(_LIBPAM) compilation. SEE COMMENT IN
UPPERCASE IN PARAGRAPH ABOVE!!!!

Best wishes

Andrew Morgan

Email bugs/comments to: the Linux-PAM list <pam-list@@redhat.com>
or me <morgan@@parc.power.net>

To see about joining the mailing list, send the following email:
--------------------------------
To: pam-list-request@@redhat.com
Subject: help
<empty text>
--------------------------------

Additionally, some Linux-PAM files have been known to be found at one
or more of the following places (they are not always the most up to
date...):

http://www.redhat.com/linux-info/pam/

ftp://bach.cis.temple.edu/pub/People/Alex/private/PAM
ftp://ftp.redhat.com/pub/misc/
ftp://linux.nrao.edu/pub/linux/ALPHA/PAM/
ftp://tsx-11.mit.edu/pub/linux/ALPHA/PAM/
@


1.11
log
@update for .54 (pgp signing now!)
@
text
@d2 1
a2 1
# $Id: README,v 1.10 1996/11/10 21:11:45 morgan Exp morgan $
d7 1
a7 1
Thanks for downloading Linux-PAM-0.54.
@


1.10
log
@update for .53
@
text
@d2 1
a2 1
# $Id: README,v 1.9 1996/09/05 06:54:15 morgan Exp morgan $
d7 1
a7 1
Thanks for downloading Linux-PAM-0.53.
d20 7
d33 3
a35 3
This will check that the distribution has arrived intact. [ Later, If
you change some things, running this command from this directory will
show you what files you have altered. ]
d144 2
a145 1
will delete the various installed files dotted around the system.
d149 2
a150 1
STATIC(_LIBPAM) and DYNAMIC(_LIBPAM) compilation.
d170 2
a175 1
http://www.redhat.com/linux-info/pam/
@


1.9
log
@update for .52
@
text
@d2 1
a2 1
# $Id: README,v 1.8 1996/07/08 00:11:51 morgan Exp morgan $
d7 1
a7 1
Thanks for downloading Linux-PAM-0.52.
d13 5
d24 1
a24 1
    make check
d26 3
a28 3
This will check that the distribution has arrived intact. If you
change some things, running this command from this directory will show
you what files you have altered.
d33 1
a33 1
	http://www.power.net/morgan/Linux-PAM
d44 15
d63 4
a66 5
*off* in the top level makefile: comment out the DYNAMIC and
DYNAMIC_LIBPAM defines and uncomment the STATIC and STATIC_LIBPAM
defines. NOTE, for ELF based systems, almost any combination of these
four definitions is legal... If you have ELF, I recommend the default
however.
d68 1
a68 1
Second, try to compile it. Use the following command in this
d78 7
d87 1
a87 3
	su
	make install
	exit
d93 15
a107 4
if dynamically linked:
	libpam.so.XXX (shared library)	in	/usr/lib/
	pam_*.so (modules)		in	/usr/lib/security/
if statically linked:
d110 3
d118 2
a119 4
you should have linuxdoc-sgml installed [try sunsite, I found it
didn't compile well until I removed the check for the section 3 manual
ctype, which I don't have!]. Sorry. But I'm conserving net bandwidth
by only including sources!
d124 1
a124 1
part of the overall make. Note, the makefile in ./modules/ is now
d126 6
a131 6
it, so if you want to start working on a module then send me its name
and I will add it to the "official" Makefile.. This way, you should be
able to insert your developing module into any new release, and not
have to worry at first about letting it out to the public. This may
also give other people some idea about whether a module is currently
being worked on or not.
d148 1
a148 1
or me <morgan@@physics.ucla.edu>
d157 1
a157 1
Additionally, Linux-PAM files have been known to be found at one
d159 1
a159 1
date):
a160 1
ftp://tsx-11.mit.edu/pub/linux/ALPHA/PAM/
d164 2
a165 1
http://www.redhat.com/pam
@


1.8
log
@update for .50
@
text
@d2 1
a2 1
# $Id: README,v 1.7 1996/06/02 07:09:22 morgan Exp morgan $
d7 1
a7 1
Thanks for downloading Linux-PAM-0.50.
d28 1
a28 1
	http://gluon.physics.ucla.edu/~morgan/pam
d57 1
a57 1
make...
a74 3
* the unix module is only partially STATIC-aware. Watch the list for an
updated version.

d101 1
a101 1
will delete the various files dotted around the system.
@


1.7
log
@partially rewritten and updated for .42
@
text
@d2 1
a2 1
# $Id: README,v 1.6 1996/05/26 16:05:27 morgan Exp morgan $
d7 1
a7 1
Thanks for downloading Linux-PAM-0.42.
d75 1
a75 5
You can verify that the "applications" in ./bin are working as well as
they do for me by running them...

* 'su' does not currently work with STATIC modules. This is because
the unix module is only partially STATIC-aware. Watch the list for an
d80 1
a80 1
* The documentation, what there is of it, is in ./doc. I only
d124 1
a124 1
Additionally, the Linux-PAM files have been known to be found at one
d132 1
@


1.6
log
@updated version number
@
text
@d2 1
a2 1
# $Id: README,v 1.5 1996/05/26 04:25:23 morgan Exp morgan $
d7 8
a14 1
Thanks for downloading Linux-PAM-0.41. (0.40 was broken in the box)
d25 1
a25 1
[For the paranoid, there is an md5 checksum for the whole tar.gz file
d39 10
d54 4
a57 1
[ or 'make all' if you prefer ].
d67 7
a73 4
	some executables		in	./bin
	libpam.so.XXX (shared library)	in	/usr/lib
	libpam.a (static library)	in	/usr/lib
	pam_*.so (modules)		in	/usr/lib/security
d78 4
d84 2
a85 2
* The documentation, what there is of it, is in ./doc. I am only
including the sgml format source-files. But will try to make .ps files
d110 3
a112 4
* Michael Johnson has added support for static modules.. you can alter
where/how libpam looks up the modules by changing the exported variables
in the top level makefile (I have made some effort to automate it so
any problems might well be my fault!)
d118 1
a118 1
Email bugs/comments to: the Linux-PAM list <linux-pam@@mit.edu>
d121 7
d129 2
a130 1
or more of the following places:
@


1.5
log
@updated for .40
@
text
@d2 1
a2 1
# $Id: README,v 1.4 1996/05/21 05:44:46 morgan Exp morgan $
d7 1
a7 1
Thanks for downloading Linux-PAM-0.40.
@


1.4
log
@updated for .34
@
text
@d2 1
a2 1
# $Id: README,v 1.3 1996/05/02 05:43:18 morgan Exp morgan $
d7 1
a7 1
Thanks for down-loading Linux-PAM-0.34 .
d49 1
d82 5
@


1.3
log
@updated for .32
@
text
@d2 1
a2 1
# $Id: README,v 1.2 1996/03/17 03:18:47 morgan Exp morgan $
d7 1
a7 1
Thanks for down-loading Linux-PAM-0.32 .
@


1.2
log
@updated for 0.3 and included 'make remove' option which is intended
to purge the system of Linux-PAM files.
@
text
@d2 1
a2 1
# $Id: README,v 1.1 1996/03/10 18:46:48 morgan Exp morgan $
d7 1
a7 1
Thanks for down-loading Linux-PAM-0.3 .
d25 2
a26 2
If you choose to get install the RCS files that accompany this release,
you may also run
d48 1
a48 1
	libpam.so (shared library)	in	/usr/lib
d52 1
a52 2
they do for me by running them. [currently they all report access
denied :( ]
d57 6
a62 6
including the sgml format source-files this time. But will try to make
.ps files available from the above http address. To locally use these
sgml files you should have linuxdoc-sgml installed [try sunsite, I
found it didn't compile well until I removed the check for the section
3 manual ctype, which I don't have!]. Sorry. But I'm conserving net
bandwidth by only including sources!
d67 8
a74 1
part of the overall make.
d89 2
a90 2
Additionally, the Linux-PAM files are normally available at one or
more of the following places:
a95 1

@


1.1
log
@Initial revision
@
text
@d2 1
a2 1
# $Id: README,v 1.2 1996/03/10 18:32:27 morgan Exp $
d7 1
a7 1
Thanks for down-loading Linux-PAM-0.21 .
d62 1
a62 1
3 manual ctype, which I don't have!]. Sorry. But I'm preserving net
d72 3
@
