tor-project

tor-project@lists.torproject.org

16 participants
2324 discussions

Joydeep's Monthly Status Report for June 2022
by Joydeep Sen Gupta 05 Jul '22

05 Jul '22

Hello everyone! This is my monthly report for the month of June. In the last month I have finished all documentation updates to the Tor Browser Manual for the upcoming 11.5 release. The new updates to the documentation include information about the new Bridge-moji feature, HTTPS-only mode in Tor Browser, Connection Assist and changes to the bridge UI. I wrote a post on the forum [0] to recruit more volunteers for testing the Connection Assist feature. We have now moved our cdr.link/zammad instance (Telegram user support channel) [1] and I worked on some migration related tasks [2]. Across our support platforms, we received a number of reports of Tor being slow (due to the ongoing DDoS issue), a good number of requests of unlisted obfs4 bridges from users in regions with active Tor censorship and a few bug reports for Tor Browser for Android. That is all for the highlights from the last month, following are the stats from our user support platforms: ## Frontdesk Timeline : 01 June - 30 June 2022 Tickets: new: 48 open: 13 resolved: 256 Breakdown of number of RT tickets received with respect to operating system: (Note: This includes tickets where the user mentioned the operating system or it was evident from the issue they were running into and/or enclosed screenshots.) Windows - 13 macOS - 3 GNU/Linux - 2 Android - 10 Breakdown of most frequent tickets (at least 3 RT tickets): 1. 109 RT Tickets - How to use Tor Bridges in Russia. [3] 2. 59 RT Tickets - Private Bridge requests. This is not related to the .ru censorship but requests from Tor users in China, Iran, etc. [4] 3. 4 RT Tickets - "Tor is very slow" (ongoing DDoS) [5] 4. 3 RT Tickets - Bug in rendering webpages (on Tor Browser for Android) [6] 5. 3 RT Tickets - "Proxy Server refused connection" (Tor fails to bootstrap) if link from other app are opened in TBA [7] ## Tor Forum Most popular topics in the Support category (in terms of no. of views): 1. "Tor is much slower latterly than it used to be" [5] 2. "Choppy video playback with Tor Browser Flatpak (Tor Browser Launcher)" [8] 3. "Tor Relay low traffic and keep disconnecting randomly" [9] 4. "Download the latest (Tor Browser) version via curl or wget" [10] 5. "Tor Relay disconnects automatically" [11] Thanks, -- Joydeep [0]: https://forum.torproject.net/t/help-us-test-the-new-connection-assist-in-to… [1]: https://gitlab.torproject.org/tpo/community/support/-/issues/40083 [2]: https://gitlab.torproject.org/tpo/community/support/-/issues/40084 [3]: https://forum.torproject.net/t/tor-blocked-in-russia-how-to-circumvent-cens… [4]: https://support.torproject.org/censorship/connecting-from-china/ [5]: https://forum.torproject.net/t/tor-is-much-slower-latterly-than-it-used-to-… [6]: https://gitlab.torproject.org/tpo/applications/fenix/-/issues/40216 [7]: https://gitlab.torproject.org/tpo/applications/tor-browser/-/issues/40536 [8]: https://forum.torproject.net/t/choppy-video-playback-with-tor-browser-flatp… [9]: https://forum.torproject.net/t/tor-relay-low-traffic-and-keep-disconnecting… [10]: https://forum.torproject.net/t/download-the-latest-version-via-curl-or-wget… [11]: https://forum.torproject.net/t/tor-relay-disconnects-automatically/3561

1 0

Nina's Monthly Status Report, June 2022
by nina13＠riseup.net 05 Jul '22

05 Jul '22

