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

meskio meskio at torproject.org
Thu Feb 15 16:27:34 UTC 2024


Here are our meeting logs:

  http://meetbot.debian.net/tor-meeting/2024/tor-meeting.2024-02-15-15.57.html 

And our meeting pad:


Anti-censorship
--------------------------------

Next meeting: Thursday, February 22 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: meskio

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

	* Elections in Indonesia (2024-02-14): https://explorer.ooni.org/chart/mat?probe_cc=ID&since=2024-01-16&until=2024-02-16&time_grain=day&axis_x=measurement_start_day&test_name=tor
	* Belarus - General elections (2024-02-25): https://explorer.ooni.org/chart/mat?probe_cc=BY&since=2024-01-16&until=2024-02-16&time_grain=day&axis_x=measurement_start_day&test_name=tor
	* Cambodia - Senate election (2024-02-25): https://explorer.ooni.org/chart/mat?probe_cc=KH&since=2024-01-16&until=2024-02-16&time_grain=day&axis_x=measurement_start_day&test_name=tor

== Discussion ==

	* 
	
== Actions ==


== Interesting links ==

	* FOCI registration is open (attendance is free): https://foci.community/register
		* February 19th

== 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-02-15
	Last week:
	    - caught up on manifest v3 updates
	        - https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snowflake-webext/-/merge_requests/21
	    - release new version of snowflake addon (0.7.3)
	        - updated addon stores
	        - updated website
	    - opened tor-browser-build MR to get SQS rendezvous in Tor Browser
	        - https://gitlab.torproject.org/tpo/applications/tor-browser-build/-/merge_requests/913
	    - fixed shadow integration tests
	        - https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snowflake/-/merge_requests/242
	    - opened an issue for country-specific client rendezvous poll counts
	        - https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snowflake/-/issues/40330
	    - caught up on dependency update backlog
	    - mostly caught up on review backlog
	This week:
	    - 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
	    - more testing of available domain fronts
	Needs help with:

dcf: 2024-02-15
	Last week:
		- snowflake azure CDN bookkeeping https://gitlab.torproject.org/tpo/anti-censorship/team/-/wikis/Snowflake-costs/diff?version_id=31fa3979db6efcfdc2c95f49cf033824971f531c
	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-02-15
    Last week:
        - catching up after long vacation
    Next week:
        - react to S96 code audit


Shelikhoo: 2024-02-15
    Last Week:
				- [Merge Request]HTTPS distributors in rdsys: https://gitlab.torproject.org/tpo/anti-censorship/rdsys/-/merge_requests/260
				- [Research] Inspect Snowflake Situation In China
				- Merge request reviews
    Next Week/TODO:
				- Inspect Snowflake Situation In China
				- Create Issue for "Merging webtunnel + lyrebird"
				- Update WebTunnel Container Image

onyinyang: 2023-02-15
	Last week(s):
		- Finished up fixing problems with syncing functions
		- Opened ticket to Lox invitation endpoint only accessible via telegram
		
	This week:
		- redeploy rdsys and lox-distributor with bug fixes and telegram bot
		- improve metrics collection/think about how to show Lox is working/valuable
		- start prep for HACS/DRL meeting
		- 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

-- 
meskio | https://meskio.net/
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
 My contact info: https://meskio.net/crypto.txt
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Nos vamos a Croatan.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: signature
URL: <http://lists.torproject.org/pipermail/tor-project/attachments/20240215/fd5de36c/attachment.sig>


More information about the tor-project mailing list