CD-ROM Aktief 1995 #3/CDA3.iso/survival/secureml.zip/SECUREML.DOC

Text File | 1994-08-09 | 9KB | 176 lines

                     The FidoNet (r) SecureMail System
                                 30 Mar 94
                       Copyright (C) 1994 Jim Cannell
              [Source: GK Pace, 1993; Christopher Baker, 1994]

Introduction:

        This document describes the SecureMail FidoNet (r) Routing
System, its Statement of Purpose, and defines the principles by which it
shall be operated.  It should be noted that FidoNet is a registered
trademark owned by Tom Jennings, used by permission to refer to the
FidoNet, a hobbyist network of amateur, independent, interconnected
systems (Nodes) providing E-Mail transfer services world-wide.


Definition:

        SecureMail can be defined as a group of FidoNet Sysops who have
volunteered to provide an alternative E-Mail routing service within the
FidoNet Network.  The SecureMail System is a component of the FidoNet
Network.  SecureMail is NOT an alternative, separate, or distinct
network.


Statement of Purpose:

        The primary purpose of Securemail, and reason for its creation
is the desire for providing increased privacy in the routing of FidoNet
E-Mail.

        The term privacy as used in the transfer of E-Mail is an
arbitrary one.  Absolute privacy cannot be expected. The degree of
privacy obtained will always be related to the procedure(s), effort used
to insure privacy, and should not be expected to be absolute if data is
to be communicated from one place to another.  Routing of E-Mail, as
compared to sending it direct, cannot be expected to have as high of a
degree of privacy as might be expected when sending it direct.  Those who
are engaged in operating the Securemail system do so with the primary
goal of insuring that all E-Mail routed thru it be afforded the highest
degree of privacy technically possible.

        Those using the Securemail System can expect to enjoy a higher
degree of privacy than other forms of routing, but should not expect
absolute privacy.


Functional Description:

        The SecureMail System is a group of individual FidoNet Sysops who
have volunteered to work together to provide the SecureMail Routing
Service to FidoNet Sysops.  This group is organized, but does not have
authoritative positions.  Each SecureMail Sysop is an independent
volunteer furnishing a service.  There are no monetary rewards, each
Sysop contributes the resources he or she uses to provide the service,
including all costs incurred in providing it.  The operational structure
may appear to have hierarchical order and indeed it does, however such
structure implements a routing matrix, not positions of authority.

        The SecureMail operational philosophy can be described as
cooperative autocracy.  Each SecureMail Sysop is an independent operator
who has volunteered to assume the various responsibilities required of an
organized effort.  No one is compelled to participate, but participation
requires the performance of certain agreed upon functions, standards, and
of course interaction as a group.  Most of the activities parallel or are
incidental to normal FidoNet activities.


Routing Hierarchy:

        The basic routing strategy follows the normal FidoNet pattern of
routing thru Zones, Regions, Nets, to Nodes.  The difference is that
SecureMail traffic is routed thru SecureMail Hosts rather than the
FidoNet Hosts.

        A SecureMail Sysop serving in each position is referred to as a
Host.  There are functional (not Authoritative) positions such as Zone
SecureMail Host (ZSMH) Region SecureMail Host (RSMH) and Net SecureMail
Host (NSMH). An International SecureMail Host (ISMH) functions as a
central coordinator for this functional hierarchy and maintains the
routing lists and this document of intent and mission.

        Note that at any given time, all positions may not be filled, due
to the fact that positions are filled by those who have the means and
desire to provide the service of each position.


Operational Practices:

        Each SecureMail Host (SMH) has agreed to route E-Mail (referred
to as In-Transit mail) in a manner which provides the highest degree of
privacy technically possible.  Some variances can be expected, as the
technical characteristics of each system differ, however each SecureMail
Host strives to provide the best service possible.

        Specific operational practices include:

        - In-Transit mail shall not be read.  Note that some systems do
not provide the ability to restrict a Sysop from viewing In-Transit mail.
In such cases the Sysop makes every effort to avoid noticing the content
of such E-Mail as they scan thru their message bases.

        - The content of In-Transit mail shall not be disclosed, or given
to anyone but the addressee, except as required for routing thru the
SecureMail System.

        - All SecureMail Hosts agree to route any In-Transit mail they
receive. This includes encrypted and clear-signed traffic now refused by
some systems in FidoNet. In-Transit mail that cannot be delivered shall
be returned to the sender along with a brief explanation of why it could
not be delivered. If no local routing via another SMH is available, the
mail will be sent directly to its destination by the receiving SMH.

        - In-Transit mail shall not be censored.  Routing of In-Transit
mail shall not be refused for any reason even remotely associated to the
content of such E-Mail.  Note: how could it be if it isn't read in the
first place?


Avoidance of Liability:

        Those participating in the SecureMail Routing System do so to
provide a service at no cost to those who choose to make use of it.
There is no guarantee of performance implied nor accepted by the
SecureMail System as an organization, nor by the individuals who
voluntarily participate to provide this service.  Those who choose to
make use of this service should recognize that although we strive to
provide the best service possible, we cannot and will not offer any
guarantees, nor do we accept any obligation for providing any service,
or the performance of any service to a defined standard.

        Those who provide this service specifically deny any liability
for the content of In-Transit E-Mail.  Any liability that may apply
must rest upon the originator.  It is the stated practice of those who
participate to provide this service, that In-Transit E-Mail is not read.
On that basis, those who participate in the SecureMail Routing System
will not have knowledge of the content of In-Transit E-Mail, will not
censor, make judgements as to the legality, morality, nor suitability of
any In-Transit E-Mail to be routed, before during or after having any
contact with it.

        Those who participate in the SecureMail Routing System do so for
the purpose of providing a service to others using the FidoNet E-Mail
System.  It is specifically denied that such service is supplied for the
purpose of promoting, enhancement, implementation, or aiding the
accomplishment of any illegal activity.  No one participating in the
SecureMail Routing System will knowingly allow its use to aid, abet, or
otherwise participate in illegal activities, or make use of the
SecureMail System for any illegal purpose.  Further it is our stated
operational practice that we shall not be engaged in viewing In-Transit
E-Mail for the purposes of knowing whether or not the content of such
could be considered illegal, and specifically deny that we could have any
such knowledge.

        Those engaged in SecureMail Routing are constrained by the ECPA
[Electronic Communication Protection Act] and FidoNet Policy in their
ultimate handling of In-Transit E-Mail in regard to disclosure.

        Anyone who supports the goal of E-Mail privacy and who agrees to
abide by the standards herein proclaimed, may apply to act as a SecureMail
Host Routing System at their own expense and without regard to In-Transit
E-Mail content. A list of current SMH Nodes is contained in the file
SECUREML.MAP which accompanies this document. Applications may be made via
direct Ne