ANNOUNCE: TIS/MOSS Version 7.1

James M Galvin <tismoss-support@tis.com> Wed, 13 September 1995 23:16 UTC

Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa21327; 13 Sep 95 19:16 EDT
Received: from CNRI.Reston.VA.US by IETF.CNRI.Reston.VA.US id aa21323; 13 Sep 95 19:16 EDT
Received: from list.cren.net by CNRI.Reston.VA.US id aa05703; 13 Sep 95 19:16 EDT
Received: from localhost ([127.0.0.1]) by list.cren.net with SMTP id <4372-9>; Wed, 13 Sep 1995 19:06:47 -0400
Received: from TIS.COM ([192.94.214.96]) by list.cren.net with SMTP id <4391-3>; Wed, 13 Sep 1995 19:06:17 -0400
Received: by neptune.TIS.COM id ad05807; 13 Sep 95 17:00 EDT
Received: from relay.tis.com by neptune.TIS.COM id aa04872; 13 Sep 95 16:13 EDT
Received: from sol.tis.com(192.33.112.100) by relay.tis.com via smap (g3.0.1) id xma005366; Wed, 13 Sep 95 16:01:23 -0400
Received: from pulsar.tis.com by tis.com (4.1/SUN-5.64) id AA19261; Wed, 13 Sep 95 16:11:35 EDT
Message-Id: <9509132011.AA19261@tis.com>
Date: Wed, 13 Sep 1995 16:11:35 -0400
Reply-To: James M Galvin <tismoss-support@tis.com>
X-Orig-Sender: owner-ietf-822@list.cren.net
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: James M Galvin <tismoss-support@tis.com>
Illegal-Object: Syntax error in To: address found on list.cren.net: To: "MOSS.Announce.List":;tis.com@TIS.COM ^-missing end of address
To: ietf-smtp-ml@ux1.cso.uiuc.edu
MMDF-Warning: Parse error in original version of preceding line at CNRI.Reston.VA.US
To: troth@ua1vm.ua.edu
MMDF-Warning: Parse error in original version of preceding line at CNRI.Reston.VA.US
To: sdm7g@virginia.edu
MMDF-Warning: Parse error in original version of preceding line at CNRI.Reston.VA.US
To: rens@cs.columbia.edu
MMDF-Warning: Parse error in original version of preceding line at CNRI.Reston.VA.US
To: matty@cs.su.oz.au
MMDF-Warning: Parse error in original version of preceding line at CNRI.Reston.VA.US
To: bob@cs.su.oz.au
MMDF-Warning: Parse error in original version of preceding line at CNRI.Reston.VA.US
To: mconstab@alsvid.scu.edu.au
MMDF-Warning: Parse error in original version of preceding line at CNRI.Reston.VA.US
To: ietf822@uniwa.uwa.edu.au
MMDF-Warning: Parse error in original version of preceding line at CNRI.Reston.VA.US
To: Trevor.Hales@mel.dit.csiro.au
MMDF-Warning: Parse error in original version of preceding line at CNRI.Reston.VA.US
To: ietf-822@mel.dit.csiro.au
MMDF-Warning: Parse error in original version of preceding line at CNRI.Reston.VA.US
To: S9GONDIM@imerj.bitnet
MMDF-Warning: Parse error in original version of preceding line at CNRI.Reston.VA.US
To: tim@pipex.net
MMDF-Warning: Parse error in original version of preceding line at CNRI.Reston.VA.US
To: post-ietf-822@uunet.uu.net
MMDF-Warning: Parse error in original version of preceding line at CNRI.Reston.VA.US
To: conklin@info.cren.net
MMDF-Warning: Parse error in original version of preceding line at CNRI.Reston.VA.US
To: meganac@rahul.net
MMDF-Warning: Parse error in original version of preceding line at CNRI.Reston.VA.US
To: klensin+smtp@mail1.reston.mci.net
MMDF-Warning: Parse error in original version of preceding line at CNRI.Reston.VA.US
To: dely@CNRI.Reston.VA.US
MMDF-Warning: Parse error in original version of preceding line at CNRI.Reston.VA.US
To: corth@CNRI.Reston.VA.US
MMDF-Warning: Parse error in original version of preceding line at CNRI.Reston.VA.US
To: ietf-archive@CNRI.Reston.VA.US
MMDF-Warning: Parse error in original version of preceding line at CNRI.Reston.VA.US
To: john@loverso.southborough.ma.us
MMDF-Warning: Parse error in original version of preceding line at CNRI.Reston.VA.US
To: internet.ietf.rfc822@dbc.mtview.ca.us
MMDF-Warning: Parse error in original version of preceding line at CNRI.Reston.VA.US
To: surya@utu.premenos.com
MMDF-Warning: Parse error in original version of preceding line at CNRI.Reston.VA.US
To: ietf-smtp@isgate.is
MMDF-Warning: Parse error in original version of preceding line at CNRI.Reston.VA.US
To: syhan@cosmos.kaist.ac.kr
MMDF-Warning: Parse error in original version of preceding line at CNRI.Reston.VA.US
To: iusung@cosmos.kaist.ac.kr
MMDF-Warning: Parse error in original version of preceding line at CNRI.Reston.VA.US
To: yannis.Corovesis@isosun.ariadne-t.gr
MMDF-Warning: Parse error in original version of preceding line at CNRI.Reston.VA.US
To: takis@isosun.ariadne-t.gr
MMDF-Warning: Parse error in original version of preceding line at CNRI.Reston.VA.US
To: ietf-smtp@csi.forth.gr
MMDF-Warning: Parse error in original version of preceding line at CNRI.Reston.VA.US
To: ietf-822@csi.forth.gr
MMDF-Warning: Parse error in original version of preceding line at CNRI.Reston.VA.US
To: ietf-822@enst.fr
MMDF-Warning: Parse error in original version of preceding line at CNRI.Reston.VA.US
To: Christophe.Wolfhugel@grasp.insa-lyon.fr
MMDF-Warning: Parse error in original version of preceding line at CNRI.Reston.VA.US
To: Sylvain.Langlois@der.edf.fr
MMDF-Warning: Parse error in original version of preceding line at CNRI.Reston.VA.US
To: peter.sylvester@edelweb.fr
MMDF-Warning: Parse error in original version of preceding line at CNRI.Reston.VA.US
To: schara@inf.puc-rio.br
MMDF-Warning: Parse error in original version of preceding line at CNRI.Reston.VA.US
To: ysato@etl.go.jp
MMDF-Warning: Parse error in original version of preceding line at CNRI.Reston.VA.US
To: taka@fxis.fujixerox.co.jp
MMDF-Warning: Parse error in original version of preceding line at CNRI.Reston.VA.US
To: hisashi@rsl.crl.fujixerox.co.jp
MMDF-Warning: Parse error in original version of preceding line at CNRI.Reston.VA.US
To: seki@sysrap.cs.fujitsu.co.jp
MMDF-Warning: Parse error in original version of preceding line at CNRI.Reston.VA.US
To: suzuki@isr.recruit.co.jp
MMDF-Warning: Parse error in original version of preceding line at CNRI.Reston.VA.US
To: makr@airco.co.jp
MMDF-Warning: Parse error in original version of preceding line at CNRI.Reston.VA.US
To: same@ori.hitachi-sk.co.jp
MMDF-Warning: Parse error in original version of preceding line at CNRI.Reston.VA.US
To: shigeya@foretune.co.jp
MMDF-Warning: Parse error in original version of preceding line at CNRI.Reston.VA.US
To: hi@jain.ad.jp
MMDF-Warning: Parse error in original version of preceding line at CNRI.Reston.VA.US
To: ietf-822@iij.ad.jp
MMDF-Warning: Parse error in original version of preceding line at CNRI.Reston.VA.US
To: umerin@bisque.mse.kyutech.ac.jp
MMDF-Warning: Parse error in original version of preceding line at CNRI.Reston.VA.US
To: mohta@necom830.cc.titech.ac.jp
MMDF-Warning: Parse error in original version of preceding line at CNRI.Reston.VA.US
To: kazu@is.aist-nara.ac.jp
MMDF-Warning: Parse error in original version of preceding line at CNRI.Reston.VA.US
To: kazusi-m@is.aist-nara.ac.jp
MMDF-Warning: Parse error in original version of preceding line at CNRI.Reston.VA.US
To: collins@sware.uucp
MMDF-Warning: Parse error in original version of preceding line at CNRI.Reston.VA.US
To: Harald.T.Alvestrand@uninett.no
MMDF-Warning: Parse error in original version of preceding line at CNRI.Reston.VA.US
To: ietf-822ext@redist.uit.no
MMDF-Warning: Parse error in original version of preceding line at CNRI.Reston.VA.US
To: ietf-822@ifi.uio.no
MMDF-Warning: Parse error in original version of preceding line at CNRI.Reston.VA.US
To: ietf-822@wimsey.com
MMDF-Warning: Parse error in original version of preceding line at CNRI.Reston.VA.US
To: hilljj@ruby.cray.com
MMDF-Warning: Parse error in original version of preceding line at CNRI.Reston.VA.US
To: masinter@parc.xerox.com
MMDF-Warning: Parse error in original version of preceding line at CNRI.Reston.VA.US
To: janssen@parc.xerox.com
MMDF-Warning: Parse error in original version of preceding line at CNRI.Reston.VA.US
To: jjc@pobox.com
MMDF-Warning: Parse error in original version of preceding line at CNRI.Reston.VA.US
To: ybmcu@panix.com
MMDF-Warning: Parse error in original version of preceding line at CNRI.Reston.VA.US
To: sjt@ssw.com
MMDF-Warning: Parse error in original version of preceding line at CNRI.Reston.VA.US
To: jpg@ssw.com
MMDF-Warning: Parse error in original version of preceding line at CNRI.Reston.VA.US
To: THINDER@softsw.ssw.com
MMDF-Warning: Parse error in original version of preceding line at CNRI.Reston.VA.US
To: GTL@softsw.ssw.com
MMDF-Warning: Parse error in original version of preceding line at CNRI.Reston.VA.US
To: RAH@softsw.ssw.com
MMDF-Warning: Parse error in original version of preceding line at CNRI.Reston.VA.US
To: jfox@spyder.ssw.com
MMDF-Warning: Parse error in original version of preceding line at CNRI.Reston.VA.US
To: ietfsmtp.sjogren@tgv.com
MMDF-Warning: Parse error in original version of preceding line at CNRI.Reston.VA.US
To: nsblist-mime@nsb.fv.com
MMDF-Warning: Parse error in original version of preceding line at CNRI.Reston.VA.US
To: dan_grillo@next.com
MMDF-Warning: Parse error in original version of preceding line at CNRI.Reston.VA.US
To: Lennart_Lovstrand@next.com
MMDF-Warning: Parse error in original version of preceding line at CNRI.Reston.VA.US
To: Paul.Lustgarten@att.com
MMDF-Warning: Parse error in original version of preceding line at CNRI.Reston.VA.US
To: gregory.c.sheehan@att.com
MMDF-Warning: Parse error in original version of preceding line at CNRI.Reston.VA.US
To: jcr@pegasus.att.com
MMDF-Warning: Parse error in original version of preceding line at CNRI.Reston.VA.US
To: hansen@pegasus.att.com
MMDF-Warning: Parse error in original version of preceding line at CNRI.Reston.VA.US
To: tal@big.att.com
MMDF-Warning: Parse error in original version of preceding line at CNRI.Reston.VA.US
To: acus02@ems13.corp.mot.com
MMDF-Warning: Parse error in original version of preceding line at CNRI.Reston.VA.US
To: feldmark@sequent.com
MMDF-Warning: Parse error in original version of preceding line at CNRI.Reston.VA.US
To: david_goldsmith@taligent.com
MMDF-Warning: Parse error in original version of preceding line at CNRI.Reston.VA.US
To: kmark@zoomit.com
MMDF-Warning: Parse error in original version of preceding line at CNRI.Reston.VA.US
To: sukvg@microsoft.com
MMDF-Warning: Parse error in original version of preceding line at CNRI.Reston.VA.US
To: IsaacC@microsoft.com
MMDF-Warning: Parse error in original version of preceding line at CNRI.Reston.VA.US
To: dougst@wspu.microsoft.com
MMDF-Warning: Parse error in original version of preceding line at CNRI.Reston.VA.US
To: ned+ietf-822@innosoft.com
MMDF-Warning: Parse error in original version of preceding line at CNRI.Reston.VA.US
To: troth@compassnet.com
MMDF-Warning: Parse error in original version of preceding line at CNRI.Reston.VA.US
To: mb@ebt.com
MMDF-Warning: Parse error in original version of preceding line at CNRI.Reston.VA.US
To: randy@mv-oc.unisys.com
MMDF-Warning: Parse error in original version of preceding line at CNRI.Reston.VA.US
To: IETF822@mpa15ab.mv-oc.unisys.com
MMDF-Warning: Parse error in original version of preceding line at CNRI.Reston.VA.US
To: Paul_Lyons.LOTUS@crd.lotus.com
MMDF-Warning: Parse error in original version of preceding line at CNRI.Reston.VA.US
To: Michael_J_Taylor.NOTES@crd.lotus.com
MMDF-Warning: Parse error in original version of preceding line at CNRI.Reston.VA.US
To: Michael_Harer.NOTES@crd.lotus.com
MMDF-Warning: Parse error in original version of preceding line at CNRI.Reston.VA.US
To: galvin@tis.com
MMDF-Warning: Parse error in original version of preceding line at CNRI.Reston.VA.US
To: Tom.Moore@daytonoh.ncr.com
MMDF-Warning: Parse error in original version of preceding line at CNRI.Reston.VA.US
To: davew@wrq.com
MMDF-Warning: Parse error in original version of preceding line at CNRI.Reston.VA.US
To: kam@hpcvxkm.cv.hp.com
MMDF-Warning: Parse error in original version of preceding line at CNRI.Reston.VA.US
To: kirshenbaum@hplabs.hp.com
MMDF-Warning: Parse error in original version of preceding line at CNRI.Reston.VA.US
To: bkelley@cup.hp.com
MMDF-Warning: Parse error in original version of preceding line at CNRI.Reston.VA.US
To: shepherd@hplabs.hpl.hp.com
MMDF-Warning: Parse error in original version of preceding line at CNRI.Reston.VA.US
To: maeyama@sumitomo.com
MMDF-Warning: Parse error in original version of preceding line at CNRI.Reston.VA.US
To: vlau@sun.com
MMDF-Warning: Parse error in original version of preceding line at CNRI.Reston.VA.US
To: hhiura@sun.com
MMDF-Warning: Parse error in original version of preceding line at CNRI.Reston.VA.US
To: takahasi@japan.sun.com
MMDF-Warning: Parse error in original version of preceding line at CNRI.Reston.VA.US
To: suzuki@japan.sun.com
MMDF-Warning: Parse error in original version of preceding line at CNRI.Reston.VA.US
Subject: ANNOUNCE: TIS/MOSS Version 7.1
Mime-Version: 1.0
Content-Type: multipart/mixed; boundary="----- =_aaaaaaaaaa0"
Content-Id: <2977.811023088.1@tis.com>
X-Sender: galvin@TIS.COM
X-Listprocessor-Version: 7.2 -- ListProcessor by CREN

