


For example, this would make the first directory authority (DA)ĭocker run -e ROLE=DA -network tornet antitree/private-torĭocker run -e ROLE=RELAY -network tornet antitree/private-tor Also make sure you create a user defined interface so that it doesn't try to use the default bridge. You can manually build a tor network if you don't want to use docker-compose but you'll need to make sure you pass the correct DA fingerprints to each of the servers.

Easiest way is: docker-compose rmĭocker volume rm privatetornetwork_torvol If you are running multiple instances or are rebuilding it, make sure you delete this named volume or you'll accidentally use a previous iteration's keys. Storage & Tor Network ConfigurationĪll of the required information that other nodes need to know about on the network are stored in a named volume torvol which you can find the path for doing docker volume inspect privatetornetwork_torvol or use docker volume ls to find its name on your system. If this needs to be said, this should never be used as a replacement for tor. Traffic analysis: Test out the latest tor exploit and pretend to be a nation state adversary. Tor development: in the case you're working on a patch that is more complex and requires seeing what happens on the tor network, you can apply the patches to the containers. Originally this project was part of a class I wrote to teach about how tor works. Tor research: learn how tor interacts with nodes, make modifications to settings and see what happens, understand how the Tor Network operates without affecting real people. If you're going "Why do I want this?" here's a few examples: This will create 3 directory authorities (DA's), 1 client listning on port 9050, 5 relays, and 3 exits. The easiest way to get a tor network up and running is to use the docker-compose create and then scale function docker-compose up Private Tor Network on Docker An isolated, private tor network running entirely in Docker containers Quickstart
