Hey everyone!

Here are our meeting logs: http://meetbot.debian.net/tor-meeting/2024/tor-meeting.2024-09-05-16.00.html

And our meeting pad:

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

Next meeting: Thursday, September 12 16:00 UTC Facilitator: onyinyang ^^^(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 ==

* (empty) == Actions ==

== Interesting links ==

* https://www.bamsoftware.com/talks/wac7-fep/         * dcf's recent talk (45 min) "How cryptography relates to Internet censorship circumvention"

== Reading group ==     * We will discuss "SpotProxy: Rediscovering the Cloud for Censorship Circumvention " on September 12         * https://www.cs-pk.com/sec24-spotproxy-final.pdf         * https://censorbib.nymity.ch/#Kon2024b         * 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-08-29     Last week:         - went through massive todo backlog         - dealt with breaking changes in KCP library         - answered a bunch of Lox questions for integration work         - cleared out review backlog     This week:         - take a look at snowflake web and webext translations and best practices         - make changes to Lox encrypted bridge table             - https://gitlab.torproject.org/tpo/anti-censorship/lox/-/merge_requests/147     Needs help with:

dcf: 2024-09-05     Last week:     Next week:         - archive snowflake webextension v0.9.0 (manifest V3)         - comment as requested on kcp v5.6.17 upgrade         - 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:         - tell me when to restart the brokers for https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snowf...

meskio: 2023-08-29     Last week:         - don't distribute blocked-in bridges in moat and https (rdsys#204)         - plan switch from BridgeDB to rdsys (rdsys#218)     Next week:         - add ipversion subscription to rdsys         - be ready for the BridgeDB switch

Shelikhoo: 2024-09-05     Last Week:             - snowflake broker update/reinstall             - Review fix: extension not starting after browser restart( https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snowf... )             - Research: respond to YSA-2024-03 (YubiKey < 5.7 side-channel attack on ECC private keys) (https://gitlab.torproject.org/tpo/tpa/team/-/issues/41744)             - Release Snowflake Webext(again)             - Merge request reviews     Next Week/TODO:         - Merge request reviews         - snowflake broker update/reinstall: https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snowf...

onyinyang: 2023-08-29     Last week(s):         - continued with key rotation integration work         - collected issues and TODOs for all Lox work that needs to be done before deployment

Next week:         - finish up key rotation integration work         - add pref to handle timing for pubkey checks in Tor browser         - update lox protocols to return duplicate responses for an already seen request         - add trusted invitation logic to tor browser integration: https://gitlab.torproject.org/tpo/applications/tor-browser/-/issues/42974         - Work on outstanding milestone issues:             in particular: https://gitlab.torproject.org/tpo/anti-censorship/lox/-/issues/69             - key rotation automation

Later:         - begin implementing 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

(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: 2024-08-22         Last weeks:             - Expose hooks in pion/webrtc library         Next weeks:             - Update Snowflake to use latest pion upstream releases (DTLS: v3 and WebRTC: beta v4)             - Test Snowflake fork with covert-dtls             - Condensing thesis into paper         Help with:             - Feedback on thesis

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

(This message is unsigned as my email client is having some issues....)