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

Hey everyone!

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

And our meeting pad:

Anti-censorship work meeting pad

···

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

Next meeting: Thursday, June 13 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 ==

 \*

== Discussion ==

 \* can we retire monit in favor of prometheus?
     \* https://gitlab.torproject.org/tpo/tpa/prometheus-alerts/-/merge_requests/41
     \* https://gitlab.torproject.org/tpo/anti-censorship/monit-configuration/-/commits/main/?ref_type=HEADS
     \* we agree it makes sense to retire the monit service
     \* once the alerts are in place meskio will coordinate with philip to retire it
     \* this work is making me notice that some builtin bridges are not reachable since a while, looks like the monit service was down
     \* meskio will investigate the reachability of builtin bridges

 \* do we wish to include snowflake into lyrebrid?
     \* https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/lyrebird/-/issues/40015
     \* cohosh will start that work with the integration of conjure into lyrebird
     \* snowflake will have two challenges
         \* lyrebird is keeping an old version of uTLS to maintain a go version supported by windows 7 \(the plan is to drop that mid\-september\)
         \* udp proxy support might be triky to do in lyrebird
     \* we decide that we are ok with adding snowflake client support to lyrebird, but we&#39;ll need to see when and how complex will be
 \* lyrebird supports a bunch of PTs that are deprecated \(obfs2\-3 and scramblesuit\) should we remove those to gain space?
     \* https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/lyrebird/-/issues/40016
     \* once in a while there are reports of users still using those
     \* meskio will explore if removing them will gain any space and if not will drop the idea

== Actions ==

== Interesting links ==

 \* https://opencollective.com/censorship-circumvention/projects/snowflake-daily-operations/updates/2024-may-update

== 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-06
Last week:
- opened MR for lox db test fixup
- Use temporary directory for database tests (!188) · Merge requests · The Tor Project / Anti-censorship / lox · GitLab
- reviewed Lox MRs
- onboarded onyinyang on how to do reproducible builds and update the Lox module in Tor Browser
This week:
- take a look at shell's mv3 changes
- 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
- follow up on reported SQS errors
- update wasm-bindgen fork to fix some bugs and hopefully upstream changes
Needs help with:

dcf: 2024-06-06
Last week:
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-06
Last week:
- use safeprom in rdsys (rdsys#203)
- use safelog in rdsys
- add prometheus metrics to replace bridgedb metrics in rdsys (rdsys#188)
- add prometheus blackbox targets to replace monit targets (prometheus-alerts!41)
- add webtunnel bridges to the settings distributor (rdsys-admin!31)
- review lox key rotation MR (lox!183)
- review STATUS version support in tor (tor!820)
Next week:
- create an rdsys requests metrics puller that produces metrics for collector (rdsys#188)

Shelikhoo: 2024-06-06
Last Week:
- [Merge Request Waiting] Add Container Image Mirroring from Tor Gitlab to Docker Hub(Add Container Image Mirroring from Tor Gitlab to Docker Hub (!280) · Merge requests · The Tor Project / Anti-censorship / Pluggable Transports / Snowflake · GitLab)
- [Merge Request Waiting] Snowflake Performance Improvement rev2 (Draft: Unreliable+unordered WebRTC data channel transport for Snowflake rev2 (!315) · Merge requests · The Tor Project / Anti-censorship / Pluggable Transports / Snowflake · GitLab)
- Chrome Manifest V3 transition: Migrate to Manifest V3 (#29) · Issues · The Tor Project / Anti-censorship / Pluggable Transports / Snowflake WebExtension · GitLab
- Upgrade snowflake broker machine from Debian 10 (Upgrade snowflake broker machine from Debian 10 (#40349) · Issues · The Tor Project / Anti-censorship / Pluggable Transports / Snowflake · GitLab)
- Address TTP-03-001 WP1: Snowflake broker vulnerability(TTP-03-001 WP1: Snowflake broker vulnerability (#40329) · Issues · The Tor Project / Anti-censorship / Pluggable Transports / Snowflake · GitLab)
- Vantage point maintaince
- merge request processing
- Merge request reviews
Next Week/TODO:
- Merge request reviews

onyinyang: 2023-06-06
Last week(s):
- Finished key rotation implementation
- Working toward building tor-browser with lox-wasm binary to help out with
integration work as needed
- Preparation for MSR talk
Next week:
- MSR talk
- 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
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&#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-06
Last weeks:
- Writing for my thesis
Next weeks:
- Add hook to pion/webrtc so it can be used in snowflake, currently waiting on new pion/dtls release
- Add randomized fingerprints
- Writing my thesis
Help with:
- Finding conferences that are relevant for submitting paper on my work. (unfortunately too late for FOCI24)

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