Thursday March 6 0:44:?? PST 1996 ( Andrew Morgan <morgan@physics.ucla.edu> )

These notes are for Linux-PAM release 0.2.  They cover what's changed
since Marc Ewing relased 0.1.

**** Please note. All of the directories in this release have been modified
**** slightly to conform to the new pamlib. A couple of new directories have
**** been added. As well as some documentation. If some of your code
**** was in the previous release. Feel free to update it, but please
**** try to conform to the new headers and Makefiles.

* Andrew Morgan (morgan@physics.ucla.edu) is making this release
 availible, Marc has been busy...!

* Marc's pam-0.1/lib has been (quietly) enhanced and integrated into
 Alex Yurie's collected tree of library and module code
 (linux-pam.prop.1.tar.gz). Most of the changes are to do with error
 checking. Some more robustness in the reading of the pam.conf file
 and the addition of the pam_get_user() function.

* The pam_*.h files have been reorganized to logically enforce the
 separation of modules from applications. [Don't panic! Apart from
 changing references of the form

	#include "pam_appl.h"

 to

	#include <security/pam_appl.h>

 The reorganization should be backwardly compatable (ie. a module
 written for SUN will be as compatable as it was before with the
 previous version ;)~ ]

 (All of the source in this tree now conforms to this scheme...)

 The new reorganization means that modules can be compiled with a
 single header, <security/pam_modules.h>, and applications with
 <security/pam_appl.h>.

* I have tried to remove all the compiler warnings from the updated
 "pamlib/*.c" files. On my system, (with a slightly modified <dlfcn.h>
 email me if it interests you..) there are only two warnings that
 remain: they are that ansi does not permit void --> fn ptr
 assignment. K&Rv2 doesn't mention this....? As a matter of principle,
 if anyone knows how to get rid of that warning... please
 tell. Thanks! "-pedantic"

* you can "make all" as a plain user, but

* to "make install" you must be root. The include files are placed in
 /usr/include/security. The libpam.so library is installed in /usr/lib
 and the modules in /usr/lib/security. The two test binaries
 are installed in the Linux-PAM-0.2/bin directory and a chance is given to
 replace your /etc/pam.conf file with the one in Linux-PAM-0.2/conf.

* I have included some documentation (pretty preliminary at the
moment) which I have been working on in .../doc .

I have had a little trouble with the modules, but atleast there are no
segfaults! Please try it out and discuss your results... I actually
hope it all works for you. But, Email any bugs/suggestions to the
Linux-PAM list: linux-pam@mit.edu .....

Regards,

Andrew Morgan
(morgan@physics.ucla.edu)


Sat Feb 17 17:30:24 EST 1996 (Alexander O. Yuriev alex@bach.cis.temple.edu)

	* conf directory created with example of pam_conf
	* stable code from pam_unix is added to modules/pam_unix
	* test/test.c now requests username and password and attempts
	  to perform authentication

