[tor-bugs] #10722 [Tor]: Wanted to contact directory mirror XXX ... but but it's in our ExcludedNodes list and StrictNodes is set.

[Tor Bug Tracker & Wiki]

#10722: Wanted to contact directory mirror XXX ... but but it's in our
ExcludedNodes list and StrictNodes is set.
------------------------+--------------------------------------------
     Reporter:  mr-4    |      Owner:
         Type:  defect  |     Status:  needs_review
     Priority:  normal  |  Milestone:  Tor: 0.2.5.x-final
    Component:  Tor     |    Version:  Tor: 0.2.4.19
   Resolution:          |   Keywords:  tor-client tor-hs 024-backport
Actual Points:          |  Parent ID:
       Points:          |
------------------------+--------------------------------------------

Comment (by mr-4):

 Replying to [comment:1 nickm]:
 > It looks like the right solution here is to add an ExcludeNodes check
 earlier, in directory_get_from_hs_dir().
 Seems reasonable.

 > For review: branch "bug10722" in my public repository.   Marking as
 backportable.
 I'll pull this and test it if not later today, then tomorrow.

 > (Re 2: {Alternative}DirAuthority has nothing to do with hidden service
 directories.  The HSDir directory system uses a hash ring to decide where
 to store the hidden service descriptors for each hidden service; the
 directory authorities don't enter into it.)
 Is there any reason why #10461 isn't looked at?

 Also, if I understand you correctly, then using AlternateHSAuthority
 should fix the problem, at least temporarily, even without your patch
 applied - provided AlternateHSAuthority works as advertised and I don't
 get myself in the same situation as with AlternateDirAuthority where tor
 completely ignores this option and does what it likes (which is what
 #10461 really is all about).

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