#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: Major | Resolution: Keywords: 034-must, 035-must, regression, | Actual Points: tor-bridge 034-backport | Parent ID: | Points: Reviewer: | Sponsor: -------------------------------------------------+------------------------- Changes (by teor):
* status: new => needs_information Comment: Thanks! I had a quick look through that commit. The code changes shouldn't change tor's behaviour. I wonder if the bug is in this commit, but the behaviour actually starts happening in the commit after it (a4fcdc5dec). In a4fcdc5dec, the following roles seem inconsistent: {{{ + CALLBACK(retry_dns, PERIODIC_EVENT_ROLE_ROUTER), + CALLBACK(check_dns_honesty, PERIODIC_EVENT_ROLE_RELAY), }}} It's probably unrelated, but I don't think clients write stats: {{{ + CALLBACK(write_stats_file, PERIODIC_EVENT_ROLE_ALL), }}} (Do onion services write stats?) I'll do some testing over the next 2 days, and try to work out what's happening. -- Ticket URL: <https://trac.torproject.org/projects/tor/ticket/27080#comment:4> Tor Bug Tracker & Wiki <https://trac.torproject.org/> The Tor Project: anonymity online
_______________________________________________ tor-bugs mailing list tor-bugs@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs