                       SECURITY FILTER
                 Vers. 01-ab / March 1998
             Copyright (C) 1996, 1997, 1998 SW Wings

DESCRIPTION

The SECURITY FILTER is a system designed to restrict and control the
access to Web pages. The SECURITY FILTER access control is not based on
USERID/PASSWORD information but on internet addresses (i.e. only
requests coming from a predefined set of hosts/domains are allowed to
access the restricted pages). This way it is possible to set-up a
protected, private Web (only usable by a predefined set of
people/organization) on top of the public one. Being a CGI, the SECURITY
FILTER dows not require privileged access (as root) to the Web Server.
So people connecting to the Web via an Internet Provider and not
controlling the Web server can still protect their pages. 


INSTALLATION


1. Decompress the SECURITY FILTER Distribution Files

The Security Filter distribution contains the following files:

        htm_w32.zip - Security Filter HTML documentation 
        sf_w32.zip  - Security Filter executable file 
        uti_w32.zip - Utilities to register the Security Filter
        readme.txt  - this file

Supposing that the files set has been downloaded in the directory

c:\tmp

these are the commands that have to be executed:

c:                              (the actual target disk must be put
                                 here, so instead of c: we could
                                 have d:, e: and so on)
cd \                            (to go to the root)
pkunzip -d c:\tmp\htm_w32.zip   (to decompress the HTML files)
pkunzip -d c:\tmp\sf_w32.zip    (to decompress the Security
                                 Filter files)
pkunzip -d c:\tmp\uti_w32.zip   (to decompress the registration
                                 utilities)

When using a Windows version on "pkunzip" care must be taken so that the
ordinal directories/files names are kept. 


2. Setting the WWW Server

The World Wide Web Server has to be set up in such a way that the
Security Filter can be properly accessed. In other words it is necessary
to copy the Security Filter in the server "cgi-bin" directory or make
sure the directory where the Security Filter is located can be seen by
the server via an "alias". Supposing that the server is similar to the
NCSA one, hereafter are listed the required changes. 

2.1 "access.conf"

In the file "access.conf" an entry similar to the following has to be inserted. This
change will make the SWWINGS directory visible to the WWW Server.

<Directory C:/SWWINGS/>
</Directory>

2.2 "srm.conf"

In the file "srm.conf", and namely in the "alias" section, an entry similar to the
following has to be inserted. This change will allow the Security Filter to be seen
by the server.

ScriptAlias /cgi-bin/ C:/SWWINGS/BIN/

3. Preparing for the first run

After all the steps described above have been performed, it will be
necessary to define the start-up file secfil.ini as described in the
documentation HTML pages. When all the necessary files have been created
(or updated), it will possible to use the Security Filter. 

NOTE

It is recommended to put the Security Filter, as well as the
registration utilities, in a different directory than the original ones.
The batch files "go.bat" in SECFIL and UTILS directories will put these
executable files in the directory /SWWINGS/BIN. It is also recommended
to add this directory to the environment variable PATH; this way the
Security Filter and the registration utilities will be directly
available. 

REGISTRATION

The Security Filter is shareware (and not freeware). If you find the
Security Filter valuable you should register it. To register check out
the relevant HTML pages in the distributed documentation. 


COPYRIGHT AND DISCLAIM

1. Copyright

Copyright (c) 1996 SW Wings.

Permission to copy, distribute and use the unregistered version of the
Security Filter and its documentation is hereby granted without fee,
provided that the above copyright notice and this permission notice
appear in all copies of this software and related documentation. 


2. Disclaim

The Security Filter is provided "as-is" and without warranty of any
kind, express, implied or otherwise, including without limitation, any
warranty of merchantability or fitness for a particular purpose. 

In no event shall SW Wings be liable for any special, incidental,
indirect or consequential damages of any kind, or any damages whatsoever
resulting from loss of use, data or profits, whether or not advised of
the possibility of damage, and on any theory of liability, arising out
or in connection with the use or performance of this software. 


PROBLEMS AND FEEDBACKS

Installation/usage problems, feedbacks and so on can be reported to
SW WINGS. 

Alessandra Scarpari
SW WINGS
Van der Weijdenlaan 26
2211 JM Noordwijkerhout
The Netherlands
swwings@swwings.com
