[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
Re: [tor-bugs] #24110 [Core Tor/Tor]: document control protocol router status format surprises when using microdescriptors
#24110: document control protocol router status format surprises when using
microdescriptors
-------------------------------------------------+-------------------------
Reporter: teor | Owner: (none)
Type: defect | Status: new
Priority: Medium | Milestone: Tor:
| 0.3.3.x-final
Component: Core Tor/Tor | Version: Tor:
| 0.3.0.1-alpha
Severity: Normal | Resolution:
Keywords: bwauth-needs, tor-control, tor-spec | Actual Points:
Parent ID: | Points: 1
Reviewer: | Sponsor:
| SponsorV-can
-------------------------------------------------+-------------------------
Comment (by arma):
Replying to [comment:12 catalyst]:
> * TODO: check whether it's possible for a single instance of tor to
download both ns- and microdescriptor-flavored consensuses.
Yes, it should be possible. Anybody who is a dir cache does it, because
they want to fetch both of them so they can serve both.
But a given Tor will only make client-side path selection choices based on
one of them -- whichever flavor it is set to use. That's controlled by
UseMicrodescriptors and the associated consensus param.
One of the challenges is that it's unclear which use case we're trying to
cover here, and they at least somewhat contradict: telling the controller
about new directory objects, or telling the controller about information
that we're going to be using for our future circuit choices.
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/24110#comment:16>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
_______________________________________________
tor-bugs mailing list
tor-bugs@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs