Description • Introduction • How To Use • Parameters • Requirements • Docker • Other • License • Wiki

It provides one single endpoint for clients. Supports HAProxy, socks protocol and http-proxy servers: polipo, privoxy and hpts.

In addition, you can view previously running TOR processes and create a new identity for all or selected processes.

The multitor has been completely rewritten on the basis of:

• Multi-TOR project written by Jan Seidl: Multi-TOR
• original source is (Sebastian Wain project): Distributed Scraping With Multiple TOR Circuits

multitor was created with the aim of initialize many TOR processes as quickly as possible. I could use many instances for my daily use programs (web browsers, messangers and other). In addition, I was looking for a tool that would increase anonymity when conducting penetration tests and testing the security of infrastructure.

Before using the multitor you need to remember:

• TOR does attempt to generate a bunch of streams for you already. From this perspective, it is already load balancing (and it's much smarter at it than HAproxy)
• the main goal is masking from where we get by sending requests to multiple streams. It is not so easy to locate where an attacker comes from. If you used http/https servers e.g. proxy servers, you will know what is going on but...
• using multiple TOR instances can increase the probability of using a compromised circuit
• multitor getting some bandwidth improvements just because it's a different way of connecting to TOR network
• in multitor configuration mostly HAProxy checks the local (syn, syn/ack) socket - not all TOR nodes (also exist nodes). If there is a problem with the socket it tries to send traffic to others available without touching what's next - it does not ensure that the data will arrive
• TOR network is a separate organism on which the multitor has no effect If one of the nodes is damaged and somehow the data can not leave the exit node, it is likely that a connection error will be returned or, at best, the data will be transferred through another local socket
• HAProxy load balance network traffic between local TOR or http-proxy processes - not nodes inside TOR network

TOR is a fine security project and an excellent component in a strategy of defence in depth but it isn’t (sadly) a cloak of invisibility. When using the TOR, always remember about ssl (e.g. https) wherever it is possible.

Look also at Limitations.

❗ For a more detailed understanding of multitor, its parameters, functions and how it all works, see the Manual.

It's simple:

# Clone this repository
git clone https://github.com/trimstray/multitor

# Go into the repository
cd multitor

# Install
./setup.sh install

# Run the app
multitor --init 2 --user debian-tor --socks-port 9000 --control-port 9900 --proxy privoxy --haproxy

• symlink to bin/multitor is placed in /usr/local/bin
• man page is placed in /usr/local/man/man8

Provides the following options:

  Usage:
    multitor <option|long-option>

  Examples:
    multitor --init 2 --user debian-tor --socks-port 9000 --control-port 9900
    multitor --init 10 --user debian-tor --socks-port 9000 --control-port 9900 --proxy socks
    multitor --show-id --socks-port 9000

  Options:
        --help                        show this message
        --debug                       displays information on the screen (debug mode)
        --verbose                     displays more information about TOR processes
    -i, --init <num>                  init new tor processes
    -k, --kill                        kill all multitor processes
    -s, --show-id                     show specific tor process id
    -n, --new-id                      regenerate tor circuit
    -u, --user <string>               set the user (only with -i|--init)
        --socks-port <port_num|all>   set socks port number
        --control-port <port_num>     set control port number
        --proxy <proxy_type>          set socks or http (polipo, privoxy, hpts) proxy server
        --haproxy                     set HAProxy as a frontend for http proxies (only with --proxy)

multitor uses external utilities to be installed before running:

• tor
• netcat
• haproxy
• polipo
• privoxy
• http-proxy-to-socks

This tool working with:

• GNU/Linux (testing on Debian and CentOS)
• Bash (testing on 4.4.19)

Also you will need root access.

This project includes a Dockerfile and docker-compose.yml for easy setup and deployment.

• Docker: Install Docker
• Docker Compose: Install Docker Compose (usually included with Docker Desktop)

You can build the Docker image directly using the docker build command:

docker build -t multitor .

The easiest way to run multitor with Docker is by using Docker Compose. This method utilizes the docker-compose.yml file which is pre-configured for common use cases.

1. Start multitor:

   docker-compose up

   By default, this will start multitor with 5 Tor instances and expose HAProxy on port 16379 of your host machine.

2. Customize Tor Instances: You can change the number of Tor instances by setting the TOR_INSTANCES environment variable. You can do this by:

   • Creating a .env file in the same directory as docker-compose.yml with the line:

     TOR_INSTANCES=10
     

   • Or by prefixing the command:

     TOR_INSTANCES=10 docker-compose up

3. Using Custom Templates: If you need to use custom configuration templates for Tor, HAProxy, Privoxy, or Polipo:

   • Create a directory named custom_templates in the root of the project (same directory as docker-compose.yml).
   • Place your custom template files in this directory (e.g., custom_templates/torrc-template.cfg).
   • Docker Compose is configured to mount this directory into the container at /usr/src/app/templates. multitor will then use any templates it finds there, falling back to its default templates if a custom one isn't provided.

   The default template files that can be overridden are:

   • haproxy-template.cfg
   • polipo-template.cfg
   • privoxy-template.cfg
   • torrc-template.cfg

4. Accessing the Proxy: Once running, the HAProxy load balancer will be accessible at http://localhost:16379 (or whatever host your Docker daemon is running on).

5. Stopping multitor:

   docker-compose down

If you prefer not to use Docker Compose, you can run the container directly using docker run.

1. Build the image first (if you haven't already):

   docker build -t multitor .

2. Run the container:

   docker run -d -p 16379:16379 --name multitor_container -e TOR_INSTANCES=5 multitor

   • -d: Run in detached mode.
   • -p 16379:16379: Map port 16379.
   • --name multitor_container: Assign a name to the container.
   • -e TOR_INSTANCES=5: Set the number of Tor instances.
   • To use custom templates, you would need to add a volume mount:

     docker run -d -p 16379:16379 --name multitor_container \
       -e TOR_INSTANCES=5 \
       -v "$(pwd)/custom_templates:/usr/src/app/templates" \
       multitor

     Ensure the custom_templates directory exists locally.

3. Viewing Logs:

   docker logs -f multitor_container

4. Stopping and Removing the Container:

   docker stop multitor_container
   docker rm multitor_container

If you use this tool in other scripts where the output is saved everywhere, not on the screen, remember that you will not be able to use the generated password. I will correct this in the next version. If you do not use regenerate function of single or all TOR circuits with a password, you can safely restart the multitor which will do it for you.

• each TOR, http-proxy and HAProxy processes needs a certain number of memory. If the number of TOR processes is too big, the oldest one will be automatically killed by the system
• Polipo is no longer supported but it is still a very good and light proxy. In my opinion the best http-proxy solution is Privoxy
• I think this topic will be usefull for You before using multitor - How to run multiple Tor processes at once with different exit IPs?

See this.

See this.

GPLv3 : http://www.gnu.org/licenses/

Free software, Yeah!