commit df496945881e69d7a85a94b4bc98019c7bbf8661 Author: David Fifield <david@bamsoftware.com> Date: Mon Apr 2 09:35:17 2012 -0700 Remove notice of public connector. That won't be working at the moment. --- README | 15 --------------- 1 files changed, 0 insertions(+), 15 deletions(-) diff --git a/README b/README index a28c608..2351195 100644 --- a/README +++ b/README @@ -79,21 +79,6 @@ From tor you are looking for: [notice] Tor has successfully opened a circuit. Looks like client functionality is working. [notice] Bootstrapped 100%: Done. -=== Using a public connector - -Rather than running connector.py on your computer, you can use a public -connector. This way is not as realistic because all your Tor traffic -will first go to a public connector, which is at 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. - -1. Edit the included torrc file to comment one line and uncomment - another: - # Socks4Proxy 127.0.0.1:9001 - Socks4Proxy tor-facilitator.bamsoftware.com:9999 -2. Run Tor using the included torrc file. - $ tor -f flashproxy/torrc - === Troubleshooting Make sure someone is viewing https://crypto.stanford.edu/flashproxy/, or