- tor-project - lists.torproject.org

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

Tor Browser Weekly Meeting cancelled this week (2022-06-27)
by Richard Pospesel 26 Jun '22

26 Jun '22

Hi Everyone, This week is HackWeek, so we will be skipping our weekly Tor Browser meeting and meet again July 5th at 1100 UTC in #tor-meeting on OFTC IRC. best, -Richard

1 0

Tor's Hackweek starting June 27th at 1600 UTC
by gaba 26 Jun '22

26 Jun '22

Hola people! This week we are holding Tor's hack week. We will have people coming together to hack on several projects [0] proposed in the last few weeks. If you have any new proposal please submit it asap [1] before Monday 1600 UTC. So far we have 10 projects [0]. Each project has a pad [0] where you can find more information about it, who is on the team, and where people are going to meet during the week. All these projects will be presented on Monday at 1600 UTC in a BBB room [2]. You can add yourself to the pad of the team you want to collaborate with and ask any questions during the presentation on Monday. To summarize the presentation will be: Monday, June 27th at 1600 UTC ROOM: https://tor.meet.coop/gab-dpb-9zt-7tq happy hacking! gaba 0. https://gitlab.torproject.org/tpo/community/hackweek/#proposals-submitted-r… 1. https://hackweek.onionize.space/hackweek/ 2. https://tor.meet.coop/gab-dpb-9zt-7tq -- pronouns she/her/they GPG Fingerprint EE3F DF5C AD91 643C 21BE 8370 180D B06C 59CA BD19

1 0

Anti-censorship team meeting notes, 2022-06-23
by meskio 23 Jun '22

23 Jun '22

Hey everyone! Here are our meeting logs: http://meetbot.debian.net/tor-meeting/2022/tor-meeting.2022-06-23-15.58.html And our meeting pad: Anti-censorship work meeting pad -------------------------------- Next meeting: Thursday July 7 16:00 UTC Weekly meetings, every Thursday at 16:00 UTC, in #tor-meeting at OFTC (channel is logged while meetings are in progress) == 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 Tor. == 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 sponsors we are working on: * All needs review tickets: https://gitlab.torproject.org/groups/tpo/anti-censorship/-/merge_requests?s… * Sponsor 28 * must-do tickets: https://gitlab.torproject.org/groups/tpo/-/milestones/10 * possible tickets: https://gitlab.torproject.org/groups/tpo/-/issues?scope=all&utf8=%E2%9C%93&… * Sponsor 96 * https://gitlab.torproject.org/groups/tpo/-/milestones/24 == Announcements == * Next week is hackweek, no ant-censorship meeting!!! == Discussion == * What is the status of adjusting snowflake (pion) DTLS signature to avoid blocking in Russia? (Based on offset of supported_groups extension.) * https://gitlab.torproject.org/tpo/anti-censorship/censorship-analysis/-/iss… * https://github.com/pion/dtls/pull/474 * https://ntc.party/t/webrtc/2174/21 * https://gitlab.torproject.org/tpo/community/support/-/issues/40050 (generally) * shell will do some research on what makes sense as infra for testing snowflake connections * do we want a second broker for testing? * or multi-pool support? * snowflake spike on metrics * https://metrics.torproject.org/userstats-bridge-combined.html?start=2022-03… * being looked at the metrics side: https://gitlab.torproject.org/tpo/network-health/metrics/website/-/issues/4… == Actions == https://gitlab.torproject.org/tpo/anti-censorship/bridgestrap/-/issues/32 == 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): last updated 2022-06-23 Last week: - got tor to bootstrap fully with conjure PT in test environment - testenv: https://gitlab.torproject.org/cohosh/phantombox - conjure PT: https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/conj… - ran a quick tutorial on reproducible snowflake/tor-browser builds This week: - work with conjure developers to get the PT working with the production conjure station Needs help with: dcf: 2022-06-16 Last week: - snowflake CDN bookkeeping https://gitlab.torproject.org/tpo/anti-censorship/team/-/wikis/Snowflake-co… - commented on dnstt pluggable transport client https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/trac… - commented on restarts for snowflake probetest https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snow… Next week: - look at STATUS VERSION proposal https://gitlab.torproject.org/tpo/core/torspec/-/merge_requests/63 Help with: meskio: 2022-06-23 Last week: - gitlab implementation in gettor - metrics for gettor - test gettor-rdsys setup Next week: - deployment of rdsys-gettor Shelikhoo: 2022-06-23 Last Week: - [Merged & Deployed] Add Distributed Snowflake Server Support (snowflake!87) - [Merged] Distributed Snowflake Bridges (Javascript ver.) (snowflake-webext!29) - [Merged & Deployed] Implement metrics to measure snowflake churn (https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snow…) (snowflake!95) - [Merge Request Awaiting] Add SOCKS5 forward proxy support to snowflake (snowflake!64) - [Discussion & Deployment] Migrating Controlling git repo to Tor Gitlab Instance (shelikhoo/LogCollectorAncillary#5) - [Research & Discussion] Discussion about the possibility of adding PT support to V2Ray to serve the role of HTTPT (https://gitlab.torproject.org/tpo/anti-censorship/team/-/issues/82) - [Investigate] China "Anti-Fraud" Webpage Redirection Censorship (censorship-analysis#40026): update the research based on updated ooni result - [Deployment] Snowflake Broker Next Week: - [Coding & Deployment] Proposal: Centralized Probe Result Collector (anti-censorship/team#54) - [Research & Coding] WebSocket + CDN Based Probe Control Connection Forwarder (shelikhoo/LogCollectorAncillary#3) - [Investigate] China "Anti-Fraud" Webpage Redirection Censorship (censorship-analysis#40026): update the research based on updated ooni result Itchy Onion: 2022-06-23 Last week: - ongoing debugging s28 issues 81 - taking over part of testing snowflake This week: - ongoing debugging s28 issues 81, fixing a leaking file descriptor issue - taking over part of testing snowflake -- meskio | https://meskio.net/ -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- My contact info: https://meskio.net/crypto.txt -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Nos vamos a Croatan.

1 0

TPA-RFC-33: monitoring requirements (draft)
by Antoine Beaupré 23 Jun '22

23 Jun '22

Hi, (Yes, I send a lot of emails today, sorry. :) As part of the Debian bullseye upgrade, we're considering an upgrade of our Icinga server or a replacement with Prometheus. Considering some of you actually use one or the other, as service admins, I would be grateful if you could review the draft requirements I have written here, in TPA-RFC-33: https://gitlab.torproject.org/tpo/tpa/team/-/wikis/policy/tpa-rfc-33-monito… I also need to write a "persona" for service admins, so input on that would be welcome. Comments are welcome in the issue: https://gitlab.torproject.org/tpo/tpa/team/-/issues/40755 ... or by replying to this email, or as edits to the wiki page. Thanks! -- Antoine Beaupré torproject.org system administration

1 0