Hey everyone!

Here are our meeting logs:

http://meetbot.debian.net/tor-meeting/2024/tor-meeting.2024-07-25-16.00.html

And our meeting pad:

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

Next meeting: Thursday, August 1 16:00 UTC Facilitator: shelikhoo ^^^(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: 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 150 <-- meskio working on it * https://gitlab.torproject.org/groups/tpo/anti-censorship/-/issues/?label_nam...

== Announcements ==

* Roger wrote up his Snowflake blocking experiment notes, https://lists.torproject.org/pipermail/anti-censorship-team/2024-July/000343... -- more hackweek/experiment opportunities remain :)

== Discussion ==

== Actions ==

== Interesting links ==

* https://arxiv.org/abs/2405.13310 "Bytes to Schlep? Use a FEP: Hiding Protocol Metadata with Fully Encrypted Protocols" * update to https://censorbib.nymity.ch/#Fenske2023a "Security Notions for Fully Encrypted Protocols" from FOCI 2023 * https://github.com/tst-race/raceboat/tree/documentation Raceboat source code * https://github.com/v2fly/v2ray-core/discussions/3096 * V2Ray has received a security audit from 7ASecurity * https://www.opentech.fund/security-safety-audits/v2ray-security-audit/

== 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-06-27 Last week: - snowflake-webext updates - reviewed mv3 prototype - helped onyinyang on rebasing and debugging wasm-bindgen - worked on squashing Conjure PT into lyrebird - https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/lyreb... - https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/conju... 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-07-11 Last week: - snowflake azure CDN bookkeeping https://gitlab.torproject.org/tpo/anti-censorship/team/-/wikis/Snowflake-cos... Next week: - review snowflake unreliable+unordered data channels rev2 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 - 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-07-25 Last week: - investigate what builtin bridges are offline and contact operators (team#141) - work on Sponsor 96 final report - ignore dots on emails on the email distributor (rdsys#208) Next week: - check if lyrebird reduces size removing old PTs (lyrebird#40016)

Shelikhoo: 2024-07-25 Last Week: - Chrome Manifest V3 transition: https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snowf... - Merge request review - S96 Report Response to feedback - Merge request reviews Next Week/TODO: - Merge request reviews - Chrome Manifest V3 transition: https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snowf...

onyinyang: 2023-07-25 Last week(s): - FOCI/PETS online - Working on tor-browser integration with updated lox-wasm binary: - switched back to building modules and using them with a downloaded Tor browser - tor-browser-build was mixing up inputs for one function which caused the module to error at load time, flipping them seems to have fixed the error - updating Lox module for key rotation logic - Identified that the lastPassed variable is not working as expected for Lox: https://gitlab.torproject.org/tpo/anti-censorship/rdsys/-/issues/209 and is probably the reason behind this issue: https://gitlab.torproject.org/tpo/anti-censorship/lox/-/milestones/1#tab-iss... Next week: - continue with key rotation integration work - fix lastPassed issue in rdsys (or lox if the rdsys fix is too complicated) - 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: 2023-07-11 Last weeks: - Completed my master thesis (https://theodorsm.net/thesis) - Had some time off Next weeks: - Wait for pion upstream releases - Test Snowflake fork with covert-dtls - Condensing thesis into paper Help with: - Feedback on thesis

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