<?xml version="1.0" encoding="utf-8"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title>Onion Flash · Protocol</title><link>https://1aeo.com/onionflash/</link><description>Important Tor news, distilled.</description><language>en</language><atom:link xmlns:atom="http://www.w3.org/2005/Atom" href="https://1aeo.com/onionflash/tags/protocol.xml" rel="self" type="application/rss+xml" /><lastBuildDate>Tue, 10 Nov 2026 17:12:47 GMT</lastBuildDate><item><title>Tor 0.4.9.15 security release adds DoS defenses and drops 0.4.8 support</title><link>https://1aeo.com/onionflash/news/293e1780b570c80dd6b205f6/</link><guid isPermaLink="true">https://1aeo.com/onionflash/news/293e1780b570c80dd6b205f6/</guid><pubDate>Wed, 28 Oct 2026 18:31:01 GMT</pubDate><category>release</category><category>directory-authority</category><category>dos</category><category>protocol</category><category>security</category><description>&lt;p&gt;The Tor Project released version 0.4.9.15, a security update introducing new defenses against large volumes of directory requests. The release makes the HSDir flag sticky across restarts and updates directory authorities to require specific protocol capabilities, rendering Tor versions 0.4.8 and earlier incompatible with the network. Operators are advised to upgrade relays as soon as possible.&lt;/p&gt;&lt;p&gt;&lt;strong&gt;Why it matters:&lt;/strong&gt; The release includes critical DoS mitigations for relays and enforces protocol changes that will disconnect older clients from the network.&lt;/p&gt;&lt;p&gt;Confirmed · Normal priority · Released&lt;/p&gt;&lt;ol class="source-list"&gt;&lt;li&gt;&lt;a href="https://gitlab.torproject.org/tpo/core/tor/-/tags/tor-0.4.9.15" rel="noopener noreferrer"&gt;tor-0.4.9.15&lt;/a&gt; &lt;span class="source-domain"&gt;gitlab.torproject.org&lt;/span&gt;&lt;/li&gt;&lt;li&gt;&lt;a href="https://gitlab.torproject.org/tpo/network-health/metrics/timeline/-/blob/70f336c3c0af306b4aaab13b32f77b062c538ec6/README.md?plain=1#L80" rel="noopener noreferrer"&gt;Release of tor 0.4.9.15 and the deployment of a new protocol version at directory authorities. The protocol change causes some clients to repeatedly re-request consensus documents, making them appear&lt;/a&gt; &lt;span class="source-domain"&gt;gitlab.torproject.org&lt;/span&gt;&lt;/li&gt;&lt;li&gt;&lt;a href="https://lists.torproject.org/mailman3/hyperkitty/list/tor-announce@lists.torproject.org/message/WXHTSV43NO5UZQ7Q634S5NS5MIRL5JSJ/" rel="noopener noreferrer"&gt;[tor-announce] [RELEASE] New C-tor 0.4.9.15&lt;/a&gt; &lt;span class="source-domain"&gt;lists.torproject.org&lt;/span&gt;&lt;/li&gt;&lt;/ol&gt;</description></item><item><title>Arti reported to have proof-of-work queue bypass allowing zero-effort eviction</title><link>https://1aeo.com/onionflash/news/62d3ac41be0ed05572e83eee/</link><guid isPermaLink="true">https://1aeo.com/onionflash/news/62d3ac41be0ed05572e83eee/</guid><pubDate>Tue, 22 Sep 2026 20:45:02 GMT</pubDate><category>security</category><category>dos</category><category>protocol</category><description>&lt;p&gt;A security report filed via HackerOne and published on GitLab describes a defect in Arti&amp;#x27;s rendezvous queue where a client sending no proof-of-work can evict a queued client that did. The report states this defeats the priority queue&amp;#x27;s purpose but notes it does not demonstrate a sustained denial of service. A maintainer commented that the issue is a bug but does not seem like a DoS issue, and a fix issue was created.&lt;/p&gt;&lt;p&gt;&lt;strong&gt;Why it matters:&lt;/strong&gt; The report states that the defect defeats the purpose of the priority queue, allowing clients to bypass proof-of-work requirements for queue admission.&lt;/p&gt;&lt;p&gt;Reported · Normal priority · Developing&lt;/p&gt;&lt;ol class="source-list"&gt;&lt;li&gt;&lt;a href="https://gitlab.torproject.org/tpo/core/arti/-/work_items/2746" rel="noopener noreferrer"&gt;PoW bypass issue&lt;/a&gt; &lt;span class="source-domain"&gt;gitlab.torproject.org&lt;/span&gt;&lt;/li&gt;&lt;li&gt;&lt;a href="https://gitlab.torproject.org/tpo/core/arti/-/work_items/2746#note_3489309" rel="noopener noreferrer"&gt;Public comment by @wesleyac&lt;/a&gt; &lt;span class="source-domain"&gt;gitlab.torproject.org&lt;/span&gt;&lt;/li&gt;&lt;li&gt;&lt;a href="https://gitlab.torproject.org/tpo/core/arti/-/work_items/2746#note_3489319" rel="noopener noreferrer"&gt;Public comment by @wesleyac&lt;/a&gt; &lt;span class="source-domain"&gt;gitlab.torproject.org&lt;/span&gt;&lt;/li&gt;&lt;/ol&gt;</description></item><item><title>Tor releases 0.4.9.16 emergency fix for directory authority thundering herd</title><link>https://1aeo.com/onionflash/news/e62ee76ef550d41d11507dc0/</link><guid isPermaLink="true">https://1aeo.com/onionflash/news/e62ee76ef550d41d11507dc0/</guid><pubDate>Wed, 04 Nov 2026 19:53:47 GMT</pubDate><category>release</category><category>directory-authority</category><category>protocol</category><category>security</category><description>&lt;p&gt;The Tor Project released version 0.4.9.16 as an emergency update specifically for directory authorities. The release addresses a &amp;#x27;thundering herd&amp;#x27; issue caused by new required protover values in the previous release, which was causing older clients to exit. It also includes a workaround for a bug where old clients failed to handle unparseable microdescriptors correctly when TAP keys were omitted.&lt;/p&gt;&lt;p&gt;&lt;strong&gt;Why it matters:&lt;/strong&gt; Scope and consequences remain subject to the linked upstream discussion.&lt;/p&gt;&lt;p&gt;Confirmed · High priority · Released&lt;/p&gt;&lt;ol class="source-list"&gt;&lt;li&gt;&lt;a href="https://gitlab.torproject.org/tpo/core/tor/-/tags/tor-0.4.9.16" rel="noopener noreferrer"&gt;tor-0.4.9.16&lt;/a&gt; &lt;span class="source-domain"&gt;gitlab.torproject.org&lt;/span&gt;&lt;/li&gt;&lt;li&gt;&lt;a href="https://lists.torproject.org/mailman3/hyperkitty/list/tor-announce@lists.torproject.org/message/ERTTFP7CBZDGGEPBFZBVIGQR5LAMNXWM/" rel="noopener noreferrer"&gt;[tor-announce] [RELEASE] Tor release 0.4.9.16&lt;/a&gt; &lt;span class="source-domain"&gt;lists.torproject.org&lt;/span&gt;&lt;/li&gt;&lt;/ol&gt;</description></item><item><title>Tor developers revert protocol capability change to unstick clients in restart loop</title><link>https://1aeo.com/onionflash/news/20d4c07cc947b330283ddbf4/</link><guid isPermaLink="true">https://1aeo.com/onionflash/news/20d4c07cc947b330283ddbf4/</guid><pubDate>Tue, 03 Nov 2026 14:30:32 GMT</pubDate><category>network</category><category>protocol</category><category>release</category><description>&lt;p&gt;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.&lt;/p&gt;&lt;p&gt;&lt;strong&gt;Why it matters:&lt;/strong&gt; 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.&lt;/p&gt;&lt;p&gt;Reported · High priority · Merged&lt;/p&gt;&lt;ol class="source-list"&gt;&lt;li&gt;&lt;a href="https://gitlab.torproject.org/tpo/core/tor/-/merge_requests/1074" rel="noopener noreferrer"&gt;Revert &amp;quot;Authority: List multiple protocol capabilities as &amp;quot;required&amp;quot;.&amp;quot;&lt;/a&gt; &lt;span class="source-domain"&gt;gitlab.torproject.org&lt;/span&gt;&lt;/li&gt;&lt;/ol&gt;</description></item></channel></rss>