This package uses the GNU toolchain, and uses the typical installation
sequence:

./configure [option]
make
make install

GNU libtool should be installed prior to installing this package.
This is recommended.  Libtool is not required; if not present some substitute
code will be compiled and installed.  This may cause some conflicts if some
other libtool-using package is installed in the future, so libtool should
be installed if possible.

The default options will:

* Install the Socks 5 client libraries in /usr/local/lib,
  called "libsocks.so" and "libsockswrap.so" (actual names vary, depending
  on your system).

* The socksify script in /usr/local/bin

* A lone header file: /usr/local/include/socks.h

* A couple of manual pages in /usr/local/man

* The configuration directory /usr/local/etc/socksrc will be created

The usual options may be used to change these filenames (--prefix,
--exec-prefix, etc...)

If you are not familiar with the GNU toolchain options, run ./configure --help
for a summary.

Use the following procedure to verify that the Socks library was correctly
installed:

* Run 'make check' (this doesn't do much, yet, but every little bit helps)

* Set up your Socks 5 server configuration in /usr/local/etc/socksrc according
to the socksrc man page.

The following test programs will be built in the source code directory, but not
installed:

* Run 'testconnect HOSTNAME', where HOSTNAME is a well-known web server
(www.yahoo.com, www.cnn.com, and the like, are good choices).

testconnect tries to connect to the web server at the given address and
display its robots.txt file.  If all goes well, you should see the robots.txt
from the web server (or a 404 message if the server does not have a
robots.txt file).

* Run 'testbind' as root.  testbind attempts to reserve a privileged port on
the local machine, then open the same port on the Socks server.  If all goes
well 'testbind' will print the local port number, then the Socks server's IP
address and the port number it opened on the Socks server:

port 1023
Real port: 0.0.0.0;1023
Listening on: 192.168.0.15;47683

Not all Socks servers have the ability to reserve the same privileged port
that the Socks client reserved locally.  It's possible that the second message
from 'testbind' will show that its listening on a non-reserved port.

After 'testbind' displays the Socks server's IP address and the port, it
will wait for an incoming connection.  Use 'telnet' to connect to the
indicated IP address and port:

telnet 192.168.0.15 47683

(Note: it is possible that the shown IP address may not be reachable via TCP
from this machine.  This is outside the scope of the test.  The 'telnet'
connection does not have to originate from the same machine that's running
testbind.  Use any appropriate machine to connect to the listening port.)

After the connection goes through, anything typed in telnet should be
printed by testbind (the reverse isn't true, after the connection is
established testbind enters a simple loop where it prints everything received
on the socket, until it is closed).

* If the above tests succeed, chances are that everything is working correctly.
For the final example, pick a well known FTP server, and try to use the
socksify script with the ftp command:

socksify ftp ftp.example.com

You should be able to establish an FTP connection, and log in.  You should be
able to use the 'dir' command in both the active and passive FTP modes,
as well as transfer files.
