[prev in list] [next in list] [prev in thread] [next in thread]
List: tor-dev
Subject: Re: [tor-dev] Docker images for help people to run Tor (teor) (teor)
From: Alessandro Fiori <alefiori3 () gmail ! com>
Date: 2019-04-01 21:46:22
Message-ID: CAP6e1PmanY+GcvxUCacg-JbUO0aXviGU_kC5+GAhcDXVSxX7fw () mail ! gmail ! com
[Download RAW message or body]
[Attachment #2 (multipart/alternative)]
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-request@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-request@lists.torproject.org
>
> You can reach the person managing the list at
> tor-dev-owner@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 <teor@riseup.net>
> To: tor-dev@lists.torproject.org
> Subject: Re: [tor-dev] Docker images for help people to run Tor (teor)
> Message-ID: <EBC8EE49-155E-4B26-BC19-E2B0642FF2DB@riseup.net>
> Content-Type: text/plain; charset="utf-8"
>
> Hi,
>
> > On 1 Apr 2019, at 07:55, Alessandro Fiori <alefiori3@gmail.com> 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 <teor@riseup.net>
> To: tor-dev@lists.torproject.org
> Subject: [tor-dev] Next Network Team Meeting Time
> Message-ID: <68735AED-467B-40EF-B8E2-98417723FD51@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
>
> Daylight saving changed recently, so at least one of these meetings
> will be at a different local time for you.
>
> Our 1700 UTC meeting tracks north american daylight saving time.
> Our 2300 UTC meeting does not change for daylight saving time.
>
> T
>
> --
> teor
> ----------------------------------------------------------------------
>
> -------------- 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/20190401/b2888df3/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 99, Issue 1
> **************************************
>
[Attachment #5 (text/html)]
<div dir="ltr"><div dir="ltr"><div><div>Hi,</div><div>thanks for your \
support!</div><div><br></div><div>I've modified Dockerfiles to properly install \
the right Tor version and starting two relays with both scripts.</div><div>The \
images have been released on Docker Hub too.</div><div><br></div><div>Next step for \
me is preparing script and image for easily setting up a \
bridge.</div><div><br></div><div>Since all containers created are Linux containers, \
and since all my Dockerfiles are "one shot configurations", I will release \
bash scripts soon.</div><div><br></div><div>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).</div><div><br></div><div>If \
you want to control all the released code and images, the two principal repositories \
are:</div><div><a href="https://github.com/randomtable/ChimeraOS">https://github.com/randomtable/ChimeraOS</a> \
</div><div><a href="https://hub.docker.com/u/alessandrofiori">https://hub.docker.com/u/alessandrofiori</a><br></div><div><br></div><div>Many \
thanks</div></div><div><br></div><div class="gmail_quote"><div dir="ltr" \
class="gmail_attr">Il giorno lun 1 apr 2019 alle ore 14:00 <<a \
href="mailto:tor-dev-request@lists.torproject.org">tor-dev-request@lists.torproject.org</a>> \
ha scritto:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px \
0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Send tor-dev mailing \
list submissions to<br>
<a href="mailto:tor-dev@lists.torproject.org" \
target="_blank">tor-dev@lists.torproject.org</a><br> <br>
To subscribe or unsubscribe via the World Wide Web, visit<br>
<a href="https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-dev" \
rel="noreferrer" target="_blank">https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-dev</a><br>
or, via email, send a message with subject or body 'help' to<br>
<a href="mailto:tor-dev-request@lists.torproject.org" \
target="_blank">tor-dev-request@lists.torproject.org</a><br> <br>
You can reach the person managing the list at<br>
<a href="mailto:tor-dev-owner@lists.torproject.org" \
target="_blank">tor-dev-owner@lists.torproject.org</a><br> <br>
When replying, please edit your Subject line so it is more specific<br>
than "Re: Contents of tor-dev digest..."<br>
<br>
<br>
Today's Topics:<br>
<br>
1. Re: Docker images for help people to run Tor (teor) (teor)<br>
2. Next Network Team Meeting Time (teor)<br>
<br>
<br>
----------------------------------------------------------------------<br>
<br>
Message: 1<br>
Date: Mon, 1 Apr 2019 12:57:35 +1000<br>
From: teor <<a href="mailto:teor@riseup.net" \
target="_blank">teor@riseup.net</a>><br>
To: <a href="mailto:tor-dev@lists.torproject.org" \
target="_blank">tor-dev@lists.torproject.org</a><br>
Subject: Re: [tor-dev] Docker images for help people to run Tor (teor)<br>
Message-ID: <<a href="mailto:EBC8EE49-155E-4B26-BC19-E2B0642FF2DB@riseup.net" \
target="_blank">EBC8EE49-155E-4B26-BC19-E2B0642FF2DB@riseup.net</a>><br>
Content-Type: text/plain; charset="utf-8"<br>
<br>
Hi,<br>
<br>
> On 1 Apr 2019, at 07:55, Alessandro Fiori <<a \
href="mailto:alefiori3@gmail.com" target="_blank">alefiori3@gmail.com</a>> \
wrote:<br> > <br>
> Hi,<br>
> I would like to share with the community some tests I've made for setting up \
a "swarm" of Tor relays.<br> > <br>
> 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.<br> > <br>
> Due to Tor limitation, I have decided to build a template for preparing the \
cluster, and upload it to GitHub.<br> > <br>
> You can find the example mini-cluster here:<br>
> <a href="https://github.com/randomtable/ChimeraOS/tree/master/TorSwarm" \
rel="noreferrer" target="_blank">https://github.com/randomtable/ChimeraOS/tree/master/TorSwarm</a> \
<br> > <br>
> I have tested the exit capabilities on another network with different public IP \
address.<br> > <br>
> All the relays have published their own descriptors, I have prepared the \
containers as a single, separated machines.<br> > <br>
> The process is different from preparing a single relay, because of Docker build \
process.<br> > <br>
> I have disabled caching during the cluster process, so i have been able to \
modify torrc without issues.<br> > <br>
> Because its very interesting, attached to this e-mail there is the console \
Logs from the 6 relays.<br> > <br>
> All containers are read-only, so the entire relay will destroy at the end of \
session.<br> > <br>
> I hope this can be useful.<br>
<br>
Tor clients will only see 2 of your 6 relays, because the Tor directory authorities \
only publish 2 relays per IPv4 address.<br> <br>
Also, please use the <a href="http://deb.torproject.org" rel="noreferrer" \
target="_blank">deb.torproject.org</a> repositories to get the latest version of \
tor:<br> 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<br>
<br>
<a href="https://trac.torproject.org/projects/tor/wiki/TorRelayGuide/DebianUbuntu" \
rel="noreferrer" target="_blank">https://trac.torproject.org/projects/tor/wiki/TorRelayGuide/DebianUbuntu</a><br>
<br>
T<br>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <<a href="http://lists.torproject.org/pipermail/tor-dev/attachments/20190401/f30ddefa/attachment-0001.html" \
rel="noreferrer" target="_blank">http://lists.torproject.org/pipermail/tor-dev/attachments/20190401/f30ddefa/attachment-0001.html</a>><br>
<br>
------------------------------<br>
<br>
Message: 2<br>
Date: Mon, 1 Apr 2019 14:45:42 +1000<br>
From: teor <<a href="mailto:teor@riseup.net" \
target="_blank">teor@riseup.net</a>><br>
To: <a href="mailto:tor-dev@lists.torproject.org" \
target="_blank">tor-dev@lists.torproject.org</a><br>
Subject: [tor-dev] Next Network Team Meeting Time<br>
Message-ID: <<a href="mailto:68735AED-467B-40EF-B8E2-98417723FD51@riseup.net" \
target="_blank">68735AED-467B-40EF-B8E2-98417723FD51@riseup.net</a>><br>
Content-Type: text/plain; charset="utf-8"<br>
<br>
Hi,<br>
<br>
The next network team meeting is at 2300 UTC on Tuesday 2 April.<br>
<br>
Here is our full April schedule:<br>
* Tuesday 2 April at 2300 UTC<br>
* Monday 8 April at 1700 UTC<br>
* Monday 15 April at 1700 UTC<br>
* Tuesday 23 April at 1700 UTC (Monday 22 April is the Easter Monday public \
holiday)<br>
* Monday 29 April at 1700 UTC<br>
<br>
Daylight saving changed recently, so at least one of these meetings<br>
will be at a different local time for you.<br>
<br>
Our 1700 UTC meeting tracks north american daylight saving time.<br>
Our 2300 UTC meeting does not change for daylight saving time.<br>
<br>
T<br>
<br>
--<br>
teor<br>
----------------------------------------------------------------------<br>
<br>
-------------- next part --------------<br>
A non-text attachment was scrubbed...<br>
Name: signature.asc<br>
Type: application/pgp-signature<br>
Size: 833 bytes<br>
Desc: Message signed with OpenPGP<br>
URL: <<a href="http://lists.torproject.org/pipermail/tor-dev/attachments/20190401/b2888df3/attachment-0001.sig" \
rel="noreferrer" target="_blank">http://lists.torproject.org/pipermail/tor-dev/attachments/20190401/b2888df3/attachment-0001.sig</a>><br>
<br>
------------------------------<br>
<br>
Subject: Digest Footer<br>
<br>
_______________________________________________<br>
tor-dev mailing list<br>
<a href="mailto:tor-dev@lists.torproject.org" \
target="_blank">tor-dev@lists.torproject.org</a><br> <a \
href="https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-dev" rel="noreferrer" \
target="_blank">https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-dev</a><br> \
<br> <br>
------------------------------<br>
<br>
End of tor-dev Digest, Vol 99, Issue 1<br>
**************************************<br>
</blockquote></div></div></div>
[Attachment #6 (text/plain)]
_______________________________________________
tor-dev mailing list
tor-dev@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-dev
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic