January 2025 - tor-project - lists.torproject.org

UX Team meeting moved to 1600 UTC on Tuesday 21st
by Duncan R. 15 Jan '25

15 Jan '25

Hi folks, On account of MLK Day, the UX Team meeting scheduled for 1600 UTC on Monday Jan 20th has been moved to the same time on Tuesday 21st instead. See you then, Duncan

1 0

Applications Team Meeting Rescheduled for Tuesday, (2025-01-21)
by Morgan 15 Jan '25

15 Jan '25

Hi Everyone, Next Monday is MLK day, so we'll move our meeting to the following Tuesday. best, -morgan

1 0

Notes from TPA 2025 roadmap review meeting
by Gabriel Filion 13 Jan '25

13 Jan '25

Hello all, The TPA team had a meeting today where we prioritized our goals mostly for Q1 of 2025 and had discussions about how to go around furthering the merger with tails, especially on the Puppet side (e.g. so that both Tor and Tails infrastructures can become managed by only one tool) Here are the notes from the meeting: --- title: 2025 Q1 Roadmap meeting --- # Roll call: who's there and emergencies - anarcat - groente - lavamind - lelutin - zen # Dashboard review Normal per-user check-in: - <https://gitlab.torproject.org/groups/tpo/-/boards?scope=all&utf8=%E2%9C%93&…> - <https://gitlab.torproject.org/groups/tpo/-/boards?scope=all&utf8=%E2%9C%93&…> - <https://gitlab.torproject.org/groups/tpo/-/boards?scope=all&utf8=%E2%9C%93&…> - <https://gitlab.torproject.org/groups/tpo/-/boards?scope=all&utf8=%E2%9C%93&…> - <https://gitlab.torproject.org/groups/tpo/-/boards?scope=all&utf8=%E2%9C%93&…> General dashboards: - <https://gitlab.torproject.org/tpo/tpa/team/-/boards/117> - <https://gitlab.torproject.org/groups/tpo/web/-/boards> - <https://gitlab.torproject.org/groups/tpo/tpa/-/boards> # 2025Q1 Roadmap review Review priorities for January and the first quarter of 2025. Pick from the [2025 roadmap](https://gitlab.torproject.org/tpo/tpa/team/-/wikis/roadmap/2025). Possibilities for Q1: - [Puppet CI and improvements](https://gitlab.torproject.org/groups/tpo/tpa/-/milestones/8): GitLab MR workflow, etc - Prometheus - MinIO - web stuff: download page coordination and deployment - email stuff: eugeni retirement, puppet cleanup, lists server (endless stream of work?), re-examining open issues to see if we fixed anything - discussions about SVN? - tails merge: - password stores - security policy - rotations - Puppet: start to standardize and merge codebases, update TPA modules, standardize code layout, maybe switch to nftables on both sides? Hoping *not* for Q1: - rdsys containerization (but we need to discuss and confirm the roadmap with meskio) - network team test network (discussions about design maybe?) - upgrading to trixie # Discuss and adopt the long term Tails merge roadmap <https://gitlab.torproject.org/tpo/tpa/team/-/wikis/policy/tpa-rfc-73-tails-…> In [the last discussion about the tails merge roadmap](https://gitlab.torproject.org/tpo/tpa/team/-/wikis/meeting/2024-11…, we have: > postpone[d] the "what happens when" discussion. We also identified that most services above "low complexity" will require their own discussions (e.g. "how do we manage the Puppet control repo", "how do we merge weblate") that will happen later. So we try to schedule those items across the 5 years. And we can also discuss specific roadmap items to see if we can settle some ideas already. Or we postpone all of this to the 2026 roadmap. Results of the discussion: We won't have time to discuss all of these, so maybe we want to sort based on priority, and pick one or two to go more in depth. Output should be notes to add to tpa-rfc-73 and a reviewed 2025 roadmap, then we can call this done for the time being and come back closer to end of 2025. We will adopt TPA-RFC-73 as a general guide / rough plan and review as we go. Here are all the medium and high complexity items we might want to discuss: ## 2025 See also the milestone: %"TPA-RFC-73: Tails merge (2025)" - [Security Policy](#security-policy) (merge, discussion delegated to anarcat) - [Shifts](#shifts) (merge, brainstorm a plan) - Puppet merge (merge, brainstorm of a plan): - deploy dynamic environments (in progress) - we can't use environments to retire one of the two puppet servers, because of exported resources - Upgrade and converge Puppet modules - lots of default stuff get deployed by TPA when you hook up a server, we could try turning everything off by default, move the defaults to a profile - maybe prioritize things, prioritize A/B/C, example: - A: "noop TPA": Kill switch on both sides, merged ENC, g10k, review exported resources, have one codebase but 2 implementations, LDAP integration vs tails? - B: "priority merge start": one codebase, but different implementations. start merging services piecemeal, e.g. two backup systems, but single monitoring system? - C: lower priority services (e.g. backusp?) - D: etc - Implement commit signing - [EYAML](#eyaml) (2029, keep?) (migrate to trocla?) - A plan for [Authentication](#authentication) (postpone discussion to later in 2025) - [LimeSuvey](#limesurvey) (merge) (just migrate from tails to TPA?) - [Monitoring](#monitoring) (migrate, brainstorm a plan) We mostly talked about Puppet. groente and zen are going to start drafting up a plan for Puppet! ## 2026 - Basic system functionality: - [Backups](#backups) (migrate) (migrate to bacula or test borg on backup-storage-01?) - [Authentication](#authentication) (merge) (to be discussed in 2025) - [DNS](#dns) (migrate) (migrate to PowerDNS?) - [Firewall](#firewall) (migrate) (migrate to nftables) - [TLS](#tls) (migrate, brainstorm a plan) - [Web servers](#web-servers) (merge, no discussion required, part of the Puppet merge) - [Mailman](#mailman) (merge, just migrate to lists-01?) - [XMPP](#xmpp) / [XMPP bot](#xmpp-bot) (migrate, delegate to tails, postponed: does Tails have plans to ditch XMPP?) ## 2027 - [APT repository](#apt-repository) (keep, nothing to discuss?) - [APT snapshots](#apt-snapshots) (keep) - [MTA](#mta) (merge) (brainstorm a plan) - [Mirror pool](#mirror-pool) (migrate, brainstorm) - [GitLab](#gitlab) (merge) - close the tails/sysadmin gitlab project? - brainstorm of a plan for the rest? - [Gitolite](#gitolite) (migrate, retire Tails' Gitolite and puppetize TPA's?) ## 2028 - [Weblate](#weblate) (news from emmapeel?) ## 2029 - [Jenkins](#jenkins) (migrate, brainstorm a plan or date?) - [VPN](#vpn) # Metrics of the month - hosts in Puppet: 91, LDAP: 90, Prometheus exporters: 512 - number of Apache servers monitored: 33, hits per second: 618 - number of self-hosted nameservers: 6, mail servers: 11 - pending upgrades: 5, reboots: 90 - average load: 0.56, memory available: 3.11 TiB/4.99 TiB, running processes: 169 - disk free/total: 60.95 TiB/142.02 TiB - bytes sent: 434.13 MB/s, received: 282.53 MB/s - planned bookworm upgrades completion date: was completed in 2024-12! - [GitLab tickets][]: 257 tickets including... - open: 0 - icebox: 160 - roadmap::future: 48 - needs information: 2 - backlog: 21 - next: 6 - doing: 12 - needs review: 8 - (closed: 3867) [Gitlab tickets]: https://gitlab.torproject.org/tpo/tpa/team/-/boards Upgrade prediction graph lives at <https://gitlab.torproject.org/tpo/tpa/team/-/wikis/howto/upgrades/bookworm/> Now also available as the main Grafana dashboard. Head to <https://grafana.torproject.org/>, change the time period to 30 days, and wait a while for results to render.

1 0

Anti-censorship team meeting notes, 2025-01-09
by onyinyang 09 Jan '25

09 Jan '25

Hey everyone! Here are our meeting logs: http://meetbot.debian.net/tor-meeting/2025/tor-meeting.2025-01-09-16.00.html And our meeting pad: Anti-censorship work meeting pad -------------------------------- Anti-censorship -------------------------------- Next meeting: Thursday,January 16 16:00 UTC Facilitator: shelikhoo ^^^(See Facilitator Queue at tail) Weekly meetings, every Thursday at 16:00 UTC, in #tor-meeting at OFTC (channel is logged while meetings are in progress) This week's Facilitator: onyinyang == 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 the Tor Project and Tor community. == 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 projects, we are working on: * All needs review tickets: * https://gitlab.torproject.org/groups/tpo/anti-censorship/-/merge_requests?s… * Project 158 <-- meskio working on it * https://gitlab.torproject.org/groups/tpo/anti-censorship/-/issues/?label_na… == Announcements == * == Discussion == Last meeting 2024: * covert-dtls in snowflake client and standalone proxy -- is there a plan for volunteer testing before merging? * https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snow… * the recent partial blocking in Russia has ended, so asking for user testing there won't reveal whether the changed fingerprint makes a difference * but it still could be valuable to have users run with the patch as a kind of integration and interoperability test * need to test both standalone proxy and client * meskio can try running the patch on a standalone proxy * (but there's no way to get per-country statistics) * implemented per-country stadistics, will submit a MR * did test it and it looks good * covert-dtls should be tested in both modes: randomize and mimic * theodorsm will produce instructions on how to compile and test the client with the help of cohosh * cohosh is working on it * and nina will translate to post it in ntc.party (2025) * Supporting WebTunnel Early Data * we can speed up webtunnel bootstrap by sending data over the handshake * this will make the code a bit more complex * is already implemented in V2Ray and easy to port * lets keep it as an idea to see if this is really needed == Actions == == Interesting links == * https://forum.torproject.org/t/snowflake-daily-operations-december-2024-upd… * Technical Analysis of the IRGFW (IRanian Great FireWall) * https://irgfw.report/projects/project1/ * https://github.com/net4people/bbs/issues/441 == Reading group == * We will discuss "Discovering and Measuring CDNs Prone to Domain Fronting" on January 16th * https://dl.acm.org/doi/10.1145/3589334.3645656 * 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): 2025-01-09 Last week: - gitlab reviews and todos - wrote a fix to get snowflake working on firefox with strict privacy settings - snowflake-webext#107, snowflake-webext!86 - started writing a feature for geoip library that uses CAIDA asn data - snowflake#40421 This week: - finish catching up on reviews - asn mapping geoip feature dcf: 2024-12-19 Last week: - worked on making the Edgio CDN snowflake-broker.azureedge.net point to the new broker, but ran into problems with TLS certificate verification https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snow… https://lists.torproject.org/mailman3/hyperkitty/list/anti-censorship-team@… - opened an issue for an error in the Snowflake Broker Survival Guide: the documented way to read the broker logs doesn't work https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snow… - opened an issue to clean up the way multiple server names are handled on the snowflake broker https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snow… - archived snowflake-webextension 0.9.0 and 0.9.2 https://lists.torproject.org/mailman3/hyperkitty/list/anti-censorship-team@… https://archive.org/details/snowflake-webextension-0.9.0 https://archive.org/details/snowflake-webextension-0.9.2 - answered questions from a student interested in experimenting with media streams in snowflake Next week: - open issue to have snowflake-client log whenever KCPInErrors is nonzero https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snow… - parent: https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snow… - open issue to disable /debug endpoint on snowflake broker Help with: meskio: 2024-01-09 Last week: - lyrebird dual-stack (IPv4/6) support in non-linux (lyrebird#40023) - test covert-tls snowflake proxies (snowflake!448) - improve circumvention settings doc (rdsys!446) - catch up with messages, specially responding in the forum to questions Next week: - snowflake debian package Shelikhoo: 2024-01-09 Last Week: - [Pending] snowflake broker update/reinstall(cont.): https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snow… - [Awaiting Review] Unreliable+unordered WebRTC data channel transport for Snowflake rev2 (cont.)( https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snow… ) improvements - Merge request reviews - Automate bridgeline update for snowflake(https://gitlab.torproject.org/tpo/anti-censorship/connectivity-me… ) - haproxy webtunnel fail claiming Tor browsers headers are malforned (https://gitlab.torproject.org/tpo/anti-censorship/team/-/issues/154#note_31…) - Remove Snowflake broker configuration for "snowflake-broker-debianupgradestaging-j33r3zahe.torproject.net" (https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snow…) Next Week/TODO: - Merge request reviews - [Resume] Unreliable+unordered WebRTC data channel transport for Snowflake rev2 (cont.)( https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snow… ) improvements onyinyang: 2025-01-09 Last week(s): - Break - WIP on Automated key rotations - WIP Conjure stuff for Project 173 Next week: - Get conjure up and running (at least locally) - implement utls for conjure - start implementation of alternative registration methods As time allows: - Continue work on implementing issuer efficiency for check-blockage and trust-promotion protocols - Work on outstanding milestone issues: - key rotation automation Later: pending decision on abandoning lox wasm in favour of some kind of FFI? https://gitlab.torproject.org/tpo/applications/tor-browser/-/issues/43096) - add pref to handle timing for pubkey checks in Tor browser - add trusted invitation logic to tor browser integration: https://gitlab.torproject.org/tpo/applications/tor-browser/-/issues/42974 - improve metrics collection/think about how to show Lox is working/valuable - sketch out Lox blog post/usage notes for forum (long term things were discussed at the meeting!): - brainstorming grouping strategies for Lox buckets (of bridges) and gathering context on how types of bridges are distributed/use in practice Question: What makes a bridge usable for a given user, and how can we encode that to best ensure we're getting the most appropriate resources to people? 1. Are there some obvious grouping strategies that we can already consider? e.g., by PT, by bandwidth (lower bandwidth bridges sacrificed to open-invitation buckets?), by locale (to be matched with a requesting user's geoip or something?) 2. Does it make sense to group 3 bridges/bucket, so trusted users have access to 3 bridges (and untrusted users have access to 1)? More? Less? theodorsm: 2024-01-09 Last weeks: - Offline Next weeks: - Fix merge conflicts in MR (https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snow…) - Write instructions on how to configure covert-dtls with snowflake client - Condensing thesis into paper (on hold) Help with: - Test stability of covert-dtls in snowflake MR Facilitator Queue: meskio onyinyang shelikhoo 1. First available staff in the Facilitator Queue will be the facilitator for the meeting 2. After facilitating the meeting, the facilitator will be moved to the tail of the queue -- --- onyinyang GPG Fingerprint 3CC3 F8CC E9D0 A92F A108 38EF 156A 6435 430C 2036

