- tor-project - lists.torproject.org

Network Team Meeting Notes, 27 January 2020
by Alexander Færøy 05 Feb '20

05 Feb '20

Hello, Here is a short summary of the network team meeting from Monday the 27th of January 2020. 1) We started out with roadmap. 2) We went over review assignments. We talked a bit about who should review sbws tickets. 3) Teor had s55 proposals on the discussion list, but this was gonna be handled on the mailing list as part of review of proposals. 4) We discussed backports. Nick and Teor is gonna coordinate over Signal. 5) We still could use more master mergers. 6) We discussed an issue with AddressSanitizer/LeakSanitizer. 7) Nobody had anything else to discuss. --- end of summary --- You can read the network team meeting log at: http://meetbot.debian.net/tor-meeting/2020/tor-meeting.2020-01-27-17.59.html Below are the contents of our meeting pad: Nick: Week of Jan 20: (planned): - US HOLIDAY ON MONDAY - Finish fixes on #32709 (onionbalance subcredential fix) - 0.4.3.1.x-alpha - More releases? Or wait for more fixes? - Help with triage and assignment on 0.4.3.x - work on clusterfuzz failure - PETS discussion and artifact review Week of Jan 20 (actual): - Released 0.4.3.1-alpha - Finished fixes on #32709 (onionbalance subcredential fix) to address timing and performance - PETS discussion - Figured out why clusterfuzz was failing to build, and fixed it. (32783) - Helped diagnose tricky failing stem tests (33006) ("memory leak makes stem-tests fail") - Addressed blog comments - Reviewed stuff, including Teor's proposal 311. - S55 kickoff meeting Week of Jan 27 (planned): - Review all incoming 043 patches on my queue * - Read and answer Mike's big congestion document * - Release 0.4.2 and 0.4.1. (Is a final 0.4.0 called for?) * - More PETS discussion, and artifact review. * - Triage 0.4.3 and assign tickets with ahf. * - Take care of whatever 0.4.3 tickets are assigned to me. - Sketch out Walking Onions work plan. - Answer and discuss pending stuff about C style project. - Time permitting: - Review pending patches for 044 - Make more dirauth options optional (32139) - Stem tracing? (30901) catalyst: week of 01/20 (2020-W04) (planned): - reviews - TPI holiday 01/20 - GSoD - create tickets for roadmap items that need them - investigate some clang-format stuff (#32921) week of 01/20 (2020-W04) (actual): - TPI holiday 01/20 - investigated availability of features in various clang-format versions (and availability in OS packages) - memory leak fixes (##33039) - lots of fruitless troubleshooting about why LeakSanitizer doesn't report obvious leaks in tor but does report them in the same code in test programs - valgrind works but is sloooow - had to do an OS upgrade to get a valgrind that worked (the valgrind in Xenial doesn't work with anything linked with OpenSSL?) week of 01/27 (2020-W05) (planned): - reviews - retrospective 01/29 help with: - anyone who's familiar with either gcc or clang AddressSanitizer/LeakSanitizer want to help troubleshoot why it's not reporting leaks? ahf: Week of 20/1 2020 (planned): - 1:1s with everybody pretty much. - A few meetings. - Continue to work on s28 tickets. Week of 20/1 2020 (actually): - Hacked on #31009 - Hacked on #33005 - CC meeting. - Gitlab Wiki migration hacking. - A few meetings. - Joined GK's network health team meeting. Exciting we have that now. - Generally not as producitve as I had hoped largely due to not having access to my office. Week of 27/1 2020 (planned): - Ticket triage with Nick. - Continue on sponsored work. - Try to read and understand Mike Perry's epic pad. - Read and follow up on Teor's IPv6 propsal(s). - Prepare slides for FOSDEM and travel to FOSDEM (will thus be AFK from IRC on most of Thursday and all of Friday). - Hope to catch up with Juga while in Brussels and hear what they are up to. - Hope to spend some time with ln5 and hack on his key hw/vault idea. - If there is anybody we should meet and talk with at FOSDEM, now is a good time to say so. asn: Week of 20/01 (actual): - Almost recovered physically. - Took over #32709 from David (Thanks David!) and discussed it with Nick (Thanks Nick!) - Started working on remaining #32709 items. - Various S27 planning moves. Week of 27/01 (planned): - Finalize #32709 so that I can use it for testing OBv3. - Get back to doing reviews etc. Mike: Last week (planned): - Have gaba+isa review role descriptions - Metrics kickoff meeting - Work on explicit congestion notification meta-proposal - File perf-related roadmap tickets - Triage + prioritize circpad, vanguards bugs Last week (actual): - Had gaba+isa review role descriptions; worked on 2020 plan - Metrics kickoff meeting - Worked on explicit congestion notification meta-proposal This week (planned): - Mozilla all hands - Congestion control tor-dev post Maybe dropping due to Mozilla: - File perf-related roadmap tickets - Write mails to researchers re circpad docs + simulator - Triage + prioritize circpad, vanguards bugs dgoulet: Week of Jan 20th (actual): - Reviews and merges and meetings. - Worked on #33018/#33029. - The email world was strong that week. - Logistics for NetDev'14 conference in March. Rob and I were accepted for a talk there. Week of Jan 27th (planned): - Continue into the #33018 and #33029 madness world. - Hopefully make progress on ticket assigned to me on the roadmap. Gaba: Week of Jan 20th (actual) - Roadmap life - Run behind Trac Week of Jan 27th (planned) - Sustain OSS Summit - FOSDEM - look at sbws needed roadmap teor: (online first meeting of the month, offline at the usual meeting time) Week of 20 January (planned): Take Time for: - Draft sponsor 55 (relay IPv6) roadmap - Add existing ticket numbers - Make existing tickets child tickets of sponsor objective tickets (once Gaba has created the sponsor objective tickets) - Draft sponsor 55 proposals - If I write the proposals now, we can have them reviewed by 1 February, when the grant officially starts - O1.1: Relay IPv6 Reachability Checks - O1.2: Relay Auto IPv6 Address - O1.5: Relay IPv6 Statistics Roadmap: - Hand over or triage out 0.4.3 bug fixes Other: - Code Reviews Week of 20 January (actual): Take Time for: - Draft sponsor 55 (relay IPv6) roadmap - Add existing ticket numbers - Draft Proposal 311: Relay IPv6 Reachability: (please review!) https://lists.torproject.org/pipermail/tor-dev/2020-January/014132.html Roadmap: - 0.4.3 bug fixes - #32778 Initialise pubsub in Windows NT Service mode - #32962 add_c_file.py refactor - Triage #32314 Can't connect to literal IPv6 address containing double colon - Diagnose #33006 Fix test-stem `test_take_ownership_via_controller` failure - handed over incomplete tickets to other people, or triaged them out Other: - Fallback Scripts merges, CI fixes <--- is the fallback scripts something that geko/network-health should take? --gaba --> - Code Reviews: Bugs, Volunteers - Ticket triage - Merge chutney patches from new contributor Week of 27 January (planned): Take Time for: - Backports (if needed) - Draft sponsor 55 (relay IPv6) roadmap - Create tickets (once proposals have been reviewed) - Revise Proposal 311: Relay IPv6 Reachability: (please review!) https://lists.torproject.org/pipermail/tor-dev/2020-January/014132.html - Draft Proposal 312: Automatic Relay IPv6 Addresses - Draft Proposal 313: Relay IPv6 Statistics ? Roadmap: - (Transitioning between unfunded work / 0.4.3 fixes, and Sponsor 55) Other: - Code Reviews Week of 27 January (actual): Take Time for: - Roadmap: - Other: - Help cjb and ahf with #31009 - Use public relay addresses for PTs - Related to Relay Auto IPv6 Address: proposal 312 and ticket #5940 (Sponsor 55) Need help with: - Please review Proposal 311: Relay IPv6 Reachability: (for Sponsor 55) https://lists.torproject.org/pipermail/tor-dev/2020-January/014132.html -- Alexander Færøy

1 0

IPv6 project meeting, Thursday Feb 6th @ 0000 UTC
by Gaba 05 Feb '20

05 Feb '20

Hi! We are meeting on Thursday at 0000 UTC in #tor-meeting in irc.oftc.net to coordinate on the project "Improving the Tor network’s IPv6 support" numbered "S55" [0] The pad for meeting's agenda and notes will be: https://pad.riseup.net/p/tor-s55-ipv6-project-keep The proposals that Teor has been working on to reach the objectives of this project: * Prop 311: IPv6 ORPort Reachability https://github.com/torproject/torspec/pull/103/files * Prop 312: Relay Auto IPv6 Addreess https://github.com/torproject/torspec/pull/105/files cheers, gaba [0] https://trac.torproject.org/projects/tor/wiki/org/sponsors/Sponsor55 -- 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

2 1

Tor Browser release meeting today: Wednesday 5th February @ 19UTC
by Pili Guerra 05 Feb '20

05 Feb '20

Hi everyone, Please join us for the Tor Browser release meeting today at 19UTC on #tor-meeting. Thanks! 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

OONI Monthly Report: January 2020
by Maria Xynou 05 Feb '20

05 Feb '20

Hello, Happy new year, and happy new decade! ## OONI is an independent entity As of 1st January 2020, OONI is an independent entity! Back in 2011, OONI was born out of the Tor Project, which has since served as our fiscal sponsor. Thanks to Tor Project support, OONI was able to grow and become what it is today. We are immensely grateful to the Tor Project for all their support over the last 8 years, and we look forward to continuing to collaborate on the fight against internet censorship! As part of our growth, OONI is transitioning to greater autonomy and independence. As of 1st January 2020, OONI is fiscally sponsored by the Hermes Center for Transparency and Digital Human Rights (https://www.hermescenter.org/) a non-profit, digital rights organization based in Italy, which was co-founded by Arturo Filastò (OONI’s co-founder) back in 2011. OONI’s Maria Xynou and Simone Basso are also members of the Hermes Center. We may eventually create a dedicated-to-OONI NGO, but for now, the current arrangement is sufficient. ## New project management methods As of December 2019, we have changed how we do project management in our team. We now work in 2-week sprint cycles, based on which we plan and track the progress of our activities. So far, this works really well! We are using Zenhub boards to plan and estimate our activities, all of which are public, but require registration with the app. Here is our Sprint Planning board: https://app.zenhub.com/workspaces/sprint-planning-5dfa4b7355438f7e86c80e5a/… Even if the internal planning is behind a registration wall, all of our activities and priorities are still tracked using native GitHub tooling, making it possible for anyone to see what our priorities are via the public GitHub interface. We have also consolidated our GitHub issue repositories to only 9 in total: * https://github.com/ooni/ooni.org * https://github.com/ooni/backend * https://github.com/ooni/probe * https://github.com/ooni/probe-engine * https://github.com/ooni/explorer * https://github.com/ooni/run * https://github.com/ooni/design-system * https://github.com/ooni/orchestra This ticket shares more details: https://github.com/ooni/ooni.org/issues/317 To see what we are working on over the next 2 weeks for a given project, just select the next milestone of that repository on GitHub. Each issue should also have a priority label assigned to it and an effort estimate label. Each OONI team sprint has a marine-inspired name, and we encourage community members to propose names for our sprints here: https://github.com/ooni/ooni.org/issues/337 ## OONI Probe support for running circumvention tool tests During January 2020, we almost completed the implementation of all client-side logic that is required for testing Psiphon and Tor inside of OONI Probe. To add support for running Tor, we: * Wrote a first iteration of the Tor test: https://github.com/ooni/probe-engine/issues/226 * Added support for the Tor bridge reachability test in probe-engine: https://github.com/ooni/probe-engine/issues/2 * Added support for running obfs4proxy in probe-engine: https://github.com/ooni/probe-engine/issues/90 * Designed how the Tor test results should be presented in the OONI Probe desktop app: https://github.com/ooni/probe/issues/967 * Made a release of probe-cli with support for the Tor test experiment: https://github.com/ooni/probe/issues/974 * Exposed top level keys to expose top level statistics in the UI: https://github.com/ooni/probe-engine/issues/292 * Almost completed the UI work required to show the Tor test results in the OONI Probe app: https://github.com/ooni/probe/issues/975 To add support for running Psiphon, we: * Finalized support for running Psiphon in probe-engine: https://github.com/ooni/probe-engine/issues/89 * Finished integrating the Psiphon test results with the correct Psiphon icon in the OONI Probe Desktop App * Designed the UI for the circumvention tests in general: https://github.com/ooni/probe/issues/804 ## OONI Probe orchestration logic for circumvention tool testing In order to support measuring Psiphon and Tor, OONI Probe clients need to know which configurations they should use to carry out the testing. We therefore added support for giving out such testing targets (Psiphon configuration, Tor default bridges, Tor directory authorities) via authenticated backend calls. Specifically, we: * Added support for giving out Psiphon configurations: https://github.com/ooni/orchestra/issues/78 * Added support for giving out addresses for Tor tests: https://github.com/ooni/orchestra/issues/82 ## Making OONI Probe reporting logic more resilient to censorship We made a bit of progress in understanding how we can make OONI Probe testing more resilient to blocking and we added extra robustness to the app to overcome potential blocking attempts. Specifically, we: * Improved how we display measurements which have failed due to a bouncer failure: https://github.com/ooni/probe/issues/855 * Discussed solutions for what we should do when the IP lookup of a measurement fails: https://github.com/ooni/probe/issues/879 * Investigated how to allow alternative methods of sending measurement results to us via email (https://github.com/ooni/probe/issues/992) or IM apps (https://github.com/ooni/probe/issues/976) ## Analysis of circumvention tool test data and presentation in OONI Explorer We made a lot of progress with respect to presenting the new Psiphon and Tor test results inside of OONI Explorer and exposing them via the OONI API. We also worked on the scoring and analysis of the results in the data processing pipeline. Specifically, we: * Added support in the batch pipeline for scoring Tor test results: https://github.com/ooni/backend/issues/293 * Wrote data processing logic for processing Psiphon test results: https://github.com/ooni/backend/issues/209 * Re-wrote the OONI API list_measurements API call, adding support for listing and searching for Psiphon and the new Tor test results and boosting its performance: https://github.com/ooni/backend/issues/160 * Almost finished adding support for presenting Psiphon test results in OONI Explorer: https://github.com/ooni/explorer/issues/332 * Made considerable progress on presenting Tor test results in OONI Explorer: https://github.com/ooni/explorer/issues/332 To better tune the analysis engine, we need to ship the tests and increase the measurement coverage. ## OONI data processing pipeline In November 2019, we started publishing OONI measurements from around the world in near real-time (i.e. within minutes). This, however, had an impact on the performance of the OONI API (which OONI Explorer relies on). To boost the performance of the OONI API (and, by extension, the performance of OONI Explorer), we made a lot of progress on the OONI data processing pipeline, all of which can be viewed through the following tickets: https://github.com/ooni/backend/issues/161 https://github.com/ooni/backend/issues/163 https://github.com/ooni/backend/issues/160 Throughout January 2020, we added many blockpage fingerprints to the fast-path pipeline, making it possible to automatically confirm many more cases of internet censorship. See: https://github.com/ooni/pipeline/pull/289 We also experimented with adding support for calculating some statistics of measurements and anomalies. See: https://github.com/ooni/backend/issues/292 Moreover, we added support in the fast-path pipeline for anomaly, failure, and confirmed columns. We also worked on adding support for reconnections during failing SSH conditions, as we had noticed issues with this. We added support for ingesting the Citizen Lab category codes for URLs, in order to eventually support filtering URLs by category on OONI Explorer. This work is available here: https://github.com/ooni/backend/issues/231 We also discussed how we are going to move the development of the OONI data processing pipeline forward and came up with a plan for that, as documented in the following tickets: https://github.com/ooni/backend/issues/195 https://github.com/ooni/backend/issues/286 ## OONI Probe mobile app During January 2020, we added support for setting no limit to the maximum runtime. It is now possible for OONI Probe mobile app users to set the Websites test max_runtime to zero in order to test entire test lists. See: https://github.com/ooni/probe/issues/893 We also made several important bug fixes related to how certain error conditions are being handled. See: https://github.com/ooni/probe/issues/865 & https://github.com/ooni/probe/issues/926 ## OONI Probe measurement engine We introduced timing and TLS in the testing (and other low-level data collection), to ensure that OONI Probe tests are as useful as possible. Essentially, OONI Probe tests that can make use of this low-level information do so. This is an important enhancement (and an essential building block) to the Tor test and other tests. ## Data analysis We analyzed OONI measurements for the following: * Azerbaijan Internet Watch (partner): https://github.com/ooni/ooni.org/issues/332 * OTF Information Controls Fellow (hosted under OONI): https://github.com/ooni/ooni.org/issues/331 * Research on the blocking of LGBTQI sites worldwide: https://github.com/ooni/backend/issues/224 ## OONI backend We only had one major new incident to deal with in January 2020, which is documented here: https://github.com/ooni/sysadmin/issues/422 We had a relapse of an old incident (https://github.com/ooni/sysadmin/issues/128) and we worked on coming up with a fix to this here: https://github.com/ooni/backend/issues/300 ## Published OONI FAQ We published a Frequently Asked Questions (FAQ) section on our website: https://ooni.org/support/faq/ Through the OONI FAQ, we aim to address the most frequently asked questions that we have received from community members over the last years. The questions fall under the following areas: * About OONI * OONI Probe * Testing websites * OONI data * OONI Explorer We aim to continue to update the OONI FAQ on an ongoing basis, and we encourage further community feedback. ## Published OONI Glossary We published an OONI Glossary on our website: https://ooni.org/support/glossary This glossary is meant to cover terms that are commonly used in the OONI-verse, within OONI apps, documentation, and research reports. As a result, this glossary is quite OONI-specific. That said, it also includes a variety of terms that are commonly used by many other projects and may therefore be useful to others in the broader internet freedom community. Similarly to the OONI FAQ, we aim to continue to improve upon and update the OONI Glossary on an ongoing basis. We encourage further community feedback, and suggestions can be shared directly on GitHub: https://github.com/ooni/ooni.org ## Collaboration with Netalitica We reviewed the test list updates by Netalitica researchers and opened pull requests for the following test lists: * Turkmenistan: https://github.com/citizenlab/test-lists/pull/552 * Uzbekistan: https://github.com/citizenlab/test-lists/pull/553 * Jordan: https://github.com/citizenlab/test-lists/pull/554 * China: https://github.com/citizenlab/test-lists/pull/555 We also reviewed Netalitica updates to the Russian (https://github.com/citizenlab/test-lists/pull/557) Turkish and Iranian (https://github.com/citizenlab/test-lists/pull/564) test lists. ## Organization of IFF Internet Measurement Village This year OONI is co-organizing an Internet Measurement Village during the last 2 days of the Internet Freedom Festival (IFF) in Valencia, Spain. We reached out to several other measurement projects, inviting them to co-host the Internet Measurement Village with us. Throughout January 2020, we coordinated with the IFF organizers and with the other Internet Measurement Village members on logistics, and we organized and hosted two brainstorming calls. We also collected session ideas from community members, based on which we are creating the agenda for the Internet Measurement Village. ## Organization of OONI Partner Gathering In July 2017, we organized and hosted the first OONI Partner Gathering: a two-day event that brought all of our partners from around the world together to share skills and knowledge around censorship measurement. We plan to host the next OONI Partner Gathering in 2020! To this end, we wrote and submitted funding proposals, organized relevant logistics, and worked on updating relevant budgets. ## Community activities ### OONI presentation at the Nexa Center On 22nd January 2020, Arturo presented OONI and discussed censorship findings from 2019 at the Nexa Center for Internet and Society in Turin, Italy. Information about his presentation is available here: https://nexa.polito.it/lunch-75 ### Community meeting We facilitated the monthly OONI Community Meeting on 28th January 2020 on our Slack channel (https://slack.ooni.org/) during which we discussed: 1. Updates from the OONI team 2. Setting up a proxy for OONI Probe Android and iOS 3. Maxmind licensing problems ## Userbase In January 2020, OONI Probe was run 8,142,429 times from 5,307 different vantage points in 206 countries around the world. This information can also be found through our measurement stats on OONI Explorer (see chart on monthly coverage worldwide): http://explorer.ooni.org/ ~ The OONI team. -- Maria Xynou Research & Partnerships Director Open Observatory of Network Interference (OONI) https://ooni.org/ PGP Key Fingerprint: 2DC8 AFB6 CA11 B552 1081 FBDE 2131 B3BE 70CA 417E

1 0

check.torproject.org IP address change and server move
by Antoine Beaupré 04 Feb '20

04 Feb '20

Hi, Today, at around 19:49:00UTC, the IP address of check.torproject.org (AKA chiwui.torproject.org, TorDNSel and so on) has been changed. The service was using two IP addresses, which were changed as follows: 138.201.14.212 became 116.202.120.176 138.201.14.213 became 116.202.120.177 This IP change should be transparent to our users, unless you have hardcoded one of those IP addresses somewhere, which you should generally avoid for exactly that kind of situation. This work is part of a larger effort to replace old hardware in the torproject.org infrastructure. In particular, this is part of decomissioning an old KVM host (textile.torproject.org AKA kvm1). The old server is still present in case the new one is showing signs of problems, but preliminary tests show that everything is working correctly. Details of the transfer are available in ticket #31686 in Trac: https://trac.torproject.org/projects/tor/ticket/31686 The old server will be decomissionned in one week from now, on february 11th, unless significant problems are reported with the new server. No further disruptions are expected for this transition in the short term. Total outage was about an hour, intermittently. Thanks for your attention, A. -- Antoine Beaupré torproject.org system administration

1 0

Fwd: [tor-internal] IFF2020 Ticket vouchers
by Gaba 04 Feb '20

04 Feb '20

