October 2019 - tor-project - lists.torproject.org

Are there countries where using Tor is illegal?
by Cristian Consonni 11 May '25

11 May '25

Hi, (Sorry if this question has already been asked in the past, feel free to point me to the relevant resources.) I know that the legal FAQs by the EFF state that: «we believe that running a Tor relay — including an exit relay that allows people to anonymously send and receive traffic — is legal under U.S. law.»[1] I also know there is a list of countries for which there is legislation that exclude communication service providers from liability. They are indicated in the Legal of the Tor Exit Guidelines page[2], they are USA, Germany, Netherlands, Austria, France, and Sweden. >From some articles in the press[3a][3b] it may be illegal - depending on how you interpret the wording[*] - to use Tor (and other technologies such as VPNs or proxies) in the UAE, with fines ranging in the millions of dirhams (hundreds of thousand of dollars). A couple of weeks ago it was discussed - on this list as well - that a law was introduced to the state parliament to ban Tor[4a][4b]. This follows a case of some months ago of a Russian Tor exit node operator being arrested for inciting mass riots and terrorism[4c][4d]. The idea of blocking VPNs or Tor seems to have already been considered in the past[4e]. This infographic about pluggable transports[5] suggests access to the Tor network is censored or limited in China, Uzbekistan, Iran, and Kazakhstan. Tor being censored orblocked may be different from it being illegal. What about other countries? Is there a place where I can find more about this topic? Cristian [1]: https://www.torproject.org/eff/tor-legal-faq.html.en [2]: https://trac.torproject.org/projects/tor/wiki/doc/TorExitGuidelines [3a]: http://www.emirates247.com/news/emirates/dh500-000-fine-if-you-use-fraud-ip… [3b]: http://news.softpedia.com/news/people-caught-using-vpns-tor-or-proxies-in-t… [*]: «Whoever uses a fraudulent computer network protocol address (IP address) by using a false address or a third-party address by any other means for the purpose of committing a crime or preventing its discovery» [4a]: https://lists.torproject.org/pipermail/tor-talk/2017-June/043293.html [4b]: https://trac.torproject.org/projects/tor/ticket/22055 [4c]: https://lists.torproject.org/pipermail/tor-talk/2017-April/043109.html [4d]: https://techcrunch.com/2017/04/24/dmitry-bogatov-tor-russia/ [4e]; https://torrentfreak.com/vpn-and-tor-ban-looming-on-the-horizon-for-russia-… [5]: https://www.torproject.org/images/PT/2016-07-how-to-use-PT.png

4 3

fosdem?
by Gaba 17 Jan '20

17 Jan '20

Hi! The call for proposals is open for fosdem [0] as well as the stand submission [1] . It would be great to have Tor people from Europe giving a talk in the main track and setting up a stand. Any volunteer? [0] https://fosdem.org/2020/news/2019-08-13-call-for-participation/ [1] https://submission.fosdem.org/submission/stand -- Project Manager: Network, Anti-Censorship and Metrics teams gaba at torproject.org she/her are my pronouns GPG Fingerprint EE3F DF5C AD91 643C 21BE 8370 180D B06C 59CA BD19

7 11

August Fundraising Report
by Sarah Stevenson 10 Jan '20

10 Jan '20

Hello Tor world. Here is the Fundraising team’s report for August. As always, let us know if you have any questions. ## Events We ran our first booth at DEF CON in August. It was an exhausting few days, but we exceeded our goal and raised over $43,000! We also made several connections with folks who want to help us with projects in the coming months. We have compiled lessons learned and are looking forward to attending again next year. ## Appeals The Bug Smash campaign[1] ran from August 1 to August 31. We raised a little over $86K across postal mail, social media, email appeal, and in-person gifts at DEF CON and CCCamp. We received a mixture of currencies, including a variety of cryptocurrencies. This a strong increase over August 2018 when we raised $13K. ## Grants We submitted a grant to RIPE NCC Community Project’s support program for 50,000 EUR to improve our IPv6 support. Thanks to teor, Nick, & Gaba for their help writing this proposal. We submitted a concept note to OTF for a large Tor Browser project which would move us away from the ESR cycle and onto Mozilla’s regular release cycle; it would also allow us to implement some of Firefox’s Enhanced Tracking Protection features. Thanks to the Browser team and Pili for making this happen! We found out that two of our grant requests were declined, one to NLnet for ESR migration and the other to the Deer Creek Foundation for Communications work. Upcoming grant requests: DRL SOIs for Community and Scalability, due 9/20 MOSS Scalability project, due 9/?? (rolling) NLnet, due 10/1 Herb Block Foundation, due 10/3 NSF Dark Decoys project, due ?? (rolling) ## Cryptocurrency We made a connection with a company called The Giving Block[2] that helps nonprofits accept cryptocurrency donations called. We are now listed on their website and will participate in their Giving Tuesday efforts this coming December. We are also discussing other ways to collaborate. ## Monthly Donors We continue to see growth in our monthly donor program, Defenders of Privacy. In August we received $5,386.75 from this group. As you can see in the chart below, our efforts to recognize and communicate with these donors has resulted in more stable income and less attrition. We should expect the group to continue to grow through the end of the year and then have a dip again in January when people tend to reassess their monthly commitments. [1] https://blog.torproject.org/tors-bug-smash-fund-help-tor-smash-all-bugs <https://blog.torproject.org/tors-bug-smash-fund-help-tor-smash-all-bugs> [2] https://www.thegivingblock.com/donate-bitcoin <https://www.thegivingblock.com/donate-bitcoin>

1 5

Tor Browser team meeting notes, 16 September 2019
by Matthew Finkel 17 Dec '19

17 Dec '19

Hello! We held our weekly Tor Browser meeting on Monday in #tor-meeting2. Here is the IRC log: http://meetbot.debian.net/tor-meeting2/2019/tor-meeting2.2019-09-16-17.30.l… >From the weekly updates, we discussed and planned a Tor Browser Alpha release for Mac OS X due to the new notarization requirement. This will allow for additional testing before Tor Browser 9.0 becomes the stable version. We also discussed backporting a patch onto Tor Browser 8.5 for this and including it in the next stable release. >From the discussions, we decided on making about:blank the default New Tab page (instead of Firefox's new about:home page), and about:tor will be an alternative option. We are also beginning the triage of Tor Browser tickets for Bug Smashing and we are adding the keyword "BugSmashFund" on the applicable tickets. Finally, we are aiming at releasing the new Tor Network Settings UI in an upcoming alpha release. This moves the configuration settings menu from Tor Launcher into the browser's preferences screen (about:preferences#tor). Below are the notes from our meeting pad: Discussion: (acat) Should we allow users to change New Tab page to "Firefox Home" (Firefox default new tab page)? see https://trac.torproject.org/projects/tor/ticket/31575 (pili) BugSmashFund: if you see any bugs that are outside sponsor work and would be good to fix after ESR68 work is over please tag on trac with "BugSmashFund" keyword (pili) Gentle reminder to update tickets for September with points estimate and actual points once closed. (anto) could we have #31286 (Tor Network Settings on about:preferences#tor) on alpha channel? GeKo: Last week: - Bug 30126: Apple notarization - Bug 31538: Windows reproducibility - Bug 31584: Clean-up mingw-w64 project (currently testing a final patch) - fixed Windows nightly build failure (#31732) - wrote a patch for #31725 (mk localization did not work properly) - worked on missing pieces for #30429 - acat/sysrqb where are we with the reviews/fixups for #31010? Is there anything left from your side? - reviews (#24653, #26345, #30304, #31575) - double-checked our hardening flag situation for Windows and Linux bundles after toolchain updates; I think there a no surprises and unknown issues that popped up - caught up with blog comments (having 4 active blog posts to take care of in parallel is harder than thought :) ) This week: - stack smashing protection for Windows binaries (#29013) - #31597 (Mozilla bug review for bugs squashed between Firefox 61-68) - finish missing pieces for #30429 - maybe release for testing #30126 on alpha channel? we'd need #31702 for that which is supposed to apply cleanly for esr68 at least; apple is saying Catalina gets out in October so, we might have a bit more time here? - reviews mcs and brade: Last week: - Testing and research for #30126 (Make Tor Browser on macOS compatible with Apple's notarization). - Verified that #31464 is no longer an issue (meek and moat are broken on macOS 10.9). - Debugged #31607 (App menu items stop working). - On macOS, menu-related objects are being freed too soon or at the wrong time. - This is a strange issue that is proving to be difficult to debug. (GeKo: Do we know which patch is causing that? If not, could we track down this bug easier that way? mcs: We think it is not caused by a patch but by Tor Launcher opening a modal window during startup but we will confirm) This week/upcoming: - Continue work on #31607 (App menu items stop working). - #31491 (clean up the old meek http helper browser profiles). - Work on other tbb-9.0-must-alpha tickets if time permits. - Reminder: we will be on vacation next week. sysrqb: Last week: Mostly afk. Releases Began dog-fooding 9.0a6 This week: - Pick up #30943 again (only private tabs as the default) - Investigate auto-complete not working on 9.0a6 Android (#31720) - Maybe look at showing Tor Browser version number on Android (#30943) - Maybe help with getting x86_64 Android builds (#31192) _hc/eighthave: Last week: tor-android clean-up work, 64-bit builds and configure.ac --enable-android path tor-android reproducible build (given the same docker container) This week: Android-native TorService tjr: - Worked on the WASM patch but waiting on help: https://bugzilla.mozilla.org/show_bug.cgi?id=1576254 - Landed the alloc/dealloc patch in 68: https://bugzilla.mozilla.org/show_bug.cgi?id=1547519#c32 - There are a couple of concerning test failures for the MinGW build in the esr68 branch that might/are probably related to this. - I need to fix my IDA installation to be able to dig into these though... boklm: Last week: - Did some reviews: - #31450 (Still use GCC for 64bit Linux debug builds after switch to 68 ESR) - #31264 (tar.gz output files contain non-reproducible timestamps) - #31621 (Fix node bug that makes large writes to stdout fail) - #31641 (Provide link to Tor Browser for Android alpha on our alpha download page) - #31596 (Bump mingw-w64 version to pick up fix for #31567) - #31732 (Windows nightly build failure) - Made a patch for #31448 (gold and lld break linking 32bit Linux bundles we need to resort to bfd) - Opened #31755 (Separate update pings and update requests graphs for Tor Browser alpha and release users) - Looked at #31646 (Update abicheck to require newer libstdc++.so.6) This week: - Test patch for #31538 (Windows bundles based on ESR 68 are not built reproducibly) - Review #27493 ('mk_add_options' or 'export' MOZILLA_OFFICIAL) - Make patch for #31646 (Update abicheck to require newer libstdc++.so.6) - will be afk on Tuesday (tomorrow) acat: Last week: - #26345 - Finish Disable tracking protection UI in FF67-esr (in review) - Investigated if serviceworkers can still see localized msgs in #30683. - Investigated a bit RemoteSettings background requests: #31740 - Created Bugzilla ticket for #30683 (https://bugzilla.mozilla.org/show_bug.cgi?id=1581537) This week: - 31303: Browser Toolbox fails to open when tor-launcher is present V(is it fine if I take this one pospeselr?) - tbb-9.0-must-alpha tickets sisbell: Last Week: - #31564: Android bundles not reproducible - implemented solution using apktool. Need verification if it works across build machines with different OS. (GeKo: I'll do that while reviewing) - #31568: Gradle how-to. Found solution to remove missing resources that was causing double artifact entries. Documented this. This week: - open tickets for tor-android-service patches - 31564 (if additional changes needed) - 31192 - x86_64 support Pili: Last week: - mostly afk - Gave a talk on using onion services for APIs at API Days Barcelona This week: - Looking at our roadmap and capacity - Moving forward with team lead transition tasks Antonela: - #31660 - Investigating about ESR68 Onboarding > https://trac.torproject.org/projects/tor/ticket/31660 - #31286 - TB9 Network Settings is almost done. Shared with phw and the anti-censorship team to have them in the same page. > https://trac.torproject.org/projects/tor/ticket/31286 - #27511 - Working with TB New Identity > https://trac.torproject.org/projects/tor/ticket/27511 - Back to S27 Onion Services pospeselr: Last Week: got moat bridgedb requests mostly working with new about:preferences#tor page (#31286) CAPTCHA displayed, guesses can be made and submitted, bridge strings returned back but aren't displayed or saved anywhere This Week: rebase current patches to latest esr68 branch >:[ port over the read/write logic for the tor proxy settings, and integrate that into the bridgedb request logic Have a good week! Matt