1 0

cohosh's monthly status report, December 2024
by Cecylia Bocovich 07 Jan '25

07 Jan '25

Hi! This is my status report for contract work done in December 2024. # Snowflake Last month I updated our builtin and suggested Snowflake bridge lines to remove old, nonfunctional STUN servers and add new ones that would ideally present significant trade-offs for censors that would try to block them. https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snow… https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snow… https://gitlab.torproject.org/tpo/anti-censorship/rdsys-admin/-/merge_reque… https://gitlab.torproject.org/tpo/applications/tor-browser-build/-/merge_re… To help us get into a habit of doing this more often, I wrote an update script that can be run as a part of the newly documented Snowflake Release Process. https://gitlab.torproject.org/cohosh/stun-torrc-check https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snow… My main focus of work on Snowflake at the moment is to improve the metrics we collect at the Snowflake broker for the purpose of detecting and learning about issues or circumvention events. To this end I did some planning and opened several issues for specific improvements that I will work on this month. https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snow… https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snow… https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snow… Then there were the usual reviews and project maintenance tasks. # meek In anticipation of the Azure edge shutdown this month, we've now migrated all of our domain fronted services off of Microsoft Azure. We updated our builtin bridge line to use CDN77 https://gitlab.torproject.org/tpo/anti-censorship/team/-/issues/155 https://gitlab.torproject.org/tpo/applications/tor-browser-build/-/merge_re…

