[tor-project] Anti-censorship team meeting notes, 2024-06-20
onyinyang
onyinyang at torproject.org
Thu Jun 20 18:19:37 UTC 2024
Hey everyone!
Here are our meeting logs:
http://meetbot.debian.net/tor-meeting/2024/tor-meeting.2024-06-20-16.00.html
And our meeting pad:
Anti-censorship work meeting pad
--------------------------------
Anti-censorship
--------------------------------
Next meeting: Thursday, June 27 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 sponsors, 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
* Sponsor 96 <-- meskio, shell, onyinyang, cohosh
* https://gitlab.torproject.org/groups/tpo/-/milestones/24
* Sponsor 150 <-- meskio working on it
*
https://gitlab.torproject.org/groups/tpo/anti-censorship/-/issues/?label_name%5B%5D=Sponsor%20150
== Announcements ==
* No meeting July 4 (Tor's midyear break)
== Discussion ==
* theodorsm's thesis and DTLS library
* https://github.com/theodorsm/covert-dtls
* trouble integrating it into snowflake - dependency/version issues
* breaking changes with the version of pion/stun used in snowflake
* but snowflake is already using the latest pion/stun?
* theodorsm forked the older version of pion/dtls used by
snowflake and re-applied the covert-dtls changes
* snowflake is using pion/dtls v2.2.7 while latest is
v2.2.11, but unreleased code is needed (should come with v2.2.12)
* as specified by current pion/webrtc v3.2.42
https://github.com/pion/webrtc/blob/v3.2.42/go.mod#L7
== Actions ==
== Interesting links ==
*
== 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-20
Last week:
- wrote up a forum post to guide users through snowflake
browser extension consent prompt
-
https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snowflake-webext/-/issues/97
- found and fixed a bug with the consent prompt flow
-
https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snowflake-webext/-/issues/98
- deployed version 0.8.3 of the snowflake extension
- showed onyinyang how to test and debug the Lox module in Tor
Browser
- reproduced reported SQS rendezvous bug with two bridges
-
https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snowflake/-/issues/40363
- followed up on idea to set SQS anonymous access policies
-
https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snowflake/-/issues/40364
- reviewed merge requests and updated dependencies
This week:
- followup on snowflake extension UX fixes
- 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
-
https://gitlab.torproject.org/tpo/anti-censorship/lox/-/merge_requests/147
- update wasm-bindgen fork to fix some bugs and hopefully
upstream changes
Needs help with:
dcf: 2024-06-20
Last week:
Next week:
- review snowflake unreliable+unordered data channels rev2
https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snowflake/-/merge_requests/315
- 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-06-20
Last week:
- clean up bridgestrap logs to make them more readable
(bridgestrap#43)
- investigate why bridgestrap is filling polyanthum disk
- look into the builtin bridges being offline and figure more
problems with bridgestrap to look into (tpa/team##41651)
- review and merge refactor on lyrebird copyLoop (lyrebird!50)
Next week:
- investigate what builtin bridges are offline (team#141)
- why is the status page mentioning vanilla part of obfs4
bridges? (rdsys#205)
Shelikhoo: 2024-06-06
Last Week:
- [Merge Request Waiting] Add Container Image Mirroring from
Tor Gitlab to Docker
Hub(https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snowflake/-/merge_requests/280)
- [Merge Request Waiting] Snowflake Performance Improvement
rev2
(https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snowflake/-/merge_requests/315)
- Chrome Manifest V3 transition:
https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snowflake-webext/-/issues/29#note_3035763
- Upgrade snowflake broker machine from Debian 10
(https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snowflake/-/issues/40349)
- Address TTP-03-001 WP1: Snowflake broker
vulnerability(https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snowflake/-/issues/40329)
- Vantage point maintaince
- merge request processing
- Merge request reviews
Next Week/TODO:
- Merge request reviews
onyinyang: 2023-06-20
Last week(s):
- MSR talk
- Working toward building tor-browser with lox-wasm binary to
help out with
integration work as needed: ran into many issues trying to
do this with Fedora
Next week:
- Global Gathering Application
- Fix Key Rotation MR for hyper v1
- Working toward building tor-browser with lox-wasm binary to
help out with
integration work as needed: resolve build issues on Fedora
- Work on outstanding milestone issues:
https://gitlab.torproject.org/tpo/anti-censorship/lox/-/milestones/1#tab-issues
- 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'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: 2023-06-20
Last weeks:
- Writing my thesis
- Add randomized ClientHello fingerprints to library
Next weeks:
- Wait for pion upstream releases
- Test Snowflake fork with covert-dtls
- Taking time off (AFK)
Help with:
- Test Snowflake fork with covert-dtls
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/20240620/46d9382c/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/20240620/46d9382c/attachment.sig>
More information about the tor-project
mailing list