[tor-project] Anti-censorship team meeting notes, 2024-08-15
onyinyang
onyinyang at torproject.org
Mon Aug 19 14:20:30 UTC 2024
Hey everyone! Sorry for the delay in getting the meeting notes sent out
from Thursday.
Here are our meeting logs:
http://meetbot.debian.net/tor-meeting/2024/tor-meeting.2024-08-15-16.00.html
And our meeting pad:
Anti-censorship work meeting pad
--------------------------------
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:https://gitlab.torproject.org/groups/tpo/anti-censorship/-/boards
* The anti-censorship team's wiki page:
*
https://gitlab.torproject.org/tpo/anti-censorship/team/-/wikis/home
* Past meeting notes can be found at:
* https://lists.torproject.org/pipermail/tor-project/
* Tickets that need reviews: from projects, we are working on:
* All needs review tickets:
*
https://gitlab.torproject.org/groups/tpo/anti-censorship/-/merge_requests?scope=all&utf8=%E2%9C%93&state=opened&assignee_id=None
* Project 158 <-- meskio working on it
*
https://gitlab.torproject.org/groups/tpo/anti-censorship/-/issues/?label_name%5B%5D=Project%20158
== 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://gitlab.torproject.org/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
-
https://gitlab.torproject.org/tpo/anti-censorship/team/-/issues/142
- 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
-
https://gitlab.torproject.org/tpo/anti-censorship/lox/-/merge_requests/147
Needs help with:
dcf: 2024-08-10
Last week:
- opened minor issue for chaning error messages from %v to %w
https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snowflake/-/merge_requests/355
- reviewed snowflake unreliable+unordered data channels rev2
https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snowflake/-/merge_requests/315#note_3055729
- snowflake azure CDN bookkeeping
https://gitlab.torproject.org/tpo/anti-censorship/team/-/wikis/Snowflake-costs/diff?version_id=b433702d52782fa03db011d2702417afa4e29380
Next week:
- open issue to have snowflake-client log whenever KCPInErrors
is nonzero
https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snowflake/-/issues/40262#note_2886018
- parent:
https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snowflake/-/issues/40267
- 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
https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snowflake/-/issues/40349
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:
https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snowflake-webext/-/issues/29#note_3035763
- 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:
https://gitlab.torproject.org/tpo/applications/tor-browser/-/issues/42974
- Work on outstanding milestone issues:
in particular:
https://gitlab.torproject.org/tpo/anti-censorship/lox/-/issues/69
- 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
-------------- next part --------------
A non-text attachment was scrubbed...
Name: OpenPGP_0x156A6435430C2036.asc
Type: application/pgp-keys
Size: 6206 bytes
Desc: OpenPGP public key
URL: <http://lists.torproject.org/pipermail/tor-project/attachments/20240819/4c29dc26/attachment.key>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: OpenPGP_signature.asc
Type: application/pgp-signature
Size: 840 bytes
Desc: OpenPGP digital signature
URL: <http://lists.torproject.org/pipermail/tor-project/attachments/20240819/4c29dc26/attachment.sig>
More information about the tor-project
mailing list