[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
Re: [tor-bugs] #21969 [Core Tor/Tor]: We're missing descriptors for some of our primary entry guards
#21969: We're missing descriptors for some of our primary entry guards
-----------------------------------+------------------------------------
Reporter: asn | Owner:
Type: defect | Status: new
Priority: High | Milestone: Tor: 0.3.1.x-final
Component: Core Tor/Tor | Version:
Severity: Normal | Resolution:
Keywords: tor-guard, tor-bridge | Actual Points:
Parent ID: | Points: 1.5
Reviewer: | Sponsor: SponsorU
-----------------------------------+------------------------------------
Comment (by teor):
Replying to [comment:6 catalyst]:
> ...
> I attached a log of a failed bootstrap with obfs4. (Tor Browser 7.0a3
with defaults obfs4 bridge configuration) It appears to have gotten stuck
because none of the selected guards was reachable when trying to download
the consensus.
IMO, the right fix here is to fall back to a fallback directory mirror.
It's what they are there for.
> ...
> Note that two of the guards have the same fingerprint
(`A832D176ECD5C7C6B58825AE22FC4C90FA249637`), and seem to be multiple
ports on the same IP according to the TBB-generated torrc. Maybe we
should prevent this during guard selection?
Unless, of course, you are using a restricted guard set or bridges, where
we should... just try another guard?
Also, maybe we want tor to try an IPv4 and an IPv6 address for your bridge
if you only have one dual-stack bridge?
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/21969#comment:9>
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