[tor-bugs] #20667 [Core Tor/Tor]: Deprecate FetchUselessDescriptors, mentioning UseMicrodescriptors 0 in the message
Tor Bug Tracker & Wiki
blackhole at torproject.org
Wed Nov 16 10:49:33 UTC 2016
#20667: Deprecate FetchUselessDescriptors, mentioning UseMicrodescriptors 0 in the
message
--------------------------+----------------------------------------
Reporter: teor | Owner:
Type: defect | Status: new
Priority: Medium | Milestone: Tor: 0.3.0.x-final
Component: Core Tor/Tor | Version: Tor: 0.3.0.0-alpha-dev
Severity: Normal | Resolution:
Keywords: easy, intro | Actual Points:
Parent ID: | Points: 0.5
Reviewer: | Sponsor:
--------------------------+----------------------------------------
Comment (by teor):
Replying to [comment:7 arma]:
> Replying to [comment:5 teor]:
> > Do we need an option that makes a client fetch both full descriptors
and microdescriptors?
> > If not, this sounds like a sensible solution.
>
> Once upon a time, that option was called DirPort.
>
> Now I kind of assumed it would be what DirCache does, but looking at the
code, maybe it isn't.
>
> What is the thing that makes relays fetch all the things? We should let
people turn that on.
Nothing, currently - they are all conditional.
(Except for perhaps `DirPort 127.0.0.1:9999`, which is a sleazy hack.)
I think we need a new option, which makes the following functions return
true:
directory_caches_unknown_auth_certs
directory_caches_dir_info
But doesn't change:
dir_server_mode
Because DirPort, BridgeRelay, and (usually) DirCache do that.
Nor:
directory_fetches_from_authorities
Because FetchDirInfoEarly does that.
And then we might want to review every use of dir_server_mode to see if we
really meant to say one or the other of:
directory_caches_unknown_auth_certs
directory_caches_dir_info
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/20667#comment:9>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
More information about the tor-bugs
mailing list