Hi, everyone, This is my Status report for June 2022. As usual, my focus in June was on supporting Russian-speaking users of Tor Browser on various channels: Telegram, IRC, and email. 1. User support Overall: 537 tickets were successfully resolved! - Telegram channel (@TorProjectSupportBot): 407 - Email (frontdesk@tpo): 130 The majority of requests were censorship-related - bridges and troubleshooting around them. But there were issues with TB not working on Windows 10 and proxy server bug [1] 2. Migration The migration to the new cdr.link instance happened at the end of June [2]. I tested the new one final instance after it became our main one. So I shared my experience of 5 months of using the cdr.link for tech support [3], which was positive. During the discussion, a few good ideas came up - to use the tag system from the start and to communicate with the users that we deleted all the previous data, so they need to re-share background info with us. So now, this channel is published on the Tor Project website [2] and is open to any user regardless of the language. 3. Hackweek Taking part in Hackweek, I started to gather useful information on the countries with a high risk of censorship events, the work I plan to continue. [1] https://gitlab.torproject.org/tpo/applications/tor-browser/-/issues/40536 [2] https://gitlab.torproject.org/tpo/tpa/team/-/issues/40592 [3] https://gitlab.torproject.org/tpo/community/support/-/issues/40084 [4] https://support.torproject.org/misc/bug-or-feedback/

1 0

Marco's monthly status report, June 2022
by msim 05 Jul '22

05 Jul '22

Hi, here's my monthly status report for June 2022 First, as it was my first month, I had to set up a Windows debug environment for S131 MinGW WebRTC work. For the pluggable transport bundle in tor-browser-build, I finished (hopefully, it's in review now) the relevant merge request [1]. During this, the now legacy Windows expert bundle was removed, which resulted in a small patch to tor-launcher [2], and also a bug was fixed with Go 1.18 building on macOS [3]. Finally, for S131 work, I met with Tom Ritter and got access to Mozilla's Try server to help me sort out MinGW issues faster :) [4] (NB: I think this link requires a valid login to people.mozilla.org, and the relevant commit request ticket [5], is marked as confidential) In July I'm planning on having the compilation issues for WebRTC under MinGW resolved, and begin debugging issues at runtime. Cheers, Marco [1] https://gitlab.torproject.org/tpo/applications/tor-browser-build/-/merge_re… [2] https://gitlab.torproject.org/tpo/applications/tor-browser/-/issues/41039 [3] https://gitlab.torproject.org/tpo/applications/tor-browser-build/-/issues/4… [4] https://people.mozilla.org/p/msimonelli [5] https://bugzilla.mozilla.org/show_bug.cgi?id=1777230

1 0

Tor Browser meeting moving to 2022-07-05
by Richard Pospesel 04 Jul '22

04 Jul '22

Hi Everyone, I believe tomorrow is an official Tor holiday, so we will move the Tor Browser weekly meeting back a day to Tuesday (2022-07-05) at 1100 UTC in #tor-meeting on OFTC IRC. best, -Richard

1 0

Cecylia's Monthly Status Report, June 2022
by Cecylia Bocovich 01 Jul '22

01 Jul '22

Hi everyone, This is my status report for contract work in June 2022. 1. Onboard itchyonion on sponsor 28 deliverables: * Answered questions about the code base for our s28 deliverables 2. Conjure pluggable transport for Tor * Updated the test environment for Conjure to be fully automated [0] * Finished writing a MVP for both the client and bridge side of the Conjure PT [1] * Met and discussed a deployment plan with the Conjure researchers at CU Boulder * Deployed a Conjure bridge for testing purposes [2] * Got the client working with the production Conjure station and deployed bridge [3] I'll be sending an email soon with more information on how to test out Conjure+Tor for yourselves :) Thanks! - Cecylia [0] https://gitlab.torproject.org/cohosh/phantombox [1] https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/conj… [2] https://metrics.torproject.org/rs.html#details/A84C946BF4E14E63A3C92E140532… [3] https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/conj…

1 0

PieroV's Monthly Status Report, June 2022
by Pier Angelo Vendrame 01 Jul '22

01 Jul '22

