[tor-commits] [tor-cloud/master] Show the Tor configuration file on the website so that bridge operators know what we are doing

[runa@xxxxxxxxxxxxxx]

commit 2b4b4d26e6163c040c82f4eabdd177f0e291fcb1
Author: Runa A. Sandvik <runa.sandvik@xxxxxxxxx>
Date:   Mon Nov 7 08:11:01 2011 +0000

    Show the Tor configuration file on the website so that bridge operators know what we are doing
---
 html/torrc.txt |   28 ++++++++++++++++++++++++++++
 1 files changed, 28 insertions(+), 0 deletions(-)

diff --git a/html/torrc.txt b/html/torrc.txt
new file mode 100644
index 0000000..46902ef
--- /dev/null
+++ b/html/torrc.txt
@@ -0,0 +1,28 @@
+# 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 *:*



_______________________________________________
tor-commits mailing list
tor-commits@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-commits