SOCKD.CONF(5)

NAME
sockd.conf - socks server configuration file syntax

DESCRIPTION
The configuration file for sockd controls the both access control for the server and logging. It is divided into two parts, serversettings and rules. A line can be commented using the standard comment character #.

SERVERSETTINGS
The serversettings control the generic behaviour of the server. Each keyword is separated from it's value by a ':' character.

logouput
    This value controls where the server sends logoutput. It can be either syslog, stdout, stderr, a filename, or a combination.

internal
    The internal address. Connections will only be accepted on this address. Multiple internal lines may be given.

external
    The address to be used for outgoing connections.

method
    A list of acceptable authentication methods, in order of preference. Supported values are username and none.

user.privileged
    Username which will be used for doing privileged operations.

user.notprivileged
    User which the server runs as most of the time.

user.libwrap
    User used to execute libwrap commands.

compatibility
    With the sameport keyword, the server attempts to use the same port on the server and the client. This functionality is the default, but when this option is given it will also be done with ports below 1024. The reuseaddr keyword might solve problems when the bind extension is used.

srchost
    With the nomismatch keyword, the server will not accept connects from addresses having a mismatch between dns address and hostname. Default is to accept them. With the nounknown keyword, the server will not accept connects from addresses without a dns record. Default is to accept them.

connecttimeout
    The number of seconds a client has to send the request after a connect. Set it to 0 for forever.

iotimeout
    The number of seconds an established connection can be idle. Set it to 0 for forever.

RULES
There are two sets of rules. Rules prefixed with client are checked to see if the client is allowed to connect. These should not use hostnames (on ip addresses), for security and performance reasons. The other rules are checked after the request has been accepted. In the client context to means the address the request is accepted on, otherwise it means the client's destination address. The rules specify a from/to ipmask pair and a pass or deny keyword which determines if connections matching the netmask are allowed or not. In addition to the netmask there are a set of extra keywords which can be given. The format of each rules contents is:

protocol
    The rule applies only to the given protocols. Valid values are tcp and udp.

from
    The rule applies only to requests coming from the address given as value.

to  The rule applies only to requests going to the address given as value.

command
    The rule applies only to the given commands. Valid commands are bind, bindreply, connect, udpassociate. Can be used instead, or to complement, protocol.

libwrap
    The server will pass the line to libwrap for execution.

log Used to control logging. Accepted keywords are connect, disconnect, data and iooperation.

method
    Require that the connection be established using one of the given methods. Valid values are the same as in the global method line.

proxyprotocol
    The rule applies only to requests using the given proxyprotocol. Valid proxyprotocols are socks_v4 and socks_v5.

EXAMPLES
See the example directory in the distribution.

FILES
/etc/sockd.conf

AUTHORS
For Inferno Nettverk A/S, Norway:
 Michael Shuldman <michaels@inet.no>: Design and implementation.
 Karl-André Skevik <karls@inet.no>: Autoconf and porting.

SEE ALSO
sockd(8), hosts_access(5)