[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
Re: [tor-bugs] #12777 [meek]: Decide how to handle multiple meek backends in Tor Launcher
#12777: Decide how to handle multiple meek backends in Tor Launcher
------------------------+----------------------------------
Reporter: dcf | Owner: dcf
Type: defect | Status: needs_review
Priority: normal | Milestone:
Component: meek | Version:
Resolution: | Keywords: TorBrowserTeam201408
Actual Points: | Parent ID:
Points: |
------------------------+----------------------------------
Changes (by dcf):
* keywords: => TorBrowserTeam201408
* status: new => needs_review
Comment:
Here is how it looks now in 3.6.3-meek-2. There are two separate options,
meek-amazon and meek-google.
[[Image(meek-selection.png)]]
attachment:0001-Add-an-option-to-use-meek-through-CloudFront.patchâ is how
it looks in bridge_prefs.js. (Actually 3.6.3-meek-2 was not built with
that patch exactly, because the patch is against master, and bridge lines
have to look different in the maint-3.6 branch. These two commits:
[https://gitweb.torproject.org/pluggable-
transports/meek.git/commitdiff/efbfa9a2d70692e95a6f1d4191fbed56e50a2e46
meek] [https://gitweb.torproject.org/user/dcf/tor-browser-
bundle.git/commitdiff/45439b0ae6a62ed5343e9ed897c9246d116aed10 tor-
browser-bundle] are the workaround needed in maint-3.6.)
What I'm worried about is a user looking at this list of weird names and
not knowing which to pick. Adding more meeks isn't going to help things.
Maybe we ship one default and return other backends through BridgeDB?
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/12777#comment:1>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
_______________________________________________
tor-bugs mailing list
tor-bugs@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs