#28925: distinguish PT vs proxy for real in bootstrap tracker -------------------------------------------------+------------------------- Reporter: catalyst | Owner: | catalyst Type: defect | Status: | merge_ready Priority: High | Milestone: Tor: | 0.4.0.x-final Component: Core Tor/Tor | Version: Severity: Normal | Resolution: Keywords: asn-merge, teor-merge, | Actual Points: 2 s8-bootstrap, usability, ux, tor-pt, tbb- | needs, 040-must, network-team- | roadmap-2019-Q1Q2 | Parent ID: #28018 | Points: Reviewer: nickm | Sponsor: | Sponsor19 -------------------------------------------------+-------------------------
Comment (by teor): I tried rebuilding the file, but the diff was a mess: https://github.com/torproject/tor/pull/837/commits/973451edd1a8f0fe7c07ae5ba7fe8256ef279f95 I think practracker is using OS file order (or maybe an order based on python minor versions?), but we really want a stable file and function order. See #29882. I also wonder if we should replace the practracker list with every new release, so that we don't keep old exceptions. See #29883. So I guess that I'm meant to manually edit the file by finding any modified exceptions and updating them? There has to be an easier way. (Maybe #29880?) And if there isn't, it should be documented in the warning message, and at the start of the script. See #29884. -- Ticket URL: <https://trac.torproject.org/projects/tor/ticket/28925#comment:21> 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