[tor-dev] Tor master exits with a required protocol error

teor teor at riseup.net
Mon Sep 17 01:52:11 UTC 2018

(CC'd tor-relays, please direct replies to tor-dev.)


If you are running Tor master, your Tor may exit with a required
protocol error.

The issue was introduced in commit 991bec67ee (about 8 hours ago).

The following conditions will make Tor exit:
* Tor will exit on startup if it has a cached consensus from the 14th
  of September (or earlier). It does not matter how old the consensus
* If certain directory authorities go down, the remaining authorities
  may generate a consensus that will cause your Tor to exit.

These consensuses require the LinkAuth=1 protocol, which Tor master
believes it does not support. (The change was intended for NSS Tors,
but mistakenly applies to all Tors.)

Here's how you can mitigate this issue:
* downgrade to or earlier, or
* delete the cached consensuses in your data directory. These
  consensuses may be called cached-consensus,
  cached-microdesc-consensus, unverified-consensus, and
  unverified-microdesc-consensus. Some may not be present.

We should resolve this issue in master in the next 24 hours. Then it
may take another 24 hours for packages to be rebuilt.

The master ticket for this change is:



Please reply @torproject.org
New subkeys 1 July 2018
PGP C855 6CED 5D90 A0C5 29F6 4D43 450C BA7F 968F 094B

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: Message signed with OpenPGP
URL: <http://lists.torproject.org/pipermail/tor-dev/attachments/20180917/0ec88b80/attachment.sig>

More information about the tor-dev mailing list