July 2026 - tor-project - lists.torproject.org

Anti-censorship team meeting notes, 2026-07-30
by onyinyang 30 Jul '26

30 Jul '26

Hey everyone! Here are our meeting logs: https://meetbot.debian.net/tor-meeting/2026/tor-meeting.2026-07-30-16.00.ht… And our meeting pad: Anti-censorship work meeting pad -------------------------------- Anti-censorship -------------------------------- Next meeting: Thursday, August 6 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?s… * 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_na… * 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… == Announcements == * == Discussion == * PETS/FOCI is over, there are many new interesting papers to read. Let's wait for cohosh to be present to decide on one for the reading group. * snowflake-webext 0.10.1 release is in progress, with new translations. * https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snow… * There is an old npm snowflake-pt package, formerly maintained by arlo, but not updated for 6 years (still at version 0.3.1). * https://www.npmjs.com/package/snowflake-pt * Old snowflake-webext archives included it while it was still being updated, e.g. https://archive.org/details/snowflake-webextension-0.3.1 which contains snowflake-pt-0.3.1.tgz. * We could put out a notice or add something to the package to advise that it not be used. * We could also ask arlo to remove or deprecate the package. * Such an old version of the proxy probably won't work with the current broker anyway, since it doesn't know about the allowed-prefix field. == 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-07-16 Last week: - updated documentation on proxy poll-interval options (snowflake!715) - worked on rate limiting implementation (snowflake#40506) - closed issue on FIFO vs LIFO priority queue (snowflake#40473) Next week: - continue to review PT spec implementation in UAT - more work on rate limiting proxy polls - make proxy-bridge reachability checks robust to bridge outages (snowflake#40504) dcf: 2026-07-30 Last week: - commented on a goptlib code change suggestion https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/gopt… - reviewed a merge request for snowflake proxy poll interval options https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snow… - started retrospective review of snowflake webextension poll interval refactoring https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snow… Next week: Help with: meskio: 2026-07-30 Last week: - prepare lyrebird and snowflake debian packages (tpa/team#42591) - test and fail to make it work MasterDNSVPN (team#199) Next week: - research existing DNS transports (team#199) Shelikhoo: 2026-07-30 Last Week: - [Testing] Unreliable+unordered WebRTC data channel transport for Snowflake rev2 (cont.)( https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snow… ) 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/snow… ) - [Research] Add three NAT type buckets to the snowflake broker ( https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snow… ) - Implement TLS Delegate in Rust (cont.) - Released new snowflake-webext vesion: (https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snow…) 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/snow… ) 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/snow… ) - [Research] Add three NAT type buckets to the snowflake broker ( https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snow… ) - Add 3 type nat bucket to snowflake broker - Implement TLS Delegate in Rust (cont.) onyinyang: 2026-07-30 Last week(s): - PETS - 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/conj… - review Tor browser Lox integration https://gitlab.torproject.org/tpo/applications/tor-browser/-/merge_requests… - 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

1 0

Anti-censorship team meeting notes, 2026-07-23
by meskio 23 Jul '26

23 Jul '26

Hey everyone! Here are our meeting logs: https://meetbot.debian.net/tor-meeting/2026/tor-meeting.2026-07-23-16.00.ht… And our meeting pad: Anti-censorship -------------------------------- Next meeting: Thursday, July 30 16:00 UTC Facilitator: onyinyang ^^^(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?s… * 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_na… * 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… == Announcements == * == Discussion == * emmapeel is asking if something needs to be translated * onionsproutsbot has new strings will be nice to get them * emmapeel will ping once they are translated * there are new translations of the snowflake plugin/badge * emmapeel will open an issue with the list of new languages to be added * shell will make a release including them == 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-07-16 Last week: - updated documentation on proxy poll-interval options (snowflake!715) - worked on rate limiting implementation (snowflake#40506) - closed issue on FIFO vs LIFO priority queue (snowflake#40473) Next week: - continue to review PT spec implementation in UAT - more work on rate limiting proxy polls - make proxy-bridge reachability checks robust to bridge outages (snowflake#40504) dcf: 2026-07-16 Last week: -worked with Snowflake Daily Operations on a response to Mullvad funding Next week: Help with: meskio: 2026-07-23 Last week: - add orbot to telegram gettor (onionsproutsbot#74) - start looking into options for DNS transports (team#199) - make debian packages reproducible (tpa/team#42591) - release webtunnel version to test packaging (webtunnel!47) Next week: - research existing DNS transports (team#199) Shelikhoo: 2026-07-23 Last Week: - [Testing] Unreliable+unordered WebRTC data channel transport for Snowflake rev2 (cont.)( https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snow… ) 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/snow… ) - [Research] Add three NAT type buckets to the snowflake broker ( https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snow… ) - Implement TLS Delegate in Rust (cont.) 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/snow… ) 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/snow… ) - [Research] Add three NAT type buckets to the snowflake broker ( https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snow… ) - Add 3 type nat bucket to snowflake broker - Implement TLS Delegate in Rust (cont.) onyinyang: 2026-07-16 Last week(s): - Mid-year break - 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/conj… - review Tor browser Lox integration https://gitlab.torproject.org/tpo/applications/tor-browser/-/merge_requests… - 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 -- meskio | https://meskio.net/ -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- My contact info: https://meskio.net/crypto.txt -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Nos vamos a Croatan.

1 0

Anti-censorship team meeting notes, 2026-07-16
by Cecylia Bocovich 16 Jul '26

16 Jul '26

