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

gitlab 18.10 upgrade removes "issues"
by Antoine Beaupré 20 Apr '26

20 Apr '26

Hi, Today, we upgraded gitlab.torproject.org to 18.10! Among a couple of interesting new things[1], GitLab introduced a *significant* change in the way "issues" are presented and organized. It was introduced as "the work items list and saved views"[2]. It's an interesting feature! It allows you to see epics alongside issues and create saved searches of your issues, pretty neat. Except. They essentially *removed* the entire "issues" UX. You know how I keep bugging people to "file an issue"? That "new issue" button is gone. Heck, the "issues" button itself is gone. In its place, there is a "work items" button, and *there* you can find your good old issues (and, now, also epics). But, crucially, there's no "Closed" tab anymore, so you can't easily go into closed issues with one click: you need to go through the search form and a couple of clicks to find closed issues. So after consultation (well, really, it was sheer panic) with my colleagues, I found a way to revert this. So you won't yet see this view. If you really want to experiment with it, replace the "issues" string with "work_items" in URLs, that still works. I have filed a comment (like dozens of other GitLab users) objecting to the change, alongside with the instructions for other GitLab administrators to revert this change.[3] It is my hope that the feature can be improved to some maturity (at *least* keep a "closed" tab and a "new issue" button?!) and that eventually we'll be able to switch the feature back on. I can see the point of having a common view for issues and epics, even though it's not a problem I have personally struggled with in GitLab. But at this point, we can't just do that switch. Let me know if there's any other concern here! a. [1] details in https://about.gitlab.com/releases/2026/03/19/gitlab-18-10-released/ [2] https://about.gitlab.com/releases/2026/03/19/gitlab-18-10-released/#introdu… [3] https://gitlab.com/gitlab-org/gitlab/-/work_items/590689#note_3175428478 -- Antoine Beaupré torproject.org system administration

5 8

Anti-censorship team meeting notes, 2026-03-26
by Shelikhoo 26 Mar '26

26 Mar '26

Hey everyone! Here are our meeting logs: https://meetbot.debian.net/tor-meeting/2026/tor-meeting.2026-03-26-16.01.ht… And our meeting pad: Anti-censorship work meeting pad -------------------------------- Anti-censorship -------------------------------- Next meeting: Thursday, Apr 02 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: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… == Announcements == * == Discussion == * Release schedule planning for containers * https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/webt… * WebTunnel server has not needed an update, but the tor daemon has updated in the meantime; want to release container updates purely for the sake of getting an upgraded tor, even if there are no changes to WebTunnel * Shell will write a ticket about 3 month per maintaince release proposal * --> link is here: https://gitlab.torproject.org/tpo/anti-censorship/team/-/issues/181 (Mar 26 New) * 3 Bucket NAT Type Testing Proposal: * https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snow… * instead of having one single test, we run 2 webrtc connect test in parallel * one of them have a "no server reflective candidate, Endpoint+Port Dependent (Pinned) Filter, Endpoint+Port Dependent Mapping" network environment on server side's webrtc to test if the proxy is of type "open", it is open if the client can connect * one of them have a "Endpoint+Port Dependent Filter, Independent Mapping" to test if the proxy is of type "moderate", if connects then it is * the nat type test assist server get these network environment by modifying the sdp info(which we already do to remove some host candidate); connecting via socks5 proxy, the socks5 proxy simulate these network types by intentionally sabotaging the relayed connection * This design would reduce the amount of change of logic we need to make on proxy, however, would result in increase of server load. * Questions for discussion: * Is there any missing points/miscategorization that is not discussed? * Is there any unintented side effects that is not discussed? * TODO: * Shelikhoo check broker machine load * cohosh add more feedback to the ticket == 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-03-26 Last week: - merged snowflake broker pool refactor - https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snow… - opened MR for first part of letting broker inform proxies how often to poll - worked on proxy fairness proposal Next week: - continue snowflake and lyrebird go version support and release work - follow up about running shadow simulations for snowflake performance - 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-03-26 Last week: - commented on a cypherpunks patch for snowflake webextension and OS lock / sleep https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snow… - upgraded the snowflake bridges to 0.4.9.6 for a security release https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snow… Next week: - open issue to have snowflake-client log whenever KCPInErrors is nonzero https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snow… - parent: https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snow… Help with: meskio: 2026-03-26 Last week: - AFK - grant work Next week: - assignments log clean up in rdsys side Shelikhoo: 2026-03-26 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 - 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… ) - [MR] Done: Update webtunnel version to 0.0.4 and update bundled dockerfile dependencies ( https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/webt… ) 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… ) onyinyang: 2026-03-26 Last week(s): - Finished work on https distributor language selector https://gitlab.torproject.org/tpo/anti-censorship/rdsys/-/issues/196 -Reworking lox-extension MR and integration with Tor Next week: - Start new 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-02-19 Last weeks: - Bumping pion stack version with backport: https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snow… - 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

