We have an experimental gopher service in our firewalled environment up
and running. It consists of a Gopher proxy server running on an Internet
relay host and a curses gopher client with minimal changes.
As required by the fundamental design of Gopher, the Gopher proxy server
is completely stateless: it is launched by inetd for each Gopher object to
be dealt with, connects to the ultimate Gopher server, copies the retrieved
information back to the client and then ends.
The following Gopher object types are currently supported:
- File, document
- Wide Area Information Service (WAIS) indexed document
- Telnet (via itelnet)
The following Gopher object types are not yet supported:
- CSO nameserver query
- Tn3270 access
We did the development in Version 1.03 of the UNIX Gopher distribution.
As time permits, we will incorporate similar changes into the X Gopher
client (Version 1.2).
If there is enough interest, we may, after implementing the remaining
object types in the proxy server, think about getting in touch with the
Gopher developers and have them incorporate the changes and additions to
an upcoming release.
Please send me a short message if you are interested. Please don't send
the message to the firewalls mailing list, send it to hn @
Heinz Naef, hn @