Hey everyone!
Here are our meeting logs:
http://meetbot.debian.net/tor-meeting/2023/tor-meeting.2023-11-23-15.58.html
And our meeting pad:
Anti-censorship work meeting pad
···
--------------------------------
Anti-censorship
--------------------------------
Next meeting: Thursday, Nov 30 16:00 UTC
Facilitator: cohosh
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 ==
== Discussion ==
\* manifest v3 deprecation in browsers and snowflake webextension
\* https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snowflake-webext/-/issues/29
\* https://developer.chrome.com/blog/resuming-the-transition-to-mv3/
\* google chrome will stop supporting mv2 June 2024
\* will the snowflake webextension stop working? do we want to do something? or just reommend firefox?
\* BridgeStatus format change
\* Introduced in https://gitlab.torproject.org/tpo/anti-censorship/connectivity-measurement/probeobserver/-/merge_requests/5
\* Example: https://gitlab.torproject.org/tpo/anti-censorship/connectivity-measurement/bridgestatus/-/blob/main/recentResult_cnnext?ref_type=heads
== Actions ==
== Interesting links ==
\* https://www.rfc-editor.org/info/rfc9505 A Survey of Worldwide Censorship Techniques
== 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-11-09
Last week:
- conjure bridge maintenance
- caught a bug in safelog library
- Log scrubber fails to scrub messages with multiple space-separated IP addresses (#40306) · Issues · The Tor Project / Anti-censorship / Pluggable Transports / Snowflake · GitLab
- caught problem with domain front in conjure
- 503 error when contacting registration server (#38) · Issues · The Tor Project / Anti-censorship / Pluggable Transports / conjure · GitLab
This week:
- lox tor browser UX integration
- lox distributor testing
- look into alternative domain fronting providers
Needs help with:
dcf: 2023-11-09
Last week:
- revised encapsulation.ReadData redesign to return an error in the case of a short buffer Have encapsulation.ReadData read into a provided buffer (!154) · Merge requests · The Tor Project / Anti-censorship / Pluggable Transports / Snowflake · GitLab
- security upgrade to tor 0.4.8.8 on snowflake bridges Upgrade tor on snowflake bridges to 0.4.8.8 for TROVE 2023 004 (#40305) · Issues · The Tor Project / Anti-censorship / Pluggable Transports / Snowflake · GitLab
- sent emails to make contacts for uTLS-like fingerprint obfuscation in pion/dtls
Next week:
- 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
Before EOY 2023:
- move snowflake-02 to new VM
Help with:
meskio: 2023-11-23
Last week:
- run som experiments on more frequent bridgestrap tests (bridgestrap#39)
- investigate failure on rdsys integration tests (rdsys#180)
- prepare a deployment of rdsys with secret config params separated (rdsys#92)
- work on the rdsys staging server (rdsys#170)
- organize work for Sponsor 150
Next week:
- deploy rdsys with secret config params separated (rdsys#92)
- setup rdsys staging server (rdsys#170)
Shelikhoo: 2023-11-23
Last Week:
- Work on snowflake performance improvement (WIP): Files · dev-speedwithudp · shelikhoo / Snowflake · GitLab
- Updated probeobserver to support both snowflake bridges and updated communication system between China's vantage point and log collector Updated snowflake support for custom bridge line (!5) · Merge requests · The Tor Project / Anti-censorship / Connectivity Measurement / probeobserver · GitLab
- Merge request reviews
Next Week/TODO:
- Write Tor Spec for Armored URL (continue)
- Work on snowflake performance improvement (WIP): Files · dev-speedwithudp · shelikhoo / Snowflake · GitLab
- Merge request reviews
onyinyang: 2023-11-23
Last week(s):
- Vacation!
- Hackweek: Docs for Lox Improve Lox Documentation (#20) · Issues · The Tor Project / Community / Hackweek · GitLab
- Preparation for publishing Lox crates to crates.io
This week:
- Finishing up on remaining docs tasks for crates.io publishing
- SOTO anti-censorship team presentation preparation
-
(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?