SOCKS5 Shared Library Configuration

In order to control the execution of the SOCKS5 library and the operation of the SOCKS-ified clients, you must first create a configuration file, typically named /etc/ libsocks5.conf. The contents of this file are analogous to the proxy-type directives in /etc/socks5.conf, discussed earlier in this chapter. The primary purpose of this file is to define which target hosts should be reached via the proxy and which target hosts should be addressed directly. Consider the following lines from a libsocks5.conf file:

socks5 - - - - 192.168.32.1 noproxy - - 192.168.32. -

This example specifies that clients use SOCKS5 proxying to server 192.168.32.1 in all instances, except when the destination falls within the 192.168.32.0 network (the local LAN), in which case a direct connection should be established.

In addition to the configuration that controls the shared library itself, there are a number of environment variables that can be set by each user in order to tailor the execution of the library to their environment. Table 10.9 includes the most commonly used of these environment variables.

PART 4

SOCKS5_ENCRYPT N/A N/A Specifies to use encryption when GSS-API is in use.

So far, this chapter has described the SOCKS5 server and the ability to configure Linux clients to connect to the server. However, most Linux servers are also expected to provide services to other platforms. The following section explains how Windows clients can take advantage of a Linux-based proxy firewall.

Continue reading here: Configuring Windows SOCKS5 Clients

Was this article helpful?