1 13

Metrics meeting notes, 31st October 2019
by Gaba 05 Nov '19

05 Nov '19

** Next meeting: *Thursday*, November 7th, 15 UTC ** Meeting logs: http://meetbot.debian.net/tor-meeting/2019/tor-meeting.2019-10-31-15.00.html Agenda Thursday, October 31st, 15 UTC Onionoo deployments (irl) - karsten tries instructions on AWS test instance on Monday. Exit scanner (gaba) - https://trac.torproject.org/projects/tor/ticket/29650 - the intial MVP needs all tickets that are children of #29654 - the next step is #32262, which is the foundation of the scanning mechanism - we may not be able to deploy at the end of December but there will be something to deploy Updating the wiki page for the metrics team https://trac.torproject.org/projects/tor/wiki/org/teams/MetricsTeam - karsten removes stuff that is now wrong and moves old stuff like roadmaps to subpages. - karsten updates metrics timeline in metrics.tpo now and once more before moving to gitlab. Release announcements, cf. #32142 (karsten) - we include a ticket query for "Release*" tickets in Metrics/* and links to dist.tpo on the team wiki page - gaba checks tickets before the meeting and includes them here for the meeting summary. - karsten writes down steps for releasing metrics-lib and collector, and then we see how we could include those in the *ops documents on help.tpo. Roadmap - how are we doing? (gaba) https://trello.com/b/Mu5fYg53/tor-metrics-roadmap -- Project Manager: Network, Anti-Censorship and Metrics teams gaba at torproject.org she/her are my pronouns GPG Fingerprint EE3F DF5C AD91 643C 21BE 8370 180D B06C 59CA BD19

