- tor-project - lists.torproject.org

cve's monthly status report
by Clara Engler 04 Dec '24

04 Dec '24

Hello, the following contains my status report for November '24: * Wrote a tiny tool to block Tor with simple firewall rules to simulate a loss of connectivity.[^1] * Discovered a bug in arti while doing this.[^2] * Improved the recognition of being bootstrapped.[^3] * Researched upon loss of connectivity.[^4] * Upgraded various outdated crates in onionmasq by merging overdue MR's from Renovate-Bot * Upgraded `thiserror` to version 2 in arti and onionmasq, fixing a breaking change.[^5] * Allowing packets to be received when the source address is the loopback one.[^6] * This was a particularly difficult issue to tackle that is crucial for testing. * Fixed a general lack of IPv6 connectivity in onionmasq.[^7] * Implemented an HTTP integration test.[^8] * Fixed `wait_for_bootstrap` issue in chutney.[^9] * Fixed a bug in onionmasq for routing UDP datagrams to a loopback address.[^10] * Made the integration test suite ready for UDP.[^11] * Implemented a UDP integration test, thereby greatly bumping the overall coverage.[^11] * Improved documentation of the integration test suite.[^11] * Various reviews of merge requests in arti and onionmasq. * Various feature suggestions in onionmasq through the use of issues. * Legal and bureaucratic matters. [^1]: https://gitlab.torproject.org/cve/torblock [^2]: https://gitlab.torproject.org/tpo/core/arti/-/issues/1731 [^3]: https://gitlab.torproject.org/tpo/core/onionmasq/-/merge_requests/312 [^4]: https://gitlab.torproject.org/tpo/core/onionmasq/-/issues/110 [^5]: https://gitlab.torproject.org/tpo/core/arti/-/merge_requests/2626 [^6]: https://gitlab.torproject.org/tpo/core/onionmasq/-/issues/120 [^7]: https://gitlab.torproject.org/tpo/core/onionmasq/-/issues/122 [^8]: https://gitlab.torproject.org/tpo/core/onionmasq/-/merge_requests/322 [^9]: https://gitlab.torproject.org/tpo/core/chutney/-/merge_requests/39 [^10]: https://gitlab.torproject.org/tpo/core/onionmasq/-/issues/128 [^11]: https://gitlab.torproject.org/tpo/core/onionmasq/-/merge_requests/332

2 1

Tor User Support team will be partly unavailable during the holidays between December 19 2024 to January 5 2025
by ebanam 03 Dec '24

03 Dec '24

Hello, Tor User Support team will be partly unavailable between December 19th, 2024 and January 5th, 2025. If you reach out to us on our user support channels via email[0], Tor Forum[1], Telegram[2], WhatsApp[3] or Signal[4], it may take longer than usual for us to respond. Please rest assured we will get back to your messages as soon as possible. Our team will be back at our regular office hours[5] from January 6th, 2025. Thank you! Community Team Tor Project [0]: frontdesk(a)torproject.org [1]: https://forum.torproject.org [2]: https://t.me/TorProjectSupportBot [3]: https://wa.me/447421000612 [4]: https://signal.me/#p/+17787431312 [5]: https://tb-manual.torproject.org/support/

1 0

cohosh's monthly status report, November 2024
by Cecylia Bocovich 03 Dec '24

03 Dec '24

