Hi folks,
The overload bugs on the directory authorities are continuing, but they also continue to be mostly manageable.
But today, we spent several consensus intervals in a row without making a consensus -- which is supposed to be fine because Tor clients can do fine so long as they have a consensus from within the last 24 hours, but it exposed a bug in the v3 onion service implementation, where v3 onion clients and v3 onion services choose not to even attempt to fetch or publish v3 onion descriptors:
Jan 10 11:32:24.364 [warn] No live consensus so we can't get the responsible hidden service directories.
The fix imo is that we need to make v3 onion services work under the same time assumptions as the other parts of Tor -- if you have a usable consensus, then use it.
I've opened this ticket for the network team: https://gitlab.torproject.org/tpo/core/tor/-/issues/40237
--Roger
On Sun, Jan 10, 2021 at 01:54:41PM -0500, Roger Dingledine wrote:
The fix imo is that we need to make v3 onion services work under the same time assumptions as the other parts of Tor -- if you have a usable consensus, then use it.
I've opened this ticket for the network team: https://gitlab.torproject.org/tpo/core/tor/-/issues/40237
Ok, we implemented that ticket, and the fix is in Tor 0.4.5.3-rc, which means it's in the Tor Browser alpha that came out recently.
But to have the v3 onion services working even while the network is degraded, you need both sides -- client and service -- running the new version.
I've asked ahf and gus to coordinate with the network team and the browser team to get this fix into some stables, since we're going to continue having this topic come up until those stables are out.
--Roger
network-health@lists.torproject.org
-
Roger Dingledine