- tor-project - lists.torproject.org

Anti-censorship team meeting notes, 2023-04-06
by Shelikhoo 06 Apr '23

06 Apr '23

Hey everyone! Here are our meeting logs: http://meetbot.debian.net/tor-meeting/2023/tor-meeting.2023-04-06-15.59.html And our meeting pad: Anti-censorship work meeting pad -------------------------------- ------------------------------------------------------------------------------------ THIS IS A PUBLIC PAD ------------------------------------------------------------------------------------ Anti-censorship -------------------------------- Next meeting: Thursday, April 13 16:00 UTC Weekly meetings, every Thursday at 16:00 UTC, in #tor-meeting at OFTC (channel is logged while meetings are in progress) == Goal of this meeting == Weekly check-in about the status of anti-censorship work at Tor. Coordinate collaboration between people/teams on anti-censorship at the Tor Project and Tor community. == Links to Useful documents == * Our anti-censorship roadmap: * Roadmap: https://gitlab.torproject.org/groups/tpo/anti-censorship/-/boards * The anti-censorship team's wiki page: * https://gitlab.torproject.org/tpo/anti-censorship/team/-/wikis/home * Past meeting notes can be found at: * https://lists.torproject.org/pipermail/tor-project/ * Tickets that need reviews: from sponsors, we are working on: * All needs review tickets: * https://gitlab.torproject.org/groups/tpo/anti-censorship/-/merge_requests?s… * Sponsor 96 * https://gitlab.torproject.org/groups/tpo/-/milestones/24 * Sponsor 139 <-- hackerncoder, irl, joydeep, meskio, emmapeel working on it * https://pad.riseup.net/p/sponsor139-meeting-pad == Announcements == == Discussion == * Update on Analysis of speed deficiency of Snowflake in China, 2023 Q1 https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snow… * after a lot of research the proposed solution is to enable datagram transport on webrtc to deal with the packet loss situation * that will convert webrtc into an unreliable channel, and snowflake will add reliablity with kcp * (NO update from shell @ Apr 6) == Actions == == Interesting links == * https://opencollective.com/censorship-circumvention/projects/snowflake-dail… == Reading group == * We will discuss "Lox: Protecting the Social Graph in Bridge Distribution" on 2023 May 18 * https://cypherpunks.ca/~iang/pubs/lox-popets23.pdf * Questions to ask and goals to have: * What aspects of the paper are questionable? * Are there immediate actions we can take based on this work? * Are there long-term actions we can take based on this work? * Is there future work that we want to call out in hopes that others will pick it up? == Updates == Name: This week: - What you worked on this week. Next week: - What you are planning to work on next week. Help with: - Something you need help with. cecylia (cohosh): last updated 2023-03-30 Last week: - enabled wasm target for rust in tor-browser-build - https://gitlab.torproject.org/tpo/applications/tor-browser-build/-/issues/4… - helped debug blocking of Snowflake in TM - https://gitlab.torproject.org/tpo/anti-censorship/censorship-analysis/-/iss… - discussed the problem of deciding whether a bridge is blocked or not - took a look at memory issues for the Snowflake proxy - https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snow… This week: - Lox tor browser integration - fix conjure issues found by code audit Needs help with: dcf: 2023-04-06 Last week: - wrote notes on WebRTC unreliable data channels https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snow… - made graphs of DTLS packet losses in China https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snow… - snowflake CDN bookkeeping https://gitlab.torproject.org/tpo/anti-censorship/team/-/wikis/Snowflake-co… - revised snowflake-server listen error check fix and merged it https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snow… - documented more cdn.sstatic.net anomalies in Iran in March 2023 https://gitlab.torproject.org/tpo/anti-censorship/team/-/issues/115#note_28… - wrote the March 2023 update for the snowflake-01 Open Collective https://opencollective.com/censorship-circumvention/projects/snowflake-dail… - wrote a sync.Pool performance optimization for snowflake QueuePacketConn and started bridge-side CPU and RAM measurements in advance of a test deployment https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snow… - made a graph of snowflake users from Russia since the DTLS fingerprint fix (Hello Verify Request) in Tor Browser 12.0.3 (still awaiting an Orbot release) https://gitlab.torproject.org/tpo/anti-censorship/censorship-analysis/-/iss… Next week: - migrate goptlib to gitlab https://gitlab.torproject.org/tpo/anti-censorship/team/-/issues/86#note_282… (for real) - open issue to have snowflake-client log whenever KCPInErrors is nonzero https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snow… - parent: https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snow… - open issue to disable /debug endpoint on snowflake broker Help with: meskio: 2023-04-06 Last week: - AFK time Next week: - webtunnel integration in rdsys Shelikhoo: 2023-04-06 Last Week: - [Merge Request Awaiting] Add SOCKS5 forward proxy support to snowflake (snowflake!64) - [Research] HTTPT Planning https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/http… - Comment on S96 User Research Risk Assessment - Comment on various grant proposal - Write grant report - Fix Telegram Bridge Distributor responding with a blank message https://gitlab.torproject.org/tpo/anti-censorship/rdsys/-/issues/158 - Work on TPA-RFC-53: consider propagating 2FA everywhere, maybe at the April Tor Meeting - X~X time was mostly spent on urgent task Next Week: - [Research] WebTunnel planning (Continue) - Try to find a place to host another vantage point - container image for webtunnel - consider propagating 2FA everywhere, maybe, at the April Tor Meeting (https://gitlab.torproject.org/tpo/tpa/team/-/issues/41083#note_2884138) - logcollector altert system - webtunnel document for proxy opertator onyinyang: 2023-04-06 Last week: - Did a deep dive into rdsys to understand how it is handling `new`, `changed`, `gone` resources some results/discussion here: https://gitlab.torproject.org/tpo/anti-censorship/lox/lox-overview/-/issues… - updated Lox library, rdsys-backend-api and lox distributor to handle new and changed resources in a way that is more aligned with rdsys' behaviour - added some preliminary documentation: https://gitlab.torproject.org/tpo/anti-censorship/lox/lox-overview/-/wikis/… This week: - work on handling `gone resources` in a more appropriate way for Lox as outlined here: https://gitlab.torproject.org/tpo/anti-censorship/lox/lox-overview/-/issues… -If time: Start implementing a function in lox distributor/lox library to handle syncing of Lox bridgetable Needs help with: (medium term) Question 1: re: `gone` resources: under what circumstances should a `gone` bridge be replaced? - If a bridge is `gone` due to bandwidth issues or descriptors not being published, should they be replaced with working bridges in a Lox bucket ? Question 2: How easily can a censor manipulate the bridgepool/bridges to create a `gone` resource? - Does replacing bridges, especially at the untrusted user level, create an enumeration risk? My thought is that `gone` bridges should be replaced if they are determined to be unusable into the future (not just temporarily down) and the bucket risks becoming "unreachable" and requiring users to move to a new bucket. Maybe this should only be true for trusted users though? (long term) - brainstorming grouping strategies for Lox buckets (of bridges) and gathering context on how types of bridges are distributed/use in practice. Question: What makes a bridge useable for a given user and how can we encode that to best ensure we're getting the most appropriate resources to people? 1. Are there some obvious grouping strategies that we can already consider? e.g., by pt, by bandwidth (lower bandwidth bridges sacrified to open-invitation buckets?), by locale (to be matched with a requesting user's geoip or something?) 2. Does it make sense to group 3 bridges/bucket so trusted users have access to 3 bridges (and untrusted users have access to 1)? More? Less? Itchy Onion: 2023-03-22 Last week: - Closed #40252 (NAT probetest for standalone proxy) - Closed #40265 (mac user reporting standalone proxy complaning about broker cert) - Worked on #40231 (Client sometimes send offer with no ICE candidates) This week: - Tested and created a potential broker security issue (#40266) - Stil working on #40231 -- validate SDP contains candidate at the "/client" and "/answer" endpoints broke almsost all of the unit tests hackerncoder: 2023-03-09 last week: Next week: - getting ooni-exporter to work with torsf (snowflake) - ooni-exporter web_connectivity - work on "bridgetester"? - how does Iran block bridges

1 0

Joydeep's monthly status report for March 2023
by Joydeep Sen Gupta 06 Apr '23

06 Apr '23

Hello everyone! Here are my updates from March. In total, I resolved 521 tickets across our email, telegram, whatsapp and signal user support channels. Most of my work was concentrated around user support work helping users in regions where Tor is censored. Apart from that, we got a few reports of a Windows bug[0], pretty much coninciding with the Tor Browser 12.0.4 stable release. Timeframe: 01 - 31 March 2023 # Frontdesk -613 RT tickets created -560 RT tickets resolved Most frequent tickets by numbers: 1. 252 RT Tickets: Private Bridge requests from China. 2. 23 RT Tickets: How to use a Tor Bridge in Russia? 3. 13 RT tickets: Responses from our relay operator community for the obfs4 bridge campaign to help users in Turkmenistan connect to Tor[1] 4. 6 RT Tickets: Circumventing censorship with Tor in Iran. 5. 3 RT Tickets: Unable to launch Tor Browser on Windows[0] # Telegram, WhatsApp and Signal Support channel -604 tickets resolved Breakdown: -513 tickets on Telegram -67 tickets on WhatsApp -24 tickets on Signal The most frequent tickets we received have been about: 1. 139 tickets: Circumventing censorship in Russia. 2. 109 tickets: Circumventing censorship in Turkmenistan. 3. 52 tickets: Circumventing censorship in Iran. 4. 26 tickets: Circumventing censorship in China. # Tor Forum Most popular topics in the Support category (in terms of number of views): 1. "Anyone experiencing problems with Snowflake proxy?"[2] 2. "I Have Seen 0 Unique Clients - Why?"[3] 3. "(Tor) Browser not responding"[4] 4. "Is there an index for onion domains?"[5] 5. "Relay or Bridge"[6] Thanks! --Joydeep [0]: https://forum.torproject.net/t/tor-setup-application-not-launching/7069 [1]: https://lists.torproject.org/pipermail/tor-relays/2023-March/021100.html [2]: https://forum.torproject.net/t/anyone-experiencing-problems-with-snowflake-… [3]: https://forum.torproject.net/t/i-have-seen-0-unique-clients-why/6921 [4]: https://forum.torproject.net/t/browser-not-responding/7116 [5]: https://forum.torproject.net/t/is-there-an-index-for-onion-domains/6893 [6]: https://forum.torproject.net/t/relay-or-bridge/6881

1 0

cohosh's monthly status report, March 2023
by Cecylia Bocovich 06 Apr '23

06 Apr '23

Hi! This is my status report for contract work done in March 2023. # Reputation-based bridge distribution - Enabled the wasm target for the rust compiler in tor-browser-build https://gitlab.torproject.org/tpo/applications/tor-browser-build/-/merge_re… - Made progress on the client-side integration with Tor Browser https://gitlab.torproject.org/cohosh/tor-browser/-/merge_requests/1 - Reviewed and merged updates to Lox wasm bindings https://gitlab.torproject.org/tpo/anti-censorship/lox/lox-wasm - Helped fix a bug in rdsys that occurred after a recent upgrade https://gitlab.torproject.org/tpo/anti-censorship/bridgedb/-/merge_requests… - Adapted ResourceStream to implement the Stream trait rather than the Iterator trait in rdsys-backend-api https://gitlab.torproject.org/cohosh/rdsys-backend-api - Reviewed and merged work on the rdsys distributor for lox https://gitlab.torproject.org/tpo/anti-censorship/lox/lox-distributor # Snowflake Web Extension - Reviewed and merged several contributions

1 0

Nina’s Monthly status report for March’23
by Nina 04 Apr '23

04 Apr '23

Hi! This is my report for March 2023. In that month, I resolved 527 tickets: On Telegram (@TorProjectSupportBot) - 362 On RT (frontdesk@tpo) - 143 On WhatsApp (+447421000612) - 16 and Signal (+17787431312) - 6. The usual requests I deal with are helping Russian-speaking users with censorship circumvention and troubleshooting around it. This month I worked a lot on collecting information and getting feedback from our users. Among other requests are helping Windows users to install and use Tor Browser. The main issues are: - Tor Browser and antivirus, - non-ASCII symbols in folders' names - https://gitlab.torproject.org/tpo/core/tor/-/issues/10416 Another regular issue across various OS is using Tor Browser with bridges and VPN simultaneously. This month there were several requests regarding Tor Browser permissions and tracking options, which are present in FireFox, but disabled in Tor Browser.

1 0

Rhatto's Monthly Status Report, March 2023
by rhatto 03 Apr '23

03 Apr '23

Hi all :) This is my monthly status report for March 2023 with the main activities I have done during the period. ## 0. Research * Basic quality assurance check for Onion Service support in the Tor Browser. Results were sent to the Applications Team. * Started planning the Onion Plan Session for the Costa Rica meeting: https://gitlab.torproject.org/tpo/onion-services/onionplan/-/issues/7 ## 1. Development Onionprobe, a test and monitoring tool for Onion Services: * Tests and metrics for X.509 certificates: https://gitlab.torproject.org/tpo/onion-services/onionprobe/-/issues/49 * MetricsPort support: https://gitlab.torproject.org/tpo/onion-services/onionprobe/-/issues/71 * PostgreSQL version handling for the Onionprobe monitor node: https://gitlab.torproject.org/tpo/onion-services/onionprobe/-/issues/70 * These as well as other features and bug fixes marks the release of Onionprobe 1.1.0: https://gitlab.torproject.org/tpo/onion-services/onionprobe/-/blob/main/Cha… EOTK, the Enterprise Onion Toolkit: * Pull request to upgrade Tor: https://github.com/alecmuffett/eotk/pull/111 terraform-aws-bc-eotk, a Terraform module for EOTK deployments on AWS: * Minor merge requests: Set keys/certs ownership and perms: https://gitlab.com/sr2c/terraform-aws-bc-eotk/-/merge_requests/3 Cleanup EOTK during startup: https://gitlab.com/sr2c/terraform-aws-bc-eotk/-/merge_requests/2 Restart EOTK once a week: https://gitlab.com/sr2c/terraform-aws-bc-eotk/-/merge_requests/1 ## 2. Support * Detailed Onionprobe documentation: https://tpo.pages.torproject.net/onion-services/onionprobe/ https://gitlab.torproject.org/tpo/onion-services/onionprobe/-/issues/19 * Ongoing Sponsor 123 deployments, monitoring and maintenance. ## 3. Organization * Helped with project proposals, planning, management and reporting. * Time spent (from the total available for Tor-related work): | Category | Percentage |---------------|------------ | Research | 6 | Development | 29 | Support | 29 | Organization | 36 |---------------|------------ | Total | 100 -- Silvio Rhatto pronouns he/him

1 0

Moving community/policies from git.tpo to gitlab.tpo
by gus 03 Apr '23

03 Apr '23

Hello Tor, Community Council and everyone, I created this ticket[1] to move "Community/Policies" from gitolite (git.torproject.org) to our GitLab instance (gitlab.torproject.org/tpo/community/policies.git) This means that the Tor Code of Conduct and other Community policies will have a new home[2]. Please let me know if something will break before we do this migration. Or if someone has other suggestions, we're open to discussion and proposals. cheers, Gus [1] https://gitlab.torproject.org/tpo/community/team/-/issues/66 [2] I imported the 'policies' repository. I'm planning to fix the group write permission and change the repo visibility to public: https://gitlab.torproject.org/tpo/community/policies

1 1

PieroV's Monthly Status Report, March 2023
by Pier Angelo Vendrame 03 Apr '23

03 Apr '23