1 0

PSA: North america changes time forward soon, Europe next
by Antoine Beaupré 23 Mar '26

23 Mar '26

Hi! This is your bi-yearly reminder that time is changing soon! # What's happening? For people not on tor-internal, you should know that I've been sending semi-regular announcements when daylight saving changes occur. Starting now, I'm making those announcements public so they can be shared with the wider community because, after all, this affects everyone (kind of). For those of you lucky enough to have no idea what I'm talking about, you should know that some places in the world implement what is called Daylight saving time or DST: https://en.wikipedia.org/wiki/Daylight_saving_time Normally, you shouldn't have to do anything: computers automatically change time following local rules, assuming they are correctly configured, provided recent updates have been applied in the case of a recent change in said rules (because yes, this happens). Appliances, of course, will likely *not* change time and will need to adjusted unless they are so-called "smart" (also known as "part of a bot net"). If your clock is flashing "0:00" or "12:00", you have no action to take, congratulations on having the right time once or twice a day. If you haven't changed those clocks in six months, congratulations, they will be accurate again! In any case, you should still consider DST because it might affect some of your meeting schedules, particularly if you set up a new meeting schedule in the last 6 months and forgot to consider this change. # If your location does not have DST Properly scheduled meetings affecting multiple time zones are set in UTC time, which does *not* change. So if your location does not observer time changes, your (local!) meeting time will *not* change. But be aware that some other folks attending your meeting *might* have the DST bug and *their* meeting times will change. They might miss entire meetings or arrive late as you frantically ping them over IRC, Matrix, Signal, SMS, Ricochet, Mattermost, SimpleX, Whatsapp, Discord, Slack, Wechat, Snapchat, Telegram, XMPP, Briar, Zulip, RocketChat, DeltaChat, talk(1), write(1), actual telegrams, Meshtastic, Meshcore, Reticulum, APRS, snail mail, and, finally, flying a remote presence drone to their house, asking what's going on. (Sorry if I forgot your preferred messaging client here, I tried my best.) Be kind; those poor folks might be more sleep deprived as DST *steals* one hour of sleep from them on the night that implements the change. # If you do observe DST If you are affected by the DST bug, your *local* meeting times *will* change access the board. Normally, you can trust that your meetings are scheduled to take this change into account and the new time should still be reasonable. Trust, but verify; make sure the new times *are* adequate and there are no scheduling conflicts. Do this *now*: take a look at your calendar in two week *and* in April. See if any meeting need to be rescheduled because of an impossible or conflicting time. # When does time change, how and where? Notice how I mentioned "North America" in the subject? That's a lie. ("The doctor lies", as they say on the BBC.) Other places, including Europe, also changes times, just not all at once (and not all North America). We'll get into "where" soon, but first let's look at the "how". As you might already know, the trick is: > Spring forward, fall backwards. This northern-centric (sorry!) proverb says that clocks will move *forward* by an hour this "spring", after moving *backwards* last "fall". This is why we lose an hour of work, sorry, sleep. It sucks, to put it bluntly. I want it to stop and will keep writing those advisories until it does. To see where and when, we, unfortunately, still need to go into politics. ## USA and Canada First, we start with "North America" which, really, is just some *parts* of USA[1] and Canada[2]. As usual, on the Second Sunday in March (the 8th) at 02:00 local (not UTC!), the clocks will move forward. This means that properly set clocks will flip from 1:59 to 3:00, coldly depriving us from an hour of sleep that was perniciously granted 6 months ago and making calendar software stupidly hard to write. Practically, set your wrist watch and alarm clocks[3] back one hour before going to bed and go to bed early. [1] except Arizona (except the Navajo nation), US territories, and Hawaii [2] except Yukon, most of Saskatchewan, and parts of British Columbia (northeast), one island in Nunavut (Southampton Island), one town in Ontario (Atikokan) and small parts of Quebec (Le Golfe-du-Saint-Laurent), a list which I keep recopying because I find it just so amazing how chaotic it is. When your clock has its own Wikipedia page, you know something is wrong: https://en.wikipedia.org/wiki/Time_in_Saskatchewan [3] hopefully not managed by a botnet, otherwise kindly ask your bot net operator to apply proper software upgrades in a timely manner ## Europe Next we look at our dear Europe, which will change time on the last Sunday in March (the 29th) at 01:00 *UTC* (not local!). I *think* it means that, Amsterdam-time, the clocks will flip from 1:59 to 3:00 AM *local* on that night. (Every time I write this, I have doubts. I would welcome independent confirmation from night owls that observe that funky behavior experimentally.) Just like your poor fellows out west, just fix your old-school clocks before going to bed, and go to sleep early, it's good for you. ## Rest of the world with DST Renewed and recurring apologies again to the people of Cuba, Mexico, Moldova, Israel, Lebanon, Palestine, Egypt, Chile (except Magallanes Region), parts of Australia, and New Zealand which *all* have their own *individual* DST rules, omitted here for brevity. In general, changes also happen in March, but either on different times or different days, except in the south hemisphere, where they happen in April. ## Rest of the world without DST All of you other folks without DST, rejoice! Thank you for reminding us how manage calendars and clocks normally. Sometimes, doing nothing is precisely the right thing to do. You're an inspiration for us all. # Changes since last time There were, again, no changes since last year on daylight savings that I'm aware of. It seems the US congress debating switching to a "half-daylight" time zone which is an half-baked idea that I should have expected from the current USA politics: https://www.usatoday.com/story/news/nation/2026/02/19/daylight-act-of-2026-… The plan is to, say, switch from "Eastern is UTC-4 in the summer" to "Eastern is UTC-4.5". The bill also proposes to do this 90 days after enactment, which is dangerously optimistic about our capacity at deploying any significant change in human society. In general, I rely on the Wikipedia time nerds for this: https://en.wikipedia.org/wiki/Daylight_saving_time_by_country ... and Paul Eggert which seems to singlehandledly be keeping everything in order for all of us: https://lists.iana.org/hyperkitty/list/tz-announce@iana.org/latest This time, I've also looked at the normal mailing list: https://lists.iana.org/hyperkitty/list/tz@iana.org/latest ... which is where I learned about the congress bill. If your country has changed time and no one above noticed, now would be an extremely late time to do something about this, typically writing to the above list. (Incredibly, *I* need to write to the list because of this post: https://lists.iana.org/hyperkitty/list/tz@iana.org/thread/6HN5SWD2BJA7OVTPF…) One thing that *did* change since last year is that I've implemented what I hope to be a robust calendar for this, which was surprisingly tricky. If you have access to our Nextcloud, it should be visible under the heading "Daylight saving times". If you don't, you can access it using this link directly: https://gitlab.torproject.org/tpo/tpa/team/-/wikis/howto/time/dst.ics The procedures around how this calendar was created, how this email was written, and curses found along the way, are also documented in this wiki page, if someone ever needs to pick up the Time Lord duty: https://gitlab.torproject.org/tpo/tpa/team/-/wikis/howto/time A. -- Antoine Beaupré self-elected time lord in self-training torproject.org system administration

