Arti - The Future Of The Dark Web

Technological concepts & product analysis (Ry / “The Future Of The Dark Web”)

Goal: replace Tor’s C implementation with Rust (“Ry”)

• The video argues that Tor and Rust “were made for each other.”
• Ry is presented as a Rust implementation of Tor anonymity protocols, intended to replace unsafe and underperforming C code used today.

Why a rewrite is needed

• Memory safety issues
  • The speaker claims many severe Tor vulnerabilities over the years stem from memory safety problems, common in long-running C/C++ software.
• C codebase complexity (“spaghetti code”)
  • Tor is described as difficult to work with due to legacy architecture and long-term incremental feature additions since early development (circa ~2002).
• Developer friction & integration limits
  • The current implementation is portrayed as harder to develop against and harder to integrate into other applications, limiting broader adoption.

Modularity improvements

• The Rust rewrite (“Ry”) aims to be more modular than the current implementation, which the speaker characterizes as socks-proxy-like with features “glued on” over time.

Performance improvements

• The current Tor implementation is described as single-threaded, creating a bottleneck even on multi-core hardware.
• The Rust rewrite is described as multi-threaded, which should:
  • Increase throughput / speed across the Tor network (including Onion services).
  • Improve resilience to load-based DoS attacks, reducing HTTP 504 errors for onion sites.
  • Harden against introduction attacks, targeting Tor hidden service introduction points used to set up secure connections, which may otherwise help de-anonymize services (and possibly users).

Security trust debate

• The speaker acknowledges concerns:
  • Tor has been battle-tested for 20+ years, while Rust is newer.
• Counterargument presented:
  • The status quo is constrained by memory safety and concurrency difficulties, and Rust is positioned as the best candidate despite the “experimental language” perception.

---

Demo / tutorial-style instructions (how to try Ry)

Clone & build with Cargo

• The speaker clones the Ry repository, then runs the project’s provided cargo run command.
• Requires Rust + Cargo installed.

Default runtime configuration

• Ry listens by default on localhost for both IPv4 and IPv6.
• Default port mentioned: 9150.
• The port can be changed via settings, then rerun cargo run.

Build/distribution safety notice

• For distributing binaries, the speaker highlights:
  • Use Docker for reproducibility.
  • Rust/compiler may embed file system path info into binaries, potentially exposing sensitive paths (e.g., usernames), which could become an operational security issue.

---

Example use case: using Ry as a Tor SOCKS proxy

Verifying readiness

• The speaker runs Ry and confirms it’s ready (e.g., “guard is usable”).

Anonymizing application traffic via SOCKS

• Example application: Monero monero-go (remote node connection).
• The wallet lacks built-in Tor integration, so the speaker manually proxies via SOCKS.

Steps described

• In Monero GUI settings:
  • Configure the remote node endpoint (a node list is referenced, with a caution about trustworthiness).
• Point the Monero wallet to the local SOCKS proxy:
  • 127.0.0.1:9150
  • (The speaker explicitly references 127.0.0.1 and port 9150.)

Outcome claimed

• The wallet connects and synchronizes quickly, implying the Tor proxy path works.

---

Key speakers / sources

• Main speaker/source: The video narrator/host (not named in the provided subtitles).
• Referenced sources/products: Tor (The Onion Router), Rust, Ry project/repo, Cargo, axum (Rust web framework), Monero (monero-go / Monero GUI wallet).
• External mention: DARPA (organizations pushing Rust adoption).