1 1

New Tor Browser Team Meeting Time
by Matthew Finkel 31 Oct '19

31 Oct '19

Hello! Due to North America and Europe[0] changing their timezones, we are changing the time at which we meet for the weekly Tor Browser Team Meeting. Beginning this Monday (04 November, 2019), we'll begin meeting at 18:30 UTC, in #tor-meeting2. Some specific timezones are documented on the Application team wiki page[1], as well (please correct the local times if they are wrong). See some of you at the meeting! Matt (sysrqb) [0] Some places in some of the countries on the continents. [1] https://trac.torproject.org/projects/tor/wiki/org/teams/ApplicationsTeam#Co…

1 0

Re: [tor-project] Mumble and Tails in Scripts
by sajolida 31 Oct '19

31 Oct '19

Rafael Bonifaz: > Hello, Hi Rafael, I'm answering on tails-dev(a)boum.org, which is the mailing list for Tails development. I put tor-project(a)lists.torproject.org in copy once, for the others to know that the discussion moved to tails-dev(a)boum.org :) > In CAD, the organization I work for, we created some simple scripts to > setup a Mumble server in Tails and published it as Onion Service. We > wrote a blog post about it and we would be very happy if you have the > time to read, tested and give some feedback. > > English version: > > https://autonomia.digital/tails/mumble/anonymity/2019/10/09/tails-mumble.ht… > > Spanish version: > > https://autonomia.digital/es/tails/mumble/anonymity/2019/10/09/tails-mumble… > > Remember it is just a proof of concept. Thanks for developing new ways of using Tails :) We've been looking into adding VoIP support to Tails for years but we don't have a proper solution yet, so experiments are always interesting! Funnily, we experimented a bit with Mumble as well ourselves. At some point, we even had internal Tails meetings over Mumble running from Tails. Since then we moved to non-Torified VoIP solutions because of the bad UX of Mumble (poor sound quality and complex + fragile audio setup). In 2016, we also had a GSoC project on something we called "Tails Server" and that included being able to run a Mumble server from Tails: https://tails.boum.org/blueprint/tails_server/ The future of Tails Server is now uncertain. We might resume the work on Mumble from Tails if we had good clues that it would be an important solution for many people. From our short experience internally, we have serious doubts that it would. But maybe your experience could help us in this regard. How was your solution received in Ecuador? Do you have any success stories of less tech-savvy people using it successfully? (I'm guessing that the timing of your email has to do with the recent political events in Ecuador.) If you are interested in improving and maintaining your scripts, it might be possible for us to replicate your instructions in the "Advanced topics" section of our doc, making them a bit more official, and have interested people download the scripts from there. It might give us a bit more information about how popular such a solution would be. Also, would you be interested if we mentioned your instructions in our monthly community report for October? See for example: https://tails.boum.org/news/report_2019_09/ Cheers, -- sajolida Tails — https://tails.boum.org/ UX · Fundraising · Technical Writing

1 0

Anti-censorship meeting notes, 24 Oct 2019
by Cecylia Bocovich 31 Oct '19

31 Oct '19

