- tor-dev - lists.torproject.org

Next Network Team Meeting Time
by teor 01 Apr '19

01 Apr '19

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 ----------------------------------------------------------------------

1 0

Re: [tor-dev] Docker images for help people to run Tor (teor)
by Alessandro Fiori 31 Mar '19

31 Mar '19

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-request(a)lists.torproject.org> ha scritto: > Send tor-dev mailing list submissions to > tor-dev(a)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(a)lists.torproject.org > > You can reach the person managing the list at > tor-dev-owner(a)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 <teor(a)riseup.net> > To: tor-dev(a)lists.torproject.org > Subject: Re: [tor-dev] Docker images for help people to run Tor > Message-ID: <3D4905AF-1C10-47BF-8823-EB3228FF990F(a)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 <alefiori3(a)gmail.com> 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 >

2 1

Re: [tor-dev] tor-dev Digest, Vol 98, Issue 18
by Alessandro Fiori 30 Mar '19

30 Mar '19

Hi, and thanks for replying! I have built another image, for Non-Exit relays. Essentially, the Dockerfile is the same to the Dockerfile for build an Exit Relay, i have added the command for uncomment "ExitRelay 0" line in the torrc file. I have modified the Hidden Service image too, providing only the Hidden Service without opening ports, reducing the attack surface. 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. I'm presenting this project to the large community, so i can receive feedback and take actions in case of issues. Kind regards, Alessandro Fiori Il giorno ven 29 mar 2019 alle ore 13:00 < tor-dev-request(a)lists.torproject.org> ha scritto: > Send tor-dev mailing list submissions to > tor-dev(a)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(a)lists.torproject.org > > You can reach the person managing the list at > tor-dev-owner(a)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 > (Chelsea Holland Komlo) > 2. Re: Docker images for help people to run Tor (Alessandro Fiori) > 3. Re: Docker images for help people to run Tor (teor) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Thu, 28 Mar 2019 05:46:57 -0700 > From: Chelsea Holland Komlo <me(a)chelseakomlo.com> > To: tor-dev(a)lists.torproject.org > Cc: Alessandro Fiori <alefiori3(a)gmail.com> > Subject: Re: [tor-dev] Docker images for help people to run Tor > Message-ID: <554cdbb2a021c08e08faef91d3bcb9a2(a)chelseakomlo.com> > Content-Type: text/plain; charset=US-ASCII > > Hi, > > Thanks for this information and putting this together! Making relays > easier to run is always a helpful thing to us. > > We have a wiki page to aggregate relay infrastructure projects such as > this. If you can add your projects to this page (and any required > instructions), that would be great. > > > https://trac.torproject.org/projects/tor/wiki/community/relay_infrastructure > > Thanks for the contribution! > Chelsea > > On 2019-03-27 21:18, Alessandro Fiori wrote: > > Hi, I'm an Italian developer who want to help development and grow up > > the Tor network. > > I would like to share with you an idea to grow up the Tor Network. > > Working with Docker, i have released two images, a Tor Exit Relay > > image (named "tor-relay") and an image (named "torworld-template"). > > The idea is to use Docker and build images for facilitate users to run > > a Tor Relay or an Hidden Service. > > The two images are located on Docker Hub in this locations: > > > > Tor Exit Relay: https://hub.docker.com/r/alessandrofiori/tor-relay > > Tor Machine Template: > > https://hub.docker.com/r/alessandrofiori/torworld-template > > > > If you want to see how the images are built, please check the > > following Dockerfile > > > > Tor Exit Relay: > > > https://raw.githubusercontent.com/randomtable/ChimeraOS/master/DockerFile-T… > > Tor Machine Template: > > > https://raw.githubusercontent.com/randomtable/ChimeraOS/master/DockerFile-T… > > > > If you want to see how i automate the build and push process, please > > check the following script: > > > > Process with system cleanup: > > > https://raw.githubusercontent.com/randomtable/ChimeraOS/master/build-script… > > Process for rolling release: > > > https://raw.githubusercontent.com/randomtable/ChimeraOS/master/build-rollin… > > > > Actually i'm working in a Windows environment, i will release ubuntu > > scripts soon. > > > > I would like to share with everyone, so if this can be helpful, this > > can be a starting point for build up images for help people to run > > relays or hidden services. > > > > This kind of approach can be reduce costs for people who want to run a > > relay or an hidden service, and can be an help for building a more > > censorship-resistant platform, by using a Docker Swarm, and > > replicating instances. > > > > Waiting for your reply as soon as possible, i'm very curious if this > > project can be helpful for Tor Project! > > > > Kind regards (and thanks for your hard work) > > Alessandro Fiori > > _______________________________________________ > > tor-dev mailing list > > tor-dev(a)lists.torproject.org > > https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-dev > > > ------------------------------ > > Message: 2 > Date: Thu, 28 Mar 2019 23:57:46 +0100 > From: Alessandro Fiori <alefiori3(a)gmail.com> > To: Chelsea Holland Komlo <me(a)chelseakomlo.com> > Cc: tor-dev(a)lists.torproject.org > Subject: Re: [tor-dev] Docker images for help people to run Tor > Message-ID: > <CAP6e1PnzqMRXdGmnF1U=oZqA2s69gdY= > Wc+D4LSzPsygbYckNw(a)mail.gmail.com> > Content-Type: text/plain; charset="utf-8" > > Hi, and thanks for reply! > I added a line in the dedicated page, and modified the README.md on GitHub > for more specific informations to the users. > > I've decided to release two scripts (I'm releasing for Ubuntu too), for run > an Exit Relay or Hidden Service then, with Docker image. > > If needed, let me know if there would be useful releasing an image of a > Non-Exit-Relay. > > I will add more informations in the following days, for more explanations > and specific infos about building process. > I have decided to release only scripts or text file (for build process and > pull process), and no binaries, to keep processes transparent and > controllable. > > The next step for me is writing to forums and IRC, so people can review the > configurations. > I would like to meet the best practices to provide a robust and secure > service under all aspects. > > Another further step will be to contact Docker and try to achieve the > "Verified Publisher" or "Official Image" status, to keep the User Trust up. > > Official Images have automated security scans, so it can be a benefit to > community. > > I hope this can be useful, let me know! > > Kind regards (and thanks for your hard work... really!) > > Il giorno gio 28 mar 2019 alle ore 13:46 Chelsea Holland Komlo < > me(a)chelseakomlo.com> ha scritto: > > > Hi, > > > > Thanks for this information and putting this together! Making relays > > easier to run is always a helpful thing to us. > > > > We have a wiki page to aggregate relay infrastructure projects such as > > this. If you can add your projects to this page (and any required > > instructions), that would be great. > > > > > > > https://trac.torproject.org/projects/tor/wiki/community/relay_infrastructure > > > > Thanks for the contribution! > > Chelsea > > > > On 2019-03-27 21:18, Alessandro Fiori wrote: > > > Hi, I'm an Italian developer who want to help development and grow up > > > the Tor network. > > > I would like to share with you an idea to grow up the Tor Network. > > > Working with Docker, i have released two images, a Tor Exit Relay > > > image (named "tor-relay") and an image (named "torworld-template"). > > > The idea is to use Docker and build images for facilitate users to run > > > a Tor Relay or an Hidden Service. > > > The two images are located on Docker Hub in this locations: > > > > > > Tor Exit Relay: https://hub.docker.com/r/alessandrofiori/tor-relay > > > Tor Machine Template: > > > https://hub.docker.com/r/alessandrofiori/torworld-template > > > > > > If you want to see how the images are built, please check the > > > following Dockerfile > > > > > > Tor Exit Relay: > > > > > > https://raw.githubusercontent.com/randomtable/ChimeraOS/master/DockerFile-T… > > > Tor Machine Template: > > > > > > https://raw.githubusercontent.com/randomtable/ChimeraOS/master/DockerFile-T… > > > > > > If you want to see how i automate the build and push process, please > > > check the following script: > > > > > > Process with system cleanup: > > > > > > https://raw.githubusercontent.com/randomtable/ChimeraOS/master/build-script… > > > Process for rolling release: > > > > > > https://raw.githubusercontent.com/randomtable/ChimeraOS/master/build-rollin… > > > > > > Actually i'm working in a Windows environment, i will release ubuntu > > > scripts soon. > > > > > > I would like to share with everyone, so if this can be helpful, this > > > can be a starting point for build up images for help people to run > > > relays or hidden services. > > > > > > This kind of approach can be reduce costs for people who want to run a > > > relay or an hidden service, and can be an help for building a more > > > censorship-resistant platform, by using a Docker Swarm, and > > > replicating instances. > > > > > > Waiting for your reply as soon as possible, i'm very curious if this > > > project can be helpful for Tor Project! > > > > > > Kind regards (and thanks for your hard work) > > > Alessandro Fiori > > > _______________________________________________ > > > tor-dev mailing list > > > tor-dev(a)lists.torproject.org > > > https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-dev > > >

2 1

Docker images for help people to run Tor
by Alessandro Fiori 28 Mar '19

28 Mar '19

Hi, I'm an Italian developer who want to help development and grow up the Tor network. I would like to share with you an idea to grow up the Tor Network. Working with Docker, i have released two images, a Tor Exit Relay image (named "tor-relay") and an image (named "torworld-template"). The idea is to use Docker and build images for facilitate users to run a Tor Relay or an Hidden Service. The two images are located on Docker Hub in this locations: Tor Exit Relay: https://hub.docker.com/r/alessandrofiori/tor-relay Tor Machine Template: https://hub.docker.com/r/alessandrofiori/torworld-template If you want to see how the images are built, please check the following Dockerfile Tor Exit Relay: https://raw.githubusercontent.com/randomtable/ChimeraOS/master/DockerFile-T… Tor Machine Template: https://raw.githubusercontent.com/randomtable/ChimeraOS/master/DockerFile-T… If you want to see how i automate the build and push process, please check the following script: Process with system cleanup: https://raw.githubusercontent.com/randomtable/ChimeraOS/master/build-script… Process for rolling release: https://raw.githubusercontent.com/randomtable/ChimeraOS/master/build-rollin… Actually i'm working in a Windows environment, i will release ubuntu scripts soon. I would like to share with everyone, so if this can be helpful, this can be a starting point for build up images for help people to run relays or hidden services. This kind of approach can be reduce costs for people who want to run a relay or an hidden service, and can be an help for building a more censorship-resistant platform, by using a Docker Swarm, and replicating instances. Waiting for your reply as soon as possible, i'm very curious if this project can be helpful for Tor Project! Kind regards (and thanks for your hard work) Alessandro Fiori

