29 octubre 2024 red tor 2 min de lectura

Rendimiento de tor: qué mejoró de verdad y qué sigue pendiente

For years, the running joke about the tor network was that it was slow by design. That was never entirely true - and it is getting less true every release. A quiet wave of performance engineering has been reshaping how the network handles load.

Congestion control finally shipped

The biggest change arrived with Tor 0.4.7: the network switched from a decades-old fixed-window algorithm to ART, the new congestion control proposal (prop-324). Instead of guessing how much data a circuit can carry, relays now measure feedback and adapt - much closer to how TCP itself behaves on the modern internet. The practical effect, confirmed by network-wide measurements, was a meaningful drop in queueing delays under load. Downloads that used to stall mid-transfer now throttle smoothly instead. Nobody writes press releases about queueing delays, but this is the kind of change users feel without being able to name it.

Onion services got their own fixes

Hidden services historically suffered from a specific pathology: the rendezvous handshake is expensive, and busy services would choke on introduction-point overload. The 0.4.7 series also introduced rate limiting on introduction requests, which blunted the worst denial-of-service waves without operators resorting to captchas. Descriptor caching improvements and streamlined circuit building trimmed hundreds of milliseconds from first connections. On a network where every page load pays a handshake tax, that matters.

What arti promises

The Rust rewrite, arti, is the long game. Memory safety aside, its architecture is designed for embeddability - tor as a library inside other applications - and for faster iteration on exactly the kind of protocol work described above. Arti is not yet a drop-in replacement for the C daemon, especially for relays. But client-side performance work lands there first now, and the feedback loop between bug report and fix has visibly shortened.

What is still pending

Relay-side arti support remains the big unfinished item, and the C daemon will be maintained for years because of it. Bandwidth scanner modernization, better padding defaults, and onion service load-balancing beyond OnionBalance are all open work items on the Tor Project's roadmap. The honest summary: the network is faster than its reputation, improving release by release, and the remaining bottlenecks are known, named and actively being worked. Slow is a habit the network is finally breaking.

La UE reactiva Chat Control 1.0: el escaneo de mensajes vuelve pese a una mayoría votando en contra

El Parlamento Europeo no logró bloquear la reactivación del régimen temporal y voluntario de escaneo de mensajes el 9 de julio de 2026 - 314 diputados votaron en contra, pero el umbral de mayoría absoluta nunca se alcanzó. Con las negociaciones del CSAR permanente reanudándose en septiembre, la pelea por el escaneo y el cifrado define directamente el futuro de las herramientas de anonimato.

Telegram quiere .gram: qué pasa cuando la infraestructura criminal abandona las onions por un DNS controlado por la plataforma

Telegram solicitó a la ICANN el dominio de primer nivel .gram, convirtiendo nombres de usuario en dominios resolubles con sitios generados por IA detrás. Semanas después de la suspensión de t.me bajo presión de sanciones, el movimiento muestra cómo la infraestructura se aleja de los onion services hacia un DNS que los reguladores sí pueden tocar.

Kimwolf v7 y la onion cableada en duro: cómo los botnets aprendieron a dejar de temer las incautaciones

El botnet Kimwolf v7 resucitado resuelve sus servidores de mando a través del Ethereum Name Service en cinco endpoints barajados y recae en un hidden service de Tor fijo si todos fallan. Un estudio de caso de por qué los onion services siguen siendo el canal C2 más resistente a incautaciones que tienen los criminales.