- tor-project - lists.torproject.org

minutes from the sysadmin meeting
by Antoine Beaupré 16 Oct '24

16 Oct '24

# Roll call: who's there and emergencies No emergencies, some noises in Karma because of TLS monitoring misconfigurations. - anarcat - groente - lavamind - lelutin (late) - zen Note: we could have the star of the week responsible for calling and facilitating meetings, instead of always having anarcat do it. # Dashboard review Normal per-user check-in: * https://gitlab.torproject.org/groups/tpo/-/boards?scope=all&utf8=%E2%9C%93&… * https://gitlab.torproject.org/groups/tpo/-/boards?scope=all&utf8=%E2%9C%93&… * https://gitlab.torproject.org/groups/tpo/-/boards?scope=all&utf8=%E2%9C%93&… * https://gitlab.torproject.org/groups/tpo/-/boards?scope=all&utf8=%E2%9C%93&… * https://gitlab.torproject.org/groups/tpo/-/boards?scope=all&utf8=%E2%9C%93&… General dashboards: * https://gitlab.torproject.org/tpo/tpa/team/-/boards/117 * https://gitlab.torproject.org/groups/tpo/web/-/boards * https://gitlab.torproject.org/groups/tpo/tpa/-/boards Note: ~"First contribution" labels issues that are good for people looking for small, bite-sized chunks of easy work. It is used across GitLab, but especially in the `tpo/web` namespace. # Roadmap review Review priorities for October and the quarter. Here are the focuses of people in the team: - lavamind: web issues (build times, search boxes, share buttons), then Puppet 7 server upgrade, possibly Ganeti cluster upgrades after - anarcat and groente will focus on mail (mailman 3 and SRS, respectively) - lelutin will focus on finishing high priority work in the phase B of the Prometheus roadmap - zen will focus on the Nextcloud work and merge roadmap # Next meeting In the next meeting, we'll need to work on: - holidays shift rotations planning - roadmap 2025 brainstorming and elaboration # Metrics of the month * hosts in Puppet: 90, LDAP: 90, Prometheus exporters: 536 * number of Apache servers monitored: 34, hits per second: 594 * number of self-hosted nameservers: 6, mail servers: 10 * pending upgrades: 0, reboots: 0 * average load: 0.66, memory available: 3.51 TiB/4.98 TiB, running processes: 300 * disk free/total: 67.69 TiB/140.19 TiB * bytes sent: 469.78 MB/s, received: 305.60 MB/s * planned bookworm upgrades completion date: 2024-09-09 * [GitLab tickets][]: 259 tickets including... * open: 0 * icebox: 164 * future: 20 * needs information: 6 * backlog: 43 * next: 10 * doing: 8 * needs review: 9 * (closed: 3716) [Gitlab tickets]: https://gitlab.torproject.org/tpo/tpa/team/-/boards Upgrade prediction graph lives at https://gitlab.torproject.org/tpo/tpa/team/-/wikis/howto/upgrades/bookworm/ Now also available as the main Grafana dashboard. Head to <https://grafana.torproject.org/>, change the time period to 30 days, and wait a while for results to render. -- Antoine Beaupré torproject.org system administration

1 0

Anti-censorship team meeting notes, 2024-10-10
by onyinyang 10 Oct '24

10 Oct '24

Hey everyone! Here are our meeting logs: http://meetbot.debian.net/tor-meeting/2024/tor-meeting.2024-10-10-16.00.html And our meeting pad: Anti-censorship work meeting pad -------------------------------- Anti-censorship -------------------------------- Next meeting: Thursday, October 10 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… * Project 158 <-- meskio working on it * https://gitlab.torproject.org/groups/tpo/anti-censorship/-/issues/?label_na… == Announcements == * == Discussion == (Oct 3:) * Broker installation over at: * snowflake-broker-debianupgradestaging-j33r3zahe.torproject.net * ready to be tested and then switch to be the primary broker * ./proxy -nat-probe-server https://snowflake-broker-debianupgradestaging-j33r3zahe.torproject.net:8443… -broker https://snowflake-broker-debianupgradestaging-j33r3zahe.torproject.net/ -verbose * https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snow… * Follow up Oct 10: * Testing from commandline worked * testing from tor browser still connects to original broker but should be fine once domain name is switched (Oct 10 New): * Prepare DeploymentTool for Publishing * https://gitlab.torproject.org/tpo/anti-censorship/connectivity-measurement/… == 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? == 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): 2024-09-26 Last week: - worked with meek bridge operator to update domain names - dove into family support for bridges (tor#40935) - TROVE-2024-012 - merged and then unmerged kcp library update This week: - take a look at WofWca's big changes to snowflake - finish snowflake dependency upgrades that were causing problems - take a look at snowflake web and webext translations and best practices - make changes to Lox encrypted bridge table - https://gitlab.torproject.org/tpo/anti-censorship/lox/-/merge_requests/147 dcf: 2024-10-03 Last week: - more review of snowflake webextension Manifest V3 running in background https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snow… - commented installation procedure for replacement snowflake broker https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snow… - snowflake azure CDN bookkeeping https://gitlab.torproject.org/tpo/anti-censorship/team/-/wikis/Snowflake-co… 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… - open issue to disable /debug endpoint on snowflake broker Help with: - tell me when to restart the brokers for https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snow… meskio: 2023-10-03 Last week: - Travel to the Global Gathering Next week: - investigate if bridges are still jumping distributors (rdsys#232) - plan the work on snowflake proxy packaging Shelikhoo: 2024-10-10 Last Week: - snowflake broker update/reinstall(cont.): https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snow… - Unreliable+unordered WebRTC data channel transport for Snowflake rev2 (cont.)( https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snow… ) improvements - Review CI: fix `latest` container image tag. https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snow… - Merge request reviews Next Week/TODO: - Merge request reviews - Unreliable+unordered WebRTC data channel transport for Snowflake rev2 (cont.) ( https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snow… ) improvements - Work on finishing snowflake container release(and fix the comments) - Work on Parpare DeploymentTool for Publishing https://gitlab.torproject.org/tpo/anti-censorship/connectivity-measurement/… onyinyang: 2023-10-10 Last week(s): - continue troll-patrol integration for Lox bridge blockage detection Next week: - continue troll-patrol integration for Lox bridge blockage detection - update lox protocols to return duplicate responses for an already seen request - Work on outstanding milestone issues: in particular: https://gitlab.torproject.org/tpo/anti-censorship/lox/-/issues/69 - 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: 2024-09-12 Last weeks: - Next weeks: - Update Snowflake to use latest pion upstream releases, waiting for WebRTC v4 beta. - Test Snowflake fork with covert-dtls - Condensing thesis into paper Help with: - Feedback on thesis Facilitator Queue: 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 -- --- onyinyang GPG Fingerprint 3CC3 F8CC E9D0 A92F A108 38EF 156A 6435 430C 2036

1 0

Tor Browser Meeting Rescheduled to 15 October, 2024
by Morgan 07 Oct '24

07 Oct '24

Hi folks, Next Monday is a holiday, so our regularly scheduled meeting will be delayed a day to Tuesday the 15th at 1500 UTC in #tor-meeting. best, -morgan

1 0

cohosh's monthly status report, September 2024
by Cecylia Bocovich 05 Oct '24

05 Oct '24

Hi! This is my status report for contract work done in September 2024. I was AFK for a lot of the month, and spent a lot of my time catching up on gitlab reviews and todos. I also did a bit of work on grant writing to fund Conjure development, which ended up falling through, but should hopefully be useful for a future application. # Snowflake Most of my work on snowflake this month was reviewing or commenting on several large merge requests. https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snow… https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snow… https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snow… There was a bug in the snowflake web extension that caused us to lose more browser proxies. https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snow… We also had some upstream library upgrades that caused CI failures. These have yet to be fully addressed, but I spent some time narrowing down the causes. https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snow… https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snow… # meek We have some follow up tasks for the meek bridge handover. I reached out to the bridge operator to help switch over domains and take care of a few remaining tasks. https://gitlab.torproject.org/tpo/anti-censorship/team/-/issues/133 https://gitlab.torproject.org/tpo/tpa/team/-/issues/41742 Dove into family support for bridges and caught TROVE-2024-012 https://gitlab.torproject.org/tpo/core/tor/-/issues/40976

1 0

ebanam's monthly status report and user support report for September 2024
by ebanam 04 Oct '24

04 Oct '24

Hello everyone, This is a summary of the work I did in the month of September followed by a more detailed report of the work done by our user support team. I made some small additions to the user-facing documentation on our Support Portal[0]. With 7 Tor Browser (Alpha and Stable) releases in the month, I answered a number of Tor Browser related user support tickets and allocated some time to test the latest Alpha releases. Majority of my work was dedicated to help users in regions where Tor is censored which includes but is not limited to helping users with instructions to download Tor Browser binaries from GetTor and/or official mirrors, verifying Tor Browser's GPG signature, help with using censorship circumvention methods that works best for them and overall troubleshooting. Here's a more detailed breakdown of the tickets our user support team worked on last month: # Frontdesk (email user support channel) * 543(↓) RT tickets created * 712(↑) RT tickets resolved Tickets by topics and numbers: 1. 322(↓) RT tickets: private bridge requests from Chinese speaking users. 2. 193(↓) RT tickets: circumventing censorship in Russian speaking countries. 3. 8 RT tickets: help with installing Tor Browser on desktop operating systems. 4. 6 RT tickets: questions about Tor Browser dropping support for legacy operating systems, i.e. Windows 7/8/8.1 and macOS ≤ 10.14[1]. 5. 3 RT tickets: questions about using Tor from users in Brazil after X (Twitter) was blocked. 6. 3 RT tickets: Captchas missing when fetching bridges from BridgeDB[2]. 7. 3 RT tickets: instructions to download Tor Browser binaries from GetTor (email and Telegram). 8. 3 RT tickets: questions about contributing to Tor. 9. 2(↓) RT tickets: circumventing censorship with Tor in Farsi. 10. 2 RT tickets: help with instructions to verify Tor Browser signature. 11. 2 RT tickets: reports of Letterboxing in Tor Browser visible even if disabled with tiled window managers[3]. 12. 2 RT tickets: reports of websites blocking Tor. 13. 2 RT tickets: reports of fake apps on iOS AppStore masquerading as official Tor Browser. 14. 2 RT tickets: how to add/change default search engine on Tor Browser. 15. 2 RT tickets: questions about the 'Security Levels' in Tor Browser. 16. 1 RT ticket: help with setting up a Snowflake proxy. 17. 1 RT ticket: help with setting up a Bridge relay. 18. 1 RT ticket: anti-virus (on Windows) blocking Tor Browser. # Telegram, WhatsApp and Signal Support channel * 814(↑) tickets resolved Breakdown: * 773(↑) tickets on Telegram * 41(↑) tickets on WhatsApp * 0(-) ticket on Signal Tickets by topics and numbers: 1. 471(↓) tickets: circumventing censorship in Russian speaking countries. 2. 45(↓) tickets: circumventing censorship with Tor in Farsi. 3. 30(↑) tickets: private bridge requests from Chinese speaking users. 4. 20 tickets: helping users on iOS, using Onion Browser or Orbot, to use censorship circumvention methods. 5. 11 tickets: instructions on how to get Tor Browser binaries from GetTor. 6. 8 tickets: questions about what onion services are and how to access them. 7. 6 tickets: help with using bridges with Orbot. 8. 5 tickets: help with troubleshooting Tor Browser install on Linux. 9. 4 tickets: troubleshooting Tor Browser install on Android. 10. 3 tickets: instructions to use bridges with Tails. 11. 2 tickets: help with troubleshooting Tor Browser install on macOS. 12. 2 tickets: help with setting up Snowflake proxy. 13. 2 tickets: help with using bridges with little-t-tor. 14. 1 ticket: question about using Tor from a user in Brazil after X (Twitter) was blocked. # Highlights from the Tor Forum 1. Call for alpha testers to help test the latest Tor Alpha before Tor Browser 14 release[4]. 2. Disable compatibility mode on Windows 10/11 to not get notified about Tor Browser dropping support for legacy operating systems[5][1]. 3. NoScript per-site permissions on Tor Browser[6]. 4. Do not disable NoScript in Tor Browser[7]. Thanks! e. 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. [0]: https://gitlab.torproject.org/tpo/web/support/-/commits/main?author=ebanam [1]: https://support.torproject.org/tbb/tor-browser-and-legacy-os/ [2]: https://lists.torproject.org/pipermail/tor-relays/2024-September/021868.html [3]: https://gitlab.torproject.org/tpo/applications/tor-browser/-/issues/42670 [4]: https://forum.torproject.org/t/new-alpha-release-tor-browser-14-0a7/14862 [5]: https://forum.torproject.org/t/dont-understand-warning-about-windows-releas… [6]: https://forum.torproject.org/t/noscript-per-site-permissions-question-about… [7]: https://forum.torproject.org/t/should-i-disable-noscript-in-tor-browser/144…

