[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
Re: [tor-bugs] #27080 [Core Tor/Tor]: bridges fail on Tor 0.3.4.1-alpha and later
#27080: bridges fail on Tor 0.3.4.1-alpha and later
-------------------------------------------------+-------------------------
Reporter: teor | Owner: (none)
Type: defect | Status:
| needs_information
Priority: High | Milestone: Tor:
| 0.3.5.x-final
Component: Core Tor/Tor | Version: Tor:
| 0.3.4.1-alpha
Severity: Blocker | Resolution:
Keywords: 034-must, 035-must, regression, | Actual Points:
tor-bridge 034-backport |
Parent ID: | Points:
Reviewer: | Sponsor:
-------------------------------------------------+-------------------------
Comment (by nickm):
I found one issue, which might or might not be a complete explanation
here. This is from a client in the bridges-min network:
{{{
Aug 20 13:35:57.787 [notice] No Tor server allows exit to 127.0.0.1:4747.
Rejecting.
}}}
Looking at the cached-microdescs in the authority's directory, I saw that
there is one with a correct policy line `p accept 1-65535` --
corresponding to the network's exit, 002r. But the client did not have
that microdescriptor cached: it had an older one one.
Digging deeper, it appears that the client is receiving new conensuses,
but it is not re-launching microdescriptor downloads fast enough. The
router_have_minimum_dir_info() function is returning 1, so
directory_info_has_arrived() is not launching any new descriptor downloads
here.
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/27080#comment:12>
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