[tor-bugs] #16825 [Tor]: client with explicit EntryNodes, no cached-* files never finds its entrynodes

[Tor Bug Tracker & Wiki]

#16825: client with explicit EntryNodes, no cached-* files never finds its
entrynodes
--------------------------------+------------------------------------
 Reporter:  starlight           |          Owner:
     Type:  defect              |         Status:  needs_review
 Priority:  Medium              |      Milestone:  Tor: 0.2.9.x-final
Component:  Tor                 |        Version:  Tor: 0.2.6.10
 Severity:  Normal              |     Resolution:
 Keywords:  guards, 028-triage  |  Actual Points:
Parent ID:                      |         Points:  medium
  Sponsor:  SponsorU            |
--------------------------------+------------------------------------
Changes (by arma):

 * status:  new => needs_review


Comment:

 There's a patch that could be reviewed. We might even want it in 0.2.8,
 since we're still early in the alpha process.

 The only side effect of my patch I believe is that bootstrapping is now
 noisier again, since we log the output from thinking about minimum-dir-
 info each time we process another batch of microdescs. We could imagine
 passing an argument to directory_info_has_arrived to indicate whether you
 think it should be quiet in response to this new arrival, and then we
 could get our old behavior with respect to noisiness and the new behavior
 with respect to notifying the guard subsystem when we have a consensus
 here and ready.

 Oh, and if we wanted to be totally wild, we could consider moving the call
 to {{{entry_guards_compute_status(options, now)}}} so it only happens when
 we receive a new consensus of some flavor. Since I think that's the only
 sort of dir info that we want to actually change our behavior from? I
 think?

--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/16825#comment:11>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online