				   
			 TIS/MOSS Version 7.1
		  (previous release was TIS/PEM 7.0)
			     September 1995


The complete installation process is described in this document,
located at the top of the TIS/MOSS distribution.  The following files
may be found in this directory:

CHANGES --- This file contains release notes.  It describes the new
features in this version and the differences between this version and
the last distributed version.  If you are upgrading an existing
installation of TIS/PEM or TIS/MOSS, you should check this file to see
what has changed.

INSTALL --- This file contains the configuration and installation
instructions, which you are currently reading.

README --- This file contains a description of the TIS/MOSS distribution
and of its license agreement, including pointers to more information.

copyright.txt --- This file contains a copy of the copyright notice that
appears in each source file.

license.txt --- This file contains the full text of the license
agreement that specifies the conditions under which this software may be
used.

moss --- This directory contains the complete TIS/MOSS source
distribution.  The pathname of this directory will be referred to as
MOSS-root throughout the remainder of this document.

Listed below are the steps to be completed to configure, compile, and
install TIS/MOSS.  If you have any problems or questions, please send
email to "tismoss-support@tis.com".

1. Acquire the software.

   If you are reading this you have probably already completed this
   step and the next.  However, just in case, the TIS/MOSS software is
   retrieved via anonymous FTP from the host "ftp.tis.com".  You must
   retrieve the file "/pub/MOSS/README" and understand it before
   retrieving the software.  Complete instructions are in the
   /pub/MOSS/README file.

   You must also have a copy of RSAREF 2.0, the cryptographic engine
   used by TIS/MOSS.  RSAREF 2.0 is available via anonymous ftp from
   ftp.rsa.com.

2. Uncompress and untar the software.

   Assuming you retrieved a file named "moss-X.tar.Z", where "X" is the
   version of the software you retrieved, create a directory for the
   software distribution and place the file in it.  You can uncompress
   and untar the distribution using the commands:

     uncompress moss-X.tar.Z
     tar xpf moss-X.tar

   If you have the zcat program, you can use the following to save
   space by not creating the intermediate uncompressed tar file:

     zcat moss-X.tar.Z | tar xpf -

   Either way, this will create a directory called "moss-X", where "X"
   is the version number of the software you have retrieved.  In this
   directory will be all of the files described herein.

3. Configure the software.

   TIS/MOSS is completely configured by editing MOSS-root/makefile.com.
   Although there are many options you may configure in this file,
   there is a very small number which you must check before compiling
   the software.  If you look at the top of the file it will tell you
   exactly which options you must check.

   The macro CRYPTOLIBS deserves special mention.  As distributed,
   TIS/MOSS is dependent on RSAREF.  You must set CRYPTOLIBS to the
   pathname of an RSAREF library.  If you already have RSAREF 2.0,
   then point it at that version.  If not, you must obtain RSAREF 2.0
   via anonymous ftp from ftp.rsa.com abd build it prior to
   configuring TIS/MOSS.  We have found that on some UNIX systems,
   "-DPROTOTYPES=1" must be changed to "-DPROTOTYPES=0" in the
   makefile.  Note, if you copy rsaref.a to a new location and don't
   use the -p option on cp, you may need to run ranlib on it.

   You will also find that all of the options in MOSS-root/makefile.com
   are preceded by a comment describing their use and various settings.
   Please read each comment to determine if the option value must be
   reset for your environment.

   Finally, TIS/MOSS has execution time defaults pre-defined in the
   file MOSS-root/h/init.h.  Although all of the values in the file
   can easily be changed by any user at run-time, you may wish to
   check the defaults to see if they are appropriate for your
   environment.

4. Build the software.

   Prior to building TIS/MOSS you must have built RSAREF 2.0.  If you
   have not already done so, retrieve RSAREF 2.0 via anonymous ftp
   from ftp.rsa.com and build it.  Be sure to set CRYPTOLIBS in
   MOSS-root/makefile.com to the location of the RSAREF library.
   Note, if you copy rsaref.a to a new location and don't use the -p
   option on cp, you must remember to run ranlib on it.

   To build TIS/MOSS, proceed to the MOSS-root directory and type
   "make".  There should be no problems during the compilation,
   including warning messages.  If you have any unusual messages
   contact "tismoss-support@tis.com" for assistance.

   TIS/MOSS uses lex and yacc to parse messages.  On some platforms,
   the look-ahead buffer in the lex-generated file, lex.yy.c, in the
   directory moss-7.1/moss/lib/parse may be too small and cause the
   verify and decrypt programs to fail.  The constant YYLMAX should be
   defined to be 500 or greater, with BUFSIZ being a reasonable value.
   If, after building TIS/MOSS you notice that the value is under 500,
   change it and rebuild.

5. Install the software.

   To install TIS/MOSS proceed to the MOSS-root directory and type
   "make inst-all".  There should be no problems during the
   installation, including warning messages.  If you have any unusual
   messages contact "tismoss-support@tis.com" for assistance.

   If executable size is a consideration and your system supports hard
   links, make and install (make, make inst-all) the monolithic
   TIS/MOSS program (in MOSS-root/monolith) after making and
   installing as described above.  This will replace the core TIS/MOSS
   programs installed on your system with a single executable that is
   capable of performing most of the TIS/MOSS functions based on the
   name by which it is invoked.

   There are several programs provided in MOSS-root/tools that are
   useful for MOSS developers and others interested in doing low level
   manipulation of MOSS data.  Because of their limited audience, they
   are not normally compiled or installed.  They can be made and
   installed by changing to the MOSS-root/tools directory and running
   make and make inst-all.

6. Use the software.

   You now have basic TIS/MOSS functionality but sending and receiving
   messages will still be beyond your grasp until you read the user
   manual.  Print the user manual located in the directory
   MOSS-root/doc/user.  It is supplied in PostScript (user.ps), DVI
   (user.dvi), and TeX source (*.tex) formats.  Manual pages are
   included in the distribution and are installed with make inst-all.
   Use the man command to access them.  Additionally, all of the
   programs can be called with the single word help to provide basic
   calling information.

   If you have had TIS/PEM 6 before you should already have a
   registration (certificate and private key).  Use your old cai
   program to export your registration.  Use the new pemdbconv program
   to convert the exported registration to your new database.  Each
   user with a registration will need to do this in order to convert
   private keys to the new database.  The pemdbconv program can also
   be used to export all other certificates from your previous
   database and make them available in a shared database file for all
   users.  This may be done by any user.
   
   Alternatively, the mosskey program can be used to generate a new
   public/private key pair, which may be embodied in a certificate or
   not, as specified by command line options; the default is no
   certificate.
   
   To send and receive enhanced mail, TIS/MOSS must be integrated with
   a mail user agent.  The relevant TIS/MOSS programs are sign,
   encrypt, decrypt, and verify.  Included in the distribution is the
   "glue" necessary to allow the Rand MH Message Handler Version 6.8.3
   to use the TIS/MOSS programs.  The glue, in the form of /bin/sh
   scripts, is located in the directory MOSS-root/interfac/mh.  See
   the file MOSS-root/interfac/mh/README for complete instructions on
   installing and using the glue.
   
   If you do not use MH or prefer an alternative user agent, the glue
   included for MH demonstrates how to integrate TIS/MOSS with other
   user agents and other applications.  A set of example generic
   scripts that provide the necessary glue between plain text, MIME
   objects, and MOSS are present in the MOSS-root/interfac/scripts
   directory.  See the file MOSS-root/interfac/scripts/README for
   instructions.  If you would like to make a contribution to the
   collection of interface glue, please contact
   "tismoss-support@tis.com".