1 0

intrigeri's report, December 2024
by intrigeri 06 Jan '25

06 Jan '25

Hi, I was on vacation during the last 1.5 week of the year, hence this slim report. User-visible ============ I reviewed and supported the work of my team-mates on a number of high priority user-visible improvements. User-invisible ============== Apart of the usual amount of KTLO work: - Migrated our Upgrader's signature verification from GnuPG to Sequoia SOP - Fixed a few security vulnerabilities identified by an ongoing security audit. Team lead ========= I've kicked off the second year of our ongoing grant (Project 165). I've kept working, together with a number of other Tor folks from my team and other teams, on a large grant proposal. This was the opportunity for me to discover the workflows and tooling used by Tor in this area, and gain some familiarity with it. We've booked time in January, with our team & sajolida, to work on our priorities for 2025. We also booked time to do a team retrospective. Accounting ========== We've kept making slow but steady progress on transitioning away from the former Tails fiscal sponsorship arrangements into Tails' new nest, the Tor project. Cheers, -- intrigeri

1 0

Nina’s Monthly Status Report, December, 2024
by Nina 06 Jan '25

06 Jan '25

Hi! Below is my December’24 report! In December, I resolved 1679 (↑110) tickets: * On Telegram (@TorProjectSupportBot) - 1459 (↑108); * On RT (frontdesk@tpo) - 219 (↑4); * On WhatsApp (+447421000612) - 1 (↓2); * and on Signal (+17787431312) - 0 (0). My main focus in December (and always)wasto provide support for Russian-speaking users in bypassing censorship. I help users to resolve any issues they are facing with Tor Browser and collect their feedback on what worked for them and what didn't. I also took part in Tor Forum moderation, took part in Relay OperatorsMeetup, and worked reviewing Google Play Store users reviews. Last months were especially challenging with number of tickets drastically growing sinceAugust'24. In December,whenRoskomnadzorblocked Viber messaging app [1] and finalised the YouTube blocking [2],the number ofuser supporttickets continued its growth. * July2024: 587 tickets * August2024: 928 tickets * September2024: 994 tickets * October2024: 1104 tickets * November2024: 1569 tickets * December2024: 1679 tickets <- this report I created a template for to help mobile users in using WebTunnel bridges as in some mobile ISPs obfs4 protocol seems to be blocked[3]. *##**Google Play Reviews for Tor Browser**(TBA)**and Tor Browser Alpha**for Android* - Tor Browser for Android had a Google Play rating of 4.382 (↓) stars in December 2024, which is lower than in November. - Tor Browser for Android (TBA) got 757 (↑85) reviews out of 59,828 for the lifetime. - Tor Browser for Android Alpha (TBA-Alpha) app had a rating of 4.228 (↓) which is lower than in November. - In December, Tor Browser for Android (TBA-Alpha) got 37 (↓1) reviews out of 8,424 for the lifetime. Most common issues on the Google Play store reviews remain the same: * "Tor Browser doesn’t work": - often from Russian users, who are struggling to find a way to connect to tor; * "Tor speed is too slow": This issue is currently under investigation. [1] https://www.reuters.com/technology/russian-watchdog-blocks-viber-messaging-… [2] https://www.rferl.org/a/youtube-practically-blocked-in-russia-expert-says/3… [3] https://gitlab.torproject.org/tpo/anti-censorship/censorship-analysis/-/iss…

1 0

ebanam's monthly status report and user support report for December 2024
by ebanam 06 Jan '25

06 Jan '25

Hello everyone, Much of my work last month focussed on helping users in regions where Tor is censored, which includes helping users with instructions to download Tor Browser binaries from GetTor and/or official mirrors, verifying Tor Browser's GPG signature, help with using censorship circumvention methods that works best for them and overall troubleshooting. With the year-end campaign into it's final month, I worked on some related support tickets, answering questions about Tor Browser. Topics included downloading, installing, using the browser, it's various privacy enhancing features and other questions about the Tor network. I also worked on some documentation updating some of the articles and templates that we use on our various user support channels. Here's a more detailed breakdown of the tickets our user support team worked on last month: # Frontdesk (email user support channel) * 658(↓) RT tickets created * 513(↓) RT tickets resolved Tickets by topics and numbers: 1. 219(↓) RT tickets: circumventing censorship in Russian speaking countries. 2. 173(↓) RT tickets: instructions to circumvent censorship for Chinese speaking users. 3. 13(↑) RT tickets: WebTunnel bridges campaign.[0] 4. 13(↑) RT tickets: help with installing Tor Browser for Desktop. 5. 9(↑) RT tickets: questions about how Tor works - is my IP visible when using Tor? what application level protections I get when using Tor Browser? etc. 6. 6(↑) RT tickets: reports of websites blocking Tor connections. 7. 5(↑) RT tickets: reports of a fake apps on iOS AppStore masquerading as official Tor Browser. 8. 5(↓) RT tickets: help with troubleshooting existing Tor Browser install on Desktop (Windows, macOS and Linux). 9. 4 RT tickets: questions about onion services and how to access them. 10. 3(-) RT tickets: instructions to download Tor Browser 13.5 legacy for legacy operating systems. 11. 2(↑) RT tickets: users seeing a "proxy refused" error when visiting websites on Tor Browser for Android using Samsung devices.[1] 12. 1 RT ticket: help with instructions to verify Tor Browser signature with GPG. 13. 1 RT ticket: help with setting up a Snowflake proxy. 14. 1 RT ticket: non-onionsite gives interstitial "Onionsite Has Disconnected" page.[2] # Telegram, WhatsApp and Signal Support channel * 1632(↑) tickets resolved Breakdown: * 1609(↑) tickets on Telegram * 22(↑) tickets on WhatsApp * 1(↑) ticket on Signal Tickets by topics and numbers: 1. 1256(↑) tickets: circumventing censorship in Russian speaking countries. 2. 18(↓) tickets: instructions to circumvent censorship for Chinese speaking users. 3. 15(↓) tickets: circumventing censorship with Tor in Farsi. 4. 14(↓) tickets: helping users on iOS, using Onion Browser or Orbot, to use censorship circumvention methods. 5. 13(↑) tickets: help with troubleshooting Tor Browser Desktop on Windows, macOS and Linux. 6. 6(↓) tickets: help with instructions to use bridges with Tails. 7. 4(↓) tickets: instructions on how to get Tor Browser binaries from GetTor. 8. 2(-) tickets: users seeing a "proxy refused" error when visiting websites on Tor Browser for Android using Samsung devices. 9. 2(↓) tickets: instructions to download Tor Browser 13.5 legacy for legacy operating systems. 10. 2 tickets: question about the differences in various security levels in the Tor Browser. 11. 1(-) ticket: help with setting up Snowflake proxy. 12. 1(↓) ticket: help with using bridges and snowflake with little-t-tor. # Highlights from the Tor Forum 1. How to use WebTunnel bridges with Tor Expert Bundle on Windows.[3] 2. Snowflake embed doesn't work on Firefox.[4] 3. Discussion on configuring all apps on Windows 10 to use Tor.[5] Note: (↑), (↓) and (-) are indicating if the number of tickets we received for these topics have been increasing, decreasing or have been the same from the previous month respectively. Thanks everyone! e. [0]: https://blog.torproject.org/call-for-webtunnel-bridges/ [1]: https://gitlab.torproject.org/tpo/applications/tor-browser/-/issues/42714 [2]: https://gitlab.torproject.org/tpo/applications/tor-browser/-/issues/40434 [3]: https://forum.torproject.org/t/where-can-you-download-webtunnel-exe-for-win… [4]: https://forum.torproject.org/t/snowflake-addon-in-firefox-has-stopped-worki… [5]: https://forum.torproject.org/t/tor-for-all-the-apps-in-a-windows-10-desktop…

