#29207: New design for broker -- proxy protocol for snowflakes -------------------------------------------------+------------------------- Reporter: cohosh | Owner: cohosh Type: enhancement | Status: | merge_ready Priority: High | Milestone: Component: Circumvention/Snowflake | Version: Severity: Normal | Resolution: Keywords: snowflake, design, ex-sponsor-19, | Actual Points: 2 anti-censorship-roadmap | Parent ID: | Points: 5 Reviewer: | Sponsor: | Sponsor28-must -------------------------------------------------+-------------------------
Comment (by cohosh): Now to talk about backwards compatibility and upgrading. The way this is written right now, it will kick out proxies that haven't updated. I think this is a feature, we have some performance problems right now that might be due to proxies that haven't updated. It also gives a means to exclude proxies in the future for not updating (by the `Version` field supplied in the polls). I tested this out using snowbox and the broker handles new as well as outdated requests just fine, and it returns a `400 Bad Request` for outdated proxies. What I could see desirable here is a way for the proxy to disable itself if it receives a `4XX` status code. We also currently have two brokers, one on the new migrated host and one on the old host due to #29258. I guess the best method is to deploy it at both hosts simultaneously. Anyone opposed to me starting this deployment? I plan to update the brokers first and then quickly do a proxy update. -- Ticket URL: <https://trac.torproject.org/projects/tor/ticket/29207#comment:29> 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