commit 59f41975368c96fd0f9c4cfbdab15a8ab7e6cbbb Author: David Fifield <david@bamsoftware.com> Date: Sat Dec 6 18:58:49 2014 -0800 Mention and link to #Webservices. https://trac.torproject.org/projects/tor/ticket/13335 --- README | 9 +++++++++ 1 file changed, 9 insertions(+) diff --git a/README b/README index 65b3fd1..b79d761 100644 --- a/README +++ b/README @@ -19,6 +19,15 @@ appspot.com while appearing to communicate with www.google.com can run the client plugin program like this: meek-client --url=https://meek-reflect.appspot.com/ --front=www.google.com +meek can use a number of web services as a transport backend. Some of +these, like CDNs, are very easy to set up for domain fronting: you just +point the CDN at an instance of meek-server. Others, like App Engine, +require you to run a small "reflector" app on the service that forwards +requests to meek-server. A description of how to set up various services +is at https://trac.torproject.org/projects/tor/wiki/doc/meek#Webservices. +Reflector apps are found in the appengine, nginx, php, and wsgi +directories. + The meek-client program by itself has a fingerprintable TLS handshake. To disguise the TLS part of HTTPS connections, meek-client should be run with the --helper option pointing at a browser extension that has been