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

[tor-project] Anti-censorship team meeting notes, 2026-01-29

Hey everyone!

Here are our meeting logs:
https://meetbot.debian.net/tor-meeting/2026/tor-meeting.2026-01-29-16.00.html

And our meeting pad:

Anti-censorship work meeting pad
--------------------------------
Anti-censorship
--------------------------------

Next meeting: Thursday, February 5 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 
        * Project 158 <-- meskio working on it
            * https://gitlab.torproject.org/groups/tpo/anti-censorship/-/issues/?label_name%5B%5D=Project%20158 


== Announcements ==

== Discussion ==

    * Proceed with merging DTLS imitation MR
        * https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snowflake/-/merge_requests/644 
        * will merge it but it is diabled by default for now
    * snowflake proxies overloaded with the surge of Iranian users
        * https://gitlab.torproject.org/tpo/anti-censorship/censorship-analysis/-/issues/40068#note_3330856         * go TLS might be blocked in Iran now, wich might affect in country proxies         * we are misscounting IR snowflake users as US but not other transports             * https://gitlab.torproject.org/tpo/network-health/analysis/-/issues/108 

== Actions ==

    *

== Interesting links ==

    *

== Reading group ==
    * We will discuss "Fingerprint-resistant DTLS for usage in Snowflake" on Feb 5 
        * https://www.petsymposium.org/foci/2025/foci-2025-0006.php
        * 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-01-29
    Last week:
        - added more standard functions for proxy poll messages (snowflake!658) 
        - reviewed bridge reachability error checking MR
    Next week:
        - 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-01-29
    Last week:
        - commented on snowflake proxy rate limiting proposal https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snowflake/-/issues/40507#note_3330191         - reconsidered my position on backward compatibility in the snowflake messages package https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snowflake/-/merge_requests/658#note_3333181         - posted some brainstorming ideas about future tunnels for the Iran situation https://gitlab.torproject.org/tpo/anti-censorship/censorship-analysis/-/issues/40068#note_3333227 
    Next week:
        - 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-01-29
    Last week:
        - P146 report
        - monitor the situation in Iran
        - look into why gettor email is not sending links, but it is now (computers are magic...) (rdsys#290)         - investigate why there is webtunnel bridges in the email distributor (rdsys#174) 
    Next week:
        - investigate why there is webtunnel bridges in the email distributor (rdsys#174) 


Shelikhoo: 2026-01-29
    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
    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


onyinyang: 2026-01-29
    Last week(s):
        -Making it harder to inject a bridge to a specific client https://gitlab.torproject.org/tpo/anti-censorship/rdsys/-/issues/257#note_3322645         - Use root key for rdsys to derive keys for each of the distributors
        - Working on https distributor language selector https://gitlab.torproject.org/tpo/anti-censorship/rdsys/-/issues/196 
                - fixing some errors in the translated pages
                - does the translation work for bridges.torproject.org exist somewhere already? 

Next week:
    - Continue work on rdsys#257 and 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-01-29
        Last weeks:
            - Working on implementing review comments on MR: https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snowflake/-/merge_requests/644 
            - Implementing DTLS 1.3 in pion
        Next weeks:
            - Implementing DTLS 1.3 in pion
        Help with:
            -



Facilitator Queue:
    onyinyang shelikhoo meskio cohosh
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