1 0

Anti-censorship team meeting notes, 2024-10-03
by meskio 03 Oct '24

03 Oct '24

Hey everyone! Here are our meeting logs: http://meetbot.debian.net/tor-meeting/2024/tor-meeting.2024-10-03-16.00.html And our meeting pad: Anti-censorship -------------------------------- Next meeting: Thursday, October 10 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… * Project 158 <-- meskio working on it * https://gitlab.torproject.org/groups/tpo/anti-censorship/-/issues/?label_na… == Announcements == * == Discussion == (Sep 26 New:) * probetest delay-before-disconnect to reduce incorrect "restricted" measurements * https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snow… * shelikhoo will deploy next week, maybe Monday 2024-09-30 (Oct 3 New:) * Broker installation over at: * snowflake-broker-debianupgradestaging-j33r3zahe.torproject.net * ready to be tested and then switch to be the primary broker * ./proxy -nat-probe-server https://snowflake-broker-debianupgradestaging-j33r3zahe.torproject.net:8443… -broker https://snowflake-broker-debianupgradestaging-j33r3zahe.torproject.net/ -verbose * https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snow… == Actions == == Interesting links == Notes from our circle on signalling channel at the Global Gathering are posted: - https://pad.riseup.net/p/GG-2024-Day2-Village1b == 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? == 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): 2024-09-26 Last week: - worked with meek bridge operator to update domain names - dove into family support for bridges (tor#40935) - TROVE-2024-012 - merged and then unmerged kcp library update This week: - take a look at WofWca's big changes to snowflake - finish snowflake dependency upgrades that were causing problems - take a look at snowflake web and webext translations and best practices - make changes to Lox encrypted bridge table - https://gitlab.torproject.org/tpo/anti-censorship/lox/-/merge_requests/147 dcf: 2024-10-03 Last week: - more review of snowflake webextension Manifest V3 running in background https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snow… - commented installation procedure for replacement snowflake broker https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snow… - snowflake azure CDN bookkeeping https://gitlab.torproject.org/tpo/anti-censorship/team/-/wikis/Snowflake-co… 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… - open issue to disable /debug endpoint on snowflake broker Help with: - tell me when to restart the brokers for https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snow… meskio: 2023-10-03 Last week: - Travel to the Global Gathering Next week: - investigate if bridges are still jumping distributors (rdsys#232) - plan the work on snowflake proxy packaging Shelikhoo: 2024-10-03 Last Week: - snowflake broker update/reinstall(cont.): https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snow… - Unreliable+unordered WebRTC data channel transport for Snowflake rev2 (cont.)( https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snow… ) improvements - Merge request reviews Next Week/TODO: - Merge request reviews - Unreliable+unordered WebRTC data channel transport for Snowflake rev2 (cont.) ( https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snow… ) improvements - Work on finishing snowflake container release onyinyang: 2023-10-03 Last week(s): - Global Gathering Next week: - continue troll-patrol integration for Lox bridge blockage detection - update lox protocols to return duplicate responses for an already seen request - Work on outstanding milestone issues: in particular: https://gitlab.torproject.org/tpo/anti-censorship/lox/-/issues/69 - 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: 2024-09-12 Last weeks: - Next weeks: - Update Snowflake to use latest pion upstream releases, waiting for WebRTC v4 beta. - Test Snowflake fork with covert-dtls - Condensing thesis into paper Help with: - Feedback on thesis Facilitator Queue: 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

