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

Shelikhoo shelikhoo at torproject.org
Thu Apr 18 17:09:12 UTC 2024


Hey everyone!

Here are our meeting logs:
http://meetbot.debian.net/tor-meeting/2024/tor-meeting.2024-04-18-16.15.html

And our meeting pad:

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

Next meeting: Thursday, Apr 25 16:00 UTC
Facilitator: onyingyang
^^^(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: shelikhoo

== 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 ==

== Discussion ==
     * Latest snowflake addon reviewer feedback requires a consent 
prompt for the collection of personal data
         * 
https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snowflake-webext/-/issues/89
         * is already being implemented and the addon is in the store

== Actions ==


== Interesting links ==

     * Snowflake support in Greatfire Envoy (using their own proxies and 
bridge as I understand)
         * https://github.com/greatfire/envoy/pull/63
     * "Snowflake Anonymous Network Traffic Identification" January 2024
         * https://link.springer.com/chapter/10.1007/978-981-99-9247-8_40
         * Research from China, too recent to have been referenced in 
the Snowflake paper
         * Corresponding author Xu Dawei also has a paper on secure 
rendezvous using a blockchain 
https://link.springer.com/chapter/10.1007/978-3-031-15777-6_14

== 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-04-18
     Last week:
         - added a consent prompt for the snowflake addon
             - 
https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snowflake-webext/-/issues/89
         - deployed snowflake addon v0.8.0 (got approved)
         - updated npm script for preparing addon
             - 
https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snowflake-webext/-/merge_requests/72
         - added a button to reopen consent prompt for addon
             - 
https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snowflake-webext/-/merge_requests/73
         - Added a fingerprint field to Lox bridge table after feedback 
from vecna
             - 
https://gitlab.torproject.org/tpo/anti-censorship/lox/-/merge_requests/147
         - reviewed and merged dependency updates
         - added a new meek bridge to the censorship settings
             - 
https://gitlab.torproject.org/tpo/anti-censorship/rdsys-admin/-/merge_requests/30
     This week:
         - release a new version of snowflake addon once !72 and !73 are 
merged
         - follow up on reported SQS errors
         - update wasm-bindgen fork to fix some bugs and hopefully 
upstream changes
         - create a Lox test environment and instructions for the 
browser team
             - 
https://gitlab.torproject.org/tpo/applications/tor-browser/-/issues/42503
     Needs help with:

dcf: 2024-04-18 (since 2024-03-21)
     Last week:
         - reviewed draft MR for unreliable data channels 
https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snowflake/-/merge_requests/219
         - investigated a momentary drop in users of the snowflake-01 
bridge 
https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snowflake/-/issues/40355#note_3015360
         - azure CDN bookkeeping 
https://gitlab.torproject.org/tpo/anti-censorship/team/-/wikis/Snowflake-costs/diff?version_id=da6fabe745db58babebb866e200ecfd5fca6e040
         - archived snowflake-webext 0.8.0 
https://archive.org/details/snowflake-webextension-0.8.0
     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:

meskio: 2023-04-18
     Last week:
         - persistency for resources in rdsys (rdsys#56)
         - use the same distributor for bridges sharing IP or 
fingerprint (rdsys!293)
         - integration tests for rdsys (rdsys#180)
     Next week:
         - email distributor in rdsys (rdsys#186)


Shelikhoo: 2024-04-18
     Last Week:
         - [Merge Request WIP] 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 Done] Update lyrebird version to v0.2.0 
https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/lyrebird/-/merge_requests/35
         - [Merge Request] Rename Stable Container Tags to Latest 
https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snowflake/-/merge_requests/284
                 - Merge request reviews
     Next Week/TODO:
         - Merge request reviews
         - Investigate broken debian-testing pipeline for snowflake


onyinyang: 2023-04-18
     Last week(s):
         - HACS
         - DRL meeting
         - AFK for 1 week

     This week:
         - Responding to pre-existing MR reviews and other 
notifications/questions in gitlab
     Probably next week and beyond:
         - preparing for upcoming panel
         - implement 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
         - 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-04-18
         Last weeks:
             - WIP: extended Pion dtls library to support mimicking of 
client hellos. A github action generate fresh dtls handshakes of the 
newest firefox and chromium versions. The bytes of the client hello are 
replayed to mimick common dlts fingerprints.
         Next weeks:
             - Test and validate mimicked client hello with snowflake.
             - PR to pion github, talk with sean.
         Help with:



Facilitator Queue:
     onyinyang meskio shelikhoo
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

-------------- next part --------------
A non-text attachment was scrubbed...
Name: OpenPGP_signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: OpenPGP digital signature
URL: <http://lists.torproject.org/pipermail/tor-project/attachments/20240418/72be3297/attachment.sig>


More information about the tor-project mailing list