1 2

two important security vulnerabilities for Linux users
by Antoine Beaupré 19 Mar '26

19 Mar '26

Hi! We don't usually share bulletins about security issues like this here; we expect you to perform routine (and preferably automated!) upgrades of your software at home. But those two issues are critical enough to warrant a special announcement. This week, two major security issues affecting server and desktop users in the Linux community have come up. They are: - a local privilege escalation in snapd: https://lwn.net/Articles/1063453/ - a series of vulnerabilities in AppArmor: https://lwn.net/Articles/1062778/ Both issues are quite serious; they could lead to an attacker getting administrator access on your machine, bypassing normal security controls entirely. If you use Ubuntu, you are most certainly using "snapd" and should upgrade. If you don't, you might still be using it as it's also available for other operating systems. AppArmor is also used a lot on Ubuntu, but is also available for some platforms. Red Hat derivatives like Fedora are less affected by both of those, as they typically use Flatpak (instead of snapd) and SELinux (instead of AppArmor). A. -- Antoine Beaupré torproject.org system administration

1 0

Anti-censorship team meeting notes, 2026-03-19
by Cecylia Bocovich 19 Mar '26

19 Mar '26

Hi everyone, Here are our meeting logs: https://meetbot.debian.net/tor-meeting/2026/tor-meeting.2026-03-19-16.01.ht… and our meeting pad: Anti-censorship -------------------------------- Next meeting: Thursday, March 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?s… Project 158 <-- meskio working on it https://gitlab.torproject.org/groups/tpo/anti-censorship/-/issues/?label_na… == Announcements == == Discussion == New stun servers being added, any policy issue with these servers? https://gitlab.torproject.org/tpo/anti-censorship/rdsys-admin/-/merge_reque… we don't see any issues with them will apply them first to circumvention settings and after to the builtin bridges (New 03/17:)Done, we are monitoring the metrics Release schedule planning for containers https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/webt… WebTunnel server has not needed an update, but the tor daemon has updated in the meantime; want to release container updates purely for the sake of getting an upgraded tor, even if there are no changes to WebTunnel Shell will write a ticket about 3 month per maintaince release proposal == Actions == == Interesting links == https://tailscale.com/blog/how-nat-traversal-works <- nice write up about challages about NAT types, for someone look to learn more about NAT dramas (no discussion necessary) == 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-03-19 Last week: - merged snowflake message library changes - https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snow… - rewrote broker pool refactor - https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snow… - worked on proxy fairness proposal Next week: - continue snowflake and lyrebird go version support and release work - follow up about running shadow simulations for snowflake performance - 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-03-19 Last week: - upgraded the OS and the tor daemon on the snowflake-02 bridge https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snow… https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snow… - added a section on important files to back up to the Snowflake Bridge Installation Guide https://gitlab.torproject.org/tpo/anti-censorship/team/-/wikis/Survival-Gui… - commented on proposal for 3 NAT buckets for snowflake broker https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snow… - adjusted permissions on the metrics timeline repository, in an attempt to make it easier for people to commit directly https://gitlab.torproject.org/tpo/network-health/metrics/timeline/-/merge_r… Next week: - open issue to have snowflake-client log whenever KCPInErrors is nonzero https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snow… - parent: https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snow… Help with: meskio: 2026-03-12 Last week: - debug tails issue with meek, was python upstream library issue (lyrebird#40034) - try out gitlab SAST in lyrebird, doesn't produce much output (is that good?) - grant writting Next week: - AFK Shelikhoo: 2026-03-12 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 - 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… ) - [MR Merged] Replace broken stun server with working one ( https://gitlab.torproject.org/tpo/anti-censorship/rdsys-admin/-/merge_reque… ) - [MR] Draft: Update webtunnel version to 0.0.4 and update bundled dockerfile dependencies ( https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/webt… ) 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… ) onyinyang: 2026-02-26 Last week(s): - attended FOCI - Working on https distributor language selector https://gitlab.torproject.org/tpo/anti-censorship/rdsys/-/issues/196 Next week: - Away until March 18 - 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/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-02-19 Last weeks: - Bumping pion stack version with backport: https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snow… - 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