Rhatto's Monthly Status Report, September 2024
by rhatto 02 Oct '24

02 Oct '24

Hi all :) This is my monthly status report for September 2024 with the main relevant activities I have done, was involved or are related to my work during the period. For other Onion Services news, check this post: https://forum.torproject.org/t/some-news-from-the-onionspace-2024-09/14963 # Planning Helped with the overall planning for the upcoming Onion Service tooling development. It allowed me to figure out priorities, and finally clean my backlog. This also resulted in creating an Onion Services feature matrix comparing Arti and C Tor: https://onionservices.torproject.org/dev/implementations/ The current plan is summarized below. ## Oniongroove - next generation onionsite manager Project page: https://onionservices.torproject.org/apps/web/oniongroove/ Plan: have Oniongroove acting as a middleware, abstracting specifics from the underlying Tor (and perhaps the HTTPS rewriting proxy) implementation. Advantages: it might be easier for Onion Service Operators to adopt a tool supporting both backends. They can start using the C Tor backend and later on switch for Arti, eg. once the needed feature set becomes supported. Current goals: * Goal 1: support both C Tor and Arti as backends (prototype). * Goal 2: feature-parity with Onionspray, for the C Tor backend (taking some onionsites we manage as a reference for the requirements); migration procedure from Onionspray (production-ready). ## Onionspray - current onionsite manager Project page: https://onionservices.torproject.org/apps/web/onionspray/ Current focus: * Keep supporting Onionspray until there's feature parity with Oniongroove, plus a migration procedure. * Merge requests are welcome :) ## Onionbalance - load balancer for Onion Services Project page: https://onionservices.torproject.org/apps/base/onionbalance/ The road mapping discussion for Onionbalance is still ongoing. Meanwhile, my focus would be to keep the software working, and going through issues and MRs when doable. It's still uncertain how load balancing with Onion Services should be done in the long term, since: * Proof of Work (PoW) Support in Onionbalance is still in the discussion phase: https://gitlab.torproject.org/tpo/onion-services/onionbalance/-/issues/13 * A replacement built-in directly on Arti still needs design; it will possibly be based on changes in the descriptor; a publisher node would be way simpler than the current functionality. There's still no timeline for that. On the other hand, Onionbalance is basically a descriptor publisher. So, roughly speaking, migrating away from Onionbalance to an Arti-equivalent implementation won't require Operators to migrate all their C Tor setup to Arti: they could just replace their Onionbalance instance with something else and keep all their backend onionsites with C Tor for a while. That said, depending on the design changes to implement PoW, it would still be needed to backport this feature to the C Tor backends and clients, which may not be a lot of stuff (possibly just descriptor changes). In summary, one way to move forward could be (but these are still only speculations): 1. Creating a spec for PoW with descriptor-based load balancing: this seems to be mostly about (new) descriptor field(s). 2. Evaluate/scope what would be needed to: * Implement this both for Onionbalance. Maybe it's just a few changes... * Implement this on Arti. That involves implementing the whole load balancing feature. * Backport the changes needed on C Tor both for backends and clients. 3. Then we could decide whether to do it for Onionbalance to win time, or just skip it in favor of a migration. ## Onionprobe - monitoring tool for onionsites Project page: https://onionservices.torproject.org/apps/web/onionprobe/ Current focus: properly set the Grafana dashboard within Tor Project: https://gitlab.torproject.org/tpo/onion-services/onion-support/-/issues/93 Support for the Arti backend was postponed to future (2026+), after Arti's RPC is stabilized. This is being tracked at https://gitlab.torproject.org/tpo/onion-services/onionprobe/-/issues/86 There are lots of ideas for improvements, that may be implemented opportunistically. # Documentation Did some documentation updates, including: * The Certificate Proposals page: https://onionservices.torproject.org/research/proposals/usability/certifica… * Some roadmap scenarios (but these still need more work): https://onionservices.torproject.org/research/scenarios/ux/ https://onionservices.torproject.org/research/scenarios/network/ -- Silvio Rhatto pronouns he/him

1 0

Nina’s Monthly Status Report, September, 2024
by Nina 02 Oct '24

02 Oct '24

Hi! Below is my September’24 report! In September, I resolved 994 (↑16) tickets: * On Telegram (@TorProjectSupportBot) - 728 (↑41); * On RT (frontdesk@tpo) - 189 (↓44); * On WhatsApp (+447421000612) - 27 (↑19); * and on Signal (+17787431312) - 0 (0). I also took part in forum moderation [1], worked with storereviews, and joinedthe Tor relay operators meetup. The focus of my work is to help Russian-speaking users: - to bypass censorship and to connect to Tor; - to troubleshoot any problems with Tor Browser; - to collect users' feedback and then use it to provide working bridges. We still got many tickets from Russia due to internet censorship getting stronger; our users reported that many Tor bridges didn't work for them.Also, we got multiple requests from Russian-speakingTails users. In September, I also checked and edited several user support templatesused in our support tools. *Google Play Reviews for Tor Browser**(TBA)**and Tor Browser Alpha**for Android* Tor Browser App had a Google Play rating of 4.388-4.390 stars in September 2024. Tor Browser App got 668 reviews out of 57976 for the lifetime. Most often topics of the reviews: - Samsung users point out the error "Proxy server refused connection" on their devices; [2] - Some (mostly Google Pixel) users complain about Tor Browser draining battery of their devices; [3] - Tor Browser doesn't work - mostly from users from Russia, who are struggling to find the working bridge; - Kind words from Portuguese-speaking users from Brazil who started using Tor Browser due to an internet censorship case in the country - the X platform (former Twitter) was blocked [4]. Tor Browser Alpha App had a rating of 4.265, lower than Tor Browser Stable. In September, Tor Browser Alpha got 35 reviews out of 8337 for the lifetime. [1] https://forum.torproject.org [2] https://gitlab.torproject.org/tpo/applications/tor-browser/-/issues/42714 [3] https://gitlab.torproject.org/tpo/applications/tor-browser/-/issues/43137 [4] https://en.wikipedia.org/wiki/Blocking_of_Twitter_in_Brazil

1 0

Felicia's Montly Status Report, September 2024
by Priscila 01 Oct '24

01 Oct '24

