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

Hey everyone!

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

And our meeting pad:

Anti-censorship work meeting pad

···

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

Next meeting: Thursday, December 12 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: onyinyang

== 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 projects, we are working on:
* All needs review tickets:
* Merge requests · Anti-censorship · GitLab
* Project 158 <-- meskio working on it
* Issues · Anti-censorship · GitLab

== Announcements ==

== Discussion ==

 \* Creating container mirror for anti\-cenosorship projects to deal with docker hub restriction
     \* https://gitlab.torproject.org/tpo/tpa/team/-/issues/41914#note_3138851
     \* https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snowflake/-/issues/40393#note_3138149
     \* we&#39;ll create a repo in gitlab that mirrors the needed images by it&#39;s CI
 \* WIP MR: Add covert\-dtls to proxy and client
     \* https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snowflake/-/merge_requests/448
     \* is a big change, shelikhoo did review it but more eyes are needed
     \* cohosh will look into it
 \* Reasonable PollInterval for Orbot? https://github.com/tladesignz/IPtProxy/pull/58
     \* standalone proxy does 5seconds poll interval
     \* orbot was doing the same but being mobile it might be better to be slower
     \* 120sec sounds like a good number seeing that there are already a lot of proxies

== Actions ==

== Interesting links ==

 \* call out for webtunnel bridges for Russia:
     \* https://blog.torproject.org/call-for-webtunnel-bridges/
 \* Deprecation BridgeDB blogpost:
     \* https://blog.torproject.org/making-connections-from-bridgedb-to-rdsys/

== Reading group ==

 \* We will discuss &quot;&quot; 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-12-05
Last week:
- fixed the logging of the new proxy event (snowflake#40413)
- fixed "bad offer from broker" log spam (snowflake#40408)
- started looking at alerts for censorship events (snowflake#40416)
- updated the RFC 5780 compatible STUN servers in bridge lines (snowflake#40304)
- deployed new Snowflake bridge lines (tor-browser-build!1115, rdsys-admin!32)
- worked on analysis of snowflake metrics (snowflake#40394)
- created wiki page for snowflake release procedure

This week:
- work on snowflake broker metrics improvements
- write a script to easily test STUN servers in snowflake's torrc
- finish snowflake dependency upgrades that were causing problems
- take a look at snowflake web and webext translations and best practices
- make changes to Lox encrypted bridge table
- Draft: Simplify BridgeLine struct and make it variable length (!147) · Merge requests · The Tor Project / Anti-censorship / lox · GitLab
Needs help with:
- what was that censorship alerts mailing list?

dcf: 2024-11-21
Last week:
- released goptlib v1.6.0 goptlib v1.6.0 - anti-censorship-team - lists.torproject.org
Next week:
- comment on updates to unreliable snowflake transport 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
Help with:

meskio: 2024-12-05
Last week:
- rdsys stopped accepting new bridges (rdsys#249)
- deploy onionsproutsbot distributing TorBrowser for win7 (onionsproutsbot#64)
- support webtunnel bridge operators
- prepare splintercon presentations
- more grant writting life
- review BridgeDB deprecation blogpost
Next week:
- AFK at splintercon

Shelikhoo: 2024-12-05
Last Week:
- [Pending] snowflake broker update/reinstall(cont.):

- [Awaiting Review] Unreliable+unordered WebRTC data channel transport for Snowflake rev2 (cont.)( Draft: Unreliable+unordered WebRTC data channel transport for Snowflake rev2 (!315) · Merge requests · The Tor Project / Anti-censorship / Pluggable Transports / Snowflake · GitLab ) improvements
- Merge request reviews
- Work on finishing snowflake container release(and fix the comments)
- Incorrectly flattened container image with "pull" command
Incorrectly flattened container image with "pull" command (#40417) · Issues · The Tor Project / Anti-censorship / Pluggable Transports / Snowflake · GitLab
Next Week/TODO:
- Merge request reviews
- Incorrectly flattened container image with "pull" command
Incorrectly flattened container image with "pull" command (#40417) · Issues · The Tor Project / Anti-censorship / Pluggable Transports / Snowflake · GitLab
(cont.)
- Create mirror for frequently used container image

onyinyang: 2024-12-05
Last week(s):
- working on refactor of Lox (library) protocols to improve issuing efficiency as described in: https://eprint.iacr.org/2024/1552.pdf
- finished aside from check-blockage and trust promotion protocols which may not be convertable
- Released lox-library and lox-utils 0.2.0 for browser integration
- stablized some dependencies for integration into firefox with XPCOM
- created bridgeauth feature to separate client/server lox functionality
- Improved pipeline for lox workspace
- Added lox-context db cleanup
Next week:
- Fix up Troll-patrol MR
- Deploy test distributor
- update lox protocols to return duplicate responses for an already seen request
- Continue work on implementing issuer efficiency for check-blockage and trust-promotion protocols
- Work on outstanding milestone issues:
in particular: Increase the acceptable time for bridgeline failure (#69) · Issues · The Tor Project / Anti-censorship / lox · GitLab
- key rotation automation

     Later:
     pending decision on abandoning lox wasm in favour of some kind of FFI? https://gitlab.torproject.org/tpo/applications/tor-browser/-/issues/43096):
         \- add pref to handle timing for pubkey checks in Tor browser
         \- add trusted invitation logic to tor browser integration:

- 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\!\):
     \- 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: 2024-12-05
Last weeks:
- Adjusting to post-student life
- WIP MR: Add covert-dtls to proxy and client
- Add covert-dtls to proxy and client (!448) · Merge requests · The Tor Project / Anti-censorship / Pluggable Transports / Snowflake · GitLab
Next weeks:
- Test Snowflake fork with covert-dtls
- Condensing thesis into paper (on hold)
Help with:
- Test covert-dtls in Snowflake

Facilitator Queue:
onyinyang meskio shelikhoo
1. First available staff in the Facilitator Queue will be the facilitator for the meeting

--
---
onyinyang

GPG Fingerprint 3CC3 F8CC E9D0 A92F A108 38EF 156A 6435 430C 2036

1 Like