1 0

User Support Report for February 2026
by ebanam 16 Mar '26

16 Mar '26

Hello everyone, This is the report from user support team for the month of February 2026. Note: (↑), (↓) and (-) are indicating if the number of tickets we received for these topics have been increasing, decreasing or have been the same from the previous month respectively. - Summary of updates from user support - General user support - Farsi-speaking user support - Russian-speaking user support - Frontdesk (email user support channel) - Telegram, WhatsApp and Signal user support channels - Highlights from the Tor Forum - Highlights from Google Play Store # Summary of updates from user support ## General user support * 596 tickets in total (↑9 as compared to January) * 423 tickets on Email * 127 tickets on Telegram * 20 tickets on Signal * 26 tickets on WhatsApp * Tor Browser legacy for Windows 7, 8 and 8.1 and macOS 10.12, 10.13 and 10.14 received it's final update, i.e. Tor Browser 13.5.29 and we updated the [Forum guide][] with up-to-date instructions. Users on legacy operating systems are encouraged to update to the [supported operating systems][]. [Forum guide]: https://forum.torproject.org/t/download-tor-browser-13-5-legacy-on-windows-… [supported operating system]: https://support.torproject.org/tor-browser/getting-started/installing/ ## Chinese-speaking user support * Updated the [support entry][] with instructions to censorship circumvention for users in China, to make it more clear that users can get WebTunnel bridges using our Telegram bot (GetBridgesBot) and the bridges website. [support entry]: https://support.torproject.org/tor-browser/circumvention/connecting-from-ce… ## Farsi-speaking user support * 108 tickets in total (↓149 as compared to January) * 27 tickets on Email * 81 tickets on Telegram * We have observed reports of severe filtering measures on Iran’s internet network. Users using Tor with Snowflake reported it has not been working reliably and we have been encouraging users to try connecting to Tor with WebTunnel bridges and [dnstt][] servers (a DNS tunnel to circumvent internet censorship) available through our [dnstt servers distributor][] on Telegram as an alternative. Since the onset of the war, the government has imposed a nationwide internet shutdown. Only a limited number of whitelisted services remain accessible and, as per user reports, most censorship circumvention tools are not working. [dnstt]: https://dnstt.network/ [dnstt servers distributor]: https://t.me/getdnsttbot ## Russian-speaking user support * 888 tickets in total (↑112 as compared to January) * 157 tickets on Email * 725 tickets on Telegram * 6 tickets on WhatsApp * We received many tickets from Russian users of Tor VPN Beta after an article about the app was published in [Meduza][], a popular dissident media outlet. The user support tickets primarily concerning troubleshooting and helping users with instructions to use bridges. * There are multiple requests from the users who are worried about ["whitelist"][] periods when only services from the list are available and all these services are based in Russia. Tor is not available during these periods which can last for hours. [Meduza]: https://meduza.io/cards/sozdateli-tor-odnogo-iz-samyh-nadezhnyh-instrumento… ["whitelist"]: https://gitlab.torproject.org/tpo/anti-censorship/censorship-analysis/-/iss… # Frontdesk (email user support channel) * 485(↓) RT tickets created * 607(↓) RT tickets resolved Tickets by topics and numbers: 1. 181(↓) tickets: instructions to circumvent censorship for Chinese speaking users. 2. 157(↑) tickets: circumventing censorship in Russian speaking countries. 3. 73(↑) tickets: help with troubleshooting existing Tor Browser install on Desktop (Windows, macOS and Linux). 4. 27(↓) tickets: circumventing censorship with Tor in Farsi. 5. 13(↑) tickets: help with installing, uninstalling and updating Tor Browser and Desktop. 6. 11(↑) tickets: reports of fake apps on iOS AppStore masquerading as official Tor Browser and questions about which Tor app to install on iOS (i.e. Onion Browser or Orbot). 7. 6(↑) tickets: report of websites blocking Tor connections or not performing well in Tor Browser. 8. 5(↑) tickets: help with troubleshooting Tor VPN beta. 9. 5(↑) tickets: instructions on how to get Tor Browser binaries from GetTor. 10. 4(↑) tickets: help with setting up Snowflake proxy. 11. 4(↑) tickets: issues with various onion services. The concerned onion services are not maintained by the Tor Project and users are encouraged to report any issues to the onion service operator directly. 12. 3(↑) tickets: users seeing a "proxy refused" error when visiting websites on Tor Browser for Android using Samsung devices. 13. 3(↑) tickets: question about modifying the Tor circuit in Tor Browser. 14. 3(↑) tickets: questions about recommended Tor apps to install on iOS (Onion Browser and Orbot). 15. 3(↑) tickets: instructions for importing and exporting bookmarks on Tor Browser Desktop. 16. 2(↑) tickets: reports of bugs with Tor Browser for Android Alpha 16.0a1 and 16.0a2 (The bugs are resolved in the later versions). 17. 2(↑) tickets: instructions to install little-t tor. 18. 2(↑) tickets: [uBlock Origin integration][] with Tor Browser. 19. 2(↓) tickets: instructions to download Tor Browser 13.5 legacy for legacy operating systems. 20. 2(↑) tickets: help with post-install steps for running a Tor bridge and configuring a bridge distribution method for Tor bridge. 21. 2(↑) tickets: reports of anti-virus software blocking Tor Browser from running on Windows. 22. 2(↑) tickets: unable to save passwords on Tor Browser Desktop. 23. 2(↑) tickets: instructions to setup a Tor Relay. 24. 1(↓) ticket: reports of links on the new support portal giving a 404. 25. 1(-) ticket: question about contributing to Tor. 26. 1(↑) ticket: how to [report Bad Relays][]. 27. 1(↑) ticket: question about Tor Browser Alpha and how is it different from Tor Browser stable. 28. 1(↑) ticket: Error prompting that DLL files are missing when installing / running Tor Browser for Windows. 29. 1(↑) ticket: help with using bridges with Tails. 30. 1(↑) ticket: instructions to install Tor Browser Android from F-Droid. 31. 1(↑) ticket: instructions to setup an onion service. 32. 1(↑) ticket: latest versions of Tor not available from Tor Project's RPM repository for Fedora and CentOS. (The issue has been resolved). 33. 1(↑) ticket: [WebTunnel bridges][] are not available from the Bridges website intermittently.[] 34. 1(↑) ticket: list the [system codecs][] required to run Tor Browser Linux.[] 35. 1(↑) ticket: [Mouse not working][] after updating to Tails 7.4.2.[] 36. 1(↑) ticket: [Tor Browser Flatpak fails to launch][] could not import module PySide6.QtGui. (The issue is resolved). [uBlock Origin integration]: https://forum.torproject.org/t/ublock-origin-integration-with-tor-browser/1… [report Bad Relays]: https://community.torproject.org/relay/community-resources/bad-relays/ [WebTunnel bridges]: https://gitlab.torproject.org/tpo/anti-censorship/rdsys/-/issues/297 [system codecs]: https://gitlab.torproject.org/tpo/web/marble/support/-/issues/104 [Mouse not working]: https://forum.torproject.org/t/mouse-not-working-immediately-after-updating… [Tor Browser Flatpak fails to launch]: https://github.com/flathub/org.torproject.torbrowser-launcher/issues/180 # Telegram, WhatsApp and Signal user support channels * 985(↑) tickets resolved Breakdown: * 933(↓) tickets on Telegram * 20(↑) tickets on Signal * 32(↑) tickets on WhatsApp Tickets by topics and numbers: 1. 731(↑) tickets: circumventing censorship in Russian speaking countries. 2. 81(↓) tickets: circumventing censorship with Tor in Farsi. 3. 70(↑) tickets: using bridges with Tor VPN Beta. 4. 31(↑) tickets: helping users on iOS, using Onion Browser or Orbot, to use censorship circumvention methods. 5. 27(↓) tickets: instructions to circumvent censorship for Chinese speaking users. 6. 23(↓) tickets: instructions to use manually obtained bridges with Tor Browser. 7. 17(↑) tickets: help with troubleshooting existing Tor Browser install on Desktop (Windows, macOS and Linux). 8. 15(↓) tickets: help with instructions to use bridges with Orbot on Android. 9. 10(↑) tickets: GetBridgesBot on Telegram freezes and stops sending bridges and users have to clear chat history. 10. 7(↓) tickets: help with troubleshooting existing Tor Browser install on Android. 11. 6(-) tickets: instructions to use WebTunnel bridges with Tor Browser. 12. 5(↓) tickets: instructions on how to get Tor Browser binaries from GetTor. 13. 4(↑) tickets: help with troubleshooting Tor VPN beta. 14. 4(↑) tickets: help with installing Tor Browser on Desktop on Linux. 15. 3(-) tickets: questions about onion services and how to access them. 16. 3(↓) tickets: help with using Snowflake with Tor to circumvent censorship. 17. 2(↑) tickets: reports of fake apps on iOS AppStore masquerading as official Tor Browser and questions about which Tor app to install on iOS (i.e. Onion Browser or Orbot). 18. 2(-) tickets: help with configuring bridges to use with little-t tor (the network daemon). 19. 1(↓) ticket: instructions to download Tor Browser 13.5 legacy for legacy operating systems. 20. 1(↓) ticket: users seeing a "proxy refused" error when visiting websites on Tor Browser for Android using Samsung devices. 21. 1(↑) ticket: instructions to verify Tor Browser's GPG signature. 22. 1(↑) ticket: Tor Browser on Arm Linux support. # Highlights from the Tor Forum 1. [Tor Browser 13.5.29][] is the final update to the Tor Browser 13.5 legacy for Windows 7, 8, 8.1 and macOS 10.12-10.14. 2. Understanding [Font Fingerprinting][] on Tor Browser. [Tor Browser 13.5.29]: https://forum.torproject.org/t/download-tor-browser-13-5-legacy-on-windows-… [Font Fingerprinting]: https://forum.torproject.org/t/understanding-font-fingerprinting/21260 # Highlights from Google Play Store ## Tor Browser for Android * Tor Browser for Android (TBA) had a Google Play rating of 4.416 (↑0.02) stars in February, which is higher as compared to in January. * Tor Browser for Android (TBA) got 660 (↓24) new reviews. The total count of reviews for the app stands at 68,037. * For Tor Browser, the most common issue mentioned was the censorship against browser in the countries like Russia, China, Iran. ## Tor Browser for Android Alpha * Tor Browser for Android Alpha app had a rating of 4.131 (↓0.001) in February which is lower as compared to in January. * In February, Tor Browser for Android Alpha got 15 (↓12) new reviews. The total count of reviews for the app stands at 8,772. ## Tor VPN Beta * Tor VPN beta was installed almost 83,000 (↑12,000) times by the end of February. The top 5 countries by the number of installations being (in descending order): Iran, Russia, Turkmenistan, India, and the United States. Thanks! -- ebanam

