[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
[tor-project] Anti-censorship meeting notes, 2026-06-25
Hey everyone!
Here are our meeting logs:
https://meetbot.debian.net/tor-meeting/2026/tor-meeting.2026-06-25-16.00.html
And our meeting pad:
Anti-censorship work meeting pad
--------------------------------
Anti-censorship
--------------------------------
Next meeting: Thursday, July 2 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 ==
* Tor mid-year break: July 6-10
* no meeting on July 9
== Discussion ==
*
== 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?
* 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-06-25
Last week:
- fixed security issue in Snowflake where malformed webrtc
offers and answers could cause crashes in the client, proxy, and broker
(snowflake#40546)
- worked on rate limiting feature of proxy fairness proposal
(snowflake#40506)
Next week:
- continue to review PT spec implementation in UAT
- make proxy-bridge reachability checks robust to bridge
outages (snowflake#40504)
- more work on letting broker inform proxies how often to poll
- rate limiting
- follow up about running shadow simulations for snowflake
performance
- revisit conjure integration with lyrebird
- take a look at potential snowflake orbot bug
- https://github.com/guardianproject/orbot-android/issues/1183
dcf: 2026-06-25
Last week:
Next week:
- look at issues
https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/meek/-/work_items/40007
meek-server session ID file descriptor limit
https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/meek/-/merge_requests/2
goptlib upgrade in meek
Help with:
meskio: 2026-06-25
Last week:
- telegram distributing bridges with local addresses (rdsys#306)
- research security report on rdsys memory exhaustion (rdsys#309)
- update meek dependencies (meek!2)
Next week:
- telegram distributing bridges with local addresses (rdsys#306)
Shelikhoo: 2026-06-18
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
- [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 Socks5 Based Interactive Connectivity Test for
snowflake
(https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snowflake/-/merge_requests/699)
(Done)
- [Research] Request for Comment: Rust Library for TLS
Fingerprint Imitation with Delegation Route Usage in Tor Browser)
https://gitlab.torproject.org/tpo/applications/tor-browser/-/work_items/45056#note_3426867
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
- [Research] Request for Comment: Rust Library for TLS
Fingerprint Imitation with Delegation Route Usage in Tor Browser)
https://gitlab.torproject.org/tpo/applications/tor-browser/-/work_items/45056
(cont.)
onyinyang: 2026-06-25
Last week(s):
- Work for project #170 to detect bridge blocking
Next week:
- Continue tasks for project #170
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:
onyinyang shelikhoo cohosh 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