Re: [tor-dev] Docker images for help people to run Tor (teor) (teor)
Hi, thanks for your support! I've modified Dockerfiles to properly install the right Tor version and starting two relays with both scripts. The images have been released on Docker Hub too. Next step for me is preparing script and image for easily setting up a bridge. Since all containers created are Linux containers, and since all my Dockerfiles are "one shot configurations", I will release bash scripts soon. I will contact the community very soon for more advices on relays, and promote-review the project (since the project is newborn, I want to spread for find issues and fix them). If you want to control all the released code and images, the two principal repositories are: https://github.com/randomtable/ChimeraOS https://hub.docker.com/u/alessandrofiori Many thanks Il giorno lun 1 apr 2019 alle ore 14:00 < tor-dev-requ...@lists.torproject.org> ha scritto: > Send tor-dev mailing list submissions to > tor-dev@lists.torproject.org > > To subscribe or unsubscribe via the World Wide Web, visit > https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-dev > or, via email, send a message with subject or body 'help' to > tor-dev-requ...@lists.torproject.org > > You can reach the person managing the list at > tor-dev-ow...@lists.torproject.org > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of tor-dev digest..." > > > Today's Topics: > >1. Re: Docker images for help people to run Tor (teor) (teor) >2. Next Network Team Meeting Time (teor) > > > -- > > Message: 1 > Date: Mon, 1 Apr 2019 12:57:35 +1000 > From: teor > To: tor-dev@lists.torproject.org > Subject: Re: [tor-dev] Docker images for help people to run Tor (teor) > Message-ID: > Content-Type: text/plain; charset="utf-8" > > Hi, > > > On 1 Apr 2019, at 07:55, Alessandro Fiori wrote: > > > > Hi, > > I would like to share with the community some tests I've made for > setting up a "swarm" of Tor relays. > > > > I setted up 3 exit relays and 3 middle relays on the same IPv4 address, > to make some testing, and the entire swarm works like a charm. > > > > Due to Tor limitation, I have decided to build a template for preparing > the cluster, and upload it to GitHub. > > > > You can find the example mini-cluster here: > > https://github.com/randomtable/ChimeraOS/tree/master/TorSwarm > > > > I have tested the exit capabilities on another network with different > public IP address. > > > > All the relays have published their own descriptors, I have prepared the > containers as a single, separated machines. > > > > The process is different from preparing a single relay, because of > Docker build process. > > > > I have disabled caching during the cluster process, so i have been able > to modify torrc without issues. > > > > Because its very interesting, attached to this e-mail there is the > console Logs from the 6 relays. > > > > All containers are read-only, so the entire relay will destroy at the > end of session. > > > > I hope this can be useful. > > Tor clients will only see 2 of your 6 relays, because the Tor directory > authorities only publish 2 relays per IPv4 address. > > Also, please use the deb.torproject.org repositories to get the latest > version of tor: > Mar 31 19:57:08.000 [warn] Please upgrade! This version of Tor (0.3.3.9) > is not recommended, according to the directory authorities. Recommended > versions are: > 0.2.9.15,0.2.9.16,0.2.9.17,0.3.4.10,0.3.4.11,0.3.5.7,0.3.5.8,0.4.0.1-alpha,0.4.0.2-alpha,0.4.0.3-alpha > > https://trac.torproject.org/projects/tor/wiki/TorRelayGuide/DebianUbuntu > > T > -- next part -- > An HTML attachment was scrubbed... > URL: < > http://lists.torproject.org/pipermail/tor-dev/attachments/20190401/f30ddefa/attachment-0001.html > > > > -- > > Message: 2 > Date: Mon, 1 Apr 2019 14:45:42 +1000 > From: teor > To: tor-dev@lists.torproject.org > Subject: [tor-dev] Next Network Team Meeting Time > Message-ID: <68735aed-467b-40ef-b8e2-98417723f...@riseup.net> > Content-Type: text/plain; charset="utf-8" > > Hi, > > The next network team meeting is at 2300 UTC on Tuesday 2 April. > > Here is our full April schedule: > * Tuesday 2 April at 2300 UTC > * Monday 8 April at 1700 UTC > * Monday 15 April at 1700 UTC > * Tuesday 23 April at 1700 UTC (Monday 22 April is the Easter Monday > public holiday) > * Monday 29 April at 1700 UTC &g
Re: [tor-dev] Docker images for help people to run Tor (teor)
Hi, > On 1 Apr 2019, at 07:55, Alessandro Fiori wrote: > > Hi, > I would like to share with the community some tests I've made for setting up > a "swarm" of Tor relays. > > I setted up 3 exit relays and 3 middle relays on the same IPv4 address, to > make some testing, and the entire swarm works like a charm. > > Due to Tor limitation, I have decided to build a template for preparing the > cluster, and upload it to GitHub. > > You can find the example mini-cluster here: > https://github.com/randomtable/ChimeraOS/tree/master/TorSwarm > > I have tested the exit capabilities on another network with different public > IP address. > > All the relays have published their own descriptors, I have prepared the > containers as a single, separated machines. > > The process is different from preparing a single relay, because of Docker > build process. > > I have disabled caching during the cluster process, so i have been able to > modify torrc without issues. > > Because its very interesting, attached to this e-mail there is the console > Logs from the 6 relays. > > All containers are read-only, so the entire relay will destroy at the end of > session. > > I hope this can be useful. Tor clients will only see 2 of your 6 relays, because the Tor directory authorities only publish 2 relays per IPv4 address. Also, please use the deb.torproject.org repositories to get the latest version of tor: Mar 31 19:57:08.000 [warn] Please upgrade! This version of Tor (0.3.3.9) is not recommended, according to the directory authorities. Recommended versions are: 0.2.9.15,0.2.9.16,0.2.9.17,0.3.4.10,0.3.4.11,0.3.5.7,0.3.5.8,0.4.0.1-alpha,0.4.0.2-alpha,0.4.0.3-alpha https://trac.torproject.org/projects/tor/wiki/TorRelayGuide/DebianUbuntu T___ tor-dev mailing list tor-dev@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-dev
Re: [tor-dev] Docker images for help people to run Tor (teor)
Hi, I would like to share with the community some tests I've made for setting up a "swarm" of Tor relays. I setted up 3 exit relays and 3 middle relays on the same IPv4 address, to make some testing, and the entire swarm works like a charm. Due to Tor limitation, I have decided to build a template for preparing the cluster, and upload it to GitHub. You can find the example mini-cluster here: https://github.com/randomtable/ChimeraOS/tree/master/TorSwarm I have tested the exit capabilities on another network with different public IP address. All the relays have published their own descriptors, I have prepared the containers as a single, separated machines. The process is different from preparing a single relay, because of Docker build process. I have disabled caching during the cluster process, so i have been able to modify torrc without issues. Because its very interesting, attached to this e-mail there is the console Logs from the 6 relays. All containers are read-only, so the entire relay will destroy at the end of session. I hope this can be useful. Alessandro Fiori Il giorno sab 30 mar 2019 alle ore 13:00 < tor-dev-requ...@lists.torproject.org> ha scritto: > Send tor-dev mailing list submissions to > tor-dev@lists.torproject.org > > To subscribe or unsubscribe via the World Wide Web, visit > https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-dev > or, via email, send a message with subject or body 'help' to > tor-dev-requ...@lists.torproject.org > > You can reach the person managing the list at > tor-dev-ow...@lists.torproject.org > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of tor-dev digest..." > > > Today's Topics: > >1. Re: Docker images for help people to run Tor (teor) > > > -- > > Message: 1 > Date: Sat, 30 Mar 2019 13:08:53 +1000 > From: teor > To: tor-dev@lists.torproject.org > Subject: Re: [tor-dev] Docker images for help people to run Tor > Message-ID: <3d4905af-1c10-47bf-8823-eb3228ff9...@riseup.net> > Content-Type: text/plain; charset="utf-8" > > Hi, > > (Please try to reply to the thread, not the digest!) > > > On 30 Mar 2019, at 11:51, Alessandro Fiori wrote: > > > > Because the images are built separately, and Containers doesn't have > persistent data by default, i'm testing the launch of a "relay swarm", > which isn't the "Docker Swarm". > > The concept of a "Relay swarm" is to have multiple running relay > containers on the same user machine, without any conflict. > > > > The idea (i will testing it very soon) is possible, by pulling an image > and running it multiple times, creating intermetiate containers. > > > > A function like the "relay swarm" can be very useful, i don't know if > this approach can be risky, so i'm preparing a script for launching only > one type of relay swarm (middle or exit relays). > > > > If there is no security concerns, this function will be a very key > function for grow up the Network, because a user can run multiple relays at > a time. > > Tor only allows 2 relays per IPv4 address. > > T > -- next part -- > A non-text attachment was scrubbed... > Name: signature.asc > Type: application/pgp-signature > Size: 833 bytes > Desc: Message signed with OpenPGP > URL: < > http://lists.torproject.org/pipermail/tor-dev/attachments/20190330/666cdc2c/attachment-0001.sig > > > > -- > > Subject: Digest Footer > > ___ > tor-dev mailing list > tor-dev@lists.torproject.org > https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-dev > > > -- > > End of tor-dev Digest, Vol 98, Issue 20 > *** > C:\Users\Alessandro Fiori\Desktop\TorSwarm>DEL /F /Q /A "C:\Users\Alessandro Fiori\Desktop\TorSwarm\image.txt" Impossibile trovare C:\Users\Alessandro Fiori\Desktop\TorSwarm\image.txt C:\Users\Alessandro Fiori\Desktop\TorSwarm>DEL /F /Q /A "C:\Users\Alessandro Fiori\Desktop\TorSwarm\container.txt" Impossibile trovare C:\Users\Alessandro Fiori\Desktop\TorSwarm\container.txt C:\Users\Alessandro Fiori\Desktop\TorSwarm>docker build --no-cache=true "C:\Users\Alessandro Fiori\Desktop\TorSwarm\9001" --iidfile "C:\Users\Alessandro Fiori\Desktop\TorSwarm\image.txt" Sending build context to Docker daemon 2.048kB Step 1/8 : FROM ubuntu:rolling rolling: Pulling from library/ubuntu e58ad9fd24ca: Pull complete 0a4c669d2dea: Pull complete ab60767ef52b: Pull complete 8cc3b738fbea: Pull complete Digest: sha256:1da669e3481b6c2c8bb25ad287b75202871b1511249000e3bc35679d02e007f4 Status: Downloaded newer image for ubuntu:rolling ---> b977ae81df17 Step 2/8 : RUN apt-get update && apt-get upgrade -y ---> Running in 771d930b65b7 Get:1 http://archive.ubuntu.com/ubuntu cosmic InRelease [242 kB] Get:2 http://security.ubuntu.com/ubuntu cosmic-security InRelease [88.7
