- tor-project - lists.torproject.org

Proxy Leak Detector/Preventor (Outreachy)
by Robert Mindo 17 Jan '23

17 Jan '23

Greetings! I wanted to share an update on the progress of the project. So far, the ability to detect the IP address and port that socket system calls are sending data to has been successfully implemented. Additionally, the capability to block system calls that are sending data to an IP address and port that is not the desired proxy. An option to kill the application if a proxy leak occurs has been added, which is useful for manual QA testing of applications. Furthermore, an option to allow … [View More]

1 0

Next Tor Browser Meeting Moved to 2023-01-17
by Richard Pospesel 13 Jan '23

13 Jan '23

Hi Everyone, The 16th is a US Federal Holiday and therefore an official Tor Project holiday as well. We will therefore move the weekly applications dev meeting to Tuesday the 17th at 1500 UTC in #tor-meeting on OFTC IRC. best, -Richard

1 0

Anti-censorship team meeting notes, 2023-01-12
by Shelikhoo 12 Jan '23

12 Jan '23

Hey everyone! Here are our meeting logs: http://meetbot.debian.net/tor-meeting/2023/tor-meeting.2023-01-12-15.58.html And our meeting pad: Anti-censorship work meeting pad -------------------------------- ------------------------------------------------------------------------------------ &… [View More]

1 0

OONI Monthly Report: December 2022
by Maria Xynou 11 Jan '23

11 Jan '23

Hello, Below I share OONI's status report for December 2022. *# OONI Monthly Report: December 2022* Throughout December 2022, the OONI team worked on the following sprints: * Sprint 79 (1st-4th December 2022) * Sprint 80 (5th-18th December 2022) * Sprint 81 (19th-31st December 2022) Our work can be tracked through the various OONI GitHub repositories: https://github.com/ooni Highlights are shared in this report below. *## Year in Review: OONI in 2022* We published our annual blog post, "… [View More]

1 0

OONI Monthly Report: November 2022
by Maria Xynou 11 Jan '23

11 Jan '23

Hello, Below I share OONI's status report for November 2022. *# OONI Monthly Report: November 2022* Throughout November 2022, the OONI team worked on the following sprints: * Sprint 77 (1st-6th November 2022) * Sprint 78 (7th-20th November 2022) * Sprint 79 (21st-30th November 2022) Our work can be tracked through the various OONI GitHub repositories: https://github.com/ooni Highlights are shared in this report below. *## Technical multi-stakeholder research report on Internet shutdowns … [View More]

1 0

OONI Monthly Report: October 2022
by Maria Xynou 11 Jan '23

11 Jan '23

Hello, Happy New Year! We'd like to share updates from the OONI team over the last 3 months. Below I share our October 2022 report, and I'll follow-up to share our November and December 2022 reports. *# OONI Monthly Report: October 2022* Throughout October 2022, the OONI team worked on the following sprints: * Sprint 75 (1st-9th October 2022) * Sprint 76 (10th-23rd October 2022) * Sprint 77 (24th-31st October 2022) Our work can be tracked through the various OONI GitHub repositories: … [View More]

1 0

Joydeep's Monthly Status Report for December 2022
by Joydeep Sen Gupta 07 Jan '23

07 Jan '23

Hello everyone! :) Here are my updates from December. I resolved 1120 tickets via email and 203 tickets on our telegram/signal user support channel. With Tor Browser 12 release, I, along with @nina13, finished reviewing and updating[1] all of our internal support documentation, including all articles and templates we have on our Request Tracker and cdr.link support channels. I was also involved with some testing before the release. Post-release we got a few reports about false positives with … [View More]

1 0

Marcos monthly status report, December 2022
by msim 07 Jan '23

07 Jan '23

Hi all :) Here's my monthly status report for December 2022 This month was effectively purely focused on Windows WebRTC things. Since Mozilla doesn't support building with mingw on a windows host, this turned out to be a very deep rabbit hole of many different possible approaches. At the beginning of the month, I did some work on my build merge request [1], but then I decided to focus on getting windows builds working, since that was my goal for this month, and also no major releases were … [View More]happening that would've included the WebRTC build MR. I first tried testing out of a linux host using wine, but that very quickly fell apart, and I have little experience with wine so I decided to not pursue that any further. The first part of getting Windows host builds working was setting up a development environment. I first tried building on a linux host, copying the artefacts to a windows machine, and trying to test from there, but this didn't work, for reasons which I cant remember. However since then, I've done a lot of dev environment set up, so this may potentially be a viable approach again. The next approach I tried was building in WSL, and testing straight out of a WSL shell. I decided to do this as I was most familiar with linux environments, and WSL allows windows executables to run, which wouldn't run under wine when I tested from linux. This again failed, but this time it was because certutil.exe would fail first due to missing dlls, which was fixed very quickly, but then with `CKR_GENERAL_ERROR`, which is incredibly vague. After trying to investigate this, I deemed this approach non viable, as there were hundreds of potential code paths that could trigger this error. WSL failing, I tried to build the recommended way from firefox (except using MinGW instead of MSVC), which as I suspected before, failed again. Numerous weird issues were encountered here, such as the build system not being able to find simple tools that would normally be found when I would build with MSVC, but didn't belong to MSVC or MinGW (such as rm, tar, awk, etc) That being said, while this approach currently is far behind the WSL approach (WSL can build it, but fails to test. This approach doesn't build, yet), I'm hoping it will work out better since there won't be any cross platform weirdness that might be breaking anything. Currently this approach is failing due to various weird errors that seem to be from mach assuming I'm building from a unix like host, and not windows, but as far as I can tell these assumptions should be OK since the build happens in an MSys2 environment. The near future is focussed on getting windows builds happening, which I was hoping to have finished by the end of December but couldn't due to numerous unexpected issues. The plan for next steps as discussed with Richard is to try and get a build running with MSVC and then swap out the toolchain, and if that fails, I'll try the first approach again, but using artefacts out of tor browser build. Best, Marco [1]: https://gitlab.torproject.org/tpo/applications/tor-browser/-/merge_requests… [View Less]

1 0

Nina's Monthly status report for December'22
by Nina 05 Jan '23

05 Jan '23

Hi! This is my status report for December 2022. This month, I successfully resolved 799 tickets. On Telegram (@TorProjectSupportBot) - 544 On RT (frontdesk@tpo) - 235 In December 2022, most of the requests (more than 300) came from Russia; however, there is a growing number of tickets from Turkmenistan (around 50) where Tor Browser and Orbot are the popular ways of censorship circumvention. And I also helped users from Iran and China. My focus was as usual on censorship circumvention; … [View More]

1 0

HackerNCoder's Monthly Status Report, December 2022
by HackerNCoder 05 Jan '23

05 Jan '23

Hello! Here is what I have been working on for December 2022. Pretty much all of my time has been spent working on ooni-exporter[1], which takes data from ooni and exports it for prometheus. With some time spent looking into making an arti-based program for testing obfs4 reachability. [1] https://gitlab.torproject.org/hackerncoder/ooni-exporter -- HackerNCoder https://www.encryptionin.space Translating queer games at https://queerscriptors.org

1 0