Hi! This is my status report for contract work done in November 2024. # Snowflake Snowflake was blocked in Russia in early November. The blocking has since stopped (at least temporarily). I did some analysis using the automatically generated pcaps from our vantage point, and write a few patches to more easily test whether specific proxies or versions of Snowflake can evade the blocking. We'll continue to monitor reachability in case the blocking returns. https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snow… My main ongoing task on Snowflake is to look at how we can use Snowflake broker metrics to more accurately detect and respond to censorship events. https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snow… https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snow… I released version 0.9.2 of the webextension and version 2.10.1 of snowflake this month. We had a major upgrade of the Snowflake broker at the end of November. This required a few followup tasks and debugging. I worked on getting metrics back up and running. https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snow… And lastly, a few small logging fixups for Snowflake proxies https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snow… https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snow… # PT library work After October, there were a few outstanding tasks and issues with the IPtProxy rewrite. This has now been merged and released as version 4.0.0! https://github.com/tladesignz/IPtProxy/tree/4.0.0 https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/lyre… # Domain fronting A few of the remaining Fastly front domains renewed their certificates recently, so we had to update all of our settings to use non-Fastly configurations. https://gitlab.torproject.org/tpo/anti-censorship/team/-/issues/151 https://github.com/guardianproject/orbot/pull/1197 I made some more progress on the meek bridge handover, and updated the bridge to use the new meek.torproject.net and meektm.torproject.net domains. https://gitlab.torproject.org/tpo/anti-censorship/team/-/issues/133 # Lox I worked on a few code quality changes last month, including simplifying some Lox tests so they run more easily on laptops. https://gitlab.torproject.org/tpo/anti-censorship/lox/-/merge_requests/281 https://gitlab.torproject.org/tpo/anti-censorship/lox/-/merge_requests/277 # Miscellaneous All the usual merge request reviews and general project maintenance tasks :) I helped with some grant writing and planning early this month. I also helped debug a tor bootstrapping issue with PTs https://gitlab.torproject.org/tpo/core/tor/-/issues/40990

1 0

Nina’s Monthly Status Report, November, 2024
by Nina 03 Dec '24

03 Dec '24

Hi! Below is my November’24 report! In November, I resolved 1569 (↑465) tickets: * On Telegram (@TorProjectSupportBot) - 1351 (↑496); * On RT (frontdesk@tpo) - 215 (↓33); * On WhatsApp (+447421000612) - 3 (↑2); * and on Signal (+17787431312) - 0 (0). Since August 2024, I've noticed a significant increase in Russian-speaking user requests on our support channels: * July: 587 tickets * August: 928 tickets * September: 994 tickets * October: 1104 tickets * November: 1569 tickets (this report) My main focus in November was to help Russian-speaking users bypass censorship and help users to resolve any issues they are facing with Tor Browser. I also took part in Tor Forum moderation and worked reviewingGoogle PlayStore users reviews. In November,we had much more tickets from Russian-speaking users than usual (+42% comparing with October). It happened due to internet censorship in Russia is getting more severe, and some pluggable transports are being blocked or partially blocked[1]. So in November,we launched a WebTunnelcampaign and asked the Tor community to help users in Russia by running more bridges [2], which is a pluggable transport reported to work well in Russia. Last monthwe got multiple requests from Apple devices users from Russia regarding what app to use on iOS or how to downloadTor Browser - macOS does not allow to install apps downloaded from Telegram [3], so users need to use website mirror. The process of upgrading CDR.link has started in November[4],which included upgrade to a newer Zammad version, testing, bug reporting and consultation with the contractor. *##**Google Play Reviews for Tor Browser**(TBA)**and Tor Browser Alpha**for Android* Tor Browser for Androidhad a Google Play rating of 4.89 (↓) stars in November 2024, which is lower than in October. Tor Browser for Android (TBA) got 672 (↓19) reviews out of 59,115 for the lifetime. Tor Browser for Android Alpha (TBA-Alpha) app had a rating of 4.241 (↓) which is lower than in October. In November, Tor Browser for Android (TBA-Alpha) got 38 (↓2) reviews out of 8,396 for the lifetime. Most common issues on the Google Play store reviews: * Tor Browser doesn’t work: mostly from Russian users, who are struggling to find a bridge that is not blocked; * Tor speed is too slow:This issue is currently under investigation, I'lloffer users some ways to improve the speed and gather their feedback. [1] https://gitlab.torproject.org/tpo/anti-censorship/censorship-analysis/-/iss… [2] https://blog.torproject.org/call-for-webtunnel-bridges/ [3] https://gitlab.torproject.org/tpo/applications/tor-browser-build/-/issues/4… [4] https://gitlab.torproject.org/tpo/community/support/-/issues/40165

1 0

intrigeri's report, November 2024
by intrigeri 03 Dec '24

03 Dec '24

