commit 3406eb1884f8032deb2ecafa49cc44b7f24a384e Author: David Fifield david@bamsoftware.com Date: Thu Nov 21 13:54:12 2013 -0800
Remove the README section on using a public flashproxy-client.
This is less necessary than it was in the early days, when no one wanted to bother to download the client software. I probably won't run a public flashproxy-client on the next facilitator I set up. --- README | 10 ---------- 1 file changed, 10 deletions(-)
diff --git a/README b/README index aa1dc6a..7888b22 100644 --- a/README +++ b/README @@ -62,16 +62,6 @@ computer into a flash proxy as long as the page is open. http://crypto.stanford.edu/flashproxy/
-== Using a public client transport plugin - -Rather than running flashproxy-client on your computer, you can use a -public instance of it. This way is not as realistic because all your Tor -traffic will first go to a fixed address and can be easily blocked. -However this is an easy way to try out the system without having to do -port forwarding. - $ tor ClientTransportPlugin "flashproxy socks4 fp-facilitator.org:9999" UseBridges 1 Bridge "flashproxy 0.0.1.0:1" LearnCircuitBuildTimeout 0 CircuitBuildTimeout 60 - - == Troubleshooting
Make sure someone is viewing http://crypto.stanford.edu/flashproxy/, or