[tor-project] Anti-censorship team meeting notes, 2023-12-21

meskio meskio at torproject.org
Thu Dec 21 16:41:19 UTC 2023 

Hey everyone!

Here are our meeting logs:

http://meetbot.debian.net/tor-meeting/2023/tor-meeting.2023-12-21-15.57.html 

And our meeting pad:

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

Next meeting: Thursday, January 11 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 ==

	* No meetings December 28, neither January 4

== Discussion ==

	* Tor Browser users on Windows 7/8 have started having problems with PTs because Go 1.21 removed support
		* tor-browser-build now uses Go 1.20 for everything except Snowflake: https://gitlab.torproject.org/tpo/applications/tor-browser-build/-/commit/22731a740529dc055ba2f59f1c5be38bad4e602d
		* we'll try to fix the issue by providing our own random source and see how invasive si the change

	* manifest v2 deprecation in browsers and snowflake webextension
		* https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snowflake-webext/-/issues/29
		* https://developer.chrome.com/blog/resuming-the-transition-to-mv3/
		* google chrome will stop supporting mv2 June 2024
		* will the snowflake webextension stop working? do we want to do something? or just recommend firefox?
		* cohosh will look into this next year and see how hacky needs to be the solution

	* validation for bridgelines
		* https://gitlab.torproject.org/tpo/applications/tor-browser/-/issues/41913#note_2978927
		* there is no fingerprint in the conjure bridgeline we shared, and we have some doubts if giving an error on bridgelines without fingerprint in TB or not
		* we'll include a fingerprint in future conjure bridgelines
		* and we'll not give an error for now on missing fingerprint bridgelines

== 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): 2023-12-21
	Last week:
	    - debugged some issues with the lox distributor deployment
	        - https://gitlab.torproject.org/tpo/tpa/team/-/issues/41406
	    - lox tor browser integration work
	    - removed extra log message for snowflake connection closure
	        - https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snowflake/-/issues/40310
	    - worked on finding alternative domain fronting providers
	This week:
	    - conjure bridge maintenance
	    - review SQS rendezvous
	Needs help with:

dcf: 2023-12-14
	Last week:
		- opened issue to upgrade snowflake bridges to 0.4.8.10 https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snowflake/-/issues/40311
		- azure CDN bookkeeping https://gitlab.torproject.org/tpo/anti-censorship/team/-/wikis/Snowflake-costs/diff?version_id=b4faa975599a628653d261641590c78a31a2f21f
	Next week:
		- upgrade snowflake bridges to 0.4.8.10 https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snowflake/-/issues/40311
		- 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
	Before EOY 2023:
		- move snowflake-02 to new VM
Help with:

meskio: 2023-12-21
    Last week:
        - grant writing
    Next week:


Shelikhoo: 2023-12-21
    Last Week:
				- Work on snowflake performance improvement (WIP): https://gitlab.torproject.org/shelikhoo/snowflake/-/tree/dev-udp-performance-rebased-exp?ref_type=heads
				https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snowflake/-/merge_requests/219
				- Analysis of S150 HTTPS distributors design: https://gitlab.torproject.org/tpo/anti-censorship/rdsys/-/issues/191
				- Merge request reviews
    Next Week/TODO:


onyinyang: 2023-12-21
	Last week(s):
		- Worked on Telegram bot: https://gitlab.torproject.org/tpo/anti-censorship/rdsys/-/merge_requests/223
		- Added several additional Lox wasm stubs needed by applications team
		
	This week:
		- Finish up Telegram bot dev
		- Continue to support Lox wasm stubs as needed
		- attempt hyper upgrade again
		- Holiday!
		


(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?

-- 
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/20231221/c57f41a5/attachment.sig>

More information about the tor-project mailing list