Small example of how to run a bridge as a server operator.
Jacob Appelbaum

Jacob Appelbaum commited on 2008-08-04 22:11:41
Zeige 1 geänderte Dateien mit 33 Einfügungen und 0 Löschungen.

... ...
@@ -129,6 +129,39 @@ Here are your bridge relays:
129 129
 Once you've received the email with bridge information,
130 130
 you can continue the Vidalia configuration steps outlined <a
131 131
 href="#UsingBridges">above</a>.
132
+</p>
133
+
134
+<a id="RunningABridge"></a>
135
+<h2><a class="anchor" href="#RunningABridge">Running a Tor Bridge</a></h2>
136
+<hr />
137
+
138
+<p>
139
+If you're a server operator, it's possible that you'd like to run a bridge 
140
+node. Below is a minimal <tt>torrc</tt> configuration that allows for bridged 
141
+entry into the Tor network:
142
+
143
+<pre>
144
+SocksPort 0
145
+Nickname BridgeExample
146
+ORPort 443
147
+BridgeRelay 1
148
+PublishServerDescriptor bridge
149
+Exitpolicy reject *:*
150
+</pre>
151
+
152
+When configured as a bridge, your server will <b>not</b> appear in the public
153
+Tor network.
154
+
155
+If you wish to tell a user to use your bridge, simply give them the IP
156
+adddress of the Tor node, the TCP port as configured by <tt>ORPort</tt> and the
157
+fingerprint of the server. The fingerprint should be in your Tor log files or
158
+in <tt>/var/lib/tor/fingerprint</tt> depending on your platform.
159
+
160
+If you would like to learn more about Bridges from a technical standpoint,
161
+please read the <a
162
+href="https://tor-svn.freehaven.net/svn/tor/trunk/doc/spec/bridges-spec.txt">Tor
163
+bridges specification</a>. If you're interested in running a private bridge or
164
+other specific uses, please do read the specification.
132 165
 </p>
133 166
 
134 167
   </div><!-- #main -->
135 168