Hi, I took 1.5 week off for personal reasons mid-November. The work time & energy I had left was barely enough to do most of the usual day-to-day work that's not worth reporting about, hence this slim report. User-visible ============ I prepared a short talk for the State of the Onion, then recorded it in highly challenging circumstances. I'm happy with the script, I think the slides are good ~enough, and the actual delivery has lots of margin for improvement. User-invisible ============== I did the usual amount of KTLO work; nothing worth highlighting this month. Team lead ========= I've been working, together with a number of other Tor folks from my team and other teams, on a large grant proposal. This was the opportunity for me to discover the workflows and tooling used by Tor in this area, and gain some familiarity with it. Accounting ========== We've been making some more progress on transitioning away from the former Tails fiscal sponsorship arrangements into Tails' new nest, the Tor project. Cheers, -- intrigeri

1 0

Rhatto's Monthly Status Report, November 2024
by rhatto 02 Dec '24

02 Dec '24

Hi all :) This is my monthly status report for November 2024 with the main relevant activities I have done, was involved or are related to my work during the period. ## SOTO 2024 * Did a presentation at Tor's State of the Onion 2024. Video available at https://www.youtube.com/watch?v=HjPdReNmf_g&t=596s ## Internet Archive * Support given for the Archive's new onionsite! It was released on SOTO: https://www.youtube.com/watch?v=EODNtLqD7f8&t=3196s ## Onionspray * Released Onionspray 1.6.2 (application to serve regular websites as onionsites): https://forum.torproject.org/t/onionspray-release-1-6-2/16014 ## Onionprobe * Released Onionprobe 1.2.1 (Onion Services monitoring application): https://forum.torproject.org/t/onionprobe-release-1-2-1/16015 * The Onionprobe role is not available at the Ansible Galaxy: https://galaxy.ansible.com/ui/standalone/roles/torproject/onionprobe/ ## Support Did the usual and ongoing sponsored work with deployment, maintenance and monitoring of Onion Services. -- Silvio Rhatto pronouns he/him

1 0

minutes from the sysadmin meeting
by Antoine Beaupré 02 Dec '24

02 Dec '24

# Roll call: who's there and emergencies anarcat, groente, lavamind, lelutin, zen # Dashboard review We did our normal weekly checkin. # Last minute December coordination We're going to prioritize the converging the email stuff, ganeti and puppet upgrades, and security policy, although that might get delayed to 2025. # Holidays planning Confirmed shifts discussed in the 1:1s. # 2025 roadmap validation No major change, pauli upgraded before 2025, and anarcat will unsubscribe from Tails nagios notifications. # Metrics of the month * hosts in Puppet: 90, LDAP: 90, Prometheus exporters: 505 * number of Apache servers monitored: 33, hits per second: 669 * number of self-hosted nameservers: 6, mail servers: 11 * pending upgrades: 20, reboots: 0 * average load: 1.02, memory available: 3.73 TiB/4.99 TiB, running processes: 380 * disk free/total: 65.44 TiB/139.91 TiB * bytes sent: 395.69 MB/s, received: 248.31 MB/s * planned bookworm upgrades completion date: 2024-10-23 * [GitLab tickets][]: 257 tickets including... * open: 0 * icebox: 157 * future: 39 * needs information: 10 * backlog: 21 * next: 12 * doing: 11 * needs review: 8 * (closed: 3804) [Gitlab tickets]: https://gitlab.torproject.org/tpo/tpa/team/-/boards Obviously, the completion date is incorrect here, as it's in the past. As mentioned above, we're hoping to complete the bookworm upgrade before 2025. Upgrade prediction graph lives at: https://gitlab.torproject.org/tpo/tpa/team/-/wikis/howto/upgrades/bookworm/ Note that the all-time graph was updated to be more readable, see the gorgeous result in: https://gitlab.torproject.org/tpo/tpa/team/-/wikis/howto/upgrades/#all-time… -- Antoine Beaupré torproject.org system administration

1 0

Felicia's Montly Status Report, November 2024
by Priscila 02 Dec '24

02 Dec '24