Here are our meeting notes: http://meetbot.debian.net/tor-meeting/2019/tor-meeting.2019-10-31-16.59.html And here is our meeting pad: Anti-censorship work meeting pad -------------------------------- @@@ @@@ @@@ @@@ @@@@@@@@@@@@@@@@@@@@@@ @@@@@@@@@@@@@@@@@@@@@@@@@@ @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ @@@@@@@@ @@@@@@@@@@@@@@@@ @@@@@@@@ @@@@@@@@@ @@@@@@@@@@@@@@ @@@@@@@@@ @@@@@@@@@@ @@@@@@@@@@@@ @@@@@@@@@@ @@@@@@@@@@ @@@@ @@@@ @@@@@@@@@@ @@@@@@@@@@@@@@@@@@@@ @@@@@@@@@@@@@@@@@@@@ @@@@@@@@@@@@@@@@@@ @@@@@@@@@@@@@@@@@@ @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ @@@@@@@@@ @@@@@@@@@@@@@@@@@@@@@@@@ @@@@@@@@@ @@@@@@@@ @@ @@ @@ @@ @@ @@ @@ @ @@@@@@@@ @@@@@@@ @@@@@@@ @@@@@@ @@ @@ @@ @@ @@ @@ @ @@@@@@ @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ @@@@@@@@@@@@@@@@@@@@@@@@@@ @@@@@@@@@@@@@@@@@@@@@@ Next meeting: Thursday October 31th 17:00 UTC Weekly meetings, every Thursday at 17:00 UTC, in #tor-meeting at OFTC (channel is logged while meetings are in progress). == Goal of this meeting == Weekly checkin about the status of anti-censorship work at Tor. Coordinate collaboration between people/teams on anti-censorship at Tor. == Links to Useful documents == Our anti-censorship roadmap: https://dip.torproject.org/torproject/anti-censorship/roadmap/boards Our roadmap consists of a subset of trac tickets. The anti-censorship team's wiki page: https://trac.torproject.org/projects/tor/wiki/org/teams/AntiCensorshipTeam GetTor's roadmap: https://dip.torproject.org/groups/torproject/anti-censorship/gettor-project… Tickets that need reviews: https://trac.torproject.org/projects/tor/query?status=needs_review&componen… Projects from sponsors we are working on: https://trac.torproject.org/projects/tor/wiki/org/sponsors/Sponsor30 https://trac.torproject.org/projects/tor/wiki/org/sponsors/Sponsor28 --------------------------- --- 31st October 2019 --- --------------------------- == Announcements == None this week == Discussion == Snowflake upgrade for #29207 will exclude old, unupdated proxies Is this a good thing? Anything we should be aware of before proceeding? Gettor update survival guide here: https://dip.torproject.org/torproject/anti-censorship/gettor-project/gettor… any update to the roadmap? https://dip.torproject.org/torproject/anti-censorship/roadmap/-/boards == Updates == FORMAT! Name: This week: - What you worked on this week. Next week: - What you are planning to work on next week (related to anti-censorship work). Help with: - Something you may need help with. Hiro: Started restoring Twitter Responder. When retrieving tweets I need to check for new tweets only otherwise Gettor will end up responding to old back log and already answered messages. <-- is this #27330 ? Next Week: - Work on gettor specs <-- Is this #3781? - More with review of strings and website content and translation phw: This week (2019-10-31): Next week: Travel to Taiwan Wrap up #32135, #32105, and #31874 Help with: Gaba: (updated October 30th) Last week (): mozfest This week (planned): sponsors ahf Last week: - Worked on #28930 This week: - Finished refactoring parts of #28930. Trying to figure out if we should begin the discussion on how PT's can report back on bootstrap info. - Continued to work on a tool to convert Trac tickets into Gitlab tickets. cecylia (cohosh): last updated 2019-10-31 Last week: - revised #29207 and added support for browser proxies - made progress on snowflake server unit tests (#32300) - merged fix to remove timeoutConn (#32131) - merged longer poll (#32129) and updated translations for webextensions - bridgedb reviews - made more progress on #29206 and started working on a way to split traffic through multiple proxies (#25723) - Re-read salmon and rBridge papers, more grant writing - merged #31310 and now one browser proxy can handle multiple clients (#25601) This week: - continue on tests (#29259) - upgrade broker and proxies and check if bumping old proxies fixes network health - more work on #29206 and #25723 - take a look at gettor code tickets and see if there are code quality improvements - more grant writing - have proxies report what kind they are to broker #31157 (related to #29207) - do a review of work so far on #31874 - review #31028 - gettor code reviews Needs help with: - would like an ok on the upgrade plan for #29207 catalyst: week of 09/19 (planned): - reviews - sponsor31 planning - coding style discussion - comment on draft network team review guidelines - #30984 week of 09/19 (actual): - reviews - sponsor31 planning - talking with people about proposed network team review processes week of 09/26 (planned): - reviews - sponsor31 doc coordination - checking in on Season of Docs work - #30984 arlolra: 2019-10-31 Last week: - finished off / tested #31028 Next week: - add a build step / documentation for code reuse in cupcake - read up on turbo tunnel - pick a new task to work on Help with: - review #31028 dcf: 2019-10-30 (will miss 2019-10-31 meeting) Last week: - helped review SetDeadline warning fixes (#32131) - reviewed changes to the broker protocol (#29207) - further review of Snowflake sequencing protocol (#29207) - archived Snowflake WebExtension 0.0.13 Next week: - prototyping KCP and QUIC in meek - revise link to Cupcake patch (#31497) - review Gorilla WebSocket patch (#31028) Help with: - need meek-azure to redeploy meek-server for #31890