Trusted Information Systems, Inc. (TIS), in cooperation with RSA Data
Security, Inc. (RSADSI), is pleased to provide TIS/MOSS, a reference
implementation of MIME Object Security Services (MOSS).  TIS/MOSS is a
security toolkit that provides digital signature and encryption services
for MIME objects.  TIS/MOSS includes the "glue" necessary for
integration with Version 6.8.3 of the Rand MH Message Handling System,
in addition to generic Bourne shell scripts that make it possible to use
it with email user agents supporting UNIX shell escapes.

In order to foster acceptance of MOSS and provide the community with a
usable, working version of this technology, TIS/MOSS is being made
available for broad use on the following basis.

TIS/MOSS is distributed in source code form, with all modules written in
the C programming language.  It runs on many UNIX derived platforms.  It
includes a DOS compilation directive that facilitates its port to
DOS/WINDOWS.

TIS/MOSS requires RSAREF, a cryptographic toolkit distributed by RSADSI.
TIS/MOSS makes use of undocumented features of RSAREF.  RSADSI has given
permission for users of TIS/MOSS to use these features, subject to the
terms and conditions of both the TIS/MOSS and RSAREF licenses, as
distributed with each software package.

TIS/MOSS is a product of Trusted Information Systems, Inc.  It may be
used by organizations and users for exchanging MOSS email messages,
subject to the terms and conditions of its license.  Enclosed below is
the MOSS Frequently Asked Questions, which includes instructions on how
to retrieve the software.

