[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]

[tor-project] Anti-censorship team meeting notes, 2026-04-16

Hi everyone,
Here is our meeting log: https://meetbot.debian.net/tor-meeting/2026/tor-meeting.2026-04-16-16.00.html 

And our meeting pad:

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

Next meeting: Thursday, Apr 16 16:00 UTC
Facilitator:meskio

^^^(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:shelikhoo
== 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 



== Announcements ==



== Discussion ==
Draft short paper about using fountain codes for rendezvous, comments welcome
https://repo.or.cz/erasure-code-rendezvous.git/blob_plain/5b4b5d1cc188cdc12adf1f407cce365b2c58babf:/paper/fountain-code-rendezvous.f23d22ad.pdf
https://repo.or.cz/erasure-code-rendezvous.git/tree/5b4b5d1cc188cdc12adf1f407cce365b2c58babf
Recent snowflake proxy updates for DTLS fingerprinting (randomizemimic by default)
https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snowflake/-/issues/40530 

    We haven't reached out to operators yet

    cohosh offers to send a tor-relays email
The snowflake default bridge lines in Tor Browser were updated with a new set of STUN servers 


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

    Last week:
- added bloco to KnownProxyTypes for broker metrics (snowflake#40534)
- implemented a way to manually update poll intervals without restart (snowflake!701)
- responded to IPtProxy issue to expose GetCurrentNATType for the snowflake proxy (snowflake#40536) 

            - https://github.com/tladesignz/IPtProxy/issues/86

        - worked on proxy fairness proposal writeup

    Next week:

        - keep following up with fingerprinting in Russia
- make proxy-bridge reachability checks robust to bridge outages (snowflake#40504) 

        - more work on letting broker inform proxies how often to poll

            - have proxies honour the NextPoll message
- 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-04-16

    Last week:

    Next week:
- comment on dynamic poll rate adjustment https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snowflake/-/issues/25598#note_3382867 

    Help with:


meskio: 2026-03-26
    Last week:
- split translation strings in the telegram distributor to make it easier to translate (rdsys#299) - stop sharing windows7 TB in Telegram gettor, as there is no releases anymore (onionsproutsbot#77) 
        - assignments log scrambled on our side (rdsys!638)
        - grant work
    Next week:
        - give it a try to gorelease to produce debian packages


Shelikhoo: 2026-04-16
    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 ) 

    - Writing Socks5 UDP proxy for nat type simuation
- [Done] Update Snowflake STUN servers at Tor browser ( https://gitlab.torproject.org/tpo/applications/tor-browser-build/-/merge_requests/1462 ) 

    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 ) 

    - Writing Socks5 UDP proxy for nat type simuation


onyinyang: 2026-04-09

    Last week(s):

    - Started background work for project #170

    Next week:

       - Start on 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-04-16

    Last weeks:
- MR fixing silent errors of fingerprint parse failure in covert-dtls: https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snowflake/-/merge_requests/705 

    - Researching possible DTLS blocking in Russia

    - Implementing DTLS 1.3 in pion

    Next weeks:

    - Implementing DTLS 1.3 in pion

    Help with:

    -




Facilitator Queue:

    meskio onyinyang cohosh shelikhoo
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 
_______________________________________________
tor-project mailing list -- tor-project@xxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to tor-project-leave@xxxxxxxxxxxxxxxxxxxx