Hi everyone, Here is my status report for September 2024: ### Tor Browser - Designed the implementation of the “New circuit for this site” feature on Android using Acorn’s updated design tokens https://gitlab.torproject.org/tpo/applications/tor-browser/-/issues/42655 - Adjusted light and dark colors of the onion pattern in about:torconnect https://gitlab.torproject.org/tpo/applications/tor-browser/-/issues/43087 ### Design System The tasks listed below refer to Figma libraries only: - Joined donuts in a meeting with Mozilla UX team - Unified Mozilla Firefox and Tor’s desktop styles libraries, adding Tor’s specific purple shades for light and dark modes and correcting elements that were out of date https://gitlab.torproject.org/tpo/ux/design/-/work_items/108 - Unified Mozilla Firefox and Tor’s mobile styles libraries, keeping visual elements for Private mode on Android only since it’s the one used in Tor Browser for Android https://gitlab.torproject.org/tpo/ux/design/-/work_items/113 - Unified Mozilla Firefox and Tor Browser’s assets libraries: https://gitlab.torproject.org/tpo/ux/design/-/work_items/109 - Unified Mozilla Firefox and Tor Browser’s components libraries, updating its colors to variables so we can quickly switch between Light and Dark modes while improving consistency (this task was actually finished on October 1, but I’m listing in September as it was almost entirely done then) https://gitlab.torproject.org/tpo/ux/design/-/work_items/110 ### Tor VPN - Joined a brainstorming session for Tor VPN ran by sajolida https://www.figma.com/board/5dWNYdBBEPVJN1kSsZEmrd/VPN-brainstorming?node-i… Cheers, - Felicia / UX Team

1 0

PieroV's Monthly Status Report, September 2024
by Pier Angelo Vendrame 01 Oct '24

01 Oct '24

Hi everyone! Here is my status report for September 2024. I dedicated a consistent part of this month to various tasks to fix regressions we got after migrating to Firefox 128 or for refinements. I started by re-implementing our search engine customization. Upstream themselves reworked their configuration, so I ended up reverting our previous patch and implementing a new one [0]. While at it, I removed some search engines we used to bundle by default, such as Yahoo and Twitter. I also re-implemented the functionality to send DuckDuckGo searches through its HTML-only version when running at the safest security level [1]. After doing this for Tor Browser, I wrote similar patches for Mullvad Browser [2]. After that, I worked on the Android part of our build system. I removed the Lox WASM blob [3], which isn't currently used on Android. This allowed us to ship x86 APKs on the Play Store again. Then, I simulated a release build to check they don't fail when we're close to the release period. However, they didn't work, and I had to fix our dependency list [4]. Also, I fixed single-arch Android test builds [5]. Then, I focused on a disk leak problem. Firefox downloads and opens some formats in the browser without asking for confirmation by default when the server sends them as attachments. There's a preference for force-inlining PDFs (browser.download.open_pdf_attachments_inline), but it doesn't work on other formats. Therefore, I extended that functionality, but I'm not completely satisfied. In our issue [6], I documented all the various problems we still have. However, I will need more time and some help from upstream to provide a better fix. I also went back to one of my passions: fonts. I investigated the differences between having and not having our custom font configuration on Linux [7], and I thought of some strategies for 14.5, as we are too late for 14.0. For now, I created some font aliases to improve compatibility and updated our bundled fonts. In addition to that, I helped with releasing. I rebased our browsers onto Firefox 115.16.0esr and 128.3.0esr. Also, I prepared 13.5.3 and 13.5a10. The latter was an unplanned alpha release from a legacy branch to test the watershed update procedure, which we need to provide alternative updates for legacy platforms (Windows 7/8 and macOS up to 10.14). Finally, I attended the Reproducible Build Summit in Hamburg [8]. I joined the group that focused on writing documentation for repro build beginners. Best, Pier [0] https://gitlab.torproject.org/tpo/applications/tor-browser/-/merge_requests… [1] https://gitlab.torproject.org/tpo/applications/tor-browser/-/issues/42617 [2] https://gitlab.torproject.org/tpo/applications/mullvad-browser/-/issues/328 [3] https://gitlab.torproject.org/tpo/applications/tor-browser/-/merge_requests… [4] https://gitlab.torproject.org/tpo/applications/tor-browser-build/-/issues/4… [5] https://gitlab.torproject.org/tpo/applications/tor-browser-build/-/issues/4… [6] https://gitlab.torproject.org/tpo/applications/tor-browser/-/issues/42220 [7] https://gitlab.torproject.org/tpo/applications/tor-browser/-/issues/41799 [8] https://reproducible-builds.org/events/hamburg2024/

1 0