- tor-project - lists.torproject.org

Anti-censorship team meeting notes, 2024-11-14
by meskio 14 Nov '24

14 Nov '24

Hey everyone! Here are our meeting logs: http://meetbot.debian.net/tor-meeting/2024/tor-meeting.2024-11-14-16.00.html And our meeting pad: Anti-censorship -------------------------------- Next meeting: Thursday, November 21 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: meskio == 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 == * Snowflake blocking in Russia November 2024 * https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snow… * No apparent difference in DTLS handshakes between proxies that continue working and proxies that stop working. * Reports say that some proxies stop working, but only after transferring some traffic. * Hard to test because we can't easily control the proxy. It would be a good idea to set up a small test deployment to afford us more experimental control. * cohosh will work on that. * Traffic analysis fingerprinting? An old padding patch: https://github.com/net4people/bbs/issues/255#issuecomment-1566227484 * let's graduate rdsys to 1.0 * is more or less stable and since some months has replaced BridgeDB completelly * next release will be 1.0 * future of the snowflake broker * https://lists.torproject.org/mailman3/hyperkitty/list/anti-censorship-team@… * we might need to start paying for the VM at elips.is from January * we can separate the broker from probetest, probetest doesn't see all clients only the proxies * the broker and the proxy are tied to the same domain name, we need first to separate them * https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snow… DefaultBrokerURL = "https://snowflake-broker.torproject.net/" DefaultNATProbeURL = "https://snowflake-broker.torproject.net:8443/probe" * meskio will look into funding options for the broker * on monday shelikhoo will start the move to the new broker * WebTunnel Server utility command interface * for certificate pinning we need to generate a hash of the certificate chain * there is no standard tooling for that, we need to extend webtunnel to do that * lets add a -gen-cert-fp flag == Actions == == Interesting links == * "Measuring and analyzing node families in the Tor anonymous communication network" (Chinese) by Fang Binxing et al. 2015 * https://www.infocomm-journal.com/txxb/EN/10.11959/j.issn.1000-436x.2015036 * Tor family was focused on design and given a family-level measurement of it. Based on Tor node families (over 3000) discovered from live Tor network data (from Jan. 2011 to Dec. 2012), a few characteristics of Tor node families were revealed, such as family size, bandwidth, geographical distribution as well as operators providing a few big families. The analysis validated the irreplaceable role played by family design in enhancing Tor's anonymity. Based on the measurement, security analysis showed the serious availability threat a compromised node family can cause to the Tor network. Besides, It also discussed Tor hidden families and the potential anonymity risk caused by them. == 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): 2024-11-14 Last week: - released new versions of snowflake and lyrebird - reviewed Troll Patrol MR (lox!263) - debugging the partial blocking of snowflake (snowflake#40407) - meek bridge handover tasks (anti-censorship/team#133) - Debugged problem with conjure deployment (conjure#44) - Removed vod.sport1.de from censorship settings front domains - reviewed MRs This week: - work with onyinyang on revisiting Lox BridgeTable fields and methods (lox#78) - follow up on snowflake blocking as we get more vantage point data - finish snowflake dependency upgrades that were causing problems - take a look at snowflake web and webext translations and best practices - make changes to Lox encrypted bridge table - https://gitlab.torproject.org/tpo/anti-censorship/lox/-/merge_requests/147 Needs help with: dcf: 2024-11-14 Last week: -snowflake azure cdn bookkeeping https://gitlab.torproject.org/tpo/anti-censorship/team/-/wikis/Snowflake-co… - allocated resources for Debian 12 replacement snowflake broker https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snow… - opened issue to remember to turn off the old Debian 10 broker https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snow… Next week: - comment on updates to unreliable snowflake transport https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snow… - 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: - tell me when to restart the brokers for https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snow… meskio: 2024-11-14 Last week: - review the status of the snowflake package dependencies (snowflake#40410) - remove race conditions in rdsys (rdsys#223) - fix email freezee in rdsys (rdsys#129) - release and deploy rdsys - inhibite ratio alerts (tpa/prometheus-alerts!60) Next week: - update snowflake proxy debian package Shelikhoo: 2024-11-14 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 - [Awaiting Input] Review CI: fix `latest` container image tag. https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snow… - Update Snowflake dependencies: https://gitlab.torproject.org/tpo/anti-censorship/connectivity-measurement/… - Update Snowflake WebExtension Domain: https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snow… - Logcollector anomaly investigate: https://gitlab.torproject.org/tpo/anti-censorship/censorship-analysis/-/iss… - Merge request reviews Next Week/TODO: - Merge request reviews - Work on finishing snowflake container release(and fix the comments) - Vantage point deployment in Iran - Snowflake broker deployment onyinyang: 2024-11-14 Last week(s): - Refactored MR for test distributor implementation into - https://gitlab.torproject.org/tpo/anti-censorship/lox/-/merge_requests/274 - Now this can remain in the main branch and the test distributor can be deployed with the --features test-branch flag - wasm changes will remain on the testing branch while https://gitlab.torproject.org/tpo/applications/tor-browser/-/issues/43096#n… is being sorted. - Updated lox-zkp to account for thiserror upgrade that was causing artifact issues, fixed testing in lox-zkp - working on refactor of Lox (library) protocols to improve issuing efficiency as described in: https://eprint.iacr.org/2024/1552.pdf Next week: - Fix up Troll-patrol MR - Fix up wasm changes in https://gitlab.torproject.org/tpo/anti-censorship/lox/-/merge_requests/271 - Deploy test distributor - Continue work on improving issuer efficiency in Lox protocols - update lox protocols to return duplicate responses for an already seen request - Work on outstanding milestone issues: in particular: https://gitlab.torproject.org/tpo/anti-censorship/lox/-/issues/69 - 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-10-24 Last weeks: - Adjusting to post-student life - Testing out beta releases of pion dtls and webrtc Next weeks: - Update Snowflake to use latest pion upstream releases - Test Snowflake fork with covert-dtls - Condensing thesis into paper Help with: - Feedback on thesis Facilitator Queue: onyinyang meskio 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 -- meskio | https://meskio.net/ -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- My contact info: https://meskio.net/crypto.txt -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Nos vamos a Croatan.

