tor-project February 2020

tor-project@lists.torproject.org

23 participants
48 discussions

Anti-censorship meeting notes, 6 Feb 2020
by Philipp Winter 06 Feb '20

06 Feb '20

Here's our meeting summary: <http://meetbot.debian.net/tor-meeting/2020/tor-meeting.2020-02-06-17.59.html> And here's our meeting pad: Anti-censorship work meeting pad -------------------------------- Next meeting: Thursday February 6th 18:00 UTC Weekly meetings, every Thursday at 18: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. For 2020 Q1, the trac keyword is anti-censorship-roadmap-2020Q1 * The anti-censorship team's wiki page: https://trac.torproject.org/projects/tor/wiki/org/teams/AntiCensorshipTeam * Past meeting's notes can be found at: https://lists.torproject.org/pipermail/tor-project/ * 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 ------------------------- --- February 6th 2020 --- ------------------------- == Announcements == * == Discussion == * Brainstorm if we want a GetTor rate limit (#33123), and if so, how we should implement it? * The Tor Browser team mentioned wanting to discuss Tor Browser with Snowflake * Team retrospective (add what went well and what can be improved and +1 on other items you agree with) (over what time period?) * What went well? * We have increasingly clear responsibilities about who takes care of what. * For many projects we now have more than one maintainer, which minimises single points of failure. * Code review has been timely and of high quality. * Our survival guides are very helpful and reduce anxiety. * Interaction with volunteers have been going well. Our team is growing! * What can be improved? * We need to get better at presenting our work to users. * Let's do more blog post about software releases, and maybe "ask us anything" types of posts. * We also need posts like "the state of circumvention in China" * We're a bit ouf of the loop on what other organisations are working on related to anti-censorship. * We need to stay updated on recent studies, third party tools, and concerns that users have. == Actions == * Karsten is wondering what OONI data from the "Tor Test" should go on Metrics: * https://trac.torproject.org/projects/tor/ticket/32126#comment:4 == Interesting links == * https://magma.lavafeld.org * "An open-licensed, collaborative repository that provides the first publicly available research framework for people working to measure information controls and online censorship activities. In it, users can find the resources they need to perform their research more effectively and efficiently." * https://tools.ietf.org/html/draft-chow-httpbis-proxy-discovery-00 * https://tools.ietf.org/html/draft-nottngham-web-proxy-desc-01 == Updates == 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: (last updated before 2020-01-09) 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 (2020-02-06): * Reviewed #33002 * Again, more work on porting BridgeDB to Python 3. * Filed #33122 for GetTor; realised that the problem actually was #33123. * Investigated how BridgeDB's new CAPTCHAs affect both users and bots (#24607). * Approved blog comments. * Compiled team report for January. * A bit more grant writing (fixed references and added my bio). * Addressed feedback for #31872 and closed ticket. Filed #33145 as follow-up ticket. * Offered t-shirts to our default bridge operators. * Asked around who runs noisebridge's default bridge for the umpteenth time. * Fixed a synchronisation issue in bridgestrap and wrote unit tests for it. * Merged #31427 and released BridgeDB 0.9.3. * Suggested a fix for #30941. * Summarised the current state of private distribution in #28526. * Learned more about building docker images for multiple architectures, paving the way for a Raspberry Pi image (#33088, #32860). * Booked flight to Austria to give talk at securityforum.at. Talk title is "Better online security and privacy with the Tor network" * Tried to get ahold of the docker "torproject" organisation which will allow us to publish official docker images (#33162). * Someone registered it five years ago and didn't do anything with the account :/ Next week: * Hopefully finish Python 3 port * Write a summary of our current BridgeDB distribution mechanisms and brainstorm new ones Help with: * #30941 * #32860 Gaba: (out at Tor meetup) Last week (Feb 3rd): * fosdem and sustain oss * sponsor 30 report * imported tickets into roadmap and added info to team wiki page: https://trac.torproject.org/projects/tor/wiki/org/teams/AntiCensorshipTeam This week (planned): * prioritize roadmap into gitlab cecylia (cohosh): last updated 2019-02-06 Last week: - deployed localization fix for gettor (#33002) - reviewed #33038, #31872, #31427, #19026 - implemented a fix for GetTor's rate limiter (#33123) - updated snowflake webextension with new translations - review of websocket conn overhall (#33144) - grant revisions - got caught up on turbotunnel and responded with some feedback - added some improvements to Snowbox This week: - UI mock up for snowflake throughput check (#32938) - started some recurring throughput tests for snowflake (#32545) - Aggregate and write up a report of snowflake throughput changes - send grant to some external reviewers - maybe pick up gettor email body localization ticket (#28233) - write some tests for #33123 - reviews of #30716 and #32860 Needs help with: - review of #31971 (from tor browser team, in progress) arlolra: 2020-02-06 Last week: - started on #19026 - read up on turbo tunnel Next week: - continue with #19026 Help with: - dcf: 2020-02-06 Last week: - turbo tunnel in Snowflake - https://lists.torproject.org/pipermail/anti-censorship-team/2020-February/0… - https://lists.torproject.org/pipermail/anti-censorship-team/2020-February/0… - https://lists.torproject.org/pipermail/anti-censorship-team/2020-February/0… - wrote up results of Azure data breach notification - https://lists.torproject.org/pipermail/anti-censorship-team/2020-February/0… - Snowflake refactoring and code quality improvements (#33144, thanks cohosh for review) - archived snowflake-webextension-0.2.1 Next week: - open ticket to deploy the turbotunnel Snowflake bridge - work on a Tor Browser package with turbotunnel Snowflake client - do Let's Encrypt upgrade for Snowflake bridge (#32964) Help with: cjb: 2019-02-06 Last week: - put up a v2 patch for #31011, still needs review - found out more about snowflake+android Next week: - thinking about offering help with snowflake+android, not sure whether we have a strong preference between using golang or JS for the proxy code Help with: - review of #31011 agix:2020-02-06 Last week: -Bumped into a few problems while trying to setup bridgedb Next week: -Solve the bridgedb issues and finally fix #31967 Help with: -What the process of closing a ticket looks like / How do I commit my changes to an open ticket -Issues I had setting up bridgedb

1 0

Metrics Team Meeting Notes, February 6th 2020
by Gaba 06 Feb '20

06 Feb '20

Hi! We had our weekly metrics team meeting today. The next one is going to be on February 13th at 1500 UTC. The pad for the meeting in 2020 is at https://pad.riseup.net/p/tor-metricsteam-2020.1-keep The log for the meeting is: http://meetbot.debian.net/tor-meeting/2020/tor-meeting.2020-02-06-15.12.log… And the agenda/notes: ------------------------------------- Agenda Thursday, February 6th, 15 UTC ------------------------------------- MOSS Objective 3 scope (#33076) (karsten) Needs to check with Mike Perry to be sure everybody is on the same page about the scope of that objective (the graphs that will be included) karsten cleans up Java/R code for making CDF-Relay-* graphs and provides it as metrics-tasks.git subdirectory for task-33076 or 77 together with a README. Torflow/sbws transition (#33077) (karsten) tickets for deploying sbws: https://trac.torproject.org/projects/tor/query?status=!closed&keywords=~sbw… Onionoo 8.0 announcement (karsten) karsten sends an announcemen to tor-project@ Exit scanner timeline (irl) https://people.torproject.org/~irl/exitscan.html Announcement: Simply Secure starting to work on metrics portal (user research and design). They will be interviewing people for their user research. Anything to bring to the network health team's plate for the next 3 months? (thinking about onionperf & scalability) Talking more about this on Monday at our roadmap meeting. Needs review tickets: https://trac.torproject.org/projects/tor/query?status=needs_review&componen… Defect tickets: https://trac.torproject.org/projects/tor/query?status=accepted&status=assig… Roadmap (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 0

Research/Scalability/Perf Progress in January
by Mike Perry 05 Feb '20

05 Feb '20

As part of my new role as Tor's Research Janitor, I'm a bit more detached from the network team, but still working with them, and also working more with several other teams. Isa suggested that I write monthly progress reports here instead of at all those meetings. This seems reasonable to me. The meeting fatigue struggle is real. Planned for January: - Congestion control review - Mozilla All Hands meeting in Berlin - Research Janitor role description draft + review - Metrics roadmap planning assistance Actually did in January: - Read a shit-ton about the congestion control history of TCP and Tor - Wrote this epic mail about congestion control options for Tor: https://lists.torproject.org/pipermail/tor-dev/2020-January/014140.html - Attended the Mozilla All Hands meeting in Berlin - Reviewed Cecylia's snowflake traffic analysis mail - Brainstormed Research Janitor roles, discussed them with folks - Started planning the Research Janitor's 2020 Goals - Helped roadmap the metrics team's onionperf improvements - Worked on cleaning up metrics to analyze Rob's relay experiment: https://lists.torproject.org/pipermail/tor-scaling/2019-December/000077.html (thread) February plans: - More metrics + graph analysis for Rob's experiment - Iterate on sbws eval metrics + graphs w/ Karsten - Funding proposal assistance - Tor Performance Pipeline R&D migration to gitlab Blockers: - Nothing stands in my way! At Risk of Dropping: - Fixing circpad bugs that impact external padding research - Various mails about circuit padding docs + research options -- Mike Perry

1 0

January Fundraising Report
by Sarah Stevenson 05 Feb '20

05 Feb '20

Hello from the Fundraising Team. Here is what we were up to in January. Please let us know if you have any questions. ## Grants Relationship building: In January we met with two major foundations that are not currently funding Tor - the Hewlett Foundation and Omidyar. The Hewlett Foundation focuses on policy work, so they are unlikely to fund Tor, but we hope they may be able to open doors to others in the foundation world. DRL: Tor: We received invitations to submit full proposals for two projects -- one for network scalability and one to expand our User Testing Program in partnership with Tails and Guardian Project. We’ll be working on these applications through February and submit them at the beginning of March. OONI: We submitted final proposal revisions for the Measuring Internet Censorship project. Nathan Cummings Foundation: We submitted an LOI to improve onion services and SecureDrop support in partnership with Freedom of the Press Foundation. Charles Stewart Mott Foundation: We submitted an LOI to the “strengthening civic spaces” track. Zcash Foundation: We officially submitted the Walking Onions proposal and talked how we can engage other stakeholders in funding this project. We have a meeting set with the Interchain Foundation next week to discuss this work. OTF: We received word that our Tor Browser proposal has moved to Advisory Council Review. Guerilla Foundation: We were informed that now is not the right time for the foundation to support Tor. Coming up: NSF Dark Decoys project, due ?? (rolling) Comcast Innovation Fund, due ?? (rolling) Open Source Center Catalytic fund, due February 23 DRL full proposal - Scalability, due March 6 DRL full proposal - Usability joint project, due March 6 Grand for the Web, due ?? (to be announced) ## EOY Campaign As we previously reported, the EOY campaign was a great success. You can read about our detailed efforts, successes, and lessons learned on the Fundraising Wiki [1]. We created this chart for our report to Mozilla to show month-to-month individual giving from 2015 to 2019 [2]. We’ve seen growth over all past years in most months. We saw a huge bump in May when we received a couple major gifts. ## Roadmap We worked on our 2020 Roadmap and created a public version [3]. This will be updated periodically throughout the year. ## Monthly Donors Every January we send receipts to monthly donors detailing their donations from the past year and let them know if they’ve qualified to receive a t-shirt or stickers. We now have 703 active Defenders of Privacy who generate over $8,000 of income each month. This is almost double the income we received from this group in January of 2019. ## Events We are planning a happy hour at EFF in March and hope to have 75 people in attendance. The target audience is potential major donors. Please let Sarah know if you have any suggestions for the invite list. While we are in San Francisco we will also have a booth at Bitcoin2020. They offered us a free sponsorship and Isa and Roger will be speaking as well. We are also planning a lunch for foundations in April in NYC. [1] https://trac.torproject.org/projects/tor/wiki/org/teams/FundraisingTeam/Cam… <https://trac.torproject.org/projects/tor/wiki/org/teams/FundraisingTeam/Cam…> [2] https://trac.torproject.org/projects/tor/attachment/wiki/org/teams/Fundrais… <https://trac.torproject.org/projects/tor/attachment/wiki/org/teams/Fundrais…> [3] https://trac.torproject.org/projects/tor/wiki/org/teams/FundraisingTeam/Roa… <https://trac.torproject.org/projects/tor/wiki/org/teams/FundraisingTeam/Roa…>

1 0

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

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

tor-project February 2020