[tor-project] Anti-censorship team meeting notes, 2024-06-27

Hey everyone!

Here are our meeting logs:

And our meeting pad:

Anti-censorship work meeting pad



Next meeting: Thursday, July 11 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:Development · Boards · Anti-censorship · GitLab
* The anti-censorship team's wiki page:
* Home · Wiki · The Tor Project / Anti-censorship / Team · GitLab
* Past meeting notes can be found at:
* The tor-project Archives
* Tickets that need reviews: from sponsors, we are working on:
* All needs review tickets:
* Merge requests · Anti-censorship · GitLab
* Sponsor 96 <-- meskio, shell, onyinyang, cohosh
* Sponsor 96: Rapid Expansion of Access to the Uncensored Internet through Tor in China, Hong Kong, & Tibet · The Tor Project · GitLab
* Sponsor 150 <-- meskio working on it
* Issues · Anti-censorship · GitLab

== Announcements ==

 \* No meeting July 4 \(Tor&#39;s midyear break\)

== Discussion ==

 \* Snowflake WebExtension for Manifest version 3 is almost done, only lacking user info consent support\. \(shelikhoo\)
 \* Ongoing censorship events:
     \* https://gitlab.torproject.org/tpo/anti-censorship/censorship-analysis/-/issues/40043 \(Myanmar\)
     \* https://gitlab.torproject.org/tpo/anti-censorship/censorship-analysis/-/issues/40044 \(Algeria\)
     \* https://gitlab.torproject.org/tpo/anti-censorship/censorship-analysis/-/issues/40031 \(Uzbekistan\)

== Actions ==

== Interesting links ==


== 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 ==
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
- Squash PTs into Lyrebrid (#40015) · Issues · The Tor Project / Anti-censorship / Pluggable Transports / lyrebird · GitLab
- Adapt Conjure Tor PT into a library that could be easily integrated into lyrebird (#42) · Issues · The Tor Project / Anti-censorship / Pluggable Transports / conjure · GitLab
This week:
- take a look at snowflake web and webext translations and best practices
- make changes to Lox encrypted bridge table
- Simplify BridgeLine struct and make it variable length (!147) · Merge requests · The Tor Project / Anti-censorship / lox · GitLab
Needs help with:

dcf: 2024-06-27
Last week:
- archived snowflake-webextension-0.8.3 Snowflake WebExtension 0.8.3 : The Tor Project : Free Download, Borrow, and Streaming : Internet Archive
Next week:
- review snowflake unreliable+unordered data channels rev2 Draft: Unreliable+unordered WebRTC data channel transport for Snowflake rev2 (!315) · Merge requests · The Tor Project / Anti-censorship / Pluggable Transports / Snowflake · GitLab
- open issue to have snowflake-client log whenever KCPInErrors is nonzero Deploy snowflake-server for QueuePacketConn buffer reuse fix (#40260) (#40262) · Issues · The Tor Project / Anti-censorship / Pluggable Transports / Snowflake · GitLab
- parent: Improve bug discovery process (#40267) · Issues · The Tor Project / Anti-censorship / Pluggable Transports / Snowflake · GitLab
- 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 Upgrade snowflake broker machine from Debian 10 (#40349) · Issues · The Tor Project / Anti-censorship / Pluggable Transports / Snowflake · GitLab

meskio: 2023-06-27
Last week:
- fix a parsing problem for cache-extrainfo when there is transport-info, don't reject the PT part of bridges (rdsys#205)
- sponsor 96 final report
- debug moat domain front failures
- add transport-info to the cached-extrainfo spec (torspec!63)
- report lyrebird version to tor (lyrebird!51)
Next week:
- investigate what builtin bridges are offline (team#141)
- report other PT versions to tor (snowflake, webtunnel)

Shelikhoo: 2024-06-27
Last Week:
- Chrome Manifest V3 transition: Migrate to Manifest V3 (#29) · Issues · The Tor Project / Anti-censorship / Pluggable Transports / Snowflake WebExtension · GitLab

             \- Merge request reviews
 Next Week/TODO:
     \- Merge request reviews
     \- Chrome Manifest V3 transition: https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snowflake-webext/-/issues/29#note_3035763

onyinyang: 2023-06-20
Last week(s):
- MSR talk
- Working toward building tor-browser with lox-wasm binary to help out with
integration work as needed: ran into many issues trying to do this with Fedora
Next week:
- Global Gathering Application
- Fix Key Rotation MR for hyper v1
- Working toward building tor-browser with lox-wasm binary to help out with
integration work as needed: resolve build issues on Fedora
- Work on outstanding milestone issues: Lox Ready for Open Testing Call · Milestones · The Tor Project / Anti-censorship / lox · GitLab
- prepare for end to end testing of the Lox system with browser integration
- 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&#39;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&#39;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-06-20
Last weeks:
- Writing my thesis
- Add randomized ClientHello fingerprints to library
Next weeks:
- Wait for pion upstream releases
- Test Snowflake fork with covert-dtls
- Taking time off (AFK)
Help with:
- Test Snowflake fork with covert-dtls

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

1 Like