Roger Dingledine commited on 2009-06-24 08:27:44
Zeige 1 geänderte Dateien mit 19 Einfügungen und 18 Löschungen.
| ... | ... |
@@ -137,9 +137,12 @@ href="#UsingBridges">above</a>. |
| 137 | 137 |
<hr /> |
| 138 | 138 |
|
| 139 | 139 |
<p> |
| 140 |
-If you're a server operator, it's possible that you'd like to run a bridge |
|
| 141 |
-node. Below is a minimal <tt>torrc</tt> configuration that allows for bridged |
|
| 142 |
-entry into the Tor network: |
|
| 140 |
+If you want to help out and you can't run a <a href="<page |
|
| 141 |
+docs/tor-doc-relay>">normal Tor relay</a>, you should |
|
| 142 |
+run a bridge relay. You can configure it <a href="<page |
|
| 143 |
+docs/tor-doc-relay>">using Vidalia</a>, or you can manually <a |
|
| 144 |
+href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#torrc">edit |
|
| 145 |
+your torrc file</a> to be just these four lines: |
|
| 143 | 146 |
</p> |
| 144 | 147 |
|
| 145 | 148 |
<pre><code> |
| ... | ... |
@@ -150,30 +153,28 @@ Exitpolicy reject *:* |
| 150 | 153 |
</code> |
| 151 | 154 |
</pre> |
| 152 | 155 |
|
| 153 |
-<p> |
|
| 154 |
-(If you don't know how to edit your <tt>torrc</tt> file, see |
|
| 155 |
-<a href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#torrc">this |
|
| 156 |
-FAQ entry</a>.) |
|
| 157 |
-</p> |
|
| 158 |
- |
|
| 159 | 156 |
<p> |
| 160 | 157 |
When configured as a bridge, your server will <b>not</b> appear in the public |
| 161 | 158 |
Tor network. |
| 162 | 159 |
</p> |
| 163 | 160 |
|
| 164 | 161 |
<p> |
| 165 |
-If you wish to tell a user to use your bridge, simply give them the IP |
|
| 166 |
-address of the Tor node, the TCP port as configured by <tt>ORPort</tt> and the |
|
| 167 |
-fingerprint of the server. The fingerprint should be in your Tor log files or |
|
| 168 |
-in <tt>/var/lib/tor/fingerprint</tt> depending on your platform. |
|
| 162 |
+Your bridge relay will automatically publish its address to the bridge |
|
| 163 |
+authority, which will give it out via https or email as above. You can |
|
| 164 |
+also tell a user about your bridge directly: if you're using Vidalia, |
|
| 165 |
+you can copy-and-paste the bridge address from the Settings window. If |
|
| 166 |
+you're on Linux or BSD, you can construct the bridge address manually |
|
| 167 |
+using the <a href="#Understanding">format above</a> (you can find the |
|
| 168 |
+fingerprint in your Tor log files or in <tt>/var/lib/tor/fingerprint</tt> |
|
| 169 |
+depending on your platform). |
|
| 169 | 170 |
</p> |
| 170 | 171 |
|
| 171 | 172 |
<p> |
| 172 |
-If you would like to learn more about Bridges from a technical standpoint, |
|
| 173 |
-please read the <a |
|
| 174 |
-href="<svnsandbox>doc/spec/bridges-spec.txt">Tor |
|
| 175 |
-bridges specification</a>. If you're interested in running a private bridge or |
|
| 176 |
-other specific uses, please do read the specification. |
|
| 173 |
+If you would like to learn more about our bridge |
|
| 174 |
+design from a technical standpoint, please read the <a |
|
| 175 |
+href="<svnsandbox>doc/spec/bridges-spec.txt">Tor bridges |
|
| 176 |
+specification</a>. If you're interested in running an unpublished bridge |
|
| 177 |
+or other non-standard uses, please do read the specification. |
|
| 177 | 178 |
</p> |
| 178 | 179 |
|
| 179 | 180 |
</div><!-- #main --> |
| 180 | 181 |