This adds the HSFETCH command as well as the HS_DESC_CONTENT event to the
control specification.
The HS_DESC event is also changed a bit to fit the HSFETCH command case.
Ref.: #14847
Signed-off-by: David Goulet <dgoulet@ev0ke.net>
We use a few names for the main self-published descriptor documents...
https://trac.torproject.org/projects/tor/ticket/14987
Standardizing on the name 'server descriptor'. This change was made with a
few quick runs of sed...
% find ./* -type f -exec sed -i 's/router descriptor/server descriptor/' "{}" +;
% find ./* -type f -exec sed -i 's/Router descriptor/Server descriptor/' "{}" +;
% find ./* -type f -exec sed -i 's/Router Descriptor/Server Descriptor/' "{}" +;
... then reverting the attic changes, and scanning the rest to be sure it
doesn't include any functional impact.
If the consensus doesn't contain exits, we only build internal paths.
This is enough to allow reachability tests (which can enable exits to
bootstrap), and hidden services.
If we subsequently receive a consensus with exits, start building exit paths.
Update dir-spec and path-spec to document this.
Update control-spec to document changes in controller bootstrap messages.
Based on changes made in tor to resolve bug #13814.
Our new CONN_BW events' ConnType enumeration is poorly defined...
https://trac.torproject.org/10086
This is just a guess on my part for what it's supposed to be. I have *not*
trudged through the tor code to puzzle out how it actually allocates this
enumeration.
When adding an event type we expect spec authors to edit both section 3.4 and
4.1.x. This is error prone...
https://trac.torproject.org/10085
Dropping the redundant listing of event types and simply citing 4.1.x.
Tor moved from v2 to v3 directory information in commit 3ad6dc0e. Prior to that
Tor's 'GETINFO ns/*' options provided v2 information, but since then it's been
v3. For more information see...
https://trac.torproject.org/7953
Technically this is a tor bug, but it happens to be a convenient one so simply
updating our spec. In practice controller authors haven't noticed this
discrepancy because v3 router status entries are a superset of the fields in
v2.