1 0

mailman 2 retirement imminent
by Antoine Beaupré 13 Nov '24

13 Nov '24

Hi everyone! This is hopefully (again!) my last email about Mailman 2 ever. Normally, everything should be up and running on Mailman 3. You should have everything you need there. Next week, I will be upgrading the main mail server, eugeni, where Mailman 2 was running. This will mean the final retirement of mailman 2, along with all its metadata about lists. Note that some of those things did *not* carry over to the new server. With geko, we found some bans that didn't transfer properly for example. We also also needed to approve some pending messages on tor-relays. So I've restored the service for Mailman 2, temporarily. It should now be available at: https://mailman2.torproject.org/ It's protected by a username / password, try tor-guest, with no password. Note that this service is *not* meant to be kept running like this. This is just available to pick up your remaining stuff and move it over to Mailman 3. I'm going to give this a week and then shutdown the virtual host again. Let me know if you need more time to finish those checks! Finally, note that I've decided to keep all the mailboxes (`mbox`) files from the current archives, including public *and* private archives, from current *and* retired mailing lists, archived on the new mailing list server. That way we don't have to worry about losing data on retired lists. a. -- Antoine Beaupré torproject.org system administration

1 1

minutes from the sysadmin meeting
by Antoine Beaupré 12 Nov '24

12 Nov '24

# Roll call: who's there and emergencies anarcat, gaba, groente, lavamind, lelutin, zen. There's significant noise in monitoring, but nothing that makes it worth canceling this meeting. # Dashboard review ## Normal per-user check-in Tried to make this section quick, but there were some discussions to be had: * 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 Skipped this section. * 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 # Tails merge discussion Let's review the work Zen did. Our rough plan was: - confirm already identified consensus - try to establish consensus on remaining items, or at least detail controversies and blockers - establish what should be done in 2025, 2026, < 2030, > 2030 We followed the [TPA-RFC-73 Draft](https://gitlab.torproject.org/tpo/tpa/team/-/wikis/policy/tpa-rfc-73… as it was at the time the meeting started. We figured that today, we would agree on strategy (e.g. puppet merge), on the colors (e.g. which services are retired), and postpone 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. ## Per service notes - Alternative to puppet merge: migrate services to TPA before moving Puppet, but not a good idea because some services can't be easily migrated. - registrars and colo could just depend on password store and not be otherwise changed. - website depends on powerdns - agreement of merging puppet codebases first - eyaml: merge for now, until people get familiar with both trocla and eyaml, but we probably should have a single system for this - virtualization: proposal: treat the old stuff as legacy and don't create new VMs there or make new hosts like those, if we need to replace hardware we create a ganeti box - weblate: - option 1: move the tor weblate to the self-hosted instance, need approval from emmapeel, check what reasons there were for not self-hosting - option 2: move tails translation to tor's weblate and rethink the translation workflow of tails We didn't have time to establish a 2025 plan, and postponed the rest of the discussions here. # 2025 roadmap brainstorm Throw ideas in the air and see what sticks about what we're going to do in 2025. Following, of course, priorities established in the Tails roadmap. Postponed. ## What we promised OTF For Tails: - B.2: Keep infrastructure up-to-date and secure > As in Year 1, this will involve the day-to-day work needed to keep the > infrastructure we use to develop and distribute Tails up-to-date. This > includes our public website, our development servers for automatic builds > and tests, the translation platform used by volunteers to translate Tails, > the repositories used for our custom Debian packages and reproducible > builds, etc. Progressively over Year 2 of this contract with OTF, as Tails > integrates within the Tor Project, our sysadmins will also start maintaining > non-Tails-specific infrastructure and integrate internal services offered by > Tails within Tor’s sysadmin workflow https://nc.torproject.net/s/eAa88JwNAxL5AZd?path=%2FGrants%2FOTF%2F2024%20-… For TPA: - I didn't find anything specific for TPA. https://nc.torproject.net/s/eAa88JwNAxL5AZd?path=%2FGrants%2FOTF%2F2024%20-… # Metrics of the month * hosts in Puppet: 90, LDAP: 90, Prometheus exporters: 504 * number of Apache servers monitored: 34, hits per second: 612 * number of self-hosted nameservers: 6, mail servers: 11 * pending upgrades: 0, reboots: 77 * average load: 1.03, memory available: 3.50 TiB/4.96 TiB, running processes: 321 * disk free/total: 65.69 TiB/139.85 TiB * bytes sent: 423.32 MB/s, received: 270.22 MB/s * planned bookworm upgrades completion date: 2024-10-02 * [GitLab tickets][]: 256 tickets including... * open: 2 * icebox: 162 * future: 39 * needs information: 4 * backlog: 27 * next: 11 * doing: 5 * needs review: 7 * (closed: 3760) [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/… Note that we have only a single "buster" machine left to upgrade after the Mailman 3 upgrade, and also hope to complete the bookworm upgrades by the end of the year. The above "in 3 weeks" date is unrealistic and will be missed. The "all time" graph was also rebuilt with histograms, making it a little more readable, with the caveat that the X axis is not to scale: https://gitlab.torproject.org/tpo/tpa/team/-/wikis/howto/upgrades/#all-time… -- Antoine Beaupré torproject.org system administration

1 0

Anti-censorship team meeting notes, 2024-11-07
by onyinyang 07 Nov '24

07 Nov '24

Hey everyone! Here are our meeting logs: http://meetbot.debian.net/tor-meeting/2024/tor-meeting.2024-11-07-16.00.html And our meeting pad: Anti-censorship work meeting pad -------------------------------- Anti-censorship -------------------------------- Next meeting: Thursday, November 14 16:00 UTC Facilitator: meskio ^^^(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 == * The rest of our Fastly front domains have stopped working over the last few months, and have been replaced * https://gitlab.torproject.org/tpo/anti-censorship/team/-/issues/151 * https://github.com/net4people/bbs/issues/309#issuecomment-2440083301 == Discussion == * Is a push notifications distributor for circumvention settings worth pursuing? * some privacy concerns with the connection to the push notification service * benefit: recovery from single point of failure moat domain fronting channel * obfs4 blocked in mobile networks in russia * https://gitlab.torproject.org/tpo/anti-censorship/censorship-analysis/-/iss… * https://gitlab.torproject.org/tpo/anti-censorship/censorship-analysis/-/iss… * https://ntc.party/t/11010/15 * https://github.com/net4people/bbs/issues/393#issuecomment-2461603654 * "All Cloudflare ECH-enabled services are blocked in Russia." * "It is detected by the presence of SNI = `cloudflare-ech.com` and ECH extension in ClientHello. Just SNI = `cloudflare-ech.com` without ECH extension is not affected, as well as ECH grease without SNI = `cloudflare-ech.com`." * https://ntc.party/t/12732 == Actions == == 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): 2024-11-07 Last week: - collaborated on the IPtProxy rewrite - https://github.com/tladesignz/IPtProxy/tree/refactor - updates to the snowflake transport in Lyrebird - lyrebird!64 - released snowflake-webext v0.9.2 - updated circumvention settings to not use Fastly domains - https://gitlab.torproject.org/tpo/anti-censorship/team/-/issues/151 - update orbot to remove (unused) fastly domain - https://github.com/guardianproject/orbot/pull/1197 - helped debug a tor bootstrapping delay with PTs - https://gitlab.torproject.org/tpo/core/tor/-/issues/40990 Next week: - finish snowflake dependency upgrades that were causing problems - take a look at snowflake web and webext translations and best practices - make changes to Lox encrypted bridge table - https://gitlab.torproject.org/tpo/anti-censorship/lox/-/merge_requests/147 Needs help with: dcf: 2024-11-07 Last week: - made a post comparing relative usage of the snowflake-01 and snowflake-02 bridges https://forum.torproject.org/t/snowflake-daily-operations-october-2024-upda… Next week: - comment on updates to unreliable snowflake transport https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snow… - 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: - tell me when to restart the brokers for https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snow… meskio: 2024-11-07 Last week: - search race conditions in rdsys (rdsys#223) - fix email hungup problems in rdsys (rdsys#129) - fix the propagation of gone bridges in rdsys (rdsys#245) - look at blockade situation in russia (censorship-analysis#40046) - AFK for IETF/PITG Next week: - update snowflake proxy debian package Shelikhoo: 2024-11-07 Last Week: - [Next Action 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 - [Awaiting Input] Review CI: fix `latest` container image tag. https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snow… - Prepare State of the Onion script/slide - Merge request reviews Next Week/TODO: - Merge request reviews - Work on finishing snowflake container release(and fix the comments) - Vantage point deployment in Iran - Snowflake broker deployment onyinyang: 2024-11-07 Last week(s): - MR for test distributor implementation - https://gitlab.torproject.org/tpo/anti-censorship/lox/-/merge_requests/271 Next week: - Deploy test distributor - update lox protocols to return duplicate responses for an already seen request - add issuer improvements to lox protocols - Work on outstanding milestone issues: in particular: https://gitlab.torproject.org/tpo/anti-censorship/lox/-/issues/69 - 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-10-24 Last weeks: - Adjusting to post-student life - Testing out beta releases of pion dtls and webrtc Next weeks: - Update Snowflake to use latest pion upstream releases - Test Snowflake fork with covert-dtls - Condensing thesis into paper Help with: - Feedback on thesis Facilitator Queue: onyinyang meskio 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, October 2024
by Cecylia Bocovich 06 Nov '24

06 Nov '24

Hi! This is my status report for contract work done in October 2024. I was AFK for the first half of the month. # Snowflake My main project last month was to add a snowflake transport to Lyrebird. This will help with reducing the PT binary size and simplify the process of integration with other applications (such as IPtProxy). https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/lyre… https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/lyre… I also worked on a few Snowflake fixes and features towards a similar purpose of making the Snowflake library more usable for other applications. https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snow… https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snow… # Pluggable transport libraries I've been working with Guardian Project on making our PT libraries more usable. Last month we started a rewrite of IPtProxy[0], which is a bundling of PT libraries for use with gomobile to produce java and Objective C bindings. This work has now been merged, and is just waiting for a few outstanding upstream changes before a release. [0] https://github.com/tladesignz/IPtProxy/pull/61

1 0

cve's monthly status report
by cve 05 Nov '24

05 Nov '24

Hi, the following contains my status report for October '24. This month was my first month working for Tor. During this time, I primarily worked upon improving the test infrastructure for the [onionmasq](https://gitlab.torproject.org/tpo/core/onionmasq) project. In particular, I have done the following things: * Implement support for coverage reports, allowing the inspection of the coverage for each line within the codebase. [!289](https://gitlab.torproject.org/tpo/core/onionmasq/-/merge_requests/289) * A live demo is [available](https://tpo.pages.torproject.net/-/core/onionmasq/-/jobs/742690/…. * General clean-ups in the CI YAML file. !289 * Bugfix for payload advancement in the `parser` for IPv6 extensions. [!291](https://gitlab.torproject.org/tpo/core/onionmasq/-/merge_requests/291) * >80% coverage for the `parser`, including test cases for UDP and TCP in both IPv4 and IPv6. [!292](https://gitlab.torproject.org/tpo/core/onionmasq/-/merge_requests/292), [!307](https://gitlab.torproject.org/tpo/core/onionmasq/-/merge_requests/307) * 100% coverage for the `accounting` module. [!290](https://gitlab.torproject.org/tpo/core/onionmasq/-/merge_requests/290) * Bugfix in the README. [!298](https://gitlab.torproject.org/tpo/core/onionmasq/-/merge_requests/298) * Bugfix and test case for IPv4 address collision (previously, IP addresses were overwritten in the case of a collision). [!297](https://gitlab.torproject.org/tpo/core/onionmasq/-/merge_requests/297) * Bugfix for the listening on the IPv6 DNS resolver IP address. [!299](https://gitlab.torproject.org/tpo/core/onionmasq/-/merge_requests/299) * Chutney support for onionmasq (using a custom arti configuration). [!301](https://gitlab.torproject.org/tpo/core/onionmasq/-/merge_requests/301) * Integration test environment. [!302](https://gitlab.torproject.org/tpo/core/onionmasq/-/merge_requests/302) * Integration test for DNS look-ups to see if the mappings remain constant. [!302](https://gitlab.torproject.org/tpo/core/onionmasq/-/merge_requests/302) * Bugfix for dropping ICMP packets, instead of pretending to be every host on the planet. [!305](https://gitlab.torproject.org/tpo/core/onionmasq/-/merge_requests/305) * Bugfix for performing a UDP checksum validation. [!306](https://gitlab.torproject.org/tpo/core/onionmasq/-/merge_requests/306) * Bugfix of a file descriptor leak in the Android application. [!309](https://gitlab.torproject.org/tpo/core/onionmasq/-/merge_requests/309) * Several clippy improvements. [!308](https://gitlab.torproject.org/tpo/core/onionmasq/-/merge_requests/308) * Performed research in arti's behavior in case of a loss of connectivity. Besides the aforementioned, I also had several internal tasks, primarily around general on-boarding as well as getting to know the team. Thank You

1 0

Felicia's Montly Status Report, October 2024
by Priscila 05 Nov '24

05 Nov '24

Hi everyone, Here is my status report for October 2024: ### Tor Browser - Design System - Unified Mozilla Firefox and Tor Browser’s component libraries for Android: https://gitlab.torproject.org/tpo/ux/design/-/work_items/114 ### Tor Browser for Desktop - Adapted Tor Browser’s Desktop UI applying up to date styles (colors and typography) and components + prototyped UIs that weren’t available in Figma yet: https://gitlab.torproject.org/tpo/ux/design/-/work_items/111 - Reviewed Connection settings screens in comparison to the latest version of Tor Browser Alpha: https://gitlab.torproject.org/tpo/ux/design/-/issues/54 ### Tor Browser for Android - Adjusted Tor Browser’s Android UI applying up to date styles (colors and typography) and components + prototyped UIs that weren’t available in Figma yet: https://gitlab.torproject.org/tpo/ux/design/-/work_items/112 Once I was done with the task above, the main issue to “Integrate Firefox’s Figma libraries” was resolved: https://gitlab.torproject.org/tpo/ux/design/-/issues/63 - Updated the Android library in Figma following the latest releases: https://gitlab.torproject.org/tpo/ux/design/-/issues/106 Cheers, Felicia / UX Team

1 0

ebanam's monthly status and user support report for October 2024
by ebanam 05 Nov '24

05 Nov '24

Hello everyone, This is a summary of the work I did in the month of October followed by a more detailed report of the work done by our user support team. With a number of Tor Browser releases including the last major stable release of the year - Tor Browser 14 - much of my work included alpha testing, updating the Tor Browser user manual[0] before the release. And reviewing and updating the documentation[1] on Support Portal and the various user support channels and keeping track of user feedback after the release. I worked on a number of Tor Browser related user support tickets - from general questions about installing, updating and troubleshooting to bug reports. With the onset of the year-end campaign[2], I also worked on related support tickets, answering questions about Tor Browser. Topics include downloading, installing, using the browser it's various privacy enhancing features and questions about the Tor network in general. Finally a huge part of my work was dedicated to help users in regions where Tor is censored which includes but is not limited to 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. Here's a more detailed breakdown of the tickets our user support team worked on last month: # Frontdesk (email user support channel) * 668(↑) RT tickets created * 683(↓) RT tickets resolved Tickets by topics and numbers: 1. 267(↓) RT tickets: private bridge requests from Chinese speaking users. 2. 207(↑) RT tickets: circumventing censorship in Russian speaking countries. 3. 12 RT tickets: help with Troubleshooting Tor Browser desktop on Windows, macOS and Linux. 4. 6 RT tickets: help with updating Tor Browser and questions about Tor Browser dropping support for legacy operating systems.[3] 5. 5 RT tickets: Tor Browser 14 crashing on macOS when visiting some onionsites.[4] 6. 5 RT tickets: Questions about the various Security Levels[5] in Tor Browser and issues with disabling JavaScript on higher security levels. 7. 5 RT tickets: configuring Orbot to use bridges. 8. 3(↑) RT tickets: circumventing censorship with Tor in Farsi. 9. 3 RT tickets: Letterboxing is visible even if disabled when using Tor Browser on Tiled window managers.[6] 10. 3 RT tickets: Instructions to download Tor Browser 13.5 legacy for legacy operating systems.[7] 11. 2 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. 12. Help with verifying Tor Browser signature with GPG. 13. One report of Tor Browser 14 getting flagged by anti-virus software on Windows. 14. One report of a fake app on iOS masquerading as official Tor Browser. 15. Question about using Tor bridges with Tails. 16. Instructions to use GetTor to fetch Tor Browser binaries. 17. One report of a website blocking Tor traffic. 18. Question about the various keys used by Tor[8]. 19. Tor Browser fails to work on Linux is dbus-glib is not installed[9]. This issue should be fixed with Tor Browser 14. # Telegram, WhatsApp and Signal Support channel * 1023(↑) tickets resolved Breakdown: * 1003(↑) tickets on Telegram * 20(↓) tickets on WhatsApp * 0(-) ticket on Signal Tickets by topics and numbers: 1. 667(↑) tickets: circumventing censorship in Russian speaking countries. 2. 32(↑) tickets: private bridge requests from Chinese speaking users. 3. 24(↓) tickets: circumventing censorship with Tor in Farsi. 4. 23 tickets: helping users on iOS, using Onion Browser or Orbot, to use censorship circumvention methods. 5. 16 tickets: help with troubleshooting Tor Browser Desktop on Windows, macOS and Linux. 6. 8 tickets: help with installing Tor Browser on linux. 7. 8 tickets: help with troubleshooting Tor Browser on Android. 8. 7 tickets: help with instructions to use bridges with Tails. 9. 7 tickets: questions about various features in Tor Browser (Letterboxing, Security Levels, New Circuit, New Identity, etc.) 10. 6 tickets: instructions on how to get Tor Browser binaries from GetTor. 11. 5 tickets: Tor Browser 14 crashing on macOS when visiting some onionsites.[4] 12. 5 tickets: Users seeing a "proxy refused" error when visiting websites on Tor Browser for Android using Samsung devices.[10] 13. 4 tickets: help with using bridges with Orbot. 14. 4 tickets: questions about accessing or setting up onion services. 15. 3 tickets: help with setting up Snowflake proxy. 16. 2 tickets: help with using bridges and snowflake with little-t-tor. 17. 1 ticket: Tor Browser 14 displaying a security notification on latest versions of Ubuntu.[11] 18. 1 ticket: User seeing a "proxy refused" error when visiting websites on Tor Browser for Android using a Xiaomi device.[12] 19. 1 ticket: Instructions to download Tor Browser 13.5 legacy for legacy operating systems. # Highlights from the Tor Forum 1. Configuring little-t-tor to use pluggable transports (obfs4, WebTunnel, etc.). [13] 2. Security warning on Tor Browser 14+ on latest versions of Ubuntu.[14] 3. Running Tor Browser with Wayland windowing system on Linux.[15] 4. Download Tor Browser 13.5 legacy on Windows 7, 8 and 8.1 and macOS 10.12, 10.13 and 10.14 [7] 5. Unable to render images when uploading/downloading them via Tor Browser.[16] 6. Installing Tor Browser on (Kali) Linux - troubleshooting issue with permissions.[17] 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://gitlab.torproject.org/tpo/web/manual/-/issues/174 [1]: https://gitlab.torproject.org/tpo/community/support/-/issues/40160 [2]: https://blog.torproject.org/2024-fundraiser-donations-matched/ [3]: https://support.torproject.org/tbb/tor-browser-and-legacy-os/ [4]: https://gitlab.torproject.org/tpo/applications/tor-browser/-/issues/43245 [5]: https://tb-manual.torproject.org/security-settings/ [6]: https://gitlab.torproject.org/tpo/applications/tor-browser/-/issues/42670 [7]: https://forum.torproject.org/t/download-tor-browser-13-5-legacy-on-windows-… [8]: https://support.torproject.org/about/key-management/ [9]: https://gitlab.torproject.org/tpo/applications/tor-browser/-/issues/41914 [10]: https://gitlab.torproject.org/tpo/applications/tor-browser/-/issues/42714 [11]: https://gitlab.torproject.org/tpo/applications/tor-browser/-/issues/43101 [12]: https://gitlab.torproject.org/tpo/applications/tor-browser/-/issues/41289 [13]: https://forum.torproject.org/t/error-with-the-tor-cli-client/15502 [14]: https://forum.torproject.org/t/after-updating-to-tor-browser-14-0-tor-brows… [15]: https://forum.torproject.org/t/linux-is-it-alright-to-run-the-tor-browser-o… [16]: https://forum.torproject.org/t/problem-in-the-images-that-i-download-or-try… [17]: https://forum.torproject.org/t/i-cant-open-tor-browser-on-kali-linux/15082

1 0

Rhatto's Monthly Status Report, October 2024
by rhatto 04 Nov '24

04 Nov '24

Hi all :) This is my monthly status report for October 2024 with the main relevant activities I have done, was involved or are related to my work during the period. # Onionprobe Ansible Role A considerable time was spent finding ways to structure and test Ansible roles, collections and playbooks through GitLab CI. Goal is to provide easier-to use procedures to manage Onion Services infrastructure. As a direct result of this research, it was possible to finally refactor and release an Ansible role to manage Onionprobe, a monitoring tool for onionsites: https://gitlab.torproject.org/tpo/onion-services/ansible/onionprobe-role It was interesting to research how to do basic Ansible tests using GitLab CI, and a special thanks goes to TPA for providing the base Podman image which allows running Podman in a GitLab CI job: https://gitlab.torproject.org/tpo/tpa/base-images # Onionprobe Onionprobe itself got some improvements, including support for running the standalone monitor node with Podman: https://onionservices.torproject.org/apps/web/onionprobe/standalone/ # OnionSec The OnionSec library and command line for testing onionsites got some enhancements as well: https://github.com/TheEnbyperor/onion-sec/pull/1 # Libraries The Onion Services Ecosystem got a Libraries page: https://onionservices.torproject.org/dev/libraries/ It still needs some improvements, and also some input from the upstream devs to check accuracy: https://gitlab.torproject.org/tpo/onion-services/ecosystem/-/issues/21 # Support Finally, also did the usual and ongoing sponsored work with deployment, maintenance and monitoring of Onion Services. -- Silvio Rhatto pronouns he/him

1 0

intrigeri's report, September 2024
by intrigeri 04 Nov '24

04 Nov '24

Hi, In case you missed it, Tails is now part of Tor: https://blog.torproject.org/tor-tails-join-forces/ Time-off ======== This was as short work months: I took 2 weeks off for personal reasons. I'm back. User-visible ============ - I reviewed the doc sajolida wrote to mitigate SBAT-related boot failures https://gitlab.tails.boum.org/tails/tails/-/issues/20471 - I gathered stats from bug reports to verify that our new idea (credits: sajolida) makes sense wrt. reporting errors about the partition table, partition header, and resizing. We plan to start designing and implementing in October. https://gitlab.tails.boum.org/tails/tails/-/issues/20505 https://gitlab.tails.boum.org/tails/tails/-/issues/20531 - Always notify users of N.x that they should upgrade to (N+1).y https://gitlab.tails.boum.org/tails/tails/-/issues/20542 - Fixed recent(ish) regressions - Spurious error message on Tails sticks installed a long time ago https://gitlab.tails.boum.org/tails/tails/-/issues/20519 Project and outreach ==================== - I attended the Global Gathering, together with a lovely crew of Tor people. - I helped a tiny bit with the messaging of the Tails/Tor merge announcement. Team lead ========= Most of my time left was used to set up new processes, integrating with the other Tor teams. Cheers, -- intrigeri

2 1