Hey everyone!
Here are our meeting logs:
And our meeting pad:
Anti-censorship
···
--------------------------------
Next meeting: Thursday, Aug 7 16:00 UTC
Facilitator: meskio
^^^(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:shelikhoo
== 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 ==
* snowflake-02 is down
* snowflake-02 bridge is down (#40475) · Issues · The Tor Project / Anti-censorship / Pluggable Transports / Snowflake · GitLab
* snowflake-02 is down since last friday
* meskio is trying to contact the operators, no success yet
* proxies are overloaded by requests failing to connect to it
== Actions ==
== Interesting links ==
* Available implementation and report on quantum-safe fully encrypted protocols
* Available implementation and report on quantum-safe fully encrypted protocols - tor-dev - lists.torproject.org
* Implementing and Evaluating Quantum-Safe Fully Encrypted Protocols - Research Collection
* GitHub - marc-himmelberger/lyrebird-drivel: A fork of the lyrebird repository, implemting the drivel pluggable transport for Tor as part of a Master's Thesis at ETH
* Exposing and Circumventing SNI-based QUIC Censorship of the Great Firewall of China
* Exposing and Circumventing SNI-based QUIC Censorship of the Great Firewall of China
== Reading group ==
* We will discuss "Encrypted Client Hello (ECH) in Censorship Circumvention" on August 14
* https://www.petsymposium.org/foci/2025/foci-2025-0016.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): 2025-07-31
Last week:
- tried some broker nginx config modifications to see if it reduced the number of 5xx errors (it did not)
- Find and address the root cause of client rendezvous errors (#40447) · Issues · The Tor Project / Anti-censorship / Pluggable Transports / Snowflake · GitLab
Next week:
- afk all week
- follow up on snowflake rendezvous failures
- take a look at potential snowflake orbot bug
- [BUG] 20% CPU overhead in kindness mode · Issue #1183 · guardianproject/orbot-android · GitHub
dcf: 2025-07-24
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-08-07
Last week:
- investigate snowflake proxies overload, snowflake-02 is down (snowflake#40475)
- duplicate meek and meek-azure on moat APIs (rdsys#272)
- redirect to frontdesk if no telegram bridges (rdsys#271)
- make easier to copy bridgelines in telegram (rdsys#276)
- wrap up rdsys staging (rdsys#219)
Next week:
-
Shelikhoo: 2024-08-07
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
- [Merge Request] Create new webtunnel release(STALLED BY ISSUE BELOW)(Draft: Generate Release v0.0.3 (!30) · Merge requests · The Tor Project / Anti-censorship / Pluggable Transports / WebTunnel · GitLab)
- Unexpected Gitlab Runner Failure from Rate Limiting (Unexpected Gitlab Runner Failure from Rate Limiting (#42245) · Issues · The Tor Project / TPA / TPA team · GitLab)
- [Merge Request Awaiting] Add Domain Fronting Test Support to probeobserver ( Add Domain Fronting Test Support (!8) · Merge requests · The Tor Project / Anti-censorship / Connectivity Measurement / probeobserver · GitLab )
- [Merge Request Done] Update snowflake proxy image to use most recent golang and geodb (Update snowflake proxy image to use most recent golang and geodb (!597) · Merge requests · The Tor Project / Anti-censorship / Pluggable Transports / Snowflake · GitLab)
- [Merge Request Done] Add certificate hash chain pinning support to webtunnel (Add certificate hash chain pinning support to webtunnel (!123) · Merge requests · The Tor Project / Anti-censorship / Pluggable Transports / lyrebird · GitLab)
- [Merge Request] Remove s390x from container building targets (Remove s390x from container building targets (!599) · Merge requests · The Tor Project / Anti-censorship / Pluggable Transports / Snowflake · GitLab)
- Merge request reviews
Next (working) Week/TODO:
- Merge request reviews
- 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 ) (cont.)
- Create webtunnel release v0.0.3
- invesgate webtunnel domain fronting support and dynamic bridge support
onyinyang: 2025-07-24
Last week(s):
- Finished up work on webtunnel button
- Added some logs to help debug Bridge testing gives timeout (#249) · Issues · The Tor Project / Anti-censorship / rdsys · GitLab
Next week:
- Next is looking into this mystery: Bridges website hitting a error while fetching bridges with WebTunnel pluggable transport (#262) · Issues · The Tor Project / Anti-censorship / rdsys · GitLab
- Vacation next 2 weeks
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? Consider dropping Lox's WASM (#43096) · Issues · The Tor Project / Applications / Tor Browser · GitLab):
- add pref to handle timing for pubkey checks in Tor browser
- add trusted invitation logic to tor browser integration:
Lox module doesn't include trusted invitation redemption (#42974) · Issues · The Tor Project / Applications / Tor Browser · GitLab
- 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:
meskio onyinyang shelikhoo
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
--
meskio | https://meskio.net/
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
My contact info: https://meskio.net/crypto.txt
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Nos vamos a Croatan.