Hi everyone,
Here are our meeting logs:
and our meeting pad:
Anti-censorship
···
--------------------------------
Next meeting: Thursday, March 19 16:00 UTC
Facilitator: cohosh
^^^(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: meskio
== 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 · Issues by Assignee · 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:
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 ==
New stun servers being added, any policy issue with these servers?
we don't see any issues with them
will apply them first to circumvention settings and after to the builtin bridges
(New 03/17:)Done, we are monitoring the metrics
Release schedule planning for containers
WebTunnel server has not needed an update, but the tor daemon has updated in the meantime; want to release container updates purely for the sake of getting an upgraded tor, even if there are no changes to WebTunnel
Shell will write a ticket about 3 month per maintaince release proposal
== Actions ==
== Interesting links ==
How NAT traversal works <- nice write up about challages about NAT types, for someone look to learn more about NAT dramas (no discussion necessary)
== 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?
Next in the Reading Group Queue:
== 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): 2026-03-19
Last week:
- merged snowflake message library changes
- rewrote broker pool refactor
- worked on proxy fairness proposal
Next week:
- continue snowflake and lyrebird go version support and release work
- follow up about running shadow simulations for snowflake performance
- research snowflake enumeration attacks (snowflake#40396)
- implement proxy fairness proposal
- follow up on snowflake rendezvous failures (snowflake#40447)
- revisit conjure integration with lyrebird
- take a look at potential snowflake orbot bug
- [BUG] 20% CPU overhead in kindness mode · Issue #1183 · guardianproject/orbot-android · GitHub
dcf: 2026-03-19
Last week:
- upgraded the OS and the tor daemon on the snowflake-02 bridge Upgrade OS on snowflake-02 (#40522) · Issues · The Tor Project / Anti-censorship / Pluggable Transports / Snowflake · GitLab upgrade tor in snowflake bridges to 0.4.8.22 (#40511) · Issues · The Tor Project / Anti-censorship / Pluggable Transports / Snowflake · GitLab
- added a section on important files to back up to the Snowflake Bridge Installation Guide Changes · Snowflake Bridge Installation Guide · Wiki · The Tor Project / Anti-censorship / Team · GitLab
- commented on proposal for 3 NAT buckets for snowflake broker Add three NAT type buckets to the snowflake broker (#40077) · Issues · The Tor Project / Anti-censorship / Pluggable Transports / Snowflake · GitLab
- adjusted permissions on the metrics timeline repository, in an attempt to make it easier for people to commit directly snowflake-01 upgrade (!20) · Merge requests · The Tor Project / Network Health / Metrics / Timeline · GitLab
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
Help with:
meskio: 2026-03-12
Last week:
- debug tails issue with meek, was python upstream library issue (lyrebird#40034)
- try out gitlab SAST in lyrebird, doesn't produce much output (is that good?)
- grant writting
Next week:
- AFK
Shelikhoo: 2026-03-12
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 Reviews
- Vantage point maintaince
- [Research] proxy pool overload and potential blocking in Iran ( Add three NAT type buckets to the snowflake broker (#40077) · Issues · The Tor Project / Anti-censorship / Pluggable Transports / Snowflake · GitLab )
- [Research] Add three NAT type buckets to the snowflake broker ( Add three NAT type buckets to the snowflake broker (#40077) · Issues · The Tor Project / Anti-censorship / Pluggable Transports / Snowflake · GitLab )
- [MR Merged] Replace broken stun server with working one ( Replace broken stun server with working one (!47) · Merge requests · The Tor Project / Anti-censorship / rdsys-admin · GitLab )
- [MR] Draft: Update webtunnel version to 0.0.4 and update bundled dockerfile dependencies ( Draft: Update webtunnel version to 0.0.4 and update bundled dockerfile dependencies (!41) · Merge requests · The Tor Project / Anti-censorship / Pluggable Transports / WebTunnel · GitLab )
Next (working) Week/TODO:
- Merge request reviews
- [Deployment]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 ) Building custom Tor Browser with patch applied
- Vantage point maintaince
- [Research] proxy pool overload and potential blocking in Iran ( Add three NAT type buckets to the snowflake broker (#40077) · Issues · The Tor Project / Anti-censorship / Pluggable Transports / Snowflake · GitLab )
- [Research] Add three NAT type buckets to the snowflake broker ( Add three NAT type buckets to the snowflake broker (#40077) · Issues · The Tor Project / Anti-censorship / Pluggable Transports / Snowflake · GitLab )
onyinyang: 2026-02-26
Last week(s):
- attended FOCI
- Working on https distributor language selector HTTPS distributor is missing a language selector menu (#196) · Issues · The Tor Project / Anti-censorship / rdsys · GitLab
Next week:
- Away until March 18
- Continue work on rdsys#196
- Continue Investigating rdsys#248 i.e., why dysfunctional webtunnel bridges are being distributed
- Troubleshooting conjure not connecting in China
- waiting for more information from conjure authors/maintainers
Switch back to some of these:
As time allows:
- 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
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:
- 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:
- 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: 2026-02-19
Last weeks:
- Bumping pion stack version with backport: Sign in · GitLab
- Implementing DTLS 1.3 in pion
Next weeks:
- Implementing DTLS 1.3 in pion
Help with:
-
Facilitator Queue:
cohosh 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
_______________________________________________
tor-project mailing list -- tor-project@lists.torproject.org
To unsubscribe send an email to tor-project-leave@lists.torproject.org