![]() ![]() If you’re not into this, there is always Shadow and Chutney or just manually configuring hosts/processes your self. To answer the “now what?” question, this is a clean way of getting a tor network running so you can do your research, learn about how it works, modify configurations, run some third party tor software… whatever. Or, if you want to get cool information, try setting up a depictor container that will give you data about the DA’s. If you aren’t sure if it’s working, you check out the logs If you point your browser to the Docker host running your containers and, in the same way you would connect to Tor, use it as a SOCKS5 proxy server, you will suddenly use it. To use this, there is a port listening on 9050 (you can change this in the docker-compose.yml file). That’s 15 exits, 5 relays, 1 client, and 3 dir authorities. But the current RC is too sketchy to invest any time in.Īnyways, here’s how to spin up 24 node network. Eventually, when in the next version of Docker you’ll be able to scale across multiple hosting providers. Executing this command, for example. It comes with a few examples to get you started. It does so by using configuration templates of directory authorities, bridges, relays, clients, and a variety of combinations in between. ![]() What’s nice about this is you can use the docker-compose scale command to build any size network that you want. Chutney is a tool designed to let you build your own private Tor network instance in minutes. Why give any back story, if it’s useful to you, then here you go:Īll you really need to do is clone the git repo, build the image (or download from Docker Hub) and then spin up a network to your liking. I’ve made a scalable way of building a fully private functioning tor network using Docker. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |