gaqgem.blogg.se

Tor project hopes replace fragile rust
Tor project hopes replace fragile rust









tor project hopes replace fragile rust

The team handled this work in tor#40396 and its respective sub-tickets. Roger and Cecylia from the Anti-censorship Team debugged and fixed a long-time UX issue that affects Tor’s internal Bridgestrap system and users using Tor together with bridges. Nick wrote a couple of Guard-related proposals found in Proposal #336 and Proposal #337 based on conversations with Mike et al. The problem was tracked in ticket tor#40491.Īs part of the above overload issue, the team handled another issue in how Tor reports metrics on DNS requests in tor#40490. The pipeline will run nightly and hopefully catch release critical Windows issues earlier in the process.Īs part of the daily work on maintaining Tor, the following newsworthy updates happened:ĭavid worked together with the Network Health Team on an issue where relays would incorrectly report themselves as being overloaded due to a bug in the DNS subsystem in Tor. This new feature will, in the future, allow multiple parties in the team to generate tarballs locally and mutually sign the tarballs with their respective PGP keys.Īlex wrote a new Gitlab CI-based pipeline for cross-compilation of Windows binaries on Linux. The work included:ĭavid wrote a new Gitlab CI-based pipeline for automatic large parts of the manual processes around the Tor releases (update of GeoIP files, fallback directory indexes, etc.).ĭavid wrote a new Gitlab CI-based pipeline that lets us build reproducible source tarballs from the Git branches in Tor. This work means we were down to around 14 open Merge Requests towards Tor at the end of the release preparation.Īfter the releases were out, we spent time automating the processes around the preparation of the releases to reduce time spent on this in the future. As part of the release preparation, backporting of patches took place, and some new patches were introduced to the respective releases to get them ready for release. The team has recently rotated roles such that David and Alex will generally be trying to take care of the maintenance of tor.git such that Nick can focus more of his time on the Arti project. The team worked on preparation for the 0.3.5.17, 0.4.5.11, 0.4.6.8, and 0.4.7.2-alpha releases of the Tor software.

tor project hopes replace fragile rust

This month, the team got a new member – a big welcome to eta, who will work on Tor’s Arti project with Nick. In addition to the classic Tor implementation, the team has also recently started working on a Rust implementation of Tor named Arti. The Network Team is responsible for writing the Tor network’s software and supporting tools to test and experiment with the network. Today’s update is only from the last two weeks of October, though, as we decided on this new reporting format as an experiment at that time. These updates will appear monthly and summarize what the team has been working on in the previous month. Welcome to this first monthly update from Tor’s Network Team here on our shiny new Tor Project forum.











Tor project hopes replace fragile rust