1 0

Anti-censorship team meeting notes, 2026-03-12
by meskio 12 Mar '26

12 Mar '26

Hey everyone! Here are our meeting logs: https://meetbot.debian.net/tor-meeting/2026/tor-meeting.2026-03-12-16.00.lo… And our meeting pad: Anti-censorship -------------------------------- Next meeting: Thursday, March 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?s… * Project 158 <-- meskio working on it * https://gitlab.torproject.org/groups/tpo/anti-censorship/-/issues/?label_na… == Announcements == * We can bump the min Go version in snowflake and lyrebird to 1.25 if needed * https://gitlab.torproject.org/tpo/applications/tor-browser-build/-/issues/4… == Discussion == * should we start collecting webtunnel bridges for the missing pools (email and restricted) * https://gitlab.torproject.org/tpo/anti-censorship/rdsys/-/issues/298 * let's start assigning bridges to the remaining pools and enable email once we have enough * meskio will do the config change * New stun servers being added, any policy issue with these servers? * https://gitlab.torproject.org/tpo/anti-censorship/rdsys-admin/-/merge_reque… * we don't see any issues with them * will apply them first to circumvention settings and after to the builtin bridges == Actions == * == Interesting links == https://tailscale.com/blog/how-nat-traversal-works <- nice write up about challages about NAT types, for someone look to learn more about NAT dramas (no discussion necessary) == 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-03-12 Last week: - opened a MR in tor-browser-build for legacy go1.22 support for macos - https://gitlab.torproject.org/tpo/applications/tor-browser-build/-/merge_re… - released version 2.12.1 of snowflake - https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snow… - discussed stun server testing and updates with shell - discussed cc algorithms with lanius_collaris and opened issue about it - https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snow… - gave feedback on snowflake simulations for proxy fairness proposal Next week: - continue snowflake and lyrebird go version support and release work - follow up about running shadow simulations for snowflake performance - 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-03-05 Last week: - reviewed on a "??" geoip fix in snowflake proxy https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snow… - made an issue for OS upgrade on snowflake-02, necessary before being able to updgrade tor https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snow… - wrote up a research idea for using rateless erasure codes for rendezvous https://gitlab.torproject.org/tpo/anti-censorship/team/-/wikis/Research-ide… - posted a short tutorial on using ooni-sync to download OONI measurements https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snow… - reviewed an MR to enable disable stats reporting in the snowflake standalone proxy https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snow… Next week: - upgrade OS on the snowflake-02 bridge https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snow… - open issue to have snowflake-client log whenever KCPInErrors is nonzero https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snow… - parent: https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snow… Help with: meskio: 2026-03-12 Last week: - debug tails issue with meek, was python upstream library issue (lyrebird#40034) - try out gitlab SAST in lyrebird, doesn't produce much output (is that good?) - grant writting Next week: - AFK Shelikhoo: 2026-03-12 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 - 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… ) - [MR] Replace broken stun server with working one ( https://gitlab.torproject.org/tpo/anti-censorship/rdsys-admin/-/merge_reque… ) - [Research] Add More Stun Servers to Snowflake 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… ) onyinyang: 2026-02-26 Last week(s): - attended FOCI - Working on https distributor language selector https://gitlab.torproject.org/tpo/anti-censorship/rdsys/-/issues/196 Next week: - Away until March 18 - 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/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-02-19 Last weeks: - Bumping pion stack version with backport: https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snow… - 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 -- meskio | https://meskio.net/ -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- My contact info: https://meskio.net/crypto.txt -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Nos vamos a Croatan.

