Hey everyone!

Here are our meeting logs: http://meetbot.debian.net/tor-meeting/2023/tor-meeting.2023-09-07-15.57.html

And our meeting pad:

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

Next meeting: Thursday, Sep 14 16:00 UTC Facilitator: onyinyang

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 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 139 <-- hackerncoder, irl, joydeep, meskio, emmapeel working on it * https://pad.riseup.net/p/sponsor139-meeting-pad

== Announcements ==

== Discussion ==

* No webtunnel and conjure options at https://metrics.torproject.org/userstats-bridge-transport.html * there is an issue on the metrics side: https://gitlab.torproject.org/tpo/network-health/metrics/website/-/issues/40... * is already developed and will be deployed next week * Upgrading Go toolchain for snowflake * https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snowf... * https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snowf... * some dependencies like uTLS need go 1.20+ * debian stable has go 1.19, it will be harder to make packages for backports * we'll try to get the package in apt.tpo * we think is more important to keep up to date with dependencies * release new snowflake version * https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snowf... * is broken in android API 30+ we need a release to fix it * shelikhoo will make a release * snowflake-02 outage https://lists.torproject.org/pipermail/anti-censorship-team/2023-September/0... * https://www.insidehighered.com/news/tech-innovation/teaching-learning/2023/0... * the university got disconnected from the internet for we days

== Actions ==

== Interesting links ==

* Firefox planning to ship ECH by default. Think about resurrecting meek-esni? * https://github.com/net4people/bbs/issues/280 * https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/meek/... * https://opencollective.com/censorship-circumvention/projects/snowflake-daily...

== 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): 2023-09-07 Last week: - finished writing shadow simulations guide for PTs (will post later today) - discussed weird increase in Snowflake client polls This week: - deploy the lox distributor for testing with rdsys - https://gitlab.torproject.org/tpo/anti-censorship/lox-rs/-/issues/19 - followup on conjure reliability issues - visualize and write up some snowflake shadow simulation results

Needs help with:

dcf: 2023-09-07 Last week: - investigated a snowflake-02 bridge outage that caused a temporary increase in client polls https://lists.torproject.org/pipermail/anti-censorship-team/2023-September/0... - merged goptlib STATUS TYPE=version and tagged v1.5.0 https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/goptl... - opened a merge request to remove the unique proxy IP address counting code from the broker https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snowf... Next week: - revise encapsulation.ReadData redesign to return an error in the case of a short buffer https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snowf... - 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: 2023-09-07 Last week: - vacation :) - coordinate with TPA to get a VM for a rdsys staging server - review lyrebird merge requests Next week: - deploy the rdsys staging server

Shelikhoo: 2023-09-07 Last Week: - [Merge Request Awaiting] Add SOCKS5 forward proxy support to snowflake (snowflake!64) (stalled) - logcollector alert system - Add Remote Network Address Mapping in HTTP Upgrade Transport (https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/webtu...) - Merge request reviews Next Week/TODO: - Add Remote Network Address Mapping in HTTP Upgrade Transport (https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/webtu...) (Continue) - Release new version of snowflake - Merge request reviews

onyinyang: 2023-09-07 Last week(s): - Finished up implementation of new approach for getting resources https://gitlab.torproject.org/tpo/anti-censorship/lox-rs/-/merge_requests/24 - Bug hunting for what turned out to be a serialize/deserialize issue caused by the Dedup filter implementation https://gitlab.torproject.org/tpo/anti-censorship/lox-rs/-/merge_requests/42 - Updating dependencies from renovate bot MRs This week: - Continue updating dependencies, check how complicated it will be to update failing updates, such as: - aes-gcm: https://gitlab.torproject.org/tpo/anti-censorship/lox-rs/-/merge_requests/35 - base64: https://gitlab.torproject.org/tpo/anti-censorship/lox-rs/-/merge_requests/36 - Work on adding metrics (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?