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

[tor-project] Anti-censorship team meeting notes, 2026-02-19

Hi everyone,

Here are the meeting logs:

https://meetbot.debian.net/tor-meeting/2026/tor-meeting.2026-02-19-16.00.html

and the meeting pad:

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

Next meeting: Thursday, February 19 16:00 UTC
Facilitator: cohosh

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

    Project 158 <-- meskio working on it
https://gitlab.torproject.org/groups/tpo/anti-censorship/-/issues/?label_name%5B%5D=Project%20158 



== Announcements ==

    FOCI is today! https://foci.community/


== Discussion ==

    Go version bump to v1.24 for snowflake?
we are keeping support for go 1.22 because TB needs this version to support an old version of OSX
https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snowflake/-/merge_requests/662 

    snowflake breaks support for go 1.22 with the latest version of kcp
https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snowflake/-/issues/40490 

    cohosh will roll back kcp and make a release to update snowflake in TB
Certificate Issues in Rust-based QUIC Pluggable Transport (UAT) and Future Plans
https://forum.torproject.org/t/proposal-rust-based-quic-pluggable-transport-uat/21124/4 

    https://github.com/yo-4m/UAT


== Actions ==



== Interesting links ==

    https://nordvpn.com/blog/nordwhisper-protocol/ 2025


== 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-02-19

    Last week:

        - worked on snowflake broker proxy pool refactor (snowflake!663)

        - updated reading group wiki page
- https://gitlab.torproject.org/tpo/anti-censorship/team/-/wikis/Anti-censorship-reading-group 

        - read some FOCI papers

    Next week:

        - roll back KCP version

        - research snowflake enumeration attacks (snowflake#40396)

        - implement proxy fairness proposal

        - follow up on snowflake rendezvous failures (snowflake#40447)

        - revisit conjure integration with lyrebird

        - take a look at potential snowflake orbot bug

            - https://github.com/guardianproject/orbot-android/issues/1183


dcf: 2026-02-19

    Last week:

    Next week:
- see about upgrading tor on the snowflake-02 bridge https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snowflake/-/issues/40511
- 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 

Help with:

meskio: 2026-02-19
    Last week:
        - PT bridges are also distributed as vanilla (rdsys#291)
        - merge and deploy moat-shim with cert reload fix (team#172)
- try and fail to add a CI test for building snowflake client with go 1.22 (snowflake#40490) - investigate Tor Browser problem switching from snowflake to obfs4 (tor-browser#44624) 
    Next week:
        - PT bridges are also distributed as vanilla (rdsys#291)


Shelikhoo: 2026-02-19
    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

    - Vantage point maintaince
- Expore DNS tunneling options(https://gitlab.torproject.org/tpo/anti-censorship/team/-/issues/173)
- [Merge Request Done]fix incorrect format for capacity option in README (https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snowflake/-/merge_requests/660) 

    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 
        - MR Review
        - Design experment for internet shutdown
        - Vantage point maintaince
- Expore DNS tunneling options(https://gitlab.torproject.org/tpo/anti-censorship/team/-/issues/173)
- - fix containrrr/watchtower is no longer maintained (https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snowflake/-/issues/40505) 



onyinyang: 2026-02-19

    Last week(s):
-Completed https://gitlab.torproject.org/tpo/anti-censorship/rdsys/-/issues/257#note_3322645
- Working on https distributor language selector https://gitlab.torproject.org/tpo/anti-censorship/rdsys/-/issues/196 


Next week:
    - 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


      Switch back to some of these:
          As time allows:
- 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-02-19

    Last weeks:
- Bumping pion stack version with backport: https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snowflake/-/merge_requests/662O 

    - 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 














































_______________________________________________
tor-project mailing list -- tor-project@xxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to tor-project-leave@xxxxxxxxxxxxxxxxxxxx