dante.conf(5) [debian man page]
DANTE.CONF(5) File Formats Manual DANTE.CONF(5) NAME
dante.conf - socks client configuration file syntax DESCRIPTION
The configuration file for the socks client library allow control over logging and server selection. It is divided into two parts, miscel- laneous settings and routes. A line can be commented using the standard comment character #. FORMAT
The miscellaneous settings have a keyword followed by a colon and the value. debug Setting this field to 1 turns on debugging. logoutput This value controls where the sends logoutput. It can be either syslog, stdout, stderr, a filename, or a combination. resolveprotocol The protocol used to resolve hostnames. Valid values are udp (default), tcp and fake. ROUTES The routes are specified with a route keyword. Inside a pair of parens ({}) a set of keywords control the behavior of the route. Each route can contain three address specifications; from, to and via. A route is selected for a connection based on the values within the route block. The route block can contain the following: ADDRESSES Each address field can consist of a ipaddress (and where meaningful, a netmask, separated from the ipaddress by a '/' sign.), a hostname, or a domainname (designated by the leading '.'). Each address can be followed by a optional port specifier. from The route is used only by requests coming from the address given as value. to The route is used only by requests going to the address given as value. via Address of socks server to be used for the connection. port Parameter to from, to and via. Accepts the keywords eq/=, neq/!=, ge/>=, le/<=, gt/>, lt/< followed by a number. A portrange can also be given as "port <start #> - <end #>", which will match all port numbers within the range <start #> and <end #>. command The server supports the given commands. Valid commands are bind, bindreply, connect, udpassociate and udpreply. and udpreply. Can be used instead of, or to complement, protocol. method List of authentication methods the client supports and which to offer the server. Currently supported values are none and username. protocol The protocols the server supports. Supported values are tcp and udp. proxyprotocol The proxy protocols the server supports. Currently supported values are socks_v4, socks_v5, and http_v1.0. EXAMPLES
See the example directory in the distribution. ENVIRONMENT
SOCKS_USERNAME Use SOCKS_USERNAME as the username when doing username authentication. SOCKS_PASSWORD Use SOCKS_PASSWORD as the password when doing username authentication. Not recommended as other users on the system might be able to see your password. FILES
/etc/dante.conf AUTHORS
For Inferno Nettverk A/S, Norway: Michael Shuldman <michaels@inet.no>: Design and implementation. Karl-Andre' Skevik <karls@inet.no>: Autoconf and porting. SEE ALSO
danted(8) danted.conf(5) Information about new releases and other related issues can be found on the Dante WWW home page at http://www.inet.no/dante. BUGS
See the accompanying BUGS file. New ones should be reported to dante-bugs@inet.no. February 17, 2001 DANTE.CONF(5)
Check Out this Related Man Page
FTP-PROXY(8) BSD System Manager's Manual FTP-PROXY(8) NAME
ftp-proxy -- Internet File Transfer Protocol proxy daemon SYNOPSIS
ftp-proxy [-6Adrv] [-a address] [-b address] [-D level] [-m maxsessions] [-P port] [-p port] [-q queue] [-R address] [-T tag] [-t timeout] DESCRIPTION
ftp-proxy is a proxy for the Internet File Transfer Protocol. FTP control connections should be redirected into the proxy using the pf(4) rdr command, after which the proxy connects to the server on behalf of the client. The proxy allows data connections to pass, rewriting and redirecting them so that the right addresses are used. All connections from the client to the server have their source address rewritten so they appear to come from the proxy. Consequently, all connections from the server to the proxy have their destination address rewritten, so they are redirected to the client. The proxy uses the pf(4) anchor facility for this. Assuming the FTP control connection is from $client to $server, the proxy connected to the server using the $proxy source address, and $port is negotiated, then ftp-proxy adds the following rules to the various anchors. (These example rules use inet, but the proxy also supports inet6.) In case of active mode (PORT or EPRT): rdr from $server to $proxy port $port -> $client pass quick inet proto tcp from $server to $client port $port In case of passive mode (PASV or EPSV): nat from $client to $server port $port -> $proxy pass in quick inet proto tcp from $client to $server port $port pass out quick inet proto tcp from $proxy to $server port $port The options are as follows: -6 IPv6 mode. The proxy will expect and use IPv6 addresses for all communication. Only the extended FTP modes EPSV and EPRT are allowed with IPv6. The proxy is in IPv4 mode by default. -A Only permit anonymous FTP connections. Either user "ftp" or user "anonymous" is allowed. -a address The proxy will use this as the source address for the control connection to a server. -b address Address where the proxy will listen for redirected control connections. The default is 127.0.0.1, or ::1 in IPv6 mode. -D level Debug level, ranging from 0 to 7. Higher is more verbose. The default is 5. (These levels correspond to the syslog(3) levels.) -d Do not daemonize. The process will stay in the foreground, logging to standard error. -m maxsessions Maximum number of concurrent FTP sessions. When the proxy reaches this limit, new connections are denied. The default is 100 ses- sions. The limit can be lowered to a minimum of 1, or raised to a maximum of 500. -P port Fixed server port. Only used in combination with -R. The default is port 21. -p port Port where the proxy will listen for redirected connections. The default is port 8021. -q queue Create rules with queue queue appended, so that data connections can be queued. -R address Fixed server address, also known as reverse mode. The proxy will always connect to the same server, regardless of where the client wanted to connect to (before it was redirected). Use this option to proxy for a server behind NAT, or to forward all connections to another proxy. -r Rewrite sourceport to 20 in active mode to suit ancient clients that insist on this RFC property. -T tag The filter rules will add tag tag to data connections, and not match quick. This way alternative rules that use the tagged keyword can be implemented following the ftp-proxy anchor. These rules can use special pf(4) features like route-to, reply-to, label, rtable, overload, etc. that ftp-proxy does not implement itself. -t timeout Number of seconds that the control connection can be idle, before the proxy will disconnect. The maximum is 86400 seconds, which is also the default. Do not set this too low, because the control connection is usually idle when large data transfers are taking place. -v Set the 'log' flag on pf rules committed by ftp-proxy. Use twice to set the 'log-all' flag. The pf rules do not log by default. CONFIGURATION
To make use of the proxy, pf.conf(5) needs the following rules. All anchors are mandatory. Adjust the rules as needed. In the NAT section: nat-anchor "ftp-proxy/*" rdr-anchor "ftp-proxy/*" rdr pass on $int_if proto tcp from $lan to any port 21 -> 127.0.0.1 port 8021 In the rule section: anchor "ftp-proxy/*" pass out proto tcp from $proxy to any port 21 SEE ALSO
ftp(1), pf(4), pf.conf(5) CAVEATS
pf(4) does not allow the ruleset to be modified if the system is running at a securelevel(7) higher than 1. At that level ftp-proxy cannot add rules to the anchors and FTP data connections may get blocked. Negotiated data connection ports below 1024 are not allowed. The negotiated IP address for active modes is ignored for security reasons. This makes third party file transfers impossible. ftp-proxy chroots to "/var/empty" and changes to user "proxy" to drop privileges. BSD
February 26, 2008 BSD