Hi everyone! Here is my status report for June 2022. At the beginning of the month, I finished reviewing, reordering, and improving our patch set [0], as part of the work for S131. Then, I merged other changes I had worked on during the past months: the offline manual is now a thing, and we also merged the new mechanism to deal with the .securedrop.tor.onion domains. With it, we could remove HTTPS Everywhere from the desktop version of TBB. All these changes are available in Tor Browser 11.5a13. Some other minor changes I have been working on will be available in the next release (possibly, the first stable of Tor Browser 11.5). The latest issues I have been working on are about fonts. We want to improve script support in Tor Browser [1], at least on Windows and Linux. macOS will have to wait because we found an issue with bundled fonts [2], which turned out to be an upstream problem [3], for which I proposed a patch to Mozilla. Please, let us know if the pages in your language are not rendered or rendered incorrectly in Tor Browser. Finally, the last week has been hackweek at the Tor Project. I joined the project to improve support for pluggable transport in Tails. Thanks, Pier [0] https://gitlab.torproject.org/tpo/applications/tor-browser/-/commits/tor-br… [1] https://gitlab.torproject.org/tpo/applications/tor-browser/-/issues/30589 [2] https://gitlab.torproject.org/tpo/applications/tor-browser/-/issues/41004 [3] https://bugzilla.mozilla.org/show_bug.cgi?id=1774413

1 0

Tor's Hackweek Demo Session on July 1st at 1600 UTC
by Gaba 30 Jun '22

30 Jun '22

Hi! Tomorrow at 1600 UTC we will have the presentation of what different teams worked on during this hackweek. It will be in the same BBB room https://tor.meet.coop/gab-dpb-9zt-7tq Friday July 1st at 1600 UTC ROOM: https://tor.meet.coop/gab-dpb-9zt-7tq see you there! gaba -- pronouns she/her/they GPG Fingerprint EE3F DF5C AD91 643C 21BE 8370 180D B06C 59CA BD19

1 0

TPA-RFC-35: GitLab email address changes
by Antoine Beaupré 29 Jun '22

29 Jun '22

Summary: headers in GitLab email notifications are changing, you may need to update your email filters # Background I am working on building a development server for GitLab, where we can go wild testing things without breaking the production environment. For email to work there, I need a configuration that is separate from the current production server. Unfortunately, the email address used by the production GitLab server doesn't include the hostname of the server (`gitlab.torproject.org`) and only the main domain name (`torproject.org`) which makes it needlessly difficult to add new configurations. Finally, using the full service name (`gitlab.torproject.org`) address means that the GitLab server will be able to keep operating email services even if the main email service goes down. # Proposal This changes the headers: From: gitlab(a)torproject.org Reply-To: gitlab-incoming+%{key}(a)torproject.org to: From: git(a)gitlab.torproject.org Reply-To: git+%{key}(a)gitlab.torproject.org If you are using the `From` headers in your email client filters, for example to send all GitLab email into a separate mailbox, you WILL need to make a change for that filter to work again. I know I had to make such a change, which was simply to replace `gitlab(a)torproject.org` by `git(a)gitlab.torproject.org` in my filter. The `Reply-To` change should not have a real impact. I suspected emails sent before the change might not deliver properly, but I tested this, and both the old emails and the new ones work correctly, so that change should be transparent to everyone. (The reason for that is that the previous `gitlab-incoming(a)torproject.org` address is *still* forwarding to `git(a)torproject.org` so that will work for the foreseeable future.) # Alternatives considered ## Reusing the prod email address The main reason I implemented this change is that I want to have a GitLab development server, as mentioned in the background. But more specifically, we don't want the prod and dev servers to share email addresses, because then people could easily get confused as to where a notification is coming from. Even worse, a notification from the dev server could yield a reply that would end up in the prod server. ## Adding a new top-level address So, clearly, we need two different email addresses. But why change the *current* email address instead of just adding a new one? That's trickier. One reason is that I didn't want to add a new alias on the top-level `torproject.org` domain. Furthermore, the old configuration (using `torproject.org`) is officially [discouraged upstream][] as it can lead to some security issues. [discouraged upstream]: https://docs.gitlab.com/ee/administration/incoming_email.html#security-conc… # Costs N/A, staff. # Approval This needs approval from TPA and tor-internal. # Deadline This will be considered approved tomorrow (2022-06-30) at 16:00 UTC unless there are any objections, in which case it will be rolled back for further discussion. The reason there is such a tight deadline is that I want to get the development server up and running for the Hackweek. It is proving less and less likely that the server will actually be *usable* *during* the Hackweek, but if we can get the server up as a result of the Hackweek, it will already be a good start. # Status This proposal is currently in the `proposed` state. # References Comments welcome by email or in issue [tpo/tpa/team#40820][]. [tpo/tpa/team#40820]: https://gitlab.torproject.org/tpo/tpa/team/-/issues/40820 -- Antoine Beaupré torproject.org system administration

1 0

What's happening in Shadow 2022-06
by Jim Newsome 28 Jun '22

28 Jun '22

Mirrored from https://github.com/shadow/shadow/discussions/2243 This is part of a series of periodic updates of development in Shadow. This work is sponsored by the NSF. NSF sponsorship: https://shadow.github.io/docs/guide/nsf_sponsorship.html Previous update: https://github.com/shadow/shadow/discussions/2007 We will be presenting a paper on Shadow's 2.0 architecture, "Co-opting Linux Processes for High-Performance Network Simulation", at the USENIX Annual Technical Conference. Paper: https://www.robgjansen.com/publications/phantom-atc2022.pdf USENIX ATC: https://www.usenix.org/conference/atc22 We've merged 123 non-dependabot pull requests and closed 38 issues since our previous update. Pull requests: https://github.com/shadow/shadow/pulls?q=is%3Apr+merged%3A2022-04-05..2022-… Issues: https://github.com/shadow/shadow/issues?q=closed%3A2022-04-05..2022-06-27+i… Release status ============== We have released Shadow 2.1. This release focused largely on more complete and accurate OS emulation, to increase the number of applications that can be run under Shadow. Shadow now supports newer versions of glibc, software that uses signals and "busy loops", and dynamically linked golang programs. It also has a new `--debug-hosts` feature to facilitate attaching debuggers like `gdb` to Shadow's managed processes. See the release notes for details. Shadow 2.1: https://github.com/shadow/shadow/releases/tag/v2.1.0 Release notes: https://github.com/shadow/shadow/discussions/2219 We've begun work on Shadow 2.2, which will largely be a push to refactor and migrate more of the core Shadow code to Rust, which is expected to ultimately increase velocity of Shadow development. Shadow 2.2 project: https://github.com/shadow/shadow/projects/6 Notable changes since last update ============================= Most of the changes since the last update are covered in the v2.1.0 release notes. We are now also keeping a running CHANGELOG of user-facing changes since the last release. Currently this is: * We have removed ptrace-mode, and the associated experimental options `use-o-n-waitpid-workaround` and `--interpose-method`. ptrace-mode was an alternative to Shadow's current interposition mechanism that uses `LD_PRELOAD` and `seccomp`. This change should be transparent to most users, since it hasn't been the default for several releases, and was only accessible via experimental options. See https://github.com/shadow/shadow/issues/1945 Release notes: https://github.com/shadow/shadow/discussions/2219 Changelog: https://github.com/shadow/shadow/blob/main/CHANGELOG Happy simulating! The Shadow team

1 0

Another late hackweek entry: docs hackathon!
by kez 27 Jun '22

27 Jun '22

Hi all! I also have a super last-minute hackweek proposal: a docs hackathon! There's two parts to this proposal: 1) Updating our web- and wiki-based documentation where it needs to be updated, adding to it where it's incomplete, and opening tickets for changes that should be made at some point (but that we maybe don't have time/energy for right now) 2) Finding a replacement for gitlab wikis. Gitlab wikis only allow contributions from repository developers (<https://gitlab.torproject.org/tpo/tpa/gitlab/-/issues/76>), and the restrictions of the wiki are starting to become a quality-of-life issue for some teams. Ideally we'll find a replacement that fixes our issues without introducing new ones :p Basic familiarity with gitlab and wiki software (as an admin or user) is useful. Being able to update lektor pages is also helpful, though not required! If you're interested in helping out, feel free to add yourself to the pad and stop by #hackweek-docshackathon-2022 on OFTC! Kez

1 0

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

tor-project