[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
[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: new
Priority: normal | Milestone:
Component: meek | Version:
Keywords: | Actual Points:
Parent ID: | Points:
--------------------+---------------------
I made a [https://gitweb.torproject.org/user/dcf/tor-browser-
bundle.git/shortlog/refs/tags/tbb-3.6.3-meek-2 3.6.3-meek-2] release that
has a meek capable of using both [[doc/meek#GoogleAppEngine|Google App
Engine]] and [[doc/meek#AmazonCloudFront|Amazon CloudFront]] as backends.
* https://people.torproject.org/~dcf/pt-bundle/3.6.3-meek-2/
The idea behind having two (or more) is that one may work where another
does not. The question is, how to usefully present the option? How is the
user supposed to choose between them?
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/12777>
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