#33407: Chutney bridge authorities have an empty networkstatus-bridges --------------------------+------------------------------------------------ Reporter: teor | Owner: (none) Type: defect | Status: new Priority: Medium | Milestone: Tor: 0.4.4.x-final Component: Core | Version: Tor/Tor | Severity: Normal | Keywords: ipv6, prop311, tor-bridge, chutney Actual Points: | Parent ID: #33232 Points: 1 | Reviewer: Sponsor: | Sponsor55-can | --------------------------+------------------------------------------------ Chutney bridge authorities don't have any bridges in their networkstatus- bridges. That's a problem, because we want to check networkstatus-bridges for the reachability checks in #33232.
Here are some alternative fixes: * fix bugs in tor or chutney that stop bridges posting their descriptors to the bridge authority * fix bugs in tor or chutney that stop the bridge authority writing bridges to the networkstatus (maybe it doesn't respect AssumeReachable?) * grep the bridge's logs for its reachability tests If we end up fixing tor, chutney will need to know which tor versions have these fixes (otherwise old branches will fail CI). So we may need some kind of environmental variable, tag, or version update. We don't have to do these fixes, because it should be enough to test relay reachability. But we would risk breaking bridge reachability tests, and not knowing about it until after a release. -- Ticket URL: <https://trac.torproject.org/projects/tor/ticket/33407> 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