Hey everyone!

Here are our meeting logs: http://meetbot.debian.net/tor-meeting/2025/tor-meeting.2025-03-06-16.00.html

And our meeting pad:

Anti-censorship --------------------------------

Next meeting: Thursday,March 11 16:00 UTC Facilitator: onyinyang ^^^(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: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 projects, we are working on: * All needs review tickets: * https://gitlab.torproject.org/groups/tpo/anti-censorship/-/merge_requests?sc... * Project 158 <-- meskio working on it * https://gitlab.torproject.org/groups/tpo/anti-censorship/-/issues/?label_nam...

== Announcements ==

* There is a new version of the snowflake website * https://snowflake.torproject.org/ * https://blog.torproject.org/snowflake-refresh-to-help-more-people-get-online... * you can help translating it: * https://hosted.weblate.org/projects/tor/snowflake-web/

== Discussion ==

* Should we user test snowflake with covert-dtls? It is difficult to force Snowflake client to become the DTLS client: https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snowf... * "After some debugging, reading the pion webrtc source code, and referencing RFC 5763 (DTLS-SRTP framework) I realized why hook was never triggered. The Snowflake client will almost always become the server in the DTLS handshake as sends the SDP Offer every time. According to the RFC, only the offer can decide who becomes the client or server." * we'll use the testing setup of a broker, bridge, ... that we plan to do also for the unreliable transport * meskio will update his proxies to test the new developments on covertls (DTLS 1.3)

* snowflake broker match failure rate is high? * high number of 504 errors https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snowf... * lots of client poll timeout log messages https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snowf... * SQS rendezvous seems to perform badly under high load https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snowf... * removing the rate limit at the broker didn't fully address issues https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snowf... * cohosh will prepare a MR for the broker using pprof to monitor if there are goroutinges being blocked * we'll discuss with this MR if we want to deploy it in production

== Actions ==

== Interesting links ==

* https://forum.torproject.org/t/snowflake-daily-operations-february-2025-upda... * Snowflake users still declining month by month * https://metrics.torproject.org/rs.html#details/5481936581E23D2D178105D44DB69... * https://metrics.torproject.org/rs.html#details/91DA221A149007D0FD9E5515F5786...

== 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): 2025-03-06 Last week: - AWS accounting - followed up on SQS errors (snowflake#40363) - worked on a fix for broken shadow integration tests (snowflake#40456) - helped debug conjure registration work (conjure#43) - did some tests to figure out cause of snowflake broker failure rate (snowflake#40447) This week: - support conjure work - follow up in snowflake rendezvous failures - take a look at potential snowflake orbot bug - https://github.com/guardianproject/orbot-android/issues/1183 - maybe do some lox work dcf: 2025-03-06 Last week: - Next week: - open issue to have snowflake-client log whenever KCPInErrors is nonzero https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snowf... - parent: https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snowf... Help with:

meskio: 2024-03-06 Last week: - config as env variables for dsys private data (rdsys#219) - remove moat shim token and dummy bridges - improvements on rdsys docker images - investigate how the gitlab container dependency proxy works (snowflake!522) Next week: - steps towards a rdsys in containers (rdsys#219)

Shelikhoo: 2024-03-06 Last Week: - [Testing] Unreliable+unordered WebRTC data channel transport for Snowflake rev2 (cont.)( https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snowf... ) testing environment setup/research - Vantage Point maintaince - Merge request reviews Next Week/TODO: - Merge request reviews - [Testing] Unreliable+unordered WebRTC data channel transport for Snowflake rev2 (cont.)( https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snowf... ) improvements

onyinyang: 2025-03-06 Last week(s): - continued work on ampcache registration method for conjure - WIP MR: https://github.com/cohosh/conjure/pull/1 - https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/conju... Next week: - finish up ampcache registration method (sqs on hold for now) - Begin work on decoy registration option - review Tor browser Lox integration - https://gitlab.torproject.org/tpo/applications/tor-browser/-/merge_requests/... - add TTL cache to lox MR for duplicate responses: https://gitlab.torproject.org/tpo/anti-censorship/lox/-/merge_requests/305 As time allows: - 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: https://gitlab.torproject.org/tpo/applications/tor-browser/-/issues/42974 - 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-03-06 Last weeks: - Implementing key_share extension support in covert-dtls - Implementing mimicking DTLS 1.3 extensions - Debugging Tor Build with covert-dtls: https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snowf... Next weeks: - Update MR with new covert-dtls version. - Write instructions on how to configure covert-dtls with snowflake client - Fix merge conflicts in MR (https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snowf...). - Condensing thesis into paper (on hold) Help with: - Test stability of covert-dtls in snowflake

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