TIS/MOSS is export controlled by the U.S. Government.  As a result it is
only available to U.S. and Canadian sites and individuals.  Please see
the FAQ for more information.
		  TIS/MOSS Frequently Asked Questions
			 Last Updated July 1995
	 Send questions and comments to tismoss-support@tis.com

Questions answered:

   1) What is MIME Object Security Services (MOSS)?
   2) What is MIME?
   3) How does MOSS compare to PGP and PEM?
   4) Where is the MOSS standard defined?
   5) Are there implementations of MOSS available?
   6) How do I get TIS/MOSS?
   7) Why is TIS/MOSS only available in the US and Canada?
   8) Are special privileges (e.g., root access) required to install
      TIS/MOSS?
   9) What about integrating TIS/MOSS into email user agents?
  10) What about DOS and other non-UNIX platforms?
  11) Is there a forum for MOSS users and developers?
  12) What about certificates?
  13) What is the Internet Certification hierarchy?
  14) What if I have questions or problems with TIS/MOSS?

 * means that this entry has been recently updated.
 + means that this entry has been added recently.


1
Q: What is MIME Object Security Services (MOSS)?

A: MOSS is a Privacy Enhanced Mail (PEM) derivative that is a Proposed
   Internet Standard for adding security services to Multi-purpose
   Internet Mail Extensions (MIME).  It uses the cryptographic
   techniques of digital signature and encryption to provide origin
   authentication, integrity, and confidentiality to MIME objects.
   Users of MOSS can know who originated a message, that the message
   has not been changed enroute, and that the message was kept secret
   from everyone except the intended recipients.

   MOSS depends on the existence of public/private key pairs to support
   its security services.  Users must exchange public keys with those
   other users with whom they wish to exchange MOSS email.  This may be
   accomplished manually, via mechanisms available in the protocol, via
   X.509 certificates, or any other suitable mechanism.

2
Q: What is MIME?

A: MIME is an Internet Standard (RFC 1521) that defines the format of
   email message bodies to allow multi-part textual and non-textual
   message bodies to be represented and exchanged without loss of
   information.  MIME does for message bodies what RFC822 does for
   message headers.

3
Q: How does MOSS compare to PGP and PEM?

   PGP can provide the same services but since it is not integrated with
   MIME the interpretation of the protected content is necessarily user
   controlled.  Note, however, that MIME can carry a PGP object.

   MOSS is a PEM derivative.  It integrates the security services of PEM
   with MIME, taking advantage of the extensive structuring and
   formatting facilities of MIME, limited versions of which are
   necessarily an integral part of the PEM specifications.

4
Q: Where is the MOSS standard defined?

A: There is a Proposed Standard published as an RFC that specifies MOSS.
   This document may be found in your favorite RFC repository.
   Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
   an EMAIL message to "rfc-info@ISI.EDU"; with the message body "help:
   ways_to_get_rfcs".  For example:

        To: rfc-info@ISI.EDU
        Subject: getting rfcs

        help: ways_to_get_rfcs

5
Q: Are there implementations of MOSS available?

A: Yes, Trusted Information Systems (TIS), under ARPA sponsorship, has
   released a reference implementation of MOSS (TIS/MOSS) to the
   Internet community.

   TIS/MOSS is a UNIX-based implementation that is easily integrated
   with email user agents.  The source code is openly available in the
   United States and Canada for non-commercial use.  The current version
   of TIS/MOSS is 7.1.

   Vendors interested in including TIS/MOSS in their products or
   integrating it with their services should contact Trusted Information
   Systems about licensing Trusted Mail (tm) by sending email to
   tismoss-support@tis.com.