1 0

Network Team Meeting Notes, 28 October 2019
by Alexander Færøy 30 Oct '19

30 Oct '19

Hello! Here is a short summary of the network team meeting from Monday: 1) We started out by looking at the 0.4.2 status page on Trac to see how we are doing there. 2) We went over our Kanban board. 3) We went over our review queue. Did a few delegations. 4) People were reminded to fill out October status report. 5) We discussed the next steps from the C style survey by Nick. Nick is going to send initial thoughts to the network-team mailing list and we will discuss it from there. 6) We discussed getting some more review eyes on #32103 -- Nick volunteered to work with Catalyst on this. 7) Nobody had anything additional to discuss. --- end of summary --- You can read today's network team meeting log at: http://meetbot.debian.net/tor-meeting/2019/tor-meeting.2019-10-28-17.00.html Below are the contents of our meeting pad: gaba: (updated on september 30th) Last week (actual): up to date with trac & gitlab This week (planned): mozfest Help with: teor: (online first week of the month, offline at the usual meeting time) Week of 21 October (planned): Take Time for: - team policies: - commit bit - backports Roadmap: - Sponsor 31 modularisation: disable relay mode when compiling - Disable major relay and dirauth options, when those modules are disabled - Add tor controller trace logging to diagnose stem hangs (#30901) - continue work Other: - Keep on revising monotime coarse stamp bug fix Week of 21 October (actual): Urgent: - CI issues #32177 - resolved by Travis, mitigated by deleting build jobs Take Time for: - team policies: - commit bit - voting! - backports & backport deciding 0.4.2 bugs: - Made progress on Avoid possible overflow when converting between coarse stamp to approx ms #31482 - (Prioritised Sponsor 31 over some fixes, due to deadlines) Roadmap: - Sponsor 31 modularisation: disable relay mode when compiling - Made progress on Disable major relay and dirauth options, when those modules are disabled #32213 - List of code chunks to disable - children of #31851 - Merged Sponsor 31: coccinelle tooling and CI checks (#31919) - Reviews and merged for Nick's Sponsor 31 work Other: - Fixes on merge_ready and merged code (#31684, #31762, others) - Bug fixes, ticket triage, and extra reviews - Helping with cross-compiling issues Nick: Week of 21 October (planned): - Finish 31999 (default log handling) - Reviews and merges - 042-should TBD - Prepare for fundraising/outreach event at Wendy's next week. - Work on config.c verification refactor (31241) - Help with relay modularization (31851) - More high-level documentation - Edit collaborative blog post - Start working on 0.4.1.7 - PETS meta-review Week of 21 October (actual): - Finish 31999 (default log handling) - Finished config.c verification refactor (31241) - Reviews and merges - Prepare for fundraising/outreach event at Wendy's. - More high-level documentation - Lots more doxygen work. - Started backports for 0.4.1.7 - PETS meta-review - Released 0.4.2.3-alpha - Coccinelle tooling Week of 28 October (planned): - Event at Wendy's - 042-should TBD - Finish all support code for 29211. - Start revisions on paper with Ian & Chelsea? - Documentation work - Help with relay modularization (31851) - Discuss C style survey results. Mike: Week of 10/21 (planned): - Work with Tobias on circpad simulator issues (https://trac.torproject.org/projects/tor/ticket/31788) - Blog post writing - Begin wrapping up Sponsor2 - Work on Research Director Roles Description - Catch back up on network-team mails - Catch back up with tor-scaling mails Week of 10/21 (actual): - Work with Tobias on circpad simulator issues (https://trac.torproject.org/projects/tor/ticket/31788) - Worked on Research Director Roles Description - Catch back up on network-team mails - Catch back up with tor-scaling mails Week of 10/28 (planned): - Write a circpad doc section on formalization of machine computation and why we chose state machines - Look into circpad bugs asn filed last month that I missed (#30992, #32040, #32140) <-- (gaba: should it makes sense to assign those tickets to you if you are working on them? - #32140 is on asn's plate - you also had #28804) - Look into circpad bugs RIT folks found - Sync with Tobias wrt simulator changes - Maybe write blog post on fingerprinting research paper? Need help with/at risk of dropping this month: - Deep-thought-required research project followup - (Google masque, BGP, ECN, Rob's bw experiments, Dennis's Mozilla video, etc etc...) catalyst: week of 10/21 (2019-W43) (planned): - reviews - more GSoD stuff week of 10/21 (2019-W43) (actual): - more GSoD stuff - split swati's work into multiple commits for easier reviewing and merging - sponsor31 meeting - created child tickets to #29215 (document new architecture) and assigned some - did extra review of #31919 (coccinelle check-local target and git hooks) week of 10/28 (2019-W44) (planned): - reviews - sponsor31 tickets (children of #29215, etc) - GSoD stuff as neeeded help with: - maybe some extra review on the threading stuff in #32103? asn: [Currently in Tim's timezone so not able to attend meeting] Week of 21/10 (planned): - Vacations until Friday Week of 21/10 (actual): - Vacations until Friday - Replied to C style survey - Caught up with emails + ongoing netteam proposals - Replied to a few trac tickets that were pending feedback Week of 28/10 (planned): - Continue catching up with (S27) things that happened the past two weeks. - Continue work on stem encoding of HSv3 descriptors. - Traveling to OTF summit on Thursday. - (Also 28th of October is Greek national holiday, but decided to work so that I start catching up on things. I might take a day off at some point this or next week.) Help with: - David, can you do the little-t-tor side of the S27 October report? This will also help me catch up with your side of things. ahf: Week of 21 October (planned): - Focus on 042-should and s28 PT related tickets. - Make slides for presentation in Zurich next week. - Focus on Gitlab wiki migration. - Help Swati with Windows/Asciidoc/Man page situation. Week of 21 October (actually): - Talked with GeKo about some ideas for slides. - Looked into tracboat's Wiki migration feature, ported some of them over to our migration tool for GL. - Wrote some instructions on how to use WLS on Windows for Swati to build/read man pages. - Returned to s28 tickets. Week of 28 October (planned): - Will be talking about Tor at Swiss Web Security Day on the 30/10 and at Driving IT the 1/11. - Expect longer response times from me this week because of traveling. Use email over IRC maybe. - Get #28930 rebased into shape for merging. - If I have time look into our Windows Jenkins problems that Weasel reported on IRC (#32320) dgoulet: Week of 21/10 (actual): - Almost done with #30382. I have to talk to asn about the missing two error codes that are a bit complicated to get. - S27 triage and fixes on: #32094, #31958, #28970 - 3/4 there on implementing cmux tests: #32196. - Help arma/nickm on reviewing and testing #32108. - Reviews and Merges. - Network health needed attention. Week of 28/10 (planned): - Get asn up to date on the latest s27 situation. - Have #32196 in needs_review. - I hope I can finalize #30382 with asn's feedback. - s27 report. - Network health situation is still very active. - Continue my s27 quest on fixing all bugs. <-- (gaba: we need to look into the roadmap after december) - Reviews and merges as usual All the best, Alex. -- Alexander Færøy

1 0

Tor Browser Release Meeting: Wednesday 30th October @ 18UTC
by Pili Guerra 29 Oct '19

29 Oct '19

Hi everyone, A reminder that this is happening tomorrow, Wednesday 30th October @ 18UTC. During this meeting will review whether we want to keep this time going forward once the clocks have changed for everyone. Thank you! Pili — Project Manager: Tor Browser, UX and Community teams pili at torproject dot org gpg 3E7F A89E 2459 B6CC A62F 56B8 C6CB 772E F096 9C45

1 0