[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
[tor-project] Anti-censorship team meeting notes, 2026-09-24
Hey everyone!
Here are our meeting logs:
https://meetbot.debian.net/tor-meeting/2026/tor-meeting.2026-09-24-16.00.html
And our meeting pad:
Anti-censorship work meeting pad
--------------------------------
Anti-censorship
--------------------------------
Next meeting: Thursday,October 1, 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
* Projects the TPI anti-censorship team is working on:
* Project 146: Expanding access to digital media through the
use of secure communications, infrastructure, tools, and techniques
*
https://gitlab.torproject.org/groups/tpo/anti-censorship/-/issues/?label_name%5B%5D=Project%20146
* Project 170: Monitoring and reporting on censorship against
the Tor network
* epic: https://gitlab.torproject.org/groups/tpo/-/epics/17
* Project 201: Signaling channels
* board
https://gitlab.torproject.org/groups/tpo/-/boards/2675?label_name[]=Project%20201
== Announcements ==
*
== Discussion ==
* jah
* I've been working an PT that is implementing a subset of
Upgen and I have questions regarding integration but also on the current
development of supertunnel, I tried out to reach robgjansen in the
#tor-anticensorship a couple days ago.
* As I did not got any answer yet I thought I could join this
meeting and ask them directly:
* 1. (upgen) Did you thought about how to encode and distribute
brideg line already?
* 2. (upgen) Do you think some rotation of generated protocols
would be useful? (in other words for a long running bridge, do we want
to peridocically switch protocols... as far as I can tell this could
actually increase the risk of being identified... but I'm not sure I did
not put lot of thoughts into this)
* 3. (supertunnel) It looks like you design this so it could be
use as a layer encapsulating an other PT like prometeus, is that correct?
* if yes then I'm trying to understand why we don't prefer
having such resiliency features directly inside Tor
* so it is not dependent on a specific PT. Literally such
resiliency should be useful also when using direct connection and no PT
involved, wdyt?
* Rust-pt ( A Rust-Based framework for Pluggable Transports'
development)
* I have few question regarding PT framework
* 1. some anti-censorships' member mentioned that Tor may
prefer special style for official PT framework. May I ask what is the
exactly `style`
* 2. Also @robgjansen said that they would like to review, and
I tried to reach out but they have not answered my DM
* 3. Regarding community, may I ask if Tor have way to reach
out PT developers Because I would like to let them know there is a new
framework :)
== Actions ==
*
== Interesting links ==
* https://riposte.levelflow.org/2026/07/deltachat/
* RusTLS block by fingerprinting when more than 3 connections
are made to the same sNI
* https://github.com/pryty26/rust-pt
== 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?
* Next in the Reading Group Queue:
*
== 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): 2026-09-17
Last week:
- assessed that reported proxy deadlock was AI slop
- got to the bottom of recent proxy issues
-
https://forum.torproject.org/t/running-snowflake-with-moav-260-gb-relayed-a-new-grafana-dashboard-and-a-few-questions/22041/3
-
https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snowflake/-/work_items/40561
- patched lyrebird bug (lyrebird#40039)
- proteus hacking and design
- triaged code audit bugs
Next week:
- continue review of UAT (team#178)
- continue triaging code audit bugs
- make proxy-bridge reachability checks robust to bridge outages
(snowflake#40504)
- research working group tasks: open issues for relevant
pets/foci papers
- open issue about ASL19 report suggestions
dcf: 2026-08-20
Last week:
Next week:
Help with:
meskio: 2026-09-17
Last week:
- prepare .deb packages for PTs
- release webtunnel to produce debian packages
- research existing DNS transports (team#199)
Next week:
- research existing DNS transports (team#199)
Shelikhoo: 2026-09-24
Last Week:
- [Testing] Unreliable+unordered WebRTC data channel transport
for Snowflake rev2 (cont.)(
https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snowflake/-/merge_requests/315
) testing environment setup/research
- Merge request Reviews
- [Develop] Work on TLSDelegate development
- (Undisclosed work)
Next (working) Week/TODO:
- Merge request reviews
- [Deployment]Unreliable+unordered WebRTC data channel
transport for Snowflake rev2 (cont.)(
https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snowflake/-/merge_requests/315
) Building custom Tor Browser with patch applied
- Vantage point maintaince
- [Research] proxy pool overload and potential blocking in
Iran (
https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snowflake/-/issues/40077#note_3361718
)
- [Research] Add three NAT type buckets to the snowflake
broker (
https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snowflake/-/issues/40077#note_3361718
)
- Add 3 type nat bucket to snowflake broker
- Implement TLS Delegate in Rust (cont.)
onyinyang: 2026-09-24
Last week(s):
- P170 tasks
- merged DB for connection stats
- fixed stats to flag bridges
Next week:
- Continue tasks for project #170
- send flagged bridges to vantage point or else collect them to
be sent
- develop reasonable API to collect user reports of blocked
bridges from TB
Switch back to some of these:
As time allows:
- Continue work on rdsys#196
- Continue Investigating rdsys#248 i.e., why
dysfunctional webtunnel bridges are being distributed
- Troubleshooting conjure not connecting in China
- waiting for more information from conjure
authors/maintainers
- Lox still seems to be filling up the disk on the
rdsys-test server despite changes made to delete old entries, look into
what's going wrong
Blog post for conjure:
https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/conjure/-/issues/46
- review Tor browser Lox integration
https://gitlab.torproject.org/tpo/applications/tor-browser/-/merge_requests/1300
- add TTL cache to lox MR for duplicate responses:
https://gitlab.torproject.org/tpo/anti-censorship/lox/-/merge_requests/305
- Work on outstanding milestone issues:
- 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: 2026-05-28
Last weeks:
- Researching possible DTLS block in Russia
-
https://github.com/net4people/bbs/issues/603#issuecomment-4451730751
- Implementing DTLS 1.3 in pion
Next weeks:
- Implementing DTLS 1.3 in pion
Help with:
-
Facilitator Queue:
cohosh 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
_______________________________________________
tor-project mailing list -- tor-project@xxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to tor-project-leave@xxxxxxxxxxxxxxxxxxxx