commit fc390af90fd6f42b5964ae0c0f77688e2f9b3235 Author: Runa A. Sandvik runa.sandvik@gmail.com Date: Mon Nov 7 08:09:26 2011 +0000

Comment the bridge torrc --- ec2-prep.sh | 19 +++++++++++++++++++ 1 files changed, 19 insertions(+), 0 deletions(-)

diff --git a/ec2-prep.sh b/ec2-prep.sh index e540c28..32e69e6 100644 --- a/ec2-prep.sh +++ b/ec2-prep.sh @@ -126,13 +126,32 @@ if [ $CONFIG == "bridge" ]; then echo "Configuring Tor as a $CONFIG"; cat << EOF > $CONFIG_FILE # Auto generated public Tor $CONFIG config file + +# A unique handle for your server. Nickname ec2$CONFIG$RESERVATION + +# Set "SocksPort 0" if you plan to run Tor only as a server, and not +# make any local application connections yourself. SocksPort 0 + +# What port to advertise for Tor connections. ORPort 443 + +# Listen on a port other than the one advertised in ORPort (that is, +# advertise 443 but bind to 9001). ORListenAddress 0.0.0.0:9001 + +# Start Tor as a bridge. BridgeRelay 1 + +# Never send or receive more than 10GB of data per week. The accounting +# period runs from 10 AM on the 1st day of the week (Monday) to the same +# day and time of the next week. AccountingStart week 1 10:00 AccountingMax 10 GB + +# Running a bridge relay just passes data to and from the Tor network -- +# so it shouldn't expose the operator to abuse complaints. Exitpolicy reject *:* EOF fi