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

Thu Jun 13 16:57:53 UTC 2024

Hey everyone!

Here are our meeting logs:
http://meetbot.debian.net/tor-meeting/2024/tor-meeting.2024-06-13-16.02.html

And our meeting pad:

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

Next meeting: Thursday, June 20 16:00 UTC
Facilitator: onyinyang
^^^(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: 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 ==

	* bridges running 0.4.7.x (EOL) were rejected by Serge: https://lists.torproject.org/pipermail/tor-relays/2024-June/021678.html

== Discussion ==

	* what's the plan for: https://gitlab.torproject.org/tpo/anti-censorship/team/-/issues/142
		* we've lost a lot of webextension snowblake proxies, proably due to people not noticing the new consent page
		* luckily the rise in orbot proxies (probably from the v17 rollout) makes this not as urgent as it otherwise might be
		* cohosh is working on this issue

== Actions ==

== Interesting links ==

	* https://discourse.mozilla.org/t/the-censorship-circumvention-extension-has-disappeared-from-the-russian-version-of-mozilla-addons/130914
		* https://ntc.party/t/several-proxy-firefox-extensions-are-blocked-in-russia-by-mozilla/7943/1
	* Myanmar: https://gitlab.torproject.org/tpo/anti-censorship/censorship-analysis/-/issues/40043

== 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-06-13
	Last week:
	    - looked into sharp decline of browser extension proxies 
	        - https://gitlab.torproject.org/tpo/anti-censorship/team/-/issues/142
	    - started experimenting with some fixes for the web extension consent prompt UX
	    - FOCI stuff
	This week:
	    - snowflake webextension consent prompt UX fixes
	    - take a look at shell's mv3 changes
	    - 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
	    - follow up on reported SQS errors
	    - update wasm-bindgen fork to fix some bugs and hopefully upstream changes
	Needs help with:

dcf: 2024-06-13
	Last week:
		- azure CDN bookkeeping https://gitlab.torproject.org/tpo/anti-censorship/team/-/wikis/Snowflake-costs/diff?version_id=d8e547082eb0edb0195eb263f0cc1e5a8b61b898
	Next week:
		- review snowflake unreliable+unordered data channels rev2 https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snowflake/-/merge_requests/315
		- 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:
		- tell me when to restart the brokers for https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snowflake/-/issues/40349

meskio: 2023-06-13
    Last week:
        - create an rdsys requests metrics puller that produces metrics for collector (rdsys#188)
        - plan with TPA the BridgeDB deprecation (tpa/team#41613)
        - add the new prometheus exporters (tpa/prometheus-alerts!42)
        - in progress of investigate what builtin bridges are offline (team#141)
        - test tor implementation to the STATUS type=version command for PTs (tor!820)
        - fix a bug in ptutil/safeprom registering the metric (ptutil!2)
    Next week:
        - deploy https, moat and email distributors in rdsys
        - investigate what builtin bridges are offline (team#141)

Shelikhoo: 2024-06-06
    Last Week:
        - [Merge Request Waiting] 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 Waiting] Snowflake Performance Improvement rev2 (https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snowflake/-/merge_requests/315)
			- Chrome Manifest V3 transition: https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snowflake-webext/-/issues/29#note_3035763
			- Upgrade snowflake broker machine from Debian 10 (https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snowflake/-/issues/40349)
			- Address TTP-03-001 WP1: Snowflake broker vulnerability(https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snowflake/-/issues/40329)
			- Vantage point maintaince
			- merge request processing
				- Merge request reviews
    Next Week/TODO:
        - Merge request reviews

onyinyang: 2023-06-06
	Last week(s):
		- Finished key rotation implementation
		- Working toward building tor-browser with lox-wasm binary to help out with
			integration work as needed
		- Preparation for MSR talk
	Next week:
		- MSR talk
		- Work on outstanding milestone issues: https://gitlab.torproject.org/tpo/anti-censorship/lox/-/milestones/1#tab-issues
			- prepare for end to end testing of the Lox system with browser integration
		Later:
		- begin implementing 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

	(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-06-13
		Last weeks:
			- Writing on my thesis
		Next weeks:
			- Add hook to pion/webrtc so it can be used in snowflake, currently waiting on new pion/dtls release
			- Add randomized fingerprints
			- Writing my thesis
		Help with:

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

-- 
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/20240613/eda21953/attachment.sig>