Hey everyone!

Here are our meeting logs: http://meetbot.debian.net/tor-meeting/2025/tor-meeting.2025-01-23-16.04.html

And our meeting pad:

Anti-censorship work meeting pad -------------------------------- Anti-censorship --------------------------------

Next meeting: Thursday,January  30 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: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 ==

* BridgeStatus's Snowflake bridge test output will change after deployment of         * Use gitlab circumvention setting for snowflake bridge line update         * https://gitlab.torproject.org/tpo/anti-censorship/connectivity-measurement/p...         * Be sure to check if any automated script is still working correctly     * snowflake-broker.azureedge.net is still working, a week after the announced shutdown date.         curl -s -i https://snowflake-broker.azureedge.net/amp/client/

== Discussion ==

== 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): 2025-01-23     Last week:         - worked on some phantombox (conjure test environment) improvements             - https://gitlab.torproject.org/cohosh/phantombox/-/issues/2         - fixups to switching to local storage for snowflake badges             - https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snowf...         - some reviews and gitlab todos     This week:         - asn mapping geoip feature

dcf: 2025-01-23     Last week:         - tracked status of snowflake-broker.azureedge.net after announced date of Edgio shutdown https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snowf...         - helped debug reported "AMP cache rendezvous doesn't work in China" https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snowf...     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...         - open issue to disable /debug endpoint on snowflake broker Help with:

meskio: 2024-01-23     Last week:         - debug a segfault in country based metrics to the snowflake proxy (snowflake!482)         - debug why metrics.torproject.org doesn't display distributor metrics (rdsys#235)         - keep up with snowflake debian dependencies (snowflake#40410)         - deploy onionsproutsbot (onionsproutsbot#66)         - investigate why we distribute non working bridges (rdsys#254)         - simple refactor fixes on rdsys bridge tests (rdsys!454)         - review and update P146 report         - triage the long queue of open issues (there are still some snowflake ones missing)     Next week:         - snowflake debian package

Shelikhoo: 2024-01-23     Last Week:          - [Pending] snowflake broker update/reinstall(cont.): https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snowf...          - [Awaiting Review] Unreliable+unordered WebRTC data channel transport for Snowflake rev2 (cont.)( https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snowf... ) improvements         - Merge request reviews         - Automate bridgeline update for snowflake(https://gitlab.torproject.org/tpo/anti-censorship/connectivity-measurement/p...     )     - Use assume reachable for webtunnel bridges to avoid exporting OR port(https://gitlab.torproject.org/tpo/anti-censorship/connectivity-measurement/p...)     - Update readme to include migration notice (https://gitlab.torproject.org/tpo/anti-censorship/docker-snowflake-proxy/-/m... )     -     Next Week/TODO:         - Merge request reviews         - [Resume] Unreliable+unordered WebRTC data channel transport for Snowflake rev2 (cont.)( https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snowf... ) improvements         - [Deployment] Automate bridgeline update for snowflake

onyinyang: 2025-01-23     Last week(s):         - Get conjure up and running (at least locally)         - WIP Conjure stuff for Project 173     Next week:         - Continue on getting conjure up and running (at least locally)         - implement utls for conjure         - start implementation of alternative registration methods         As time allows:         - Continue work on implementing issuer efficiency for check-blockage and trust-promotion protocols         - 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-01-22 (AFK for meeting 01-23)         Last weeks:             - Testing Tor Build with covert-dtls         Next weeks:             - Update covert-dtls to handle new DTLS extensions in recent browsers             - 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:          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