Gerard:
> Is there any way I can access the SOCKS firewall directly from DOS or
> Windows without having to go through the SUN and a UNIX environment?
Another approach is to use application level proxies, which
spoof a protocol enough that you can (almost always) use the standard
client applications without modification. This approach doesn't conflict
with using SOCKS -- it's just a different design philosophy. For example,
from my PC running Sun's PC-NFS (with no modifications) I do the following:
C:\TMP> FTP RELAY
Connected to relay.tis.com.
220 relay FTP server (Version 5.60mjr) ready.
Name (relay:mjr): anonymous @
research .
att .
com
331-(----GATEWAY CONNECTED TO research.att.com----)
331-(220 inet FTP server (Version 4.271 Fri Apr 9 10:11:04 EDT 1993) ready.)
331 Guest login ok, send ident as password.
Password:
230 Guest login ok, access restrictions apply.
Remote system type is UNIX.
Using binary mode to transfer files.
ftp>
What SOCKS gives you is the automatic re-routing of the call
(to use X.25ish terms) so the firewall connects to where you really
want to connect. Simple proxies like the FTP proxy I just demonstrated
force the user to manually re-route the call. You notice that instead
of trying to log into the FTP server on RELAY as a user, I told it:
anonymous @
research .
att .
com
and it "understood" the address and rerouted the call.
A set of proxies for FTP, rlogin, and telnet, are available as
part of the TIS firewall toolkit. (FTP from ftp.tis.com, in
pub/firewalls/toolkit)
mjr.
|
|
