[tor-commits] [tor-cloud/master] We want to create private bridges for AWS as well

[runa at torproject.org]

commit 415509d2babfea8b88ec15d1f70c3fc4d42cf280
Author: Runa A. Sandvik <runa.sandvik at gmail.com>
Date:   Thu Feb 9 18:53:39 2012 +0000

    We want to create private bridges for AWS as well
---
 ec2-prep.sh |   37 +++++++++++++++++++++++++++++++++++++
 1 files changed, 37 insertions(+), 0 deletions(-)

diff --git a/ec2-prep.sh b/ec2-prep.sh
index 4e6ad88..a886cb9 100644
--- a/ec2-prep.sh
+++ b/ec2-prep.sh
@@ -261,6 +261,43 @@ ExitPolicy reject *:*
 EOF
 fi
 
+if [ $CONFIG == "privatebridge" ]; 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
+
+# This is a private bridge.
+PublishServerDescriptor 0
+
+# 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
+
 # XXX TODO
 # Generally, we'll want to rm /var/lib/tor/* and remove all state from the system
 #