SOCKS client version of ftp
rftp [-AadFginptVv] [-P port] [-r wait] [-T dir,max[,inc]] [[user@]host [port]] [user@]host:[path][/] [file:///path] [rftp://[user[:password]@]host[:port]/path[/]] rftp -u url file [...]
If autologin is enabled, rftp checks the .netrc file in your home directory for an entry describing an account on the remote machine. Please see the ftp utility page for a description of .netrc file.
If no entry exists, rftp prompts for the login name of the remote machine (default is the user ID on the local machine) and, if necessary, for a password and an account.
The rftp and rtelnet utilities provide the well-known functionalities to hosts within a firewall. Normally, when a firewall is constructed, IP-accessibility across the firewall is cut off to reduce security risk to hosts within the firewall. As a result, inside hosts can no longer use many of the well-known tools directly to access the resources outside the firewall.
|For further information on all rftp functionalities, please refer to ftp documentation.|
These utilities restore the convenience of the well-known tools while maintaining the security requirement. Though the utilities differ very much from their counterparts in the use of the communication scheme, they should behave almost indistinguishably to the users.
|Your password is echoed as you type it in if you're using anonymous as a login name.|
These are "versatile" clients -- they can be used for connections to inside hosts directly and to outside hosts via SOCKS proxy servers. So they can be used as replacements of their traditional counterparts.
When rftp starts, it prints to stderr its version number and the name or IP address of its default SOCKS proxy server. It then consults the configuration file (/etc/socks.conf) to determine whether a request should be allowed or denied based on the requesting user, the destination host, and the requested service.
For allowable requests, the configuration file also dictates whether direct or proxy connection should be used to the given destination, and optionally the actual SOCKS servers to use for the proxy connection. See /etc/socks.conf.
You can use the environment variable SOCKS_NS to set the nameserver for domain name resolutions. Be sure you use the IP address of the nameserver you want to use, not its domain name. If SOCKS_NS doesn't exist, the IP address defined by the symbol SOCKS_DEFAULT_NS at compile time is used if the programs were compiled with that symbol defined. Otherwise, the nameservers specified in /etc/resolv.conf are used.
All the client processes log their activities using syslog() with facility daemon and level notice. In order to capture the log messages, you need to have syslogd running.
ftp, rtelnet, syslogd
syslog() in the Library Reference