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.
Bill
Follow-Ups:
|
|