1 0

minutes from the sysadmin
by Antoine Beaupré 11 Mar '26

11 Mar '26

Hi everyone, here's your monthly dose of sysadmin minutes... Do note an interesting discussion about LLMs, not a formal policy, just a discussion for now. # Roll call: who's there and emergencies all members present # Express check-in How are you doing, and are there any blockers? Then pass the mic to the next person. # Roadmap discussion Review the [2026 roadmap][] especially with the [STF grant][] not going through. One month left in the quarter, we might get some input from upstairs for the next. [STF grant]: https://gitlab.torproject.org/tpo/operations/proposals/-/issues/70 [2026 roadmap]: https://gitlab.torproject.org/groups/tpo/tpa/-/epics/2 Here's what everyone will be working on: ## zen - [profiles merge][] - [planning phase for Tails migration to Prometheus][] [planning phase for Tails migration to Prometheus]: https://gitlab.torproject.org/tpo/tpa/team/-/issues/41946 [profiles merge]: https://gitlab.torproject.org/tpo/tpa/team/-/issues/42103 ## lavamind - donate-neo - download page ## groente - anarcat carried the idea that email should be prioritized - let's meet with nadya to get a better idea of the requirements, anarcat will check for reusing the timeslot tomorrow ## lelutin - prometheus HA - garage conversion ## anarcat - wiki problem? experimented a lot with mkdocs/zensical for a [personal project][] [personal project]: https://lora.reseaulibre.ca/ # AI brainstorm? - anarcat: was extremely skeptical with capacity and morals of AI, now he's worried with the profession. We might lose an entire generation of programmers. Worried with reliability of software, environmental and political impact. But he's using it -- not vibe coding, rarely using it for coding -- it causes skills atrophy, but uses it for spell checking. Disclosure should be mandatory: disclose the model and prompt (eg. in commit messages). (Other messages here are unattributed, but from each team member.) - It's hard, and getting harder, to not use it: e.g. google pushes you towards it when you search. Concerned with our jobs and pressure on "efficiency", and that we might be forced to use LLMs. Could we have [RAG][] for our documentation? [RAG]: https://en.wikipedia.org/wiki/Retrieval-augmented_generation - groente: As for job security and pressure for "efficiency", one would hope there will always be a market for people that understand how systems work. The pressure to use LLMs will likely grow: compare it to household appliances (or many other technologies) that were thought to save us time, but in the end just created higher expectations. Resisting this will likely be extremely hard within a capitalist environment, but hopefully we can carve out some space within non-profits at least. It's kind of ironic, this LLM use is once again creating a huge dependency on a small number of US tech companies. There's now a lot of geopolitical momentum to decrease infrastructural dependency on the US, but at the same time we're massively walking into the same pitfall with AI. Let's hope Tor is smarter than that. The earlier push towards cloud computing was successfully resisted, so I'm still hopeful here. - We still have jobs through the cloud migration, even though we were told our jobs would stop existing. I like to code so I don't want to use AI, but all my friends are using it, and the reason I was getting crap outputs in first attempts was that I wasn't sending enough context. Concerned about people's mental health, especially after an article [shared this morning about "How to Talk to Someone Experiencing 'AI Psychosis'"][]. [shared this morning about "How to Talk to Someone Experiencing 'AI Psychosis'"]: https://www.404media.co/ai-psychosis-help-gemini-chatgpt-claude-chatbot-del… - Not using it. Search results are getting worse and worse. Really hesitant in jumping in, fundamentally misanthropic technology. As a temporary moratorium, anarcat announced that TPA team members are forbidden to grant any sort of execution access to LLMs for machines under their stewardship. If you want to experiment with AI, you can copy-paste things, feed it input, but in no way should you execute code from LLMs without the same level of review you would give to an untrusted contributor. This applies, in particular, to agents: if you experiment with agents like Claude Code, run those in a virtual machine. # Next meeting Next month's first Monday is Easter in some cultures and a holiday in most of our workers, so the roadmap meeting will be held the second Monday of April. # Metrics of the month * host count: 95, LDAP 140 (!), Puppet 136 (!) * number of Apache servers monitored: 32, hits per second: 659 * number of self-hosted nameservers: 6, mail servers: 13 * pending upgrades: 0, reboots: 0 * average load: 1.38, memory available: 4.3 TB/6.8 TB, running processes: 160 * disk free/total: 111.3 TB/216.5 TB * bytes sent: 534.4 MB/s, received: 362.1 MB/s * [GitLab tickets][]: 272 tickets including... * Needs Triage: 1 * Not Scheduled: 164 * Backlog: 66 * Next: 29 * Doing: 12 * (closed: 4416) * [~Needs Information][]: 3 open, 125 closed * [~Needs Review][]: 7 open, 201 closed * [~Technical Debt][]: 10 open, 38 closed [Gitlab tickets]: https://gitlab.torproject.org/tpo/tpa/team/-/boards [~Needs Information]: https://gitlab.torproject.org/groups/tpo/tpa/-/issues/?state=opened&label_n… [~Needs Review]: https://gitlab.torproject.org/groups/tpo/tpa/-/issues/?state=opened&label_n… [~Technical Debt]: https://gitlab.torproject.org/groups/tpo/tpa/-/issues/?state=opened&label_n… Upgrade prediction graph lives at https://gitlab.torproject.org/tpo/tpa/team/-/wikis/howto/upgrades/trixie/ -- Antoine Beaupré torproject.org system administration

