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

onyinyang onyinyang at torproject.org
Fri Mar 8 01:04:25 UTC 2024


Hey everyone!

Here are our meeting logs:
http://meetbot.debian.net/tor-meeting/2024/tor-meeting.2024-03-07-15.58.html

And our meeting pad:

Anti-censorship work meeting pad
--------------------------------
Anti-censorship
--------------------------------

Next meeting: Thursday, March 14 16:00 UTC
Facilitator: shelikhoo

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 ==
- Ireland Constitution Amendment Referendum: March 8th

== Discussion ==

 From last week:
     * Unclear whether AWS will allow public disclosure of credentials
         * 
https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snowflake/-/issues/40337
         * we are waiting for their response which is dependent on 
rotating credentials (at least)
         * cohosh will do this and try to move the conversation further 
afterwards

New:
     * should we deprecate docker-snowflake-proxy?
         * There is now a snowflake Dockerfile for the proxy in the main 
snowflake repo
         * 
https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snowflake/-/merge_requests/246
         * do we need to do something to integrate it in our release 
process?
         * yes, we will deprecated
         * shelikhoo will move that forward in this issue: 
https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snowflake/-/issues/40345
     * Fastly domain fronting updates
         * https://github.com/net4people/bbs/issues/309
         * 
https://gitlab.torproject.org/tpo/anti-censorship/team/-/issues/135

== Actions ==


== Interesting links ==

     * 
https://opencollective.com/censorship-circumvention/projects/snowflake-daily-operations/updates/2024-february-update

== 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-03-07
     Last week:
         - various tasks to recover from fastly issue
             - 
https://gitlab.torproject.org/tpo/anti-censorship/team/-/issues/135
             - 
https://gitlab.torproject.org/tpo/applications/tor-browser/-/merge_requests/929
             - 
https://gitlab.torproject.org/tpo/applications/tor-browser-build/-/merge_requests/929
             - 
https://gitlab.torproject.org/tpo/applications/tor-browser/-/issues/42436
         - coordinated with a new meek bridge operator
         - reviewed SQS queue reuse MR
             - 
https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snowflake/-/merge_requests/263
         - fixed snowflake shadow integration tests
             - 
https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snowflake/-/issues/40342
             - 
https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snowflake/-/merge_requests/266
     This week:
         - open MR to change front domain for OONI tests
         - continue following up on AWS support case
         - review lox synchronization fix
         - compile a list of next-steps for lox
         - update wasm-bindgen fork to fix some bugs and hopefully 
upstream changes
         - tor-browser-build updates for lox wasm + bindings generation
         - Conjure bridge maintenance
     Needs help with:

dcf: 2024-03-07
     Last week:
         - reported a slow SQS rendezvous 
https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snowflake/-/issues/40323#note_3002286
     Next week:
         - review draft MR for unreliable data channels 
https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snowflake/-/merge_requests/219
         - 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:

meskio: 2023-03-07
     Last week:
         - deal with big collector metrics in bridgestrap (bridgestrap#41)
         - obfs4-bridge now has a sable UID/GID in docker 
(docker-obfs4-proxy#17)
         - export test result on the assignments.log (rdsys#177)
         - test bridges in bridgestrap every 3h (bridgestrap#39)
         - review HTTPS rdsys distributor (rdsys!260)
         - review client poll metrics by rendezvous method by country 
(snowflake!258)
     Next week:
         - distributor persistance in rdsys (rdsys#56)


Shelikhoo: 2024-03-07
     Last Week:
                 - [Merge Request Done]HTTPS distributors in rdsys: 
https://gitlab.torproject.org/tpo/anti-censorship/rdsys/-/merge_requests/260
                 - [Merge Request] Remove translation for Tor Project 
URL 
https://gitlab.torproject.org/tpo/anti-censorship/rdsys/-/merge_requests/278
                 - Inspect Snowflake Situation In China and create 
ticket for that 
https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snowflake/-/issues/40344
                 - Create Issue for "Merging webtunnel + lyrebird" 
https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/lyrebird/-/issues/40014
                 - Write WebTunnel Blog Post Draft
                 - Merge request reviews
     Next Week/TODO:
         - [Research] Inspect Snowflake Situation In China
         - Prepare for 3-min presentation


onyinyang: 2023-03-07
     Last week(s):
         - continued prep for HACS/DRL meeting
         - finished base64 invitation encoding

     This week:
         - continue prep for HACS/DRL meeting
         - improve metrics collection/think about how to show Lox is 
working/valuable
         - sketch out Lox blog post/usage notes for forum
         - attempt hyper upgrade again

     (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-01-11
         Last weeks:
             - Currently in the start phase of writing my master thesis 
(to be finished late june 2024) in communication technology on reducing 
distinguishability of DTLS. The goal is to implement a validated DTLS 
anti-fingerprinting library similar to uTLS (useful for Snowflake).
         Next weeks:
             - Talk with Sean DuBois about contributing to adding 
anti-fingerprinting capabilities to the pion library
         Help with:
             - Find recent data set of captured DTLS traffic

-- 
---
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/20240307/78991675/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/20240307/78991675/attachment.sig>


More information about the tor-project mailing list