Hi! Does anybody here want a ticket for IFF in 2020? cheers, gaba [0] https://internetfreedomfestival.org/ -------- Mensaje reenviado -------- Asunto: [tor-internal] IFF2020 Ticket vouchers Fecha: Mon, 27 Jan 2020 19:18:15 +0100 (CET) De: Pili Guerra <pili(a)torproject.org> Hi everyone, We have some ticket vouchers available for the Internet Freedom Festival 2020 for Tor people and friends. Please let me know if you or your organisation would like to attend and how many tickets you would like and we’ll see what we can do… :) Thanks! 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

Tor Talk - NetDev 0x14, March 17th-20th 2020
by David Goulet 04 Feb '20

04 Feb '20

Greetings! Some good news. Rob Jansen and I have submitted a talk to NetDev 0x14 (https://netdevconf.info/0x14/) which has been accepted! https://netdevconf.info/0x14/session.html?talk-reducing-kernel-queuing-dela… https://twitter.com/netdev01/status/1224690477926055936 The conference white paper is still not publicly available but will be by the time the conference starts on March 17th 2020. Come see us in Vancouver! It is _just_ before the IETF meeting starting on the 21st ;). Cheers! David -- Bbbgg4u8CrNOEpbT98JqIsuQesh4Pr607DGrz6pE1F8=

1 0

Poll for the next Global South meeting
by cy63113 04 Feb '20

04 Feb '20

[EN] Hi Tor friends, last week we had very few people attending our monthly Global South meeting. So I decided to open a poll to decide which day is best for our next meeting. Please respond by February 15th. https://framadate.org/tor-global-south Cheers, [ES] Hola amigos de Tor, En la semana pasada tuvimos muy pocos participantes en nuestro encuentro mensual del Global South. Asi que decidi abrir una votación para que podamos encontrar un mejor dia para el proximo encuentro. Les pido el favor de contestar hasta el dia 15 de febrero https://framadate.org/tor-global-south <https://framadate.org/tor-global-south> Abrazos, [PT-BR] Olá amigs do Tor, Na semana passada, tivemos muito poucas pessoas participando da reunião mensal do Global South. Por isso, decidi abrir uma votação para saber qual dia vocês acham melhor para a nossa próxima reunião. Por favor, responda até 15 de fevereiro. https://framadate.org/tor-global-south <https://framadate.org/tor-global-south> Abraços, -- Cybelle DC8F 1F4C 9167 049F 7AA1 0BD6 2FB3 B0C9 F369 34C5 https://keybase.io/cy63113 @cyb3113

1 0

Network health meeting notes, 3 Feb 2020
by Georg Koppen 04 Feb '20

04 Feb '20

Hello! Yesterday, we held our first weekly meeting related to network health. For those of you who missed it (or just wanted to recap the meeting), the IRC log can be found on: http://meetbot.debian.net/tor-meeting/2020/tor-meeting.2020-02-03-18.59.log… Here comes what we were up to in the previous week(s) and what we plan to work on in the coming week: GeKo: Last week: * mostly away at the Mozilla All hands meeting * worked a bit on the DNS exit failure ticket (#32864) * getting up to speed on DocTor to help with #33067 * team planning This week: * work more on #32864 to refine test based on feeback (https://lists.torproject.org/pipermail/network-health/2020-January/000456.h…) * fix #33067 * get up to speed on sbws to be able to help with code reviews dgoulet: Last week(s): * Moved a bunch of code to dip.tpo related to health team. This week: * The usual bad-relays reject. Gus: Last week: * Talked with RotationMatrix about GoodBad ISPs new page in community portal. We were thinking to export data from metrics and work in a snapshot to suggest good ISPs. (We -- network health -- should probably discuss that in another meeting) This week: * Coming back from FOSDEM * We had a Tor meetup this saturday in FOSDEM, we didn't have too many people running relays, but the room was full. * Organizing a meetup with relay operators in Berlin, Germany on Thursday (announcing soon) * Working on Tor Legal FAQ with Cleopatra: https://trac.torproject.org/projects/tor/ticket/32934 Gaba (Feb 3): Last week: * fosdem * meeting about sbws's roadmap This week: * help with sbws's proposal for funding During the week we plan to finish our roadmapping efforts (the pad for that moved[1]) so we can discuss the result at the next weekly meeting and make changes where we think that's necessary. Georg [1] https://pad.riseup.net/redirect#https%3A//pad.riseup.net/p/network-health-t…

1 0

Anti-censorship team monthly report: January 2020
by Philipp Winter 03 Feb '20

03 Feb '20

Hi all, Here's what the anti-censorship team has been up to in January 2020: Snowflake ========= * Debugged and wrote a Tor Browser patch to fix throughput issues with Snowflake on Windows. <https://bugs.torproject.org/32870> <https://bugs.torproject.org/31971> * Started implementing a feature for proxies to conduct throughput tests before polling. <https://bugs.torproject.org/32711> * Continued Snowflake network health measurements and analysis. <https://bugs.torproject.org/32545> * David built a prototype that integrates Turbo Tunnel in Snowflake. Take a look at his detailed technical summary: <https://lists.torproject.org/pipermail/anti-censorship-team/2020-February/0…> GetTor ====== * Fixed a bug in GetTor's email responder. <https://bugs.torproject.org/32906> * Got GetTor's Gitlab distributor back up and running. <https://bugs.torproject.org/32711> * Moved GetTor's Github repository and got it up and running. <https://bugs.torproject.org/32977> * Modified GetTor to hand out localized binaries. <https://bugs.torproject.org/33002> * Fixed up GetTor's tests to run locally. <https://bugs.torproject.org/33004> * Filed a ticket on GetTor's problematic use of rate limiting. <https://bugs.torproject.org/33123> BridgeDB ======== * Damian generously spent a lot of time and effort getting BridgeDB very close to supporting Python 3. A handful of issues remain, but the bulk of the code base now support Python 3. <https://bugs.torproject.org/30946> * Started working on a patch that allows BridgeDB to test its bridges using bridgestrap. The idea is that broken bridges are logged (allowing us to inform the operator) and aren't handed out to users. <https://bugs.torproject.org/31874> * Filed a ticket to display BridgeDB's distribution bucket for a bridge on Relay Search. <https://bugs.torproject.org/33008> * Improved BridgeDB's CAPTCHAs. We modified gimp-captcha (the script that BridgeDB uses to generate CAPTCHAs) to make the CAPTCHAs easier to solve. Our BridgeDB usage metrics reveal that the success rate of our users increased from ~58% to ~87% after we deployed the new CAPTCHAs. Take a look at the following comment for a more in-depth analysis: <https://bugs.torproject.org/24607#comment:13> It's still not perfect but it's a step forward. <https://bugs.torproject.org/24607> Bridges ======= * Coordinated the set up of a new default bridge in Denmark. The bridge speaks both IPv4 and IPv6. Thanks to Toke Høiland-Jørgensen for running this new default bridge! <https://bugs.torproject.org/32891> * We did a retrospective analysis of our bridge campaign from September 2019. In particular, we tested how many bridges were still online (61%) and we sent an email to all operators. We thanked the ones who are still running a bridge and we asked the ones whose bridge vanished what went wrong. <https://bugs.torproject.org/33007> Outreach ======== * Philipp gave a talk at FH Hagenberg on the Tor network and censorship resistance: <https://www.fh-ooe.at/campus-hagenberg/die-fakultaet/aktuelles/news/news/in…> Approximately 80-100 people attended -- mostly students but also a handful of faculty members and visitors. Almost all have heard of Tor before and most have used it in the past. There were plenty of questions at the end, and the event stopped before Philipp was able to answer them all. All Tor stickers were gone almost instantly! Miscellaneous ============= * Added go.mod and go.sum to bridgestrap. <https://dip.torproject.org/phw/bridgestrap/commit/0e33599d6e6d1c0a809d5c59c…> * Coordinated with OONI on their new Tor test and its user interface. <https://github.com/ooni/backend/issues/305> <https://github.com/ooni/probe/issues/967> * Made two minor fixes to obfs4portscan (the service behind <https://bridges.torproject.org/scan/>): 1. Made it clear that the service supports IPv6 and expects IPv6 addresses in square bracket notation. 2. Made the service use GET instead of POST requests, to make it easier to hand people clickable links for their bridge. * We roadmapped the following three months, ranging from February to April 2020. Check out our team's wiki page for the goals of this roadmapping period: <https://trac.torproject.org/projects/tor/wiki/org/teams/AntiCensorshipTeam#…> * Lots of work on an NSF "Transition to Practice" grant we have been working on.

1 0