6
Q: How do I get TIS/MOSS?

A: TIS/MOSS is available via anonymous ftp in the United States and
   Canada to US and Canadian citizens and people with a US "green
   card."  To retrieve TIS/MOSS please FTP to

     host:   ftp.tis.com
     login:  anonymous

   and retrieve the files

     pub/MOSS/README
     pub/MOSS/LICENSE
     pub/MOSS/BUGS

   The README file contains further instructions.  

7
Q: Why is TIS/MOSS only available in the US and Canada?

A: The export from the United States of the cryptography used in
   TIS/MOSS is controlled by the United States government.

8
Q: Are special privileges (e.g., root access) required to install TIS/MOSS?

A: No.

9
Q: What about integrating TIS/MOSS into email user agents?

A: TIS/MOSS includes "glue", in the form of shell scripts, to integrate
   it with the Rand MH Message Handling System version 6.8.3.  It also
   includes generic scripts that make the services accessible to any
   UNIX application that supports shell escapes.  If you integrate
   TIS/MOSS with a popular email user agent, we would be happy to make
   it available to others.

10
Q: What about DOS and other non-UNIX platforms?

A: TIS/MOSS has been ported to DOS and includes a DOS compiler option
   that may be set to facilitate its installation in DOS environments.
   It has also been ported to Macintosh although it does not yet include
   a MAC compiler option.  If you port TIS/MOSS to other platforms, we
   would be happy to make the changes available to others.

