------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Anti-censorship
--------------------------------
Next meeting: Thursday, May 11 16:00 UTC
Weekly meetings, every Thursday at 16:00 UTC, in #tor-meeting at OFTC
(channel is logged while meetings are in progress)
== 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:
- The anti-censorship team's wiki page:
- Past meeting notes can be found at:
- Tickets that need reviews: from sponsors, we are working on:
- All needs review tickets:
- Sponsor 139 <-- hackerncoder, irl, joydeep, meskio, emmapeel working on it
== Announcements ==
== Discussion ==
- after a lot of research the proposed solution is to enable datagram transport on webrtc to deal with the packet loss situation
- that will convert webrtc into an unreliable channel, and snowflake will add reliablity with kcp
- (NO update from shell @ Apr 20)
- goptlib now lives in gitlab.torproject.org
== Actions ==
- read the safari snowflake extension code (team)
- try to reach the developer (itchyonion will write an email draft, and the team will go over it)
== Interesting links ==
- "Support
for features like advanced censorship circumvention or onion services
is not exactly straight forward on mobile operating systems, because
they tend to be way more locked down than traditional computers.
Currently, we can successfully test pluggable transports in 'managed'
mode on old versions of Android. However this technique will likely not
work on the latest version of Android and never worked iOS to begin
with. We have shared our findings with the Arti developer team and hope
they’ll work on getting us to full Pluggable Transports support,
integraing with our existing IPtProxy Library soon."
- Unofficial(?) Snowflake extension for Safari in Apple App Store?
== Reading group ==
- We will discuss "Lox: Protecting the Social Graph in Bridge Distribution" on 2023 May 18
- 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): last updated 2023-05-04
Last week:
- tor meeting
This week:
- catch up on emails
- foci stuff
- open issue about archiving snowflake prometheus metrics
- go over lox notes again from meeting
- lox-wasm tor browser builds
Needs help with:
dcf: 2023-04-20
- - open issue to disable /debug endpoint on snowflake broker
meskio: 2023-04-20
Last week:
- - update PTs to use goptlib from gitlab.tpo
- - distribute bridges in rdsys even if there fewer than requested in the hashring (rdsys#162)
- - add webtunnel support to BridgeDB (rdsys#142)
Next week:
Shelikhoo: 2023-05-04
Last Week:
- - [Merge Request Awaiting] Add SOCKS5 forward proxy support to snowflake (snowflake!64)
- - Finish all the accumulated task during in person meetup AFK
Next Week/TODO:
- - [Research] WebTunnel planning (Continue)
- - Try to find a place to host another vantage point
- - logcollector alert system
- - webtunnel document for proxy operator
- - Snowflake Performance Analysis
onyinyang: 2023-05-04
Last week:
- Tor meeting
This week:
- - finished up implementing metrics to check on flickering resources and ratios observed (maybe) awaiting review
- Working through changes to handle `gone` resources. rdsys changes are
tentatively implemented, Lox library changes are more hairy.
- (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 useable 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 sacrified 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?
Needs Help with:
- -
figuring out whether or not the metrics I added to rdsys actually
collect what we want them to. I can run prometheus locally but am unsure
how to match this with a realistic onbasca test that can actually show
whether the metrics are useful/correct. Is there a known way to do such
tests other than deploy and find out?
Itchy Onion: 2023-05-04
Last week:
This week:
- -
consulted network health team to understand what "offline" means from
the Metrics's POV (and discovered a small wording inconsistency in their
doc)
- - better understood the difference between "offline" and working (they are not mutually exclusive)
hackerncoder: 2023-04-20
last week:
- (py-)ooni-exporter torsf (snowflake)
- (py-)ooni-exporter web_connectivity
Next week:
- work on "bridgetester"?
- how does Iran block bridges?