#33693: snowflake's 0.0.3.0 dummy address means rate limits are skipped means BW controller events show no bandwidth used -------------------------------------+----------------------------- Reporter: arma | Owner: cohosh Type: defect | Status: merge_ready Priority: Medium | Milestone: Component: Circumvention/Snowflake | Version: Severity: Normal | Resolution: Keywords: | Actual Points: Parent ID: #19001 | Points: Reviewer: | Sponsor: -------------------------------------+----------------------------- Changes (by dcf):
* status: needs_review => merge_ready Comment: Looks great, thanks. If you would, please also change the dummy addresses in client/torrc and client/torrc-localhost in the snowflake repo. BTW the reason why the port number is 2 instead of 1 in meek-azure is that we were using a [https://gitweb.torproject.org/builders/tor-browser- build.git/tree/projects/tor-browser/Bundle- Data/PTConfigs/bridge_prefs.js?id=78ab93d70e73cf37550f45d6fb8fd61825bc1e95#n44 different port number] for each meek backend. meek-google at 0.0.2.0:1 (never deployed), meek-amazon at 0.0.2.0:2, meek-azure at 0.0.2.0:3. Then [https://gitweb.torproject.org/builders/tor-browser- build.git/commit/projects/tor-browser/Bundle- Data/PTConfigs/bridge_prefs.js?id=22af54508a1e98bec13ee9580aac7c1b907043e8 here] meek-azure took over port 2 when meek-amazon was removed. -- Ticket URL: <https://trac.torproject.org/projects/tor/ticket/33693#comment:11> 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