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

onyinyang onyinyang at torproject.org
Thu Oct 10 16:37:52 UTC 2024 

Hey everyone!

Here are our meeting logs:
http://meetbot.debian.net/tor-meeting/2024/tor-meeting.2024-10-10-16.00.html

And our meeting pad:

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

Next meeting: Thursday, October 10 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 ==

(Oct 3:)
     * Broker installation over at:
         * snowflake-broker-debianupgradestaging-j33r3zahe.torproject.net
         * ready to be tested and then switch to be the primary broker
         * ./proxy -nat-probe-server 
https://snowflake-broker-debianupgradestaging-j33r3zahe.torproject.net:8443/probe 
-broker 
https://snowflake-broker-debianupgradestaging-j33r3zahe.torproject.net/ 
-verbose
         * 
https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snowflake/-/issues/40349#note_3026336
         * Follow up Oct 10:
             * Testing from commandline worked
             * testing from tor browser still connects to original 
broker but should be fine once domain name is switched
(Oct 10 New):
     * Prepare DeploymentTool for Publishing
         * 
https://gitlab.torproject.org/tpo/anti-censorship/connectivity-measurement/logcollector-admin/-/issues/9
== 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-09-26
     Last week:
         - worked with meek bridge operator to update domain names
         - dove into family support for bridges (tor#40935)
         - TROVE-2024-012
         - merged and then unmerged kcp library update
     This week:
         - take a look at WofWca's big changes to snowflake
         - finish snowflake dependency upgrades that were causing problems
         - 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

dcf: 2024-10-03
     Last week:
         - more review of snowflake webextension Manifest V3 running in 
background 
https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snowflake-webext/-/merge_requests/83#note_3084373
         - commented installation procedure for replacement snowflake 
broker 
https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snowflake/-/issues/40349#note_3084507
         - snowflake azure CDN bookkeeping 
https://gitlab.torproject.org/tpo/anti-censorship/team/-/wikis/Snowflake-costs/diff?version_id=7ab51a375c35631ce7dfec123fd3c4c4d59d3eb6
     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
Help with:
         - tell me when to restart the brokers for 
https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snowflake/-/issues/40349

meskio: 2023-10-03
     Last week:
         - Travel to the Global Gathering
     Next week:
         - investigate if bridges are still jumping distributors (rdsys#232)
         - plan the work on snowflake proxy packaging


Shelikhoo: 2024-10-10
     Last Week:
          - snowflake broker update/reinstall(cont.):
https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snowflake/-/issues/40349#note_3026336
          - Unreliable+unordered WebRTC data channel transport for 
Snowflake rev2 (cont.)( 
https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snowflake/-/merge_requests/315 
) improvements
          - Review CI: fix `latest` container image tag. 
https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snowflake/-/merge_requests/408#note_3089605
             - Merge request reviews
     Next Week/TODO:
         - Merge request reviews
          - Unreliable+unordered WebRTC data channel transport for 
Snowflake rev2 (cont.) ( 
https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snowflake/-/merge_requests/315 
) improvements
          - Work on finishing snowflake container release(and fix the 
comments)
          - Work on Parpare DeploymentTool for Publishing 
https://gitlab.torproject.org/tpo/anti-censorship/connectivity-measurement/logcollector-admin/-/issues/9

onyinyang: 2023-10-10
     Last week(s):
         - continue troll-patrol integration for Lox bridge blockage 
detection
     Next week:
         - continue troll-patrol integration for Lox bridge blockage 
detection
         - update lox protocols to return duplicate responses for an 
already seen request
         - Work on outstanding milestone issues:
             in particular: 
https://gitlab.torproject.org/tpo/anti-censorship/lox/-/issues/69
             - key rotation automation

         Later:
         pending decision on abandoning lox wasm in favour of some kind 
of FFI? 
https://gitlab.torproject.org/tpo/applications/tor-browser/-/issues/43096):
             - add pref to handle timing for pubkey checks in Tor browser
             - add trusted invitation logic to tor browser integration:
https://gitlab.torproject.org/tpo/applications/tor-browser/-/issues/42974
         - 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!):
         - 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-09-12
         Last weeks:
             -
         Next weeks:
             - Update Snowflake to use latest pion upstream releases, 
waiting for WebRTC v4 beta.
             - 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/20241010/8f63e930/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/20241010/8f63e930/attachment.sig>

More information about the tor-project mailing list