Hi everyone! Here is my status report for March 2023. At the end of February, I was trying to fix the issues about RLBox reproducibly. So, at the beginning of March, I started from there and managed to solve the problem. As a result, we finally enabled RLBox in Tor Browser 12.5a4 [0]. I also sent a PR to the upstream project, and it is part of the latest WASI SDK release. After that, I worked on the Tor Browser updater. I cleaned up a few macros and configuration options [2][3] first, and then I tried to split our updater patches to apply part of them also to the Base Browser part of the patchset [4]. They are part of the most delicate patches, so I needed to be extra careful. Therefore, I preferred reworking them while keeping the final diff as small as possible and postponing further improvements and refinements. I also learned to set up a mock update server, which gave me more confidence that my patches were correct. Then, I finally reviewed the msim's patches to make WebRTC buildable with MinGW [5]. He did an outstanding job on it. Also, this allowed us to find that Firefox IPC mechanisms have some problems when built with MinGW [6][7]. I definitely enjoyed diving into the crash we had and analyzing its root causes. Another task I had was checking the automatic outgoing connections in Base Browser and trying to block the remaining ones. At the end of the month, I restarted refactoring the remaining code from torbutton. While it has not been a standalone extension for many years, it kept living as an essential part of Tor Browser. However, we would like to modernize its code, drop all the XPCOM parts we can, and integrate it even more with the rest of our patches. We started a few months ago by moving inside the same repository as the browser and deprecating torbutton.git. However, the most disruptive changes will have to wait at least for 13.0 because we are in an advanced stage of 12.5. I expect to work on this in April since doing that before the next ESR update might make the transition easier. Then, we would like to start with the rebase on 115 when it reaches nighly, at the beginning of May. Best, Pier [0] https://gitlab.torproject.org/tpo/applications/tor-browser-build/-/issues/4… [1] https://github.com/WebAssembly/wasi-libc/pull/399 [2] https://gitlab.torproject.org/tpo/applications/tor-browser/-/issues/41647 [3] https://gitlab.torproject.org/tpo/applications/tor-browser/-/issues/41657 [4] https://gitlab.torproject.org/tpo/applications/tor-browser/-/issues/41668 [5] https://gitlab.torproject.org/tpo/applications/tor-browser/-/merge_requests… [6] https://gitlab.torproject.org/tpo/applications/tor-browser/-/issues/41489 [7] https://gitlab.torproject.org/tpo/applications/tor-browser/-/issues/41683

1 0

OONI Monthly Report: March 2023
by Maria Xynou 03 Apr '23

03 Apr '23

Hello, This email shares OONI's monthly report for March 2023. *# OONI Monthly Report: March 2023* Throughout March 2023, the OONI team worked on the following sprints: * Sprint 86 (1st-12th March 2023) * Sprint 87 (13th-31st March 2023) Our work can be tracked through the various OONI GitHub repositories: https://github.com/ooni Highlights are shared in this report below. *## Public launch of OONI Probe Web* In March 2023, the OONI team released OONI Probe Web: a new browser-based tool for measuring the blocking of websites. Run OONI Probe Web: https://probe-web.ooni.org/ We built OONI Probe Web in response to long-term community feedback, requesting a censorship measurement tool that can be run from a browser, without requiring the installation of any software. With OONI Probe Web, you will test the same types of websites as with the OONI Probe apps ( https://ooni.org/support/faq#which-websites-will-i-test-for-censorship-with…) Upon running OONI Probe Web, your test results will be published as open data in near real-time (https://ooni.org/data/) However, please note that OONI Probe Web is very limited in comparison to the OONI Probe apps ( https://ooni.org/install/) Due to limitations in the API available to web browsers, it’s not possible to run advanced experiments necessary for accurately detecting and characterizing website blocks from a browser. We therefore kindly ask you to not treat OONI Probe Web as a replacement for the OONI Probe apps, but as a complementary tool. We encourage you to run OONI Probe Web and contribute measurements, the analysis of which will help us improve upon OONI Probe Web on an ongoing basis. You can learn more about OONI Probe Web in our blog post: https://ooni.org/post/introducing-ooni-probe-web/ In preparation for the launch, we: * Switched the endpoints used by OONI Probe Web to production ( https://github.com/ooni/probe-web/pull/6) * Made several improvements to the copy and to the layout of the pages ( https://github.com/ooni/probe-web/pull/7) with special focus on the informed consent procedure; * Made changes to OONI Probe Web to ensure that it works better on mobile platforms (https://github.com/ooni/probe-web/pull/9) * Added support to the backend for analyzing OONI Probe Web measurements ( https://github.com/ooni/backend/pull/648) * Added support for filtering OONI Probe Web measurements inside of OONI Explorer (https://github.com/ooni/explorer/pull/847) * Updated the OONI Data Policy (https://github.com/ooni/ooni.org/pull/1347) *## Launched new OONI Explorer features and pages* In March 2023, we launched several new OONI Explorer features and pages. These include: * New domain-centric pages: https://explorer.ooni.org/domains * New network-centric pages: https://explorer.ooni.org/networks * New “Internet outage” charts (integrating IODA, Google traffic, and Cloudflare Radar data), available in each country-specific ( https://explorer.ooni.org/countries) and network-specific page ( https://explorer.ooni.org/networks) * New user feedback reporting mechanism, available through the “Verify” button in the banner of each OONI measurement page The user feedback reporting mechanism enables OONI Explorer users to submit feedback for each OONI measurement, helping the OONI team to improve OONI data quality. Using the user feedback reporting mechanism requires logging in with an email address (OONI Explorer user account). Email addresses are not stored. They are just required so that we can send you a login link. Leading up to the launch of the above, we wrapped up the relevant work. Specifically, we: * Added index pages for domains and networks that we have measurements for ( https://github.com/ooni/explorer/pull/830) * Finished applying the designs for the new domain and network pages ( https://github.com/ooni/explorer/pull/830) * Unified the appearance of the pre-existent pages by implementing new designs created by a UI/UX designer (updated the general countries page, each country page and several other components); * Released third-party data integration on network and country pages ( https://github.com/ooni/explorer/pull/831) * Released OONI Explorer user accounts and the user feedback reporting mechanism for measurements (https://github.com/ooni/explorer/pull/790) *## Published new OONI Explorer user guide* In March 2023, we published a new user guide for OONI Explorer: https://ooni.org/support/ooni-explorer OONI Explorer (https://explorer.ooni.org/) is the world's largest open dataset on Internet censorship, with new measurements published in near real-time. This user guide provides step-by-step instructions (with screenshots) on how to use OONI Explorer to investigate internet censorship worldwide. Through this guide, you will learn how to use OONI Explorer to: * Discover blocked websites and apps around the world * Access measurement data that can serve as evidence of internet censorship * Generate charts based on aggregate views of OONI data * Compare censorship across countries and networks * Filter measurements based on various parameters (such as country, ASN, date range, OONI Probe test, websites categories, domains, etc.) Upon reading this guide, we hope you will feel empowered to investigate internet censorship through the use of OONI Explorer. We thank all OONI Probe (https://ooni.org/install/) users worldwide who have contributed – and continue to contribute – measurements, shedding light on internet censorship. *## Published new documentation on interpreting OONI data* In March 2023, we published new documentation which explains how to interpret OONI data. You can access this documentation here: https://ooni.org/support/interpreting-ooni-data/ OONI data is open data on Internet censorship around the world, updated in real-time. With our new guide, you can learn how to interpret OONI data to monitor and respond to Internet censorship worldwide. *## Published new documentation on coordinating censorship measurement campaigns* In March 2023, we published a new guide through which you can learn how to coordinate OONI censorship measurement campaigns with your community. Read the guide here: https://ooni.org/support/ooni-censorship-measurement-campaigns Is your country preparing for elections? Did new blocks emerge during protests? Would you like to measure censorship in different regions in your country, or in different countries around the world? Community coordination can help with rapidly measuring and responding to Internet censorship events. Through our new guide, you can learn which steps you can take to organize censorship testing with other OONI Probe users. We also share a few examples of OONI censorship measurement campaigns led by groups in the internet freedom community. *## Published new OONI Outreach Kit* In March 2023, we published a new OONI Outreach Kit: https://ooni.org/support/ooni-outreach-kit/ Our Outreach Kit includes flyers, brochures, workshop slides & other resources that you can use as part of your OONI community engagement efforts! Specifically, the Outreach Kit includes: * OONI brochures: https://ooni.org/support/ooni-outreach-kit/#ooni-brochures * OONI Probe flyers and leaflets: https://ooni.org/support/ooni-outreach-kit/#ooni-probe-flyers-and-leaflets * OONI Explorer flyers: https://ooni.org/support/ooni-outreach-kit/#ooni-explorer-flyers * Internet censorship flyers: https://ooni.org/support/ooni-outreach-kit/#internet-censorship-flyers * OONI screencasts: https://ooni.org/support/ooni-outreach-kit/#ooni-screencasts * OONI workshop slides: https://ooni.org/support/ooni-outreach-kit/#ooni-workshop-slides * Other OONI resources: https://ooni.org/support/ooni-outreach-kit/#ooni-resources We hope you find these materials useful, and we thank you for your OONI community engagement efforts! We also thank Ura Design (https://ura.design/) for the beautiful design of the OONI Outreach Kit. *## Updated the Get Involved section of the OONI website* In light of the aforementioned publications, we edited the copy of the Get Involved page on the OONI website to provide updated information and links ( https://github.com/ooni/ooni.org/pull/1366/files) The updated version of the OONI Get Involved page can be viewed here: https://ooni.org/get-involved/ *## Published OONI documents translated into 5 languages* In March 2023, we published several OONI documents translated into 5 languages: Arabic, Farsi, Russian, Swahili, and Spanish. The translated OONI documents are: * OONI Frequently Asked Questions (FAQ): https://ooni.org/support/faq * OONI Glossary: https://ooni.org/support/glossary * Potential risks: https://ooni.org/about/risks/ Below we share links for the translated documents in each of the 5 languages. *### Arabic* Thanks to Ahmed Gharbeia, the following OONI documents are now available in Arabic: * OONI Frequently Asked Questions (FAQ): https://ooni.org/ar/support/faq * OONI Glossary: https://ooni.org/ar/support/glossary * Potential risks: https://ooni.org/ar/about/risks *### Farsi* Thanks to Miaan Group, the following OONI documents are now available in Farsi: * OONI Frequently Asked Questions (FAQ): https://ooni.org/fa/support/faq * OONI Glossary: https://ooni.org/fa/support/glossary * Potential risks: https://ooni.org/fa/about/risks *### Russian* Thanks to Tatyana Boldyreva, the following OONI documents are now available in Russian: * OONI Frequently Asked Questions (FAQ): https://ooni.org/ru/support/faq * OONI Glossary: https://ooni.org/ru/support/glossary * Potential risks: https://ooni.org/ru/about/risks *### Swahili* Thanks to Zaina Foundation, the following OONI documents are now available in Swahili: * OONI Frequently Asked Questions (FAQ): https://ooni.org/sw/support/faq * OONI Glossary: https://ooni.org/sw/support/glossary * Potential risks: https://ooni.org/sw/about/risks *### Spanish* Thanks to Katherine Pennacchio and Mariengracia Chirinos, the following OONI documents are now available in Spanish: * OONI Frequently Asked Questions (FAQ): https://ooni.org/es/support/faq * OONI Glossary: https://ooni.org/es/support/glossary The Risks document had already been translated to Spanish by Derechos Digitales: https://ooni.org/es/about/risks Huge thanks to the translators who helped make important OONI documents accessible to more communities worldwide! *## Published blog post on the analysis of failed OONI measurements* In March 2023, Gurshabad Grover (OTF Information Controls Research Fellow at OONI) and Simone Basso (OONI engineer) published a new post titled: "How we're improving OONI data quality: An analysis of failed measurements". Read this post here: https://ooni.org/post/improving-data-quality-analysis-of-failed-measurement… You may have noticed that some OONI measurements are annotated as "failed". This happens when the OONI Probe experiment fails to perform as expected (e.g due to bugs). To better understand why some OONI measurements fail, Gurshabad and Simone analyzed 100 of the most failed Web Connectivity measurements collected (during 3 days in June 2022) from India, Indonesia, and Pakistan (300 measurements in total). They found that Web Connectivity measurements failed to the following reasons: * Instance of internet censorship * Tested website was down * Tested website was misconfigured * Bugs Out of the 3 countries, they found that most failed measurements (more than 75%) from Pakistan and Indonesia were symptomatic of internet censorship. Based on this study, the authors identified some next steps for improving OONI data quality: https://ooni.org/post/improving-data-quality-analysis-of-failed-measurement… We encourage researchers to analyze failed OONI measurements and help us further improve OONI data quality. *## Published URL prioritization web interface* OONI’s smart URL list system ( https://ooni.org/post/ooni-smart-url-list-system/) prioritizes the testing of certain URLs over others. Currently, popular social media websites (which are frequently blocked around the world) are prioritized for testing the most globally. To enable the internet freedom community to review URL priorities and contribute feedback (i.e suggest URLs for testing prioritization), we published a new URL prioritization web interface: https://test-lists.ooni.org/prioritization To this end, we added support for displaying URL priorities in the Test Lists Editor interface (https://github.com/ooni/backend/pull/646) and we added a web form that enables community members to suggest URLs for prioritization (https://github.com/ooni/test-lists-ui/pull/72) *## OONI Probe Mobile* In March 2023, we continued to improve upon the OONI Probe mobile app. Specifically, we: * Continued to make improvements to the next OONI Probe Mobile release (3.8.0) based on feedback from internal testing; * Made the Android Manifest general enough based on community feedback ( https://github.com/ooni/probe/issues/1989) * Continued working towards ensuring that the OONI Probe iOS app does not crash when OONI backend services are down ( https://github.com/ooni/probe/issues/2201) * Continued working towards rewriting OONI Probe in Flutter ( https://github.com/ooni/probe/issues/2359) * Worked towards addressing a bug impacting status information in dark mode (https://github.com/ooni/probe/issues/2423) * Fixed bugs (https://github.com/ooni/probe/issues/2427, https://github.com/ooni/probe/issues/2428) *## OONI Run* We released a new stable version of OONI Run (v1.0.0: https://github.com/ooni/run/releases/tag/v1.0.0) which includes some of the improvements which are backward compatible with older versions of OONI Probe. These include support for using translations with a language selector, copy edits, updating software dependencies and several bug fixes. Following the release of OONI Run v1.0.0, we deployed it and made some improvements to the deployment process. We also merged the specification for the next generation of OONI Run which is going to be implemented over the course of the next year: https://github.com/ooni/spec/pull/249 *## OONI Probe CLI* We continued working on the OONI Probe CLI 3.17 release. While performing quality assurance, we noticed and fixed an issue that prevented mobile apps from taking advantage of the prototype richer input functionality exported by the OONI backend. We fixed this issue ( https://github.com/ooni/probe-cli/pull/1123) and released OONI Probe CLI 3.17.1 (https://github.com/ooni/probe-cli/releases/tag/v3.17.1) Based on a community request, we exported all the internal Go packages used by OONI Probe CLI (https://github.com/ooni/probe-cli) in the OONI Probe Engine (https://github.com/ooni/probe-engine) repository. We will semi-automatically update this repository after each minor release, to allow community members to import our internal implementation details from their applications and libraries written in Go. We merged the dslx package, which provides a composable high-level API for writing OONI experiments (https://github.com/ooni/probe/issues/2402) For additional information on this package, please take a look at the design document that explains this functionality in detail: https://github.com/ooni/probe-cli/blob/master/docs/design/dd-005-dslx.md We continued to investigate Android crashes caused by tor. We updated the fdsan-related issue we previously opened in February 2023 ( https://gitlab.torproject.org/tpo/core/tor/-/issues/40747) providing additional information on how the problem could be fixed in a way that works on both Unix and Windows systems. We gathered additional evidence regarding the pubsub_install crash and opened another issue in the tor issue tracker (https://gitlab.torproject.org/tpo/core/tor/-/issues/40774) *## Expanding OONI’s testing model to support richer testing input* We continued exploring the design space around passing richer input to experiments (https://github.com/ooni/ooni.org/issues/1295) by discussing internally a way to update the check-in API and the OONI Run v2 specification to support richer testing input. We aim to review and finalize this design document in the next development sprints and update the existing PoC. *## Creating a throttling measurement methodology* We specified and implemented an integration testing tool, called “netem”, to facilitate writing integration tests that simulate extreme throttling conditions (https://github.com/ooni/probe/issues/2424) The netem tool, which lives in its own GitHub repository (https://github.com/ooni/netem) uses GVisor to create user-space TCP/IP network stacks. When running integration tests, the traffic generated by OONI Probe uses its own GVisor stack. We route this traffic through network links written in software that simulate latency and losses. We started integrating netem ( https://github.com/ooni/probe/issues/2431) with the OONI Probe CLI repository (https://github.com/ooni/probe-cli/) *## OONI backend* Throughout March 2023, we continued to work on a series of backend improvements. Specifically, we: * Deployed the change to the fastpath to use fingerprints from GitHub ( https://github.com/ooni/pipeline/pull/407) * Implemented the publication of the URL prioritization listing in the API ( https://github.com/ooni/backend/pull/646) * Added an updater for ASN metadata to the pipeline ( https://github.com/ooni/pipeline/pull/414) * Implemented an API endpoint for mapping ASNs to AS organization names ( https://github.com/ooni/api/pull/326, https://github.com/ooni/backend/issues/635) * Added domain and network endpoints to the API ( https://github.com/ooni/backend/pull/641) * Added backend support to the MAT to accept multiple values in input parameters (https://github.com/ooni/api/pull/324, https://github.com/ooni/backend/issues/584) * Removed the “test_name” check from the list of measurements in the API ( https://github.com/ooni/backend/pull/647) * Merged the pipeline and API git repositories into one to simplify and speed up development (https://github.com/ooni/backend/pull/638) * Fixed the API integration test (after adding new columns to the fastpath) (https://github.com/ooni/api/pull/325) * Ensured that the rotation table history is maintained ( https://github.com/ooni/pipeline/pull/412) * Increased the worker count and simplified the queue in the fastpath ( https://github.com/ooni/backend/pull/650) * Fixed a bug affecting the platform field extraction in the fastpath ( https://github.com/ooni/backend/pull/652) * Ensured that the API uses the fastpath repo in CI ( https://github.com/ooni/backend/pull/649) * Cleaned and refactored the codebase ( https://github.com/ooni/backend/pull/645) * Implemented log collection on the monitoring host using Vector. *## Automating censorship detection and characterization based on OONI measurements* We made stable progress on the front of automating the detection and characterization of censorship based on OONI measurements. In March 2023, we focused on analyzing DNS level interference, as understanding the outcome of the DNS measurement is a prerequisite for the interpretation of the following measurements. Specifically, we implemented a DNS blocking analysis that is purely based on SQL queries and we set up a system to assess its accuracy by comparing it with blocking fingerprints. We experimented with applying machine learning algorithms to the DNS analysis. They present very promising cursory results and we will be exploring this avenue further. The outcomes of this experimentation and DNS analysis were presented internally to our team, as well as to external researchers in the network measurement field to request feedback. We also improved the validation of blocking fingerprints ( https://github.com/ooni/blocking-fingerprints/pull/6) and we removed a fingerprint that was leading to false positives ( https://github.com/ooni/blocking-fingerprints/pull/7) *## Improving the quality of test lists* To improve the quality of test lists, we created a prototype script for detecting and optionally automatically removing expired domains from the lists. We implemented this functionality inside the OONI Probe CLI repository (https://github.com/ooni/probe-cli/pull/1114) We will test and discuss this prototype with our partners to gather feedback and evaluate the next steps. For the time being, we decided to refrain from automatically removing expired domains because we found cases where expired domains redirect to other domains that are blocked ( https://github.com/citizenlab/test-lists/pull/1247) and, therefore, their automatic removal would result in missing cases of censorship. We also mined OONI data to identify URLs that were manually tested by OONI Probe users, and which are not currently included in the Citizen Lab test lists (https://github.com/ooni/ooni.org/issues/1228) Based on our analysis, we identified more than 1,000 URLs (from the last 3 months) which should be peer-reviewed (and categorized by country researchers/experts) before added to the test lists ( https://gist.github.com/hellais/14e75ce8b9d5cf04f78644c8e9f66554#file-mine-…) In the meanwhile, we added a few of those URLs to test lists ( https://github.com/citizenlab/test-lists/pull/1250) *## OONI interview for Roskomsvoboda’s Privacy Day event 2023* In January 2023, OONI’s Maria provided an interview for Roskomsvoboda’s Privacy Day 2023 event (https://2023.privacyday.net/) as part of which she discussed how people in Russia can participate in OONI censorship measurement. In March 2023, Roskomsvoboda published the interview in a blog post ( https://roskomsvoboda.org/post/maria-xynou-ooni/) and on their YouTube channel (https://www.youtube.com/watch?v=_yugAH26CK0) *## Community use of OONI data### Access Now’s press release on ongoing social media blocks in Ethiopia* In March 2023, Access Now published a press release urging Ethiopian authorities to stop blocking access to social media platforms. As part of this press release, they cite OONI measurements on the ongoing blocking of social media platforms in Ethiopia. Access Now’s press release is available here: https://www.accessnow.org/press-release/ethiopia-social-media-protest/ *### Sinar Project’s article on verifying website blocks with OONI Explorer* Our partner, Sinar Project, published an article (“Is the Website Blocked? Verifying Internet Censorship with OONI Explorer”) which explains how to verify the blocking of websites through the use of OONI Explorer. Their article is available here: https://imap.sinarproject.org/news/is-the-website-blocked-verifying-interne… *## Community activities### OONI workshop for election observers in Kazakhstan* On 9th March 2023, OONI’s Elizaveta facilitated an online workshop on coordinating OONI censorship measurement campaigns for election observers in Kazakhstan. Following this workshop, the participants created a Telegram chat to coordinate on OONI censorship measurement during Kazakhstan’s elections on 19th March 2023. *### MozFest 2023* On 22nd March 2023, OONI’s Arturo attended MozFest 2023 ( https://www.mozillafestival.org/) where he participated as a speaker on the panel “Co-Creating A Better Tech Future: Mozilla Data Futures Lab” ( https://schedule.mozillafestival.org/session/EMSW79-1) As part of his presentation, Arturo shared the activities OONI plans to do (in creating the next generation OONI Run) as part of the Mozilla Data Futures Lab 2023 cohort (https://foundation.mozilla.org/en/data-futures-lab/ ). *### DEMHACK 6 hackathon* On 25th and 26th March 2023, OONI’s Simone and Elizaveta mentored the team working on OONI’s task at the DEMHACK 6 hackathon (https://6.demhack.org/) As part of this hackathon, the team of participants worked on developing a script for the automatic identification of parked domains in the Citizen Lab test lists. *### OONI workshop for digital rights organizations from Central Asia* Between 27th-29th March 2023, OONI’s Elizaveta participated in an in-person training organized by CIPI and Internews for digital rights organizations from Central Asia (Kazakhstan, Kyrgyzstan, Tajikistan, Uzbekistan). As part of this training, Elizaveta facilitated an OONI workshop and helped the organizations determine how OONI data may be useful to their work. *### RWC 2023* Between 27th-29th March 2023, OONI’s Arturo traveled to Japan to attend the Real World Crypto (RWC) 2023 conference (https://rwc.iacr.org/2023/) The goal of attending this conference was to discuss with cryptographers a problem OONI is trying to solve related to implementing a privacy preserving way to authenticate probes and which might benefit from some sort of anonymous credential system. *### OONI Community Meeting* On 28th March 2023, we hosted the monthly OONI Community Meeting on our Slack channel (https://slack.ooni.org/) during which we discussed the following topics: 1. Updates from the OONI team. 2. The effects of Russia's invasion of Ukraine on Internet censorship in Russia. 3. Enabling more extensive beta testing of OONI tools by the community. 4. OONI Probe Web: Community questions about the “URL Limit” feature. *## Measurement coverage* In March 2023, 61,415,821 OONI Probe measurements were collected from 3,058 AS networks in 167 countries around the world. This information can also be found through our measurement stats on OONI Explorer (see chart on “monthly coverage worldwide”): https://explorer.ooni.org/ ~ OONI team.

1 0

Anti-censorship team meeting notes, 2023-03-30
by meskio 31 Mar '23

31 Mar '23

Hey everyone! Here are our meeting logs: http://meetbot.debian.net/tor-meeting/2023/tor-meeting.2023-03-23-15.58.log… And our meeting pad: Anti-censorship -------------------------------- Next meeting: Thursday, April 6 16:00 UTC Weekly meetings, every Thursday at 16:00 UTC, in #tor-meeting at OFTC (channel is logged while meetings are in progress) == Goal of this meeting == Weekly check-in about the status of anti-censorship work at Tor. Coordinate collaboration between people/teams on anti-censorship at the Tor Project and Tor community. == Links to Useful documents == * Our anti-censorship roadmap: * Roadmap: https://gitlab.torproject.org/groups/tpo/anti-censorship/-/boards * The anti-censorship team's wiki page: * https://gitlab.torproject.org/tpo/anti-censorship/team/-/wikis/home * Past meeting notes can be found at: * https://lists.torproject.org/pipermail/tor-project/ * Tickets that need reviews: from sponsors, we are working on: * All needs review tickets: * https://gitlab.torproject.org/groups/tpo/anti-censorship/-/merge_requests?s… * Sponsor 96 * https://gitlab.torproject.org/groups/tpo/-/milestones/24 * Sponsor 139 <-- hackerncoder, irl, joydeep, meskio, emmapeel working on it * https://pad.riseup.net/p/sponsor139-meeting-pad == Announcements == == Discussion == * merge requests in the snowflake webextension might stay months without review * https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snow… * should we add it to triage bot? who should be in the pool of reviewers? * yes, meskio will configure triagebot to auto asign reviews to: cohosh, shelikhoo and meskio * Update on Analysis of speed deficiency of Snowflake in China, 2023 Q1 https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snow… * after a lot of research the proposed solution is to enable datagram transport on webrtc to deal with the packet loss situation * that will convert webrtc into an unreliable channel, and snowflake will add reliablity with kcp == Actions == == Interesting links == * == Reading group == * We will discuss "" on * Questions to ask and goals to have: * What aspects of the paper are questionable? * Are there immediate actions we can take based on this work? * Are there long-term actions we can take based on this work? * Is there future work that we want to call out in hopes that others will pick it up? == Updates == Name: This week: - What you worked on this week. Next week: - What you are planning to work on next week. Help with: - Something you need help with. cecylia (cohosh): last updated 2023-03-30 Last week: - enabled wasm target for rust in tor-browser-build - https://gitlab.torproject.org/tpo/applications/tor-browser-build/-/issues/4… - helped debug blocking of Snowflake in TM - https://gitlab.torproject.org/tpo/anti-censorship/censorship-analysis/-/iss… - discussed the problem of deciding whether a bridge is blocked or not - took a look at memory issues for the Snowflake proxy - https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snow… This week: - Lox tor browser integration - fix conjure issues found by code audit Needs help with: dcf: 2023-03-30 Last week: - found a bug in snowflake-webext that causes it not to report client_ip since June 2022 https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snow…, and made a merge request to fix it https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snow… Next week: - migrate goptlib to gitlab https://gitlab.torproject.org/tpo/anti-censorship/team/-/issues/86#note_282… (for real) - open issue to have snowflake-client log whenever KCPInErrors is nonzero https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snow… - parent: https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snow… Help with: - review of snowflake-server ListenAndServe error check fix https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snow… meskio: 2023-03-30 Last week: - deploy bridgestrap with webtunnel support - modify bridgedb to distribute webtunnel bridges on the https distributor - keep up with the renovate bot and it's merge requests in rdsys - add an alert for >20% rejecte bridges by bandwidth ratio - raise the bandwidth ratio threashold to 0.9 (was 0.75) - display the 'blocked in' locations in the bridge status page (rdsys!95) Next week: - AFK time Shelikhoo: 2023-03-30 Last Week: - [Merge Request Awaiting] Add SOCKS5 forward proxy support to snowflake (snowflake!64) - [Research] HTTPT Planning https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/http… - logcollector alert system - Update on Analysis of speed deficiency of Snowflake in China, 2023 Q1 https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snow… Next Week: - [Research] WebTunnel planning (Continue) - Try to find a place to host another vantage point - container image for webtunnel - consider propagating 2FA everywhere, maybe, at the April Tor Meeting (https://gitlab.torproject.org/tpo/tpa/team/-/issues/41083#note_2884138) - logcollector altert system - webtunnel document for proxy opertaor onyinyang: 2023-03-30 Last week: - Finished up the handling of changed resources in the Lox library - Added some wiki documentation to Lox overview repo: https://gitlab.torproject.org/tpo/anti-censorship/lox/lox-overview/-/wikis/… - Tried testing changed/gone resources in rdsys (mostly familiarizing myself with rdsys code) - Considered how to sync Lox bridgetable for each rdsys update of new bridges This week: - Figure out how to test changed/gone resources and ensure the rdsys backend api is behaving as expected for handling updates from rdsys - Start implementing a function in lox distributor/lox library to handle syncing of Lox bridgetable Needs help with: - Expected behaviour of rdsys on update of bridges: e.g., where all changes to bridge descriptors are recorded (i.e., networkstatus-bridges, bridge-descriptors, cached-extrainfo files), which of these trigger updates from rdsys,and how _should_ the distributor be responding (if it's working as expected) Itchy Onion: 2023-03-22 Last week: - Closed #40252 (NAT probetest for standalone proxy) - Closed #40265 (mac user reporting standalone proxy complaning about broker cert) - Worked on #40231 (Client sometimes send offer with no ICE candidates) This week: - Tested and created a potential broker security issue (#40266) - Stil working on #40231 -- validate SDP contains candidate at the "/client" and "/answer" endpoints broke almsot all of the unit tests hackerncoder: 2023-03-09 last week: Next week: - getting ooni-exporter to work with torsf (snowflake) - ooni-exporter web_connectivity - work on "bridgetester"? - how does Iran block bridges cece: 2022-12-22 This week: - working on creating a dummy WhatsApp bot Next week: - My bot is not yet working as expected s? still trying to figure that out Help with: - resources -- meskio | https://meskio.net/ -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- My contact info: https://meskio.net/crypto.txt -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Nos vamos a Croatan.

2 1

OONI Monthly Report: February 2023
by Maria Xynou 29 Mar '23

29 Mar '23

Hello, This email shares OONI's monthly report for February 2023. *# OONI Monthly Report: February 2023* Throughout February 2023, the OONI team worked on the following sprints: * Sprint 84 (1st-12th February 2023) * Sprint 85 (13th-28th February 2023) Our work can be tracked through the various OONI GitHub repositories: https://github.com/ooni Highlights are shared in this report below. *## Published research report on internet censorship in Russia* On 24th February 2023 (1 year since the start of the war in Ukraine), we co-published a new research report, in collaboration with Roskomsvoboda, which documents how Internet censorship in Russia changed over the last year based on OONI data analysis. Read our report in: * English: https://ooni.org/post/2023-russia-a-year-after-the-conflict/ * Russian: https://ooni.org/ru/post/2023-russia-a-year-after-the-conflict/ You can also read Roskomsvoboda's publication about the report here: https://roskomsvoboda.org/post/rks-ooni-odin-god/ Overall, OONI data analysis shows the blocking of 494 domains in Russia. Many more websites are also blocked, beyond those tested. The blocked domains fall under 28 categories, suggesting pervasive levels of internet censorship in Russia. New blocks that emerged in Russia over the last year include: * Blocking of Russian & international human rights websites (e.g. Human Rights Watch & Amnesty International) * Blocking of investigative journalism & news media sites * Blocking of Instagram, SoundCloud and Patreon Access to the Tor Project's website was temporarily unblocked in Russia between 15th to 28th July 2022. Several discontinued sites have been unblocked over the last year (possibly as part of a "blocklist cleanup"). We confirmed the blocking of 48 domains (including a Let's Encrypt domain) based on OONI data, which do not appear to be included in Russia's official blocking registry. OONI data also suggests that access to a major CDN was blocked in the past year. *## Published research report on internet censorship in Azerbaijan* On 28th February 2023, we co-published a new research report on internet censorship in Azerbaijan, in collaboration with our partner, Azerbaijan Internet Watch. As part of this research, we analyzed OONI data collected from Azerbaijan over the last year. The report was published by: * OONI: https://ooni.org/post/2023-azerbaijan-internet-censorship/ * Azerbaijan Internet Watch: https://www.az-netwatch.org/news/ooni-measurements-show-ongoing-internet-ce… As part of our analysis of OONI measurements collected from Azerbaijan between January 2022 to February 2023, we found: ** Blocking of news media websites. *Azerbaijan continues to block access to several independent news media websites. OONI data also suggests that some ISPs in Azerbaijan may have started blocking access to the Guardian on 25th December 2022. ** Azerbaijan and Russia block each other’s news media. *In early June 2022, Azerbaijan started blocking access to Russia’s state-run RIA Novosti media website. Since (at least) 7th June 2022, Russian ISPs have been blocking access to Azerbaijani news media websites (haqqin.az, minval.az, oxu.az, ru.oxu.az, ru.baku.ws). These blocks remain ongoing. ** Temporary blocking of TikTok amid border clashes with Armenia. *During the September 2022 border clashes, both Azerbaijan and Armenia blocked access to TikTok. While the TikTok block was lifted in Armenia by 21st September 2022 (only lasting about a week), the TikTok block remained in place in Azerbaijan until November 2022 (lasting about 2 months). ** Blocking of circumvention tool sites.* Azerbaijan continues to block access to numerous circumvention tool websites, potentially limiting the ability to circumvent internet censorship in Azerbaijan. However, most OONI measurements suggest that tested circumvention tools (Tor and Psiphon) appear to be reachable. ** Variance of censorship across networks. *While most ISPs in Azerbaijan appear to adopt similar censorship techniques (as we continued to observe connection timeouts in most anomalous measurements across ASNs), different ISPs block access to different websites over time. *## Published report on social media blocks in Ethiopia* On 15th February 2023, we published a report on the blocking of social media platforms in Ethiopia. OONI data from Ethiopia showed the ongoing blocking of: * Facebook and Telegram (since 9th February 2023) * YouTube (since 10th February 2023) Read the report here: https://ooni.org/post/2023-ethiopia-blocks-social-media/ *## Published report on DW and Wikipedia blocking in Pakistan* On 15th February 2023, we published a report on the blocking of Wikipedia and Deutsche Welle (DW) in Pakistan. OONI data from Pakistan showed: * Access to Wikipedia restricted between 1st-6th February 2023 (48-hour degradation, followed by block) * Ongoing blocking of Deutsche Welle (DW) since (at least) 16th January 2023 Read the report here: https://ooni.org/post/2023-pakistan-blocks-wikipedia-and-dw/ *## Published report on Twitter throttling in Turkey* On 15th February 2023, we published a report on the throttling and DNS blocking of Twitter in Turkey in the aftermath of a deadly earthquake. On 8th February 2023, OONI data from Turkey showed that access to Twitter was throttled on at least 4 networks, and blocked by means of DNS interference on other networks. Read the report here: https://ooni.org/post/2023-turkey-throttling-blocking-twitter/ *## OONI reports for the ISOC Pulse project on Internet shutdowns* As a data partner for ISOC’s Pulse Shutdown project ( https://pulse.internetsociety.org/shutdowns) we have been working on creating “OONI reports” (with relevant OONI data, interpretation, and charts) for all of the “service blocking” entries listed on the Pulse shutdown timeline (ranging from March 2018 to February 2023) over the last year. In February 2023, we completed this work, having written the “Data and analysis” section for all “service blocking” entries of the ISOC Pulse Shutdown timeline (where relevant OONI data exists). As part of this work, we found that OONI data is available for almost all blocking events reported worldwide over the last 5 years (at least based on those listed on the ISOC Pulse shutdown timeline). In total, we wrote 49 OONI reports for the ISOC Pulse shutdown timeline. These reports will be included in the “Data and analysis” section of “service blocking” entries. *## OONI Probe Mobile* In February 2023, we continued to improve upon the OONI Probe mobile app. Specifically, we: * Prepared the next OONI Probe Mobile release (3.8.0) for internal testing; * Fixed a bug ensuring that the network name is displayed along with the ASN (https://github.com/ooni/probe/issues/2371) * Worked towards addressing a bug affecting automated testing on OONI Probe iOS (https://github.com/ooni/probe/issues/2259) * Worked towards enabling the transfer of the OONI Probe Android app to a SD card (https://github.com/ooni/probe/issues/2019) * Worked towards ensuring that the OONI Probe iOS app does not crash when OONI backend services are down (https://github.com/ooni/probe/issues/2201) *## OONI Run* OONI Run (https://run.ooni.io/) can be translated via the Transifex ( https://explore.transifex.com/otf/ooni-run/) platform. In February 2023, thanks to the Localization Lab community, OONI Run was translated into 6 languages: Chinese, German, Thai, Russian, Spanish, and Turkish. *## OONI Probe CLI* In February 2023, we released OONI Probe CLI 3.17.0: https://github.com/ooni/probe-cli/releases/tag/v3.17.0 Notably, OONI Probe CLI 3.17.0 includes an updated version (v0.5.20) of the Web Connectivity experiment, a TLS middlebox experiment, backend proxy support for Tor Snowflake, OONI Run improvements, and many other improvements (https://github.com/ooni/probe-cli/releases/tag/v3.17.0) This new release will be the first one to support providing richer input to experiments. We now support dynamically instructing the probes to enable experimental Web Connectivity functionality through the OONI backend. As part of this release cycle, we investigated two issues related to running tor on Android devices. The first issue ( https://gitlab.torproject.org/tpo/core/tor/-/issues/40747, https://github.com/ooni/probe/issues/2405) deals with the OONI Probe Android app receiving a SIGABRT signal because tor closes a file descriptor twice, thus triggering Android’s fdsan ( https://android.googlesource.com/platform/bionic/+/master/docs/fdsan.md) We patched the problem as part of the OONI Probe CLI 3.17.0 release. The second issue deals with a mysterious SIGABRT crash that we are still investigating. While testing OONI Probe CLI 3.17.0, we also noticed and investigated excessive CPU usage in the Web Connectivity test helper ( https://github.com/ooni/probe/issues/2413) We modified the codebase to add support for profiling, started fixing the most obvious issues, and increased the number of test helper hosts to spread the load among them. As part of testing, we also triaged the following data quality issues: https://github.com/ooni/probe/issues/2410 https://github.com/ooni/probe/issues/2411 https://github.com/ooni/probe/issues/1925#issuecomment-1429373491 https://github.com/ooni/probe/issues/2412 https://github.com/ooni/probe/issues/2420 https://github.com/ooni/probe/issues/2421 We fixed some of these data quality issues, as documented below: https://github.com/ooni/probe-cli/pull/1110 https://github.com/ooni/probe-cli/pull/1111 https://github.com/ooni/probe/issues/2293 Where feasible, we backported to the OONI Probe CLI 3.17.0 branch. After M-Lab deprecated their locatev1 API, we also migrated the DASH experiment to use the locatev2 API and included this patch into the 3.17.0 branch (https://github.com/ooni/probe/issues/2398) We also started working on exposing the OONI engine API, which is part of the probe-cli repository, as a dynamic library ( https://github.com/ooni/probe/issues/2414) *## Expanding OONI’s testing model to support richer testing input* The OONI Probe CLI 3.17.0 release ( https://github.com/ooni/probe-cli/releases/tag/v3.17.0) starts adding support for richer testing input ( https://github.com/ooni/ooni.org/issues/1291) We also continued to improve such support in the main development branch of OONI Probe CLI and OONI API. Specifically, we modified the API to directly return test helper information inside the check-in API response ( https://github.com/ooni/probe/issues/2392) We also started working on a design document regarding the richer testing input functionality and we began working on the related PoC ( https://github.com/ooni/probe-cli/pull/1075) *## Creating a throttling measurement methodology* As part of our plans to create a methodology for measuring throttling ( https://github.com/ooni/ooni.org/issues/1296) we started sketching out a possible integration testing strategy. At the end of this reporting period, we wrote a diff for probe-cli ( https://gist.github.com/bassosimone/3ce52a37fc7394f7cce82391685c5477) which works as follows: * We hijack the core networking code to use a GVisor-based ( https://gvisor.dev/) TCP/IP stack in userspace; * We connect this stack, representing the OONI Probe client with other GVisor stacks representing servers; * We add latency and throttling on those virtual channels when the network traffic meets specified conditions (e.g., depending on the SNI used during the TLS handshake). Writing good integration tests for this upcoming functionality is crucial to ensure that we do not break the Web Connectivity experiment while applying the necessary changes to add support for collecting network performance metrics (as planned: https://github.com/ooni/ooni.org/issues/1297) *## OONI Explorer* We continued to work with a designer on the new OONI Explorer domain and network centric pages (https://github.com/ooni/explorer/pull/830) We updated the copy for the user feedback reporting system and we worked on end-to-end tests. We made improvements to the third-party data integration, notably adding support for the caching of proxied Cloudflare requests and other UI changes (https://github.com/ooni/explorer/pull/831) We also released a new MAT filter that allows showing data for different time intervals: hourly, daily, weekly and monthly. *## OONI backend* Through February 2023, we continued to work on a series of backend improvements. Specifically, we: * Implemented datacenter filtering in rotation ( https://github.com/ooni/pipeline/pull/408) * Scaled up our infrastructure to 4 test helpers ( https://github.com/ooni/api/pull/320) and correlated the test runtime with the deployment of the new test helpers to measure their effectiveness; * Added more networks to the Web Connectivity v0.5 feature flag ( https://github.com/ooni/api/pull/318) * Fixed a bug affecting authentication in the Test Lists Editor ( https://github.com/ooni/test-lists-ui/issues/71) * Fixed the pipeline CI permissions ( https://github.com/ooni/pipeline/pull/409) * Extracted more values from measurements including software and test version, engine details, CPU architecture and test run time ( https://github.com/ooni/pipeline/pull/411, https://github.com/ooni/pipeline/pull/410) * Implemented an initial database backup tool. *## Automating censorship detection and characterization based on OONI measurements* We made stable progress on the OONI data analysis tool ( https://github.com/ooni/data) Specifically, we: * Made several improvements to the tooling that can be used for creating plots that allow us to assess how well the analysis performs ( https://github.com/ooni/data/pull/25) * Added support for mapping several “unknown_failures” that are a result of software bugs, ensuring that the data is more clean and can be better analyzed ( https://github.com/ooni/data/pull/25/commits/dc6517e0148be6c571a9e0768b50b5… ): * Started exploring the possibility of performing the analysis directly inside of the database engine (as opposed to doing in python code). This resulted in a 10x performance increase, allowing us to analyze one day's worth of OONI data in just over 5 minutes (compared to 2 hours of the python implementation). We also ingested new blocking fingerprints ( https://github.com/ooni/pipeline/pull/407) into the fastpath data processing pipeline, thereby automatically detecting and confirming more cases of website blocking around the world. To evaluate how effectively OONI Probe measures and detects cases of internet censorship, we compared measurements from Indonesia (that show blocking) with Indonesia’s (“DNS-Trust”) blocking registry ( https://github.com/alsyundawy/dnstrust-apjii) We found that OONI measurements that show DNS-based censorship are consistent with Indonesia’s blocklist. *## Creating a Social Media Censorship Alert System* We continued to make progress on the initial event detector developed for the new Social Media Censorship Alert System ( https://github.com/ooni/backend/issues/629) Specifically, we ran experiments using Pandas, added more tests, and generated PNG/SVGs as part of the testing. *## Creating a new OONI Outreach Kit* Throughout February 2023, we coordinated with Ura Design ( https://ura.design/) who worked on designing the new OONI Outreach Kit materials. We are aiming to publish the Outreach Kit in March 2023. *## Coordination of translation of OONI documents* Throughout February 2023, we coordinated with translators with regards to the translation of several OONI documents into 5 languages: Arabic, Farsi, Russia, Swahili, and Spanish. We are aiming to publish the translated documents in March 2023. *## Test list updates* We coordinated with our partner, TEDIC (https://ooni.org/partners/tedic/) who provided extensive updates for the test list of Paraguay: https://github.com/citizenlab/test-lists/pull/1224 The test list for Cambodia was also updated extensively by API Cambodia (iMAP partner): https://github.com/citizenlab/test-lists/pull/1214 We reviewed and merged many other test list pull requests contributed by community members: https://github.com/citizenlab/test-lists/pulls?q=is%3Apr+is%3Aclosed *## Rapid response### Wikipedia blocking in Pakistan* Access to Wikipedia was temporarily restricted in Pakistan between 1st to 6th February 2023. We rapidly responded by sharing relevant OONI data collected from Pakistan (and encouraging further testing) on Twitter: https://twitter.com/OpenObservatory/status/1620845976645963778 and https://twitter.com/OpenObservatory/status/1621449233852252160 We subsequently published a report: https://ooni.org/post/2023-pakistan-blocks-wikipedia-and-dw/ *### Social media blocks in Iraq* On 6th February 2023, community members in Iraq reported to the #KeepItOn mailing list that access to social media platforms (WhatsApp, Facebook, Twitter, Instagram) would be banned during the country’s final exams, starting on 5th February 2023 and ending on 13th February 2023 (from 4 am to 12 pm local time). The decision was made by the PMO based on the ministry of education recommendation. We shared relevant OONI data with the #KeepItOn campaign on these blocks. *### Twitter throttling in Turkey* On 8th February 2023, in the aftermath of the earthquakes, Turkey throttled access to Twitter. Real-time OONI data collected from Turkey showed the block: https://explorer.ooni.org/chart/mat?probe_cc=TR&test_name=web_connectivity&… We rapidly responded by analyzing relevant OONI data collected from Turkey and sharing our analysis through a Twitter thread: https://twitter.com/OpenObservatory/status/1623398643595182083 OONI data showed that access to Twitter was throttled on at least 4 networks, and blocked by means of DNS on other networks. We subsequently published a report: https://ooni.org/post/2023-turkey-throttling-blocking-twitter/ *### Social media blocks in Ethiopia* On 9th February 2023, amid church split tensions and calls for anti-government protests, access to social media platforms was reportedly blocked in Ethiopia. We rapidly responded by sharing relevant OONI data collected from Ethiopia (and encouraging further testing) on Twitter: https://twitter.com/OpenObservatory/status/1624045402679873540 and https://twitter.com/OpenObservatory/status/1624761465453379584 We subsequently published a report: https://ooni.org/post/2023-ethiopia-blocks-social-media/ *## Community use of OONI data### Paper on internet censorship in Russia* Censored Planet (in collaboration with other researchers) published a paper (“Network Responses to Russia’s Invasion of Ukraine in 2022: A Cautionary Tale for Internet Freedom”) which analyzes OONI data (along with Censored Planet data) to examine internet censorship in Russia following the February 2022 invasion of Ukraine. Their paper (which was accepted to appear in USENIX Security 2023) is available here: https://censoredplanet.org/assets/russia-ukraine-invasion.pdf *### Paper on censorship data analysis* Censored Planet and Jigsaw published a paper (“Advancing the Art of Censorship Data Analysis”) which discusses the challenges involved in analyzing censorship measurement data. This paper shares examples from OONI data and other public censorship datasets (such as Censored Planet). Their paper (which was published by FOCI) is available here: https://www.petsymposium.org/foci/2023/foci-2023-0003.pdf *### Data Journalism guide for measuring internet shutdowns* Journalist Sabrina Faramarzi published an article (“Kill switch: reporting on and during internet shutdowns”) which aims to serve as a guide for data journalists interested in measuring internet shutdowns. This article features an interview with OONI’s Maria, where she discusses why journalists should use OONI data to investigate internet censorship around the world. The article is available here: https://datajournalism.com/read/longreads/internet-shutdowns-data-reporting *## Community activities### OONI workshop for civil society in Azerbaijan* On 1st February 2023, OONI’s Elizaveta facilitated an OONI workshop for civil society groups in Azerbaijan. This workshop was hosted in collaboration with our partner, Azerbaijan Internet Watch ( https://ooni.org/partners/azerbaijan-internet-watch/) The goal of the workshop was to introduce civil society groups in Azerbaijan to OONI tools to help boost OONI measurement coverage in Azerbaijan. *### FOSDEM 2023* On 4th and 5th February 2023, OONI’s Federico attended FOSDEM ( https://fosdem.org/2023/) in Brussels. *### OONI workshop for human rights defenders in Nigeria* On 16th February 2023, OONI’s Elizaveta facilitated an OONI workshop for human rights defenders in Nigeria. This workshop was hosted in collaboration with our partner, Paradigm Initiative ( https://ooni.org/partners/paradigm-initiative/) The goal of the workshop was to introduce participants to OONI tools and data, encouraging censorship measurement leading up to and during Nigeria’s 2023 elections (which may trigger new censorship events). *### OONI Run demo for the Localization Lab community* On 22nd February 2023, OONI’s Elizaveta provided an OONI Run ( https://run.ooni.io/) demo for the Localization Lab community to encourage the translation of the platform. *### Live OONI session for the OPTIMA community in Senegal* On 23rd February 2023, OONI’s Elizaveta briefly presented OONI and addressed questions as part of Internews’ live OPTIMA session for community members in Senegal. *### OONI Community Meeting* On 28th February 2023, we hosted the monthly OONI Community Meeting on our Slack channel (https://slack.ooni.org/) during which we discussed the following topics: 1. Updates from the OONI team. 2. Upcoming conferences and opportunities for censorship measurement sessions. 3. Community feedback on early beta testing of OONI tools. *## Measurement coverage* In February 2023, 57,841,940 OONI Probe measurements were collected from 2,844 AS networks in 164 countries around the world. This information can also be found through our measurement stats on OONI Explorer (see chart on “monthly coverage worldwide”): https://explorer.ooni.org/ ~ OONI team.

1 0