commit f5536c57ebe5ac7d8ee0cf1c6971057368b3160e Author: David Fifield <david@bamsoftware.com> Date: Sun Apr 8 20:37:48 2012 -0700 Restore public connector to the README. I restarted it using the JS/WebSocket code. --- README | 9 +++++++++ 1 files changed, 9 insertions(+), 0 deletions(-) diff --git a/README b/README index e6ad198..e9917e4 100644 --- a/README +++ b/README @@ -76,6 +76,15 @@ 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. + $ tor ClientTransportPlugin "websocket socks4 127.0.0.1:9001" UseBridges 1 Bridge "websocket tor-facilitator.bamsoftware.com:9999" + === Troubleshooting Make sure someone is viewing https://crypto.stanford.edu/flashproxy/, or