NetworkHigh priorityReported
Tor developers revert protocol capability change to unstick clients in restart loop
Published
Tor developers merged a revert of a recent change that listed multiple protocol capabilities as required. The revert addresses issues causing clients on version 0.4.8.x or lower to get stuck in a restart loop while fetching unusable consensus. This action allows affected clients to rejoin the network and treat microdescriptions as valid.
Why it matters
The revert is intended to resolve a network-wide incident where a significant number of clients were unable to connect due to consensus fetching failures.
Event status Merged
Read the sources
- Revert "Authority: List multiple protocol capabilities as "required"." gitlab.torproject.org
This is an AI-assisted summary of the linked public sources. Consult the original reports for details and operator guidance.