11
Q: Is there a forum for MOSS users and developers?

A: Yes, there is an email list for users of TIS/MOSS called
   "tismoss-users@tis.com";.  To get added to the list send a message to
   "tismoss-users-request@tis.com";.

   There is an email list for implementors and discussions of the MOSS
   specifications called "pem-dev@tis.com";.  This list originated with
   the PEM protocol, from which MOSS is derived.  To get added to the
   list send a message to "pem-dev-request@tis.com";.

12
Q: What about certificates?

A: TIS/MOSS supports the use of X.509 certificates including creation,
   validation, certificate revocation lists, distribution, and
   destruction.  Users may embody their public key in a certificate and
   may participate in the Internet certification hierarchy or some other
   private hierarchy.  TIS/MOSS neither requires nor enforces any
   certification hierarchy policy.

13
Q: What is the Internet Certification hierarchy?

A: The Internet Certification hierarchy is defined by RFC1422.  It is a
   tree structured hierarchy of certificates with a single, global root
   called the Internet PCA Registration Authority (IPRA).  The IPRA
   issues certificates to Policy Certification Authorities (PCAs) who
   issue certificates to Certification Authorities (CAs) who may issue
   certificates to users or subordinate CAs.  Identities are based on
   distinguished names and there are restrictions on their form and
   content.

   For more information on becoming a PCA see the IPRA WWW page at:

	http://bs.mit.edu:8001/ipra.html

   or contact the IPRA at:

	ipra-info@isoc.org

   For more information on becoming a CA under the TIS PCA contact:

	tispca-info@tis.com

14
Q: What if I have questions about or problems with TIS/MOSS?

