Hensa is now using the Netscape server. Hensa's current information page
Lagoon is a CGI/1.0 script: an add-on program for Unix systems, to be used with a HTTP server. To install Lagoon, you need to use server software such as CERN httpd, NCSA httpd, Apache, or other servers. (With the CERN HTTP server, which has a built-in cache, Lagoon is superfluous except in some rare occasions.)
The latest version of Lagoon has been tested under Unix (SunOS 4, Solaris 2, Esix) on several types of machines, with NCSA httpd (from which the code was originally taken), with Apache, CERN httpd, GN, and some other server software. Lagoon is also known to run on Ultrix, AIX, and other platforms.
Lagoon can be obtained from our ftp directory.
There is no online hypertext documentation for installing Lagoon. The distribution includes detailed instructions in README files, and annotated example configuration files serve to explain the options.
You can choose to use gdbm for managing the cache. gdbm is GNUware and is quite easy to install. (It can be found in many places, for example, with us.) Edit src/Makefile to tell compilation where gdbm can be found, or to tell it not to use gdbm.
To better contrast the two, lets take the example of World Wide Web and Telnet access. With Socks, you set up one configuration file and one daemon. Through this file and daemon, both Telnet and WWW are enabled, as well as any other service that you have not disabled.
With the TIS toolkit, you set up one daemon for each WWW and Telnet, as well as configuration files for each. After you have done this, other Internet access is still prohibited until explicitly set up. If a daemon for a specific utility has not been provided (like talk), there is a "plug-in" daemon, but it is neither as flexible, nor as easy to set up, as the other tools.
This might seem a minor difference, but it makes a major difference. Socks allows you to be sloppy. With a poorly set up Socks server, someone from the inside could gain more access to the Internet than was originally intended. With the TIS toolkit, the people on the inside have only the access the system administrator wants them to have.
Socks is easier to set up, easier to compile and allows for greater flexibility. The TIS toolkit is more secure if you want to regulate the users inside the protected network. Both provide absolute protection from the outside.
Sept. 17, 1996 - ab934