Hey everyone! Here are our meeting logs: https://meetbot.debian.net/tor-meeting/2026/tor-meeting.2026-07-16-16.00.ht… And our meeting pad: Anti-censorship -------------------------------- Next meeting: Thursday, July 16 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: 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?s… 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_na… 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… == Announcements == == Discussion == Snowflake Daily Operations (snowflake-01 bridge) is making a decision about what to do about Mullvad donations, which have been the largest source of funding for the bridge. https://opencollective.com/censorship-circumvention/projects/snowflake-dail… We will likely be making a statement soon. == Actions == == Interesting links == https://petsymposium.org/popets/2026/popets-2026-0030.php "Obscura: Enabling Ephemeral Proxies for Traffic Encapsulation in WebRTC Media Streams Against Cost-Effective Censors" PETS 2026 paper that is relevant to Snowflake and WebRTC Other FOCI/PETS papers: https://github.com/net4people/bbs/issues/636 == 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-07-16 Last week: - updated documentation on proxy poll-interval options (snowflake!715) - worked on rate limiting implementation (snowflake#40506) - closed issue on FIFO vs LIFO priority queue (snowflake#40473) Next week: - continue to review PT spec implementation in UAT - more work on rate limiting proxy polls - make proxy-bridge reachability checks robust to bridge outages (snowflake#40504) dcf: 2026-07-16 Last week: -worked with Snowflake Daily Operations on a response to Mullvad funding Next week: Help with: meskio: 2026-07-16 Last week: - research how to add orbot to telegram gettor (onionsproutsbot#74) - start looking into options for DNS transports (team#199) - review TPA steps to include PTs in deb.tpo (tpa/team#42591) - reports Next week: - add orbot to telegram gettor (onionsproutsbot#74) Shelikhoo: 2026-07-02 Last Week: - [Testing] Unreliable+unordered WebRTC data channel transport for Snowflake rev2 (cont.)( https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snow… ) 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/snow… ) - [Research] Add three NAT type buckets to the snowflake broker ( https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snow… ) - [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/450… (Done) - [Deployment] Release Webtunnel server v0.0.5 (https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/webt…) - [Research] Consider support of static file distribution(like Tor cached states) over amp cache to allow full Tor bootstrap over amp cache (https://gitlab.torproject.org/tpo/anti-censorship/team/-/work_items/198) 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/snow… ) 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/snow… ) - [Research] Add three NAT type buckets to the snowflake broker ( https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snow… ) - Add 3 type nat bucket to snowflake broker - Implement TLS Delegate in Rust (cont.) onyinyang: 2026-07-16 Last week(s): - Mid-year break - 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/conj… - review Tor browser Lox integration https://gitlab.torproject.org/tpo/applications/tor-browser/-/merge_requests… - 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 meskio onyinyang 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

1 0

Anti-censorship team meeting notes, 2026-07-02
by Shelikhoo 02 Jul '26

02 Jul '26

Hey everyone! Here are our meeting logs: https://meetbot.debian.net/tor-meeting/2026/tor-meeting.2026-07-02-16.00.ht… And our meeting pad: Anti-censorship work meeting pad -------------------------------- Anti-censorship -------------------------------- Next meeting: Thursday, July 16 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: 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?s… * 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_na… * 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… == Announcements == * Tor mid-year break: July 6-10 * no meeting on July 9 * arma talk at fossasia about snowflake is online * https://www.youtube.com/watch?v=J2r0rCdeDMQ == Discussion == * == Actions == * == Interesting links == * https://defcon.social/@thedarktangent/116823843127887175 * Both VPN and email are well understood services, there is no shortage of people with expertise, it is not a big technical challenge to set up and operate... * Each became impossible or unattractive after talking to people who have operated them at deep levels over time. Here is why: * https://dashboard.censoredplanet.org/cenalert.html * https://censoredplanet.org/papers/cenalert.pdf == 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-07-02 Last week: - commented on meek-server file descriptor exhaustion https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/meek… - reviewed merge request to upgrade goptlib in meek https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/meek… - analyzed a fix for collector-rs packaging snowflake-stats tarballs incorrectly since April 2026 https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snow… https://lists.torproject.org/mailman3/hyperkitty/list/network-health@lists.… - upgraded tor on snowflake bridges to 0.4.9.11 for security fixes https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snow… - participated in discussion to update the UEFI certificat on the snowflake-01 bridge https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snow… Next week: Help with: meskio: 2026-07-2 Last week: - upgrade moat's meek server - reach out to FreshTomato community about integrating snowflake proxy Next week: - AFK in a break Shelikhoo: 2026-07-02 Last Week: - [Testing] Unreliable+unordered WebRTC data channel transport for Snowflake rev2 (cont.)( https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snow… ) 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/snow… ) - [Research] Add three NAT type buckets to the snowflake broker ( https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snow… ) - [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/450… (Done) - [Deployment] Release Webtunnel server v0.0.5 (https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/webt…) - [Research] Consider support of static file distribution(like Tor cached states) over amp cache to allow full Tor bootstrap over amp cache (https://gitlab.torproject.org/tpo/anti-censorship/team/-/work_items/198) 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/snow… ) 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/snow… ) - [Research] Add three NAT type buckets to the snowflake broker ( https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snow… ) - Add 3 type nat bucket to snowflake broker - Implement TLS Delegate in Rust (cont.) onyinyang: 2026-07-02 Last week(s): - Work for project #170 to detect bridge blocking Next week: - Mid-year break - 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/conj… - review Tor browser Lox integration https://gitlab.torproject.org/tpo/applications/tor-browser/-/merge_requests… - 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 meskio onyinyang 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

1 0