Blue Tornet

How do I use the project?

To use the project, you need to be on a Linux machine. Once you’re on a machine or a VM, download the Docker container in the terminal:

docker pull netaru3/blue_tornet

To start the project, type:

docker run -p YOUR_PORT:16379 netaru3/blue_tornet

Now you just need to route your traffic through the proxy on the port you specified.

If you want all your web traffic to go through the proxy, just go to Settings, then Network Settings, click on Manual proxy configuration, click on Socks Host, enter 127.0.0.1 in the first row, and the port you set in Docker in the second row

What's the difference between this and using the Tor Browser? Both isolate circuits so that traffic is split across different nodes

There are two differences:

1: Circuit isolation is not based on SOCKS credentials, but on instances (it consumes more resources, but is less prone to failure)

2: While with Tor Browser you’re tied to a browser, with Blue Tornet you’re not tied to any specific application—any application that supports a SOCKS proxy can use Blue Tornet.

So can I use Blue Tornet for non-web applications as well?

Theoretically, yes—as I said, any application that supports a SOCKS proxy can use Blue Tornet, whether the traffic is web-based or not. But to be honest, I haven’t tested compatibility with applications other than Firefox or with non-web traffic.

So it comes down to, “It’s theoretically possible, but if you try it, you’ll probably run into bugs because it hasn’t been tested.” This is a demo; in future updates, I’ll test everything.

Inspiration

Blue Tornet was born from the question: How can I become untraceable?

I would like to live in a world where journalists and activists can continue their struggle without repercussions, and the way to create that world is through anonymity.

What it does

It helps increase your anonymity

Imagine you visit multiple websites using a VPN. Even though you don’t reveal your real IP address, you use the same IP address to access those sites, and an outside party could trace your activity just by using that IP address. Blue Tornet prevents this.

If you visit “Site A,” then “Site B,” and then “Site C,” the IP address you’ll have on Site A will be completely different from the one you’ll have on Site B and the one you’ll have on Site C. This is achieved by using 5 instances of TOR.

That’s basically like having 5 VPNs instead of just one.

How I built it

Using the Tor network, Docker, and HAProxy, you use Tor for the IP addresses, Docker to make it work on any machine, and HAProxy to balance traffic across requests, so that all requests are distributed evenly among the 5 Tor instances (which refreshes the circuits every 15 seconds).

If you want to take a closer look at the code, visit my GitHub repository: https://github.com/netaru3/herramientas-de-hacking/tree/main/privacity/blue_tornet

What's next for Blue Tornet

After Blue Tornet, I plan to develop version 2.0, which will rotate not only the IP address but also the fingerprint. To achieve this, I'm working on a networking system that connects multiple devices, so that traffic is split across several physical devices (or VMs) to change the resulting fingerprint.

Built With

• docker
• javascript