Hi all :)
This is my monthly status report for October 2024 with the main relevant
activities I have done, was involved or are related to my work during the
period.
# Onionprobe Ansible Role
A considerable time was spent finding ways to structure and test Ansible
roles, collections and playbooks through GitLab CI. Goal is to provide
easier-to use procedures to manage Onion Services infrastructure.
As a direct result of this research, it was possible to finally refactor and
release an Ansible role to manage Onionprobe, a monitoring tool for onionsites:
https://gitlab.torproject.org/tpo/onion-services/ansible/onionprobe-role
It was interesting to research how to do basic Ansible tests using GitLab CI,
and a special thanks goes to TPA for providing the base Podman image which
allows running Podman in a GitLab CI job:
https://gitlab.torproject.org/tpo/tpa/base-images
# Onionprobe
Onionprobe itself got some improvements, including support for running the
standalone monitor node with Podman:
https://onionservices.torproject.org/apps/web/onionprobe/standalone/
# OnionSec
The OnionSec library and command line for testing onionsites got some
enhancements as well: https://github.com/TheEnbyperor/onion-sec/pull/1
# Libraries
The Onion Services Ecosystem got a Libraries page:
https://onionservices.torproject.org/dev/libraries/
It still needs some improvements, and also some input from the upstream
devs to check accuracy:
https://gitlab.torproject.org/tpo/onion-services/ecosystem/-/issues/21
# Support
Finally, also did the usual and ongoing sponsored work with deployment,
maintenance and monitoring of Onion Services.
--
Silvio Rhatto
pronouns he/him
Hi! Below is my October’24 report!
In October, I resolved1104(↑110) tickets:
* On Telegram (@TorProjectSupportBot) - 855 (↑127);
* On RT (frontdesk@tpo) - 248 (↑59);
* On WhatsApp (+447421000612) - 1(↓26);
* and on Signal (+17787431312) - 0 (0).
My main focus - as usual - was to help Russian-speaking users bypass
censorship and connect to Tor, which often includes troubleshooting. I
also collected users’ feedback to monitor the censor's activity and to
help find working anti-censorship solutions.
Apart from user support I also took part in Tor Forum moderation, worked
with app store reviews, and joined the Tor relay operators meetup.
Most of the tickets were from users in Russia requesting bridges, as the
ones they received from rdsys distributors weren't working for them. I
also collected user feedback on other plugglable transports (WebTunnel,
obfs4, and Snowflake) and added it to the main ticket about censorship
in Russia[1].
*## New Tor Browser release*
Tor Browser 14 was released in October [2], with the LegacyOS
users-Windows 7-8 and macOS 10.12-10.14-staying with 13.5.9. So, I took
part in preparing the instructions for the Legacy OS users to help them
understand the transition period and make sure that censored users can
also get access to the Tor Browser version that would work for them [3].
In collaboration with @ebanam, I reported a bug affecting macOS users
who are trying to open certain .onion websites [4].
I continued taking part in the investigation of the Samsung "proxy
server refused connection" bug [5].
*## **Google Play Reviews for Tor Browser**(TBA)**and Tor Browser
Alpha**for Android*
Tor Browser App had a Google Play rating of 4.394-4.396 (↑) stars in
October 2024, which is higher than in September.
Tor Browser app(TBA)got 691 (↑23)reviews out of 58,498for the lifetime.
Most commonissuesonthe reviews:
* Samsung users point out the error "Proxy server refused
connection"on their devices; [4]
* Tor Browser doesn't work: mostly from Russian users, who are
struggling to find a non-blockedbridge;
* Tor speed is too slow.
Tor Browser Alpha (TBA) app had a rating of 4.254 (↓) which is lower
that in September.
In October, Tor Browserfor Android (TBA)Alpha got 40 (↑5)reviews out of
8359for the lifetime.
[1]
https://gitlab.torproject.org/tpo/anti-censorship/censorship-analysis/-/iss…
[2] https://blog.torproject.org/new-release-tor-browser-140/
[3] https://gitlab.torproject.org/tpo/community/support/-/issues/40163
[4]
https://gitlab.torproject.org/tpo/applications/tor-browser/-/issues/43245
[5]
https://gitlab.torproject.org/tpo/applications/tor-browser/-/issues/42714
Hi everyone!
Here is my status report for October 2024.
Ten days ago, we finally released Tor Browser 14.0 after several months
of work on it 🎉 [0].
Therefore, in the first weeks of October, I mostly fixed minor
bugs/details and tried to help my colleagues resolve other problems for
the big release.
I also spent a considerable amount of time doing QA. While doing it, I
created new resources to make the QA process faster.
I added all of them to the tests for self-signed HTTPS Onion Sites I
created a while ago [1].
I also restarted my upstream effort. I think the upstreaming of Bug
1556002 [2] and Bug 1923264 [3] were the fastest I have ever had 😄.
I also tried to start a conversation about ignoring
`content-disposition: attachment` in some cases [4], but that will need
more work downstream first.
After the release, I returned to working on issues we didn't want to
rush for the stable, such as moving FontConfig's fonts.conf [5].
While doing so, I also found a compatibility problem between the modern
Python version we self-compile to be able to build Firefox and the
legacy OpenSSL version we still have in our old build environment [6].
I fixed it by downgrading Python to 3.9.20, which is still officially
supported by the PSF and the various build systems we use. That was the
less-impacting solution, but not the only possible one. Also, we really
needed to fix it quickly, as it would have prevented us from building
14.0.1.
Currently, I am working on fixing the "Proxy server refuses connection"
problem that some Android devices (mostly Samsung phones) show [7].
I think a workaround would be to return to TCP sockets for the SOCKS
connections. I prefer Unix domain sockets, as they can be used only by
the browser with our configuration, whereas TCP sockets will be
available to other apps as well, which is a linkability concern.
If you have an Android device with this behavior and think you can help
debug it, please consider commenting on that GitLab issue [7].
With this effort, we will also get closer to solving an 11-year-old
issue, a new record for me 😄 [8].
Finally, I did the usual maintenance work. I rebased our browsers (the
128-based stable and the 115-based legacy channel) and started the new
branches for the 14.5 series.
I also prepared the 14.0.1 Tor Browser stable release and built it.
Best,
Pier
[0] https://blog.torproject.org/new-release-tor-browser-140/
[1] https://onion-tests.pierov.org/
[2] https://bugzilla.mozilla.org/show_bug.cgi?id=1556002
[3] https://bugzilla.mozilla.org/show_bug.cgi?id=1923264
[4] https://bugzilla.mozilla.org/show_bug.cgi?id=1923368
[5]
https://gitlab.torproject.org/tpo/applications/tor-browser/-/issues/43140
[6]
https://gitlab.torproject.org/tpo/applications/tor-browser-build/-/issues/4…
[7]
https://gitlab.torproject.org/tpo/applications/tor-browser/-/issues/42714
[8]
https://gitlab.torproject.org/tpo/applications/tor-launcher/-/issues/10439