Tor retires tor1 relay encryption in favour of Counter Galois Onion

The Tor Project has retired its legacy tor1 relay encryption algorithm and replaced it with a new design called Counter Galois Onion, or CGO, according to BleepingComputer. The change covers circuit traffic across the anonymity network and is described by Cybersecurity News as a significant cryptographic overhaul that ends decades of service for the older algorithm.

BleepingComputer reports that a central motivation is making the network more resilient against modern traffic interception attacks that could compromise data security and undermine Tor users. Cybersecurity News describes the new design as research backed and says it defends against a broader class of sophisticated online attackers than the algorithm it replaces. BleepingComputer points readers to a Tor Project blog post titled Introducing CGO for the technical rationale.

Cybersecurity News notes that Tor's relay encryption serves a specialized function that is distinct from the standard TLS protocol, which matters for operators trying to reason about where the new algorithm sits in the stack. Both reports treat the switch as internal to the Tor implementation. Neither account describes configuration changes, key material handling updates or manual migration steps for relay or onion service operators.

For onion service operators the practical reading is that the change arrives with the software they already run rather than as a separate deployment task. The reports do not describe any effect on onion service addressing, descriptor publication or the client side rendezvous path, so the visible behaviour of a service should not change for visitors. Relays carrying onion service traffic are the ones doing the new cryptographic work.

Tor's recent emergency release, version 0.4.9.13, remains the other live thread for operators. Cybernews reported that the update addressed high severity flaws affecting relays, clients and onion services, that the release lists 10 tracked vulnerabilities, and that full technical details were delayed to limit attacker use. Cybernews also reported that an AI firehose of automated bug reports is flooding the project, which is shaping how quickly fixes are triaged and shipped.

What to watch next

The longer term signal is Tor's move away from C. ItsFoss reports that the network has run on a C codebase since the early 2000s and that the Tor Project has been working on a Rust rewrite for some time. A memory safe rewrite touches the same components that carry onion service circuits, so its progress is worth tracking alongside the CGO rollout.

Next steps worth watching are whether the Tor Project publishes the full CGO specification and the deferred vulnerability details from the emergency release, and whether relay operators report any performance change after the new encryption is widely deployed. Operators should keep their relay and onion service packages current, since both the cryptographic switch and the emergency fixes reach them through ordinary updates.