1 0

Anti-censorship team meeting notes, 2026-03-05
by Shelikhoo 05 Mar '26

05 Mar '26

Hey everyone! Here are our meeting logs: https://meetbot.debian.net/tor-meeting/2026/tor-meeting.2026-03-05-16.00.ht… And our meeting pad: Anti-censorship work meeting pad -------------------------------- Anti-censorship -------------------------------- Next meeting: Thursday, March 12 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?s… * Project 158 <-- meskio working on it * https://gitlab.torproject.org/groups/tpo/anti-censorship/-/issues/?label_na… == Announcements == == Discussion == * Should we priorize better matching logic on snowflake broker * https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snow… * See also: https://datatracker.ietf.org/doc/html/rfc5780 * [Option C] Fix it soon * proposal to get a separate domain name for bridge reachability tests * add a record for each known *.torproject.net bridge * https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snow… == 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-03-05 Last week: - wrote a patch for go 1.22 support (snowflake#40490) - worked on proxy bridge reachability checks (snowflake#40504) - opened issue with TPA to get a bridge probe domain with multiple A records - tried out mobile snowflake proxy app by contributor - https://github.com/blocoio/snowflake - caught up on IPtProxy issue about snowflake proxy events - https://github.com/tladesignz/IPtProxy/issues/81 - created issue to disable summary stats task if duration is 0 (snowflake#40524) - implemented fix (snowflake!687) - wrote script to parse OONI stun reachability check results (snowflake#40523) - https://gitlab.torproject.org/-/snippets/240 - updated circumvention settings in rdsys (rdsys-admin!46) - more work on proxy fairness proposal Next week: - finish working on snowflake compatability with go1.22 - 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-03-05 Last week: - reviewed on a "??" geoip fix in snowflake proxy https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snow… - made an issue for OS upgrade on snowflake-02, necessary before being able to updgrade tor https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snow… - wrote up a research idea for using rateless erasure codes for rendezvous https://gitlab.torproject.org/tpo/anti-censorship/team/-/wikis/Research-ide… - posted a short tutorial on using ooni-sync to download OONI measurements https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snow… - reviewed an MR to enable disable stats reporting in the snowflake standalone proxy https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snow… Next week: - upgrade OS on the snowflake-02 bridge https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snow… - open issue to have snowflake-client log whenever KCPInErrors is nonzero https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snow… - parent: https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snow… Help with: meskio: 2026-03-05 Last week: - grant writting Next week: - no webtunnel bridges in the https distributor (rdsys#262) Shelikhoo: 2026-03-05 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 - Vantage point maintaince - Expore DNS tunneling options(https://gitlab.torproject.org/tpo/anti-censorship/team/-/issues/173) - [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… ) 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… ) onyinyang: 2026-02-26 Last week(s): - attended FOCI - Working on https distributor language selector https://gitlab.torproject.org/tpo/anti-censorship/rdsys/-/issues/196 Next week: - Away until March 18 - 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/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-02-19 Last weeks: - Bumping pion stack version with backport: https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snow… - 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

1 0