3 3

How to see the translated strings from Release_tweets.md in use
by scootergrisen 23 Mar '19

23 Mar '19

How/Where do i se the translated strings from Transifex Release_tweets.md in use?

1 0

Orbot and Tor on Android Q
by Nathan Freitas 22 Mar '19

22 Mar '19

Orbot 16.0.6-BETA-1-tor-0.3.5.8 <https://github.com/n8fr8/orbot/releases/tag/16.0.6-BETA-1-tor-0.3.5.8> https://github.com/n8fr8/orbot/releases/tag/16.0.6-BETA-1-tor-0.3.5.8 is out (binaries on Github for now) for testing, specifically on Android Q. It is built on a new release of: tor-android-binary-tor-0.3.5.8-rc <https://github.com/n8fr8/tor-android/releases/tag/tor-android-binary-tor-0.…> https://github.com/n8fr8/tor-android/releases/tag/tor-android-binary-tor-0.… This now uses the method of bundling the tor executable as a tor.so library, allowing the Android runtime to unpack them into the /data/libs read-only space within the app's private directory. We then can just execute it there, without needing to unpack it, copy it, etc. The word is that this will work on Android Q still. I have tested on an emulator, but not a real device yet. I don't have a Pixel of any kind, at the moment, so please let me know if you do and can test. Otherwise, we are working to move tor and other important binaries, like obfs4proxy, into actual in-process libraries. We've recently made great progress with this on our iOS work with Onion Browser, and so it should now be possible on Android. New commits below.... *** ATTENTION ANDROID Q / PIXEL TEST USERS: We've made changes just for you! WARNING: Meek/Obfs4 bridges WILL NOT work on Android Q yet, just plain Tor fb14c76 <https://github.com/n8fr8/orbot/commit/fb14c76c3a75977af9e86887b54dad5d15ae2…> fixed strings with two many \ escapes 4557577 <https://github.com/n8fr8/orbot/commit/455757726d519ac56cd53eaed29c3abef2570…> updating to tor-0.3.5.8-rc to add support for Android Q 22d5ffd <https://github.com/n8fr8/orbot/commit/22d5ffdf8bc3d51bb014e319d9f1e6b2ecb3e…> update gradle tools 76796fe <https://github.com/n8fr8/orbot/commit/76796fea83ef7efe3e33f6f5862fd71171a70…> Merge pull request #200 <https://github.com/n8fr8/orbot/pull/200> from eighthave/fastlane-supply 6ba0cec <https://github.com/n8fr8/orbot/commit/6ba0ceccbde67310c22fc9fa4e0dc88d93274…> add .gitlab-ci.yml setup with errorprone 3face00 <https://github.com/n8fr8/orbot/commit/3face00a66874afb793470922e381a9e463b1…> build gradle to 4.4.1, and make gradlew verify the download 69bd7fe <https://github.com/n8fr8/orbot/commit/69bd7fe9e6fd0fcde92ea53dd6236e50f7b37…> move app store graphics into fdroid/fastlane file layout f93c11e <https://github.com/n8fr8/orbot/commit/f93c11e74599cc24c7467d58ba0fc81c38c3c…> Merge pull request #190 <https://github.com/n8fr8/orbot/pull/190> from SkewedZeppelin/master 8ab13f6 <https://github.com/n8fr8/orbot/commit/8ab13f63a6f529d97816568170e02a1bced3c…> Fixup bad indentation from 6e4b700 <https://github.com/n8fr8/orbot/commit/6e4b7008035b2bf1a9035b730aad178bfd424…> 12b91c4 <https://github.com/n8fr8/orbot/commit/12b91c44f3af675dd0db5a3bacbf232c0f8d6…> Expose PreferIPv6 and NoIPv4Traffic options 8ad7668 <https://github.com/n8fr8/orbot/commit/8ad7668013a7291b98cf8689cd99961db69f8…> Move Google repo above jcenter d4befad <https://github.com/n8fr8/orbot/commit/d4befad117f3485f0aa67b2ce44d3f1b13de2…> cleanup and binary loading fixes

1 0

Testing Tor bridge assignments
by Jodi Spacek 19 Mar '19

19 Mar '19

Hi! I'm seeking advice on simulating Tor's consistent hashing, bridge ring distributor. I'm finishing up my Master's thesis on proxy distribution :) I run BridgeDB through my Python simulator to analyze the https distributor's bridge assignments over multiple bridge pool sizes and trials. So far, it follows a uniform random distribution (as expected). I'm using https distributor's prepopulateRings() example as a guideline on how the rings should be populated. Besides the default ring settings, are there any other test scenarios that I should cover? For instance, is there a possibility that the behaviour might change if there are quality of service limitations? Aside from the reserved set, are there any cases where it may not assign bridges uniform randomly that I should consider? I attempted to use the descriptors from leekspin, but ran into some hurdles integrating it with my simulator. My simulator doesn't need to persist or store state, since I only need the assignment information of proxies to clients until all proxies are enumerated. I hope the pared down version using the test data from generateFakeBridges() in test/util.py is adequate. Any advice is greatly appreciated!

1 0

Tor Friendliness Scanner
by Kevin Gallagher 18 Mar '19

18 Mar '19

Hello tor-dev! My name is Kevin and I'm a PhD student at NYU. Recently I've been working on creating a "Tor Friendliness Scanner" (TFS), or a scanner that will measure what features of a given website are broken (non-functional) when accessed on the Tor Browser (TB), along with actionable suggestions to improve it. In order to do this, we first must get an approximation of ground-truth data of how a given website should work. We then need to compare it to how the website works on the TB to determine any changes. To generate a method of determining ground-truth, we decided to modify* the Firefox (FF) browser to log all of the steps of the creation of the Content Tree (also called the DOM tree), and to log the execution of all JavaScript functions (currently underway). We then will apply these changes to the TB as well, and run a scan of popular Web sites using the modified FF and the modified TB on all three of the TB security slider settings. We will then compare the resulting logs to determine where the tree creation processes differed* and why. These differences could potentially help us illuminate two things: 1. what functionality issues the Tor Browser encounters on popular Web sites, and 2. what threats (beyond metadata surveillance) the TB is protecting its users from in-the-wild. As far as I have considered, this method seems to capture a lot, but it's far from complete. For one thing, it obviously won't detect any difference that's spawned from user interaction or input (such as a script launched by an OnClick event). However, it does seem to make automation of scanning for Tor Friendliness possible, and can allow for wide-scale use. We have moved ahead with development (though have not yet finished it) and are (hopefully) very close to a working prototype. I was wondering if there was feedback on this method, or if anyone can consider an angle we have not that would either make the TFS more robust, easier to create, or both. Thanks for your time and consideration! Kevin *Note 1: Unfortunately we cannot just rely on JavaScript for examining the content tree, since this needs to work on all 3 security settings of the TB's security slider, and the "safest" setting deactivates JavaScript by default on all Web pages. *Note 2: There can be non-functional differences in Web pages, such as different ads showing or the display of the current time. We are working on methods to distinguish these from functional differences, such as using ad blacklists to determine if a given request or script is part of an ad, and ignoring it as part of the difference between the two trees. -- Kevin Gallagher Ph.D. Candidate Center For Cybersecurity NYU Tandon School of Engineering Key Fingerprint: D02B 25CB 0F7D E276 06C3 BF08 53E4 C50F 8247 4861

8 10

Proposal: Don't include package fingerprints in consensus documents
by Iain Learmonth 13 Mar '19

13 Mar '19

Hi All, #28465 [0] needed a proposal. Feedback is welcome and encouraged. I've not written a proposal before, so if someone could let me know if I'm following the process OK (or not) then that is useful too. Thanks, Iain. [0] https://trac.torproject.org/projects/tor/ticket/28465

3 8

#3600 tech doc
by Richard Pospesel 13 Mar '19

13 Mar '19

Hey y'all, For the past little while I've been working on a technical overview doc for #3600 (Prevent redirects from transmitting+storing cookies+identifiers) detailing the problems, scenarios and possible solutions. Please take a look and feel free to comment, edit or add! Link: https://storm.torproject.org/grain/X4nhdNqR9fGRc7sgTefFkg/ best, -Richard

3 7