Hey everyone!
Here are our meeting logs:
And our meeting pad:
Anti-censorship work meeting pad
···
--------------------------------
Anti-censorship
--------------------------------
Next meeting: Thursday, Sep 18 16:00 UTC
Facilitator:shelikhoo
^^^(See Facilitator Queue at tail)
Weekly meetings, every Thursday at 16:00 UTC, in #tor-meeting at OFTC
(channel is logged while meetings are in progress)
This week's Facilitator:onyinyang
== 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:Issue Boards · Development · Boards · Anti-censorship · GitLab
* The anti-censorship team's wiki page:
* Home · Wiki · The Tor Project / Anti-censorship / Team · GitLab
* Past meeting notes can be found at:
* The tor-project Archives
* Tickets that need reviews: from projects, we are working on:
* All needs review tickets:
* Merge requests · Anti-censorship · GitLab
* Project 158 <-- meskio working on it
* Issues · Anti-censorship · GitLab
== Announcements ==
== Discussion ==
(Sep 11 New)
* Rechecked webtunnel bridge extra info intensity(before=3011):
* $ tar -O -xf bridge-extra-infos-2025-09.tar.xz | grep -B3 '^transport webtunnel' | grep '^published '|grep 2025-09-10|wc -l
* 3041
* $ tar -O -xf bridge-extra-infos-2025-09.tar.xz | grep -B3 '^transport webtunnel' | grep '^published '|grep 2025-09-09|wc -l
* 3023
* $ tar -O -xf bridge-extra-infos-2025-09.tar.xz | grep -B3 '^transport webtunnel' | grep '^published '|grep 2025-09-08|wc -l
* 3014
* tor#7349 and proposed changes for bridges
* Obfsbridges should be able to "disable" their ORPort (#7349) · Issues · The Tor Project / Core / Tor · GitLab
* 'Running' flag for counting bridges and network size (#318) · Issues · The Tor Project / Network Health / Team · GitLab
* tldr: should onionoo only get the Running flag for bridges from bridgestrap and ignore Serge's reachability check?
* recommend not exposing ORPort: Recommend not exposing OrPort for bridges (#129) · Issues · The Tor Project / Anti-censorship / Team · GitLab
== Actions ==
\* Remove webtunnel setuid script in 5 weeks\.\(decrease this by one every week\)
== Interesting links ==
\* https://opencollective.com/censorship-circumvention/projects/snowflake-daily-operations/updates/2025-august-update
\* https://interseclab.org/wp-content/uploads/2025/09/The-Internet-Coup_September2025.pdf#page=61
\* "Blocking online privacy and circumvention tools" section of InterSecLab report on Geedge Networks, mentions Tor, Snowflake, WebTunnel
\* https://www.amnesty.org/en/documents/asa33/0206/2025/en/
\* Pakistan: Shadows of Control: Censorship and mass surveillance in Pakistan
\* https://github.com/net4people/bbs/issues/519
\* Leak of Geedge Networks internal documents \(100,000\+ from Jira, Confluence, GitLab
\* \(Protests in Nepal turned deadly after thousands of youngsters marched against the blocking of social media platforms\.\)
== Reading group ==
\* We will discuss "IRBlock: A Large\-Scale Measurement Study of the Great Firewall of Iran" on September 11
\* https://www.usenix.org/system/files/usenixsecurity25-tai.pdf
\* https://irblock.org/ is supposed to have public data according to Section 8, but it shows a "Cloudflare Tunnel error"
\* https://zenodo.org/records/15572895 has limited data from November 2024 to January 2025, not raw data, but already aggregated
\* 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?
\* Next:
\* https://interseclab.org/wp-content/uploads/2025/09/The-Internet-Coup_September2025.pdf#page=61
\* "Blocking online privacy and circumvention tools" section of InterSecLab report on Geedge Networks, mentions Tor, Snowflake, WebTunnel
== 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): 2025-09-11
Last week:
- fixed snowflake extension translation bug (snowflake-webext#120)
- updated wiki page for integrating new PTs into Tor Browser
- https://gitlab.torproject.org/tpo/anti-censorship/team/-/wikis/Tor-Browser-Integration-Guide-for-New-Pluggable
-Transports
- implemented and deployed new prometheus metrics to track proxy answers by implementation
- met with Rob to discuss proteus integration steps
- updated analysis of snowflake proxy timeouts (snowflake#40447)
Next week:
- follow up on snowflake rendezvous failures
- deploy new snowflake webextension with translation fixes
- take a look at potential snowflake orbot bug
- [BUG] 20% CPU overhead in kindness mode · Issue #1183 · guardianproject/orbot-android · GitHub
dcf: 2025-09-11
Last week:
Next week:
- open issue to have snowflake-client log whenever KCPInErrors is nonzero Deploy snowflake-server for QueuePacketConn buffer reuse fix (#40260) (#40262) · Issues · The Tor Project / Anti-censorship / Pluggable Transports / Snowflake · GitLab
- parent: Improve bug discovery process (#40267) · Issues · The Tor Project / Anti-censorship / Pluggable Transports / Snowflake · GitLab
Help with:
meskio: 2024-09-11
Last week:
- brainstorm on dual stack bridges (tor!786)
- catch up with emails and fail
Next week:
Shelikhoo: 2024-09-11
Last Week:
- [Testing] Unreliable+unordered WebRTC data channel transport for Snowflake rev2 (cont.)( Draft: Unreliable+unordered WebRTC data channel transport for Snowflake rev2 (!315) · Merge requests · The Tor Project / Anti-censorship / Pluggable Transports / Snowflake · GitLab ) testing environment setup/research
- [Deploy Over] Add Domain Fronting Test Support to probeobserver
- Support the Testing of domain fronting sites ( Support the Testing of domain fronting sites (#6) · Issues · The Tor Project / Anti-censorship / Connectivity Measurement / logcollector · GitLab ) (Done)
- (Many merge reviews)
Next (working) Week/TODO:
- Merge request reviews
- Choosing domain fronting targets for domain fronting tests
- invesgate russian vantage point issues
onyinyang: 2025-09-11
Last week(s):
-Deployed and merged Fix + Logs to pinpoint #249 bug (!562) · Merge requests · The Tor Project / Anti-censorship / rdsys · GitLab
- Confirmed that we are still distributing malfunctioning webtunnel bridges are we distributing non working webtunnel bridges? (#47) · Issues · The Tor Project / Anti-censorship / bridgestrap · GitLab
- Looking into why ^
- Looking into a solution for distributing a proportion of webtunnel bridges to telegram users with new accounts Getbridgesbot - feedback and discussion on old and new accounts (#283) · Issues · The Tor Project / Anti-censorship / rdsys · GitLab
Next week:
- Continue looking into bridgestrap#47
- Continue looking into rdsys#283
- Lox still seems to be filling up the disk on the rdsys-test server despite changes made to delete old entries, look into what's going wrong
Switch back to some of these:
As time allows:
Blog post for conjure: Set up a more permanent Conjure bridge (#46) · Issues · The Tor Project / Anti-censorship / Pluggable Transports / conjure · GitLab
- review Tor browser Lox integration Bug 43096: Move to Rust for the Lox integration (!1300) · Merge requests · The Tor Project / Applications / Tor Browser · GitLab
- add TTL cache to lox MR for duplicate responses:
Enable repeat responses to successful Lox requests (!305) · Merge requests · The Tor Project / Anti-censorship / lox · GitLab
\- Work on outstanding milestone issues:
\- key rotation automation
Later:
pending decision on abandoning lox wasm in favour of some kind of FFI? https://gitlab.torproject.org/tpo/applications/tor-browser/-/issues/43096):
\- add pref to handle timing for pubkey checks in Tor browser
\- add trusted invitation logic to tor browser integration:
- improve metrics collection/think about how to show Lox is working/valuable
- sketch out Lox blog post/usage notes for forum
\(long term things were discussed at the meeting\!\):
\- 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 usable 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 sacrificed 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?
theodorsm: 2025-06-12
Last weeks:
- Applying for funding from NLnet to implement DTLS 1.3 in Pion. Got through the first round.
- Writing paper for FOCI: continuation of master thesis about reducing distinguishability of DTLS in Snowflake by implementing covert-dtls, further analysis of collected browser fingerprint and stability test of covert-dtls in snowflake proxies. Draft: https://theodorsm.net/FOCI25
- Key takeaways:
* covert-dtls is stable when mimicking DTLS 1.2 handshakes, while the randomization approach— though more resistant to fingerprinting — tends to be less stable.
* Chrome webextensions are more unstable than standalone proxies
* covert-dtls should be integrated in Snowflake proxies as they produce the ClientHello messages during the DTLS handshake.
* Chrome randomizes the order of extension list.
* Firefox uses DTLS 1.3 by default in WebRTC.
* A prompt adoption of DTLS 1.3 in both Snowflake and our fingerprint-resistant library is needed to keep up with browsers
* The evolution of browsers’ fingerprints had no noticeable effect on Snowflake’s number of daily users over the last year.
* Even with a sharp drop in the amount of proxies, it does not seem to affect the number of Snowflake users.
* Browser extensions make Snowflake resistant to ClientHello fingerprinting.
* Standalone proxies can serve more Snowflake clients per volunteer than webextensions.
* We need metrics on which types of proxies are actually being matched and successfully used by clients.
Next weeks:
- Getting paper camera ready.
- Fix merge conflicts in MR (Add covert-dtls to proxy and client (!448) · Merge requests · The Tor Project / Anti-censorship / Pluggable Transports / Snowflake · GitLab).
Help with:
- Should we do user testing of covert-dtls?
Facilitator Queue:
onyinyang shelikhoo meskio
1. First available staff in the Facilitator Queue will be the facilitator for the meeting
2. After facilitating the meeting, the facilitator will be moved to the tail of the queue
--
---
onyinyang
GPG Fingerprint 3CC3 F8CC E9D0 A92F A108 38EF 156A 6435 430C 2036