Hey everyone!

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

And our meeting pad:

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

Next meeting: Thursday,Feb  02 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 ==     * snowflake-broker.azureedge.net is still working, a week after the announced shutdown date.(It still work at Jan 30)         curl -s -i https://snowflake-broker.azureedge.net/amp/client/

== Discussion ==

== Actions ==

== Interesting links ==

* "Identifying VPN Servers through Graph-Represented Behaviors"         * https://dl.acm.org/doi/10.1145/3589334.3645552         * https://dl.acm.org/doi/pdf/10.1145/3589334.3645552         * https://github.com/chenxuStep/VPNChecker

== 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-30     Last week:         - debugged problem with tor conjure PT getting invalid addresses             - https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/conju...         - reviewed conjure merge requests         - made more improvements to phantombox, the conjure test environment     This week:         - support conjure work         - take a look at potential snowflake orbot bug             - https://github.com/guardianproject/orbot-android/issues/1183         - maybe do some lox work

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-30     Last week:         - investigate issues on TorBrowser in Iran (tor-browser#43454)         - config repositories in irc tor bot         - grant writting and review     Next week:         - containarize rdsys

Shelikhoo: 2024-01-30     Last Week:          - [Refine] Unreliable+unordered WebRTC data channel transport for Snowflake rev2 (cont.)( https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snowf... ) improvements         - Merge request reviews     Next Week/TODO:         - Merge request reviews         - [Test] Unreliable+unordered WebRTC data channel transport for Snowflake rev2 (cont.)( https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snowf... ) improvements

onyinyang: 2025-01-30     Last week(s):         - Got conjure up and running locally! (Thanks cohosh!)         - uTLS implemented for conjure         - moved uTLS library to ptutil         - started work on ampcache     Next week:         - continue on alternative registration methods (ampcache, sqs)         - Add decoy registration option         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-30         Last weeks:                 - Testing Tor Build with covert-dtls (troubleshooting becoming DTLS client with ICE and different NAT/host types).         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