Hi everyone, My status report for November 2024 is entirely focused on this Moat issue: https://gitlab.torproject.org/tpo/applications/tor-browser/-/issues/42605 Although I knew this task would be quite complex before starting, it proved to be more complex than I thought, as you can see from the numerous UI versions I made before realizing I’d need to step back to study things better: https://www.figma.com/design/4XiUaZPch3ejewlZO56lkR/Tor-Browser-14.5?node-i… Since Moat can be difficult to understand for non-tech people, comprehending how it works was the first step. For this, I used a CSD matrix based on information gathered in a meeting with the devs. Later on, it was necessary to understand the user flows where Moat calls are made so we know when we need to ask for the user’s consent. So with all that, I needed to answer some questions (e.g. what are we trying to tell users and why?) so I can summarize everything in a way to educate users on Moat calls and allow them to make an informed decision whether they consent to it or not - I’m actually in this point of the task. Besides that, I also worked on very small tasks of support to devs. Best, Priscila (aka Felicia) - UX Team

1 0

PieroV's Monthly Status Report, November 2024
by Pier Angelo Vendrame 02 Dec '24

02 Dec '24

Hi everyone! Here is my status report for November 2024. November was a short month for us, as we took a team break to rest a bit after the big 14.0 release and because of the holidays. For most of the month, I investigated how to remove Lox's WASM blob and instead integrate the Lox Rust crate in the browser build system [0]. Also, I checked the various options for exposing this integration crate to JavaScript, as the front end will remain in that language. This work will hopefully help us also when switching to Arti in the browser. We've also discussed the future changes for the Tor daemon integration in the browser, and I had to review a major refactor made by Henry [1], which took me some time. Apart from that, I rebased our 128-based channels (14.0 and 14.5), fixed the release preparation script to take the needs of the legacy channel into account [2], and made other similar fixes [3]. Also, I signed a release (13.5.10) for the first time. We decided to allow more people to sign to be more responsive under some circumstances and to spread the load on the team. Then, towards the end of the month, I resumed the work on anti-fingerprinting. I evaluated Thorin's proposal to abandon `font.system.whitelist` in favor of font visibility, which would bring us closer to Firefox [4]. While doing so, I found a problem with the changes I made to the FontConfig configuration file the previous month [5]. Finally, I proposed a fix for a conflict between the OpenSSL 3.0.x we ship with the tor daemon, and OpenSSL 3.2.x, required by a transitive dependency, which prevented the browser from starting in some systems [6]. If you have the same problem, deleting our libcrypto (form `TorBrowser/Tor`) should work, but we'll provide a proper fix in our next update. Best, Pier [0] https://gitlab.torproject.org/tpo/applications/tor-browser/-/issues/43096 [1] https://gitlab.torproject.org/tpo/applications/tor-browser/-/merge_requests… [2] https://gitlab.torproject.org/tpo/applications/tor-browser-build/-/issues/4… [3] https://gitlab.torproject.org/tpo/applications/tor-browser-build/-/merge_re… [4] https://gitlab.torproject.org/tpo/applications/tor-browser/-/issues/43322 [5] https://gitlab.torproject.org/tpo/applications/tor-browser/-/issues/43330 [6] https://gitlab.torproject.org/tpo/applications/tor-browser/-/issues/43326

1 0

Moving gitlab to our Dallas cluster on Thursday 2024-11-28
by Gabriel Filion 29 Nov '24

29 Nov '24

Hello, Additionally to the mail server switch on Monday, we're planning to move/migrate the gitlab server from our Falkenstein-based cluster to the one in Dallas. This move will be happening on Thursday november 28th starting at 18:00 UTC. The disks for the gitlab server are fairly sizeable so the transfer could be taking a long time. Our current estimates are that it could take about 18 hours to transfer. We will try launching an operation to zero out empty parts of the disk volumes before starting the transfer in the hopes that it could give the transfer a boost. So the transfer will most likely take gitlab offline until the next day, friday 29th, at which time we'll make sure that the service is coming back online properly. If there's any issue during the outage, please reach out to us via IRC or email, but not through gitlab issues since this last one will obviously be offline at that time. For status updates, see: https://status.torproject.org/issues/2024-11-28-gitlab-migration/ Cheers!

1 1