[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
Re: [tor-bugs] #23863 [Core Tor/Tor]: When our directory guards don't have each others' microdescs, we should try an authority or fallback (was: When our directory guards don't have each others' microdescs, we should mark some dead)
#23863: When our directory guards don't have each others' microdescs, we should try
an authority or fallback
-----------------------------------------------+---------------------------
Reporter: teor | Owner: (none)
Type: defect | Status: new
Priority: Medium | Milestone: Tor:
| 0.3.2.x-final
Component: Core Tor/Tor | Version: Tor:
| 0.3.0.6
Severity: Normal | Resolution:
Keywords: tor-guard, tor-bridge, tor-client | Actual Points:
Parent ID: #21969 | Points: 1
Reviewer: | Sponsor:
-----------------------------------------------+---------------------------
Comment (by teor):
Some more detailed design questions, after reviewing #23817:
* what should we do when we are using bridges, or all the authorities and
fallbacks are excluded by an EntryNodes setting?
* should we fetch mds from a fallback or an authority over a 3-hop path?
* is this what bridge clients do already, or do they give up when they
can't get something from their bridge(s)?
* if we are willing to fetch missing microdescs over a 3-hop path, can we
make should_set_md_dirserver_restriction() always return 1?
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/23863#comment:11>
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