1 0

PieroV's Monthly Status Report, December 2024
by Pier Angelo Vendrame 02 Jan '25

02 Jan '25

Hi everyone! Here is my status report for December 2024. This month, I finally had time for some overdue tasks that took me a long time. I started with the review of our patch set, particularly the Android part. We had some residues from the Tor integration migration and the last ESR rebase [0]. Also, some patches grew too much over time, so I split them. The resulting changes [1] were not a lot, but they were enough for a merge request. We will have to come back to this in the future. Then, I could work on fingerprinting. I finalized the patch to switch from the font "whitelist" to custom font visibility rules, matching Firefox [2]. After that, I started uplifting some of our letterboxing patches. The first ones were merged two years ago, and we want to have them in Firefox by ESR140. Also, regarding fingerprinting, I checked whether a leak of system accent color was possible [3], and set a preference as a defense in depth. During the month, I also helped to formalize the process for the rebases across all the RR versions [4][5] and attended some meetings about planning and grant proposals. Best, Pier [0] https://gitlab.torproject.org/tpo/applications/tor-browser/-/issues/43024 [1] https://gitlab.torproject.org/tpo/applications/tor-browser/-/merge_requests… [2] https://gitlab.torproject.org/tpo/applications/tor-browser/-/issues/43322 [3] https://gitlab.torproject.org/tpo/applications/tor-browser/-/issues/43366 [4] https://gitlab.torproject.org/tpo/applications/tor-browser/-/issues/43298 [5] https://gitlab.torproject.org/tpo/applications/tor-browser/-/merge_requests…

1 0

cve's monthly status report
by Clara Engler 02 Jan '25

02 Jan '25

Hello tor-project@, the following contains a summary of the work I have done in December 2024: * Release preparations for Arti 1.3.1 with gabi@, arti!2648, arti!2649 * Implement `--turn-secret-file` option in onionmasq, fixes onionmasq#127 * Fix clippy warnings introduced with Rust 1.83.0, onionmasq!335 * Add exclusion feature to Arti's fixup-features program, arti!2652, fixes arti#1766 * Updated several dependencies in onionmasq * Escape the coturn PID variable properly in the test suite, onionmasq!341 * Explicitly set interface in the HTTP integration test, onionmasq!340 * Hide the dangerous pcap feature behind a compile-time opt-in, fixes onionmasq#131, onionmasq!339 * Run coverage with `--all-features` enabled, onionmasq!338 * Add unit tests for config module, onionmasq!337 * Use an official Arti version in onionmasq, onionmasq!343 * Refactor device polling, onionmasq!342 * Update Arti's license year range to 2024, arti!2658 * Support for resolving local addresses in exit nodes for testing * This thing required a careful studying of the ctor source code on why it does not take `/etc/hosts` into account, despite several places in the code implying this behavior. In the end, it lead to the creation of a big ctor ticket, namely tor!40999 * Begin working on testing the DNS isolation cookie feature in onionmasq, which requires a working resolve of local addresses * Redesign the integration test suite, onionmasq!353 * Remove redundant `isolation.sh`, onionmasq!352 * IPv6 support in the integration test suite for UDP, onionmasq!351 * 38C3 related activities * Socializing with several colleagues and contributors * Watching the talk given by Gus and Hiro * Participation at the relay operator meetup on day 3 * Participation at the all-things Tor related meetup on day 4 * Freelancer bureaucracy related to the end of the year Thank You Clara

1 0