On Mon, 18 Dec 1995, Bill Husler wrote:
> Is it fair to say that I aggree with both you and ANS? ANS is
> authenticating HTTP, TELNET and FTP because these are inherently
> authenticating protocols. Gopher is not. In the rulebase you set up on
> your firewall, you define two items 1 is the direction for a connection
> (in, out, both) and the other is anthentication (which is only valid for
> authenticating protocols). Actually, I believe that what is really
> happening is that you can specify authenication for any protocol that ANS
> wrote a specific Application Proxie to handle and that the wrote them for
> FTP, TELNET and HTTP. Everything else is probably a generic proxie that
> does not support authentication. Since the Client code for Gopher does
> not have a mechanizm for authenticating the user, this would present a
> particular challenge - perhaps you would in essence be running a
> "special" authenticating Gopher.
Sounds interesting, but somehow incorrect.
HTTP also handles gopher URLs, so one would figger the service would be
proxied somehow. I don't recall reading anywhere that gopher was
"Cutting the space budget really restores my faith in humanity. It
eliminates dreams, goals, and ideals and lets us get straight to the
business of hate, debauchery, and self-annihilation." -- Johnny Hart
***testing, only testing, and damn good at it too!***
OK, so you're a Ph.D. Just don't touch anything.