A: Send them to "tismoss-support@tis.com";.
Trusted Information Systems, Inc. (TIS), in cooperation with RSA Data
Security, Inc. (RSADSI), is pleased to provide TIS/MOSS, a reference
implementation of MIME Object Security Services (MOSS).  TIS/MOSS is a
security toolkit that provides digital signature and encryption services
for MIME objects.  TIS/MOSS includes the "glue" necessary for
integration with Version 6.8.3 of the Rand MH Message Handling System,
in addition to generic Bourne shell scripts that make it possible to use
it with email user agents supporting UNIX shell escapes.

In order to foster acceptance of MOSS and provide the community with a
usable, working version of this technology, TIS/MOSS is being made
available for broad use on the following basis.

TIS/MOSS is distributed in source code form, with all modules written in
the C programming language.  It runs on many UNIX derived platforms.  It
includes a DOS compilation directive that facilitates its port to
DOS/WINDOWS.

TIS/MOSS requires RSAREF, a cryptographic toolkit distributed by RSADSI.
TIS/MOSS makes use of undocumented features of RSAREF.  RSADSI has given
permission for users of TIS/MOSS to use these features, subject to the
terms and conditions of both the TIS/MOSS and RSAREF licenses, as
distributed with each software package.

TIS/MOSS is a product of Trusted Information Systems, Inc.  It may be
used by organizations and users for exchanging MOSS email messages,
subject to the terms and conditions of its license.  Enclosed below is
the MOSS Frequently Asked Questions, which includes instructions on how
to retrieve the software.

TIS/MOSS is export controlled by the U.S. Government.  As a result it is
only available to U.S. and Canadian sites and individuals.  Please see
the FAQ for more information.
		  TIS/MOSS Frequently Asked Questions
			 Last Updated July 1995
	 Send questions and comments to tismoss-support@tis.com

Questions answered:

   1) What is MIME Object Security Services (MOSS)?
   2) What is MIME?
   3) How does MOSS compare to PGP and PEM?
   4) Where is the MOSS standard defined?
   5) Are there implementations of MOSS available?
   6) How do I get TIS/MOSS?
   7) Why is TIS/MOSS only available in the US and Canada?
   8) Are special privileges (e.g., root access) required to install
      TIS/MOSS?
   9) What about integrating TIS/MOSS into email user agents?
  10) What about DOS and other non-UNIX platforms?
  11) Is there a forum for MOSS users and developers?
  12) What about certificates?
  13) What is the Internet Certification hierarchy?
  14) What if I have questions or problems with TIS/MOSS?

 * means that this entry has been recently updated.
 + means that this entry has been added recently.


1
Q: What is MIME Object Security Services (MOSS)?

A: MOSS is a Privacy Enhanced Mail (PEM) derivative that is a Proposed
   Internet Standard for adding security services to Multi-purpose
   Internet Mail Extensions (MIME).  It uses the cryptographic
   techniques of digital signature and encryption to provide origin
   authentication, integrity, and confidentiality to MIME objects.
   Users of MOSS can know who originated a message, that the message
   has not been changed enroute, and that the message was kept secret
   from everyone except the intended recipients.

   MOSS depends on the existence of public/private key pairs to support
   its security services.  Users must exchange public keys with those
   other users with whom they wish to exchange MOSS email.  This may be
   accomplished manually, via mechanisms available in the protocol, via
   X.509 certificates, or any other suitable mechanism.

2
Q: What is MIME?

A: MIME is an Internet Standard (RFC 1521) that defines the format of
   email message bodies to allow multi-part textual and non-textual
   message bodies to be represented and exchanged without loss of
   information.  MIME does for message bodies what RFC822 does for
   message headers.

3
Q: How does MOSS compare to PGP and PEM?

   PGP can provide the same services but since it is not integrated with
   MIME the interpretation of the protected content is necessarily user
   controlled.  Note, however, that MIME can carry a PGP object.

   MOSS is a PEM derivative.  It integrates the security services of PEM
   with MIME, taking advantage of the extensive structuring and
   formatting facilities of MIME, limited versions of which are
   necessarily an integral part of the PEM specifications.

4
Q: Where is the MOSS standard defined?

A: There is a Proposed Standard published as an RFC that specifies MOSS.
   This document may be found in your favorite RFC repository.
   Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
   an EMAIL message to "rfc-info@ISI.EDU"; with the message body "help:
   ways_to_get_rfcs".  For example:

        To: rfc-info@ISI.EDU
        Subject: getting rfcs

        help: ways_to_get_rfcs

5
Q: Are there implementations of MOSS available?

A: Yes, Trusted Information Systems (TIS), under ARPA sponsorship, has
   released a reference implementation of MOSS (TIS/MOSS) to the
   Internet community.

   TIS/MOSS is a UNIX-based implementation that is easily integrated
   with email user agents.  The source code is openly available in the
   United States and Canada for non-commercial use.  The current version
   of TIS/MOSS is 7.1.

   Vendors interested in including TIS/MOSS in their products or
   integrating it with their services should contact Trusted Information
   Systems about licensing Trusted Mail (tm) by sending email to
   tismoss-support@tis.com.

6
Q: How do I get TIS/MOSS?

A: TIS/MOSS is available via anonymous ftp in the United States and
   Canada to US and Canadian citizens and people with a US "green
   card."  To retrieve TIS/MOSS please FTP to

     host:   ftp.tis.com
     login:  anonymous

   and retrieve the files

     pub/MOSS/README
     pub/MOSS/LICENSE
     pub/MOSS/BUGS

   The README file contains further instructions.  

7
Q: Why is TIS/MOSS only available in the US and Canada?

A: The export from the United States of the cryptography used in
   TIS/MOSS is controlled by the United States government.

8
Q: Are special privileges (e.g., root access) required to install TIS/MOSS?

A: No.

9
Q: What about integrating TIS/MOSS into email user agents?

A: TIS/MOSS includes "glue", in the form of shell scripts, to integrate
   it with the Rand MH Message Handling System version 6.8.3.  It also
   includes generic scripts that make the services accessible to any
   UNIX application that supports shell escapes.  If you integrate
   TIS/MOSS with a popular email user agent, we would be happy to make
   it available to others.

10
Q: What about DOS and other non-UNIX platforms?

A: TIS/MOSS has been ported to DOS and includes a DOS compiler option
   that may be set to facilitate its installation in DOS environments.
   It has also been ported to Macintosh although it does not yet include
   a MAC compiler option.  If you port TIS/MOSS to other platforms, we
   would be happy to make the changes available to others.

11
Q: Is there a forum for MOSS users and developers?

A: Yes, there is an email list for users of TIS/MOSS called
   "tismoss-users@tis.com";.  To get added to the list send a message to
   "tismoss-users-request@tis.com";.

   There is an email list for implementors and discussions of the MOSS
   specifications called "pem-dev@tis.com";.  This list originated with
   the PEM protocol, from which MOSS is derived.  To get added to the
   list send a message to "pem-dev-request@tis.com";.

12
Q: What about certificates?

A: TIS/MOSS supports the use of X.509 certificates including creation,
   validation, certificate revocation lists, distribution, and
   destruction.  Users may embody their public key in a certificate and
   may participate in the Internet certification hierarchy or some other
   private hierarchy.  TIS/MOSS neither requires nor enforces any
   certification hierarchy policy.

13
Q: What is the Internet Certification hierarchy?

A: The Internet Certification hierarchy is defined by RFC1422.  It is a
   tree structured hierarchy of certificates with a single, global root
   called the Internet PCA Registration Authority (IPRA).  The IPRA
   issues certificates to Policy Certification Authorities (PCAs) who
   issue certificates to Certification Authorities (CAs) who may issue
   certificates to users or subordinate CAs.  Identities are based on
   distinguished names and there are restrictions on their form and
   content.

   For more information on becoming a PCA see the IPRA WWW page at:

	http://bs.mit.edu:8001/ipra.html

   or contact the IPRA at:

	ipra-info@isoc.org

   For more information on becoming a CA under the TIS PCA contact:

	tispca-info@tis.com

14
Q: What if I have questions about or problems with TIS/MOSS?

A: Send them to "tismoss-support@tis.com";.