Hey everyone! Here are our meeting logs: https://meetbot.debian.net/tor-meeting/2026/tor-meeting.2026-01-08-16.01.htm... And our meeting pad: Anti-censorship work meeting pad -------------------------------- Anti-censorship -------------------------------- Next meeting: Thursday, January 15 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: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 == == Discussion ==     * Relay connect tests / feedback if proxies cannot reach the Snowflake bridge         * https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snowf... == Actions ==     * == Interesting links ==     * https://filter.watch/english/2026/01/05/network-monitorig-december-2025-inte...     * https://opencollective.com/censorship-circumvention/projects/snowflake-daily...         * €4,129.50 for snowflake-01 bandwidth in 2025 https://opencollective.com/censorship-circumvention/projects/snowflake-daily... == Reading group ==     * We will discuss "CenPush: Blocking-Resistant Control Channel Using Push     * Notifications" on January 8th, 2026         * https://petsymposium.org/popets/2025/popets-2025-0153.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?     * Next in the Reading Group Queue:         * Fingerprint-resistant DTLS for usage in Snowflake: https://www.petsymposium.org/foci/2025/foci-2025-0006.php == 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-01-08     Last week:         - Finished moving to TPO AWS account for SQS (snowflake#40498)             - deployed new Snowflake broker with multiple SQS queues             - updated snowflake sqs bridge lines in circumvention settings (rdsys-admin!45)         - Refrain from logging SQS cleanup error (snowflake!654)         - Updated SQS costs         - Completed proxy churn experiment analysis (snowflake#40494)         - Successfully tested new Conjure bridge line         - Opened an issue about proxy-bridge reachability checks             - https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snowf...     Next week:         - research snowflake enumeration attacks (snowflake#40396)         - follow up on snowflake rendezvous failures (snowflake#40447)         - revisit conjure integration with lyrebird         - take a look at potential snowflake orbot bug             - https://github.com/guardianproject/orbot-android/issues/1183 dcf: 2026-01-08     Last week:         - archived snowflake-webext 0.9.8 https://archive.org/details/snowflake-webextension-0.9.8     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: 2025-12-11     Last week:         - make an alert for failing builtin bridges (team#141)         - merge multi-domain meek and coordinate with TB to update it (lyrebird!142)         - investigate gettor email issues (rdsys#290)         - prepare grant     Next week:         - make gettor email reply Shelikhoo: 2026-01-08     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             - [MR]Update WatchTower URL for WebTunnel (https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/webtu...)             - [Invesgate] Invesage Report about utls randomlized fingerprint interference with tls1.3 (https://gitlab.torproject.org/tpo/anti-censorship/team/-/issues/171)     Next (working) Week/TODO:         - Merge request reviews         - [Deployment]Unreliable+unordered WebRTC data channel transport for Snowflake rev2 (cont.)( https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snowf... ) Building custom Tor Browser with patch applied         - [Merge] Add automated binary release support (https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snowf...) onyinyang: 2026-01-08     Last week(s):         - Break         - Closed #129 with regular cronjob to restart the distributor             - Moving to go-imap v2 is on hold until the library is more stable Next week:     - 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: https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/conju...               - 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         - 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: 2026-01-08         Last weeks:             - MR: https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snowf...             - Implementing DTLS 1.3 in pion         Next weeks:             - Implementing DTLS 1.3 in pion         Help with:             - 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