Hey everyone!

Here are our meeting logs: http://meetbot.debian.net/tor-meeting/2024/tor-meeting.2024-04-25-16.15.html

And our meeting pad:

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

Next meeting: Thursday, May 2 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: 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 sponsors, we are working on:         * All needs review tickets:             * https://gitlab.torproject.org/groups/tpo/anti-censorship/-/merge_requests?sc...         * Sponsor 96 <-- meskio, shell, onyinyang, cohosh             * https://gitlab.torproject.org/groups/tpo/-/milestones/24         * Sponsor 150 <-- meskio working on it             * https://gitlab.torproject.org/groups/tpo/anti-censorship/-/issues/?label_nam...

== Announcements ==

== Discussion ==

* What is the current repo for the snowflake website?         * https://gitlab.torproject.org/tpo/web/snowflake         * https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snowf...         * is in the process to be moved to tpo/web but not sure if it has already being moved     * Snowflake Performance Improvement:         * https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snowf...         * There is possible alternative design that would reduce complexity, should we do it? https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snowf...

== Actions ==

== Interesting links ==

* Maybe already known, Brave Browser has a snowflake proxy feature (since 2023) https://github.com/brave/brave-browser/issues/25315

== 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): 2024-04-25     Last week:         - worked on Lox integration testing         - released a new version of the snowflake addon             - https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snowf...     This week:         - follow up on reported SQS errors         - update wasm-bindgen fork to fix some bugs and hopefully upstream changes         - create a Lox test environment and instructions for the browser team             - https://gitlab.torproject.org/tpo/applications/tor-browser/-/issues/42503     Needs help with:

dcf: 2024-04-25     Last week:         - posted and briefly summarized the paper "Snowflake Anonymous Network Traffic Identification" https://lists.torproject.org/pipermail/anti-censorship-team/2024-April/00033... 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         - move snowflake-02 to new VM Help with:

meskio: 2023-04-25     Last week:         - bridgestrap not publishing collector metrics (bridgestrap#199)         - WIP of the email distributor in rdsys (rdsys#186)         - document the bridge distribution mechanisms in rdsys to replace bridges.tpo/info (rdsys#137)     Next week:         - email distributor in rdsys (rdsys#186)

Shelikhoo: 2024-04-18     Last Week:         - [Merge Request WIP] Add Container Image Mirroring from Tor Gitlab to Docker Hub(https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snowf...)         - [Merge Request Done] Rename Stable Container Tags to Latest https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snowf...         - [Fixed!] Investigate broken debian-testing pipeline for snowflake(Remove apt install lbzip2 to avoid broken dependencies: https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snowf...)                 - Merge request reviews     Next Week/TODO:         - Revise Snowflake Performance Improvement MR         - Merge request reviews

onyinyang: 2023-04-25     Last week(s):         - Responding to pre-existing MR reviews and other notifications/questions in gitlab

This week:         - Responding to pre-existing MR reviews and other notifications/questions in gitlab     Probably next week and beyond:         - preparing for upcoming panel (maybe)         - implement some preliminary user feedback mechanism to identify bridge blocking based on Vecna's work         - improve metrics collection/think about how to show Lox is working/valuable         - sketch out Lox blog post/usage notes for forum         - attempt hyper upgrade again and tokio upgrade

(long term things were discussed at the meeting!): https://pad.riseup.net/p/tor-ac-community-azaleas-room-keep         - 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: 2023-04-18         Last weeks:             - Extended Pion dtls library to support hooking of client hellos (PR: https://github.com/pion/dtls/pull/631). Fingerprint generation of firefox and chrome + mimicking using the client hello hook have been moved to its own repo: https://github.com/theodorsm/covertDTLS             - Gave some comments on the recent"Snowflake Anonymous Network Traffic Identification" paper: https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snowf....         Next weeks:             - Add hook to pion/webrtc so it can be used in snowflake.             - Test and validate mimicked client hello with snowflake.             - Add randomized fingerprint             - Analyze the snowflake captures done in "Snowflake Anonymous Network Traffic Identification" paper.         Help with:

Facilitator Queue:     meskio shelikhoo onyinyang 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