Roger Dingledine commited on 2009-06-26 08:43:34
Zeige 1 geänderte Dateien mit 10 Einfügungen und 9 Löschungen.
... | ... |
@@ -762,7 +762,7 @@ Great. That's exactly why we implemented exit policies. |
762 | 762 |
<p> |
763 | 763 |
Each Tor relay has an exit policy that specifies what sort of |
764 | 764 |
outbound connections are allowed or refused from that relay. The exit |
765 |
-policies are propagated to the client via the directory, so clients |
|
765 |
+policies are propagated to Tor clients via the directory, so clients |
|
766 | 766 |
will automatically avoid picking exit relays that would refuse to |
767 | 767 |
exit to their intended destination. This way each relay can decide |
768 | 768 |
the services, hosts, and networks he wants to allow connections to, |
... | ... |
@@ -783,14 +783,14 @@ file-sharing ports). You can change your exit policy |
783 | 783 |
using Vidalia's "Sharing" tab, or by manually editing your <a |
784 | 784 |
href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#torrc">torrc</a> |
785 | 785 |
file. If you want to avoid most if not all abuse potential, set it to |
786 |
-"reject *:*". This setting means that your relay will be used for |
|
787 |
-relaying traffic inside the Tor network, but not for connections to |
|
788 |
-external websites or other services. |
|
786 |
+"reject *:*" (or un-check all the boxes in Vidalia). This setting means |
|
787 |
+that your relay will be used for relaying traffic inside the Tor network, |
|
788 |
+but not for connections to external websites or other services. |
|
789 | 789 |
</p> |
790 | 790 |
|
791 | 791 |
<p> |
792 |
-Make sure name resolution works (that is, your computer can resolve |
|
793 |
-Internet addresses correctly). |
|
792 |
+If you do allow any exit connections, make sure name resolution works |
|
793 |
+(that is, your computer can resolve Internet addresses correctly). |
|
794 | 794 |
If there are any resources that your computer can't reach (for example, |
795 | 795 |
you are behind a restrictive firewall or content filter), please |
796 | 796 |
explicitly reject them in your exit policy — otherwise Tor users |
... | ... |
@@ -804,7 +804,8 @@ will be impacted too. |
804 | 804 |
or bridge relay?</a></h3> |
805 | 805 |
|
806 | 806 |
<p><a href="<page bridges>">Bridge relays</a> (or "bridges" for short) |
807 |
-are Tor relays that aren't listed in the main Tor directory. That means |
|
807 |
+are <a href="<page docs/tor-doc-relay>">Tor relays</a> that aren't listed |
|
808 |
+in the main Tor directory. That means |
|
808 | 809 |
that even an ISP or government trying to filter connections to the Tor |
809 | 810 |
network probably won't be able to block all the bridges. |
810 | 811 |
</p> |
... | ... |
@@ -819,7 +820,7 @@ connections to the Tor network. So getting a lot of bridges running |
819 | 820 |
right now is mostly a backup measure, a) in case the Tor network does |
820 | 821 |
get blocked somewhere, and b) for people who want an extra layer of |
821 | 822 |
security because they're worried somebody will recognize that it's a |
822 |
-Tor relay IP address they're contacting. |
|
823 |
+public Tor relay IP address they're contacting. |
|
823 | 824 |
</p> |
824 | 825 |
|
825 | 826 |
<p>So should you run a normal relay or bridge relay? If you have |
... | ... |
@@ -1010,7 +1011,7 @@ Please help on all of these! |
1010 | 1011 |
things?</a></h3> |
1011 | 1012 |
|
1012 | 1013 |
<p> |
1013 |
-For the answer to this question and others, please see our new <a |
|
1014 |
+For the answer to this question and others, please see our <a |
|
1014 | 1015 |
href="<page faq-abuse>">Tor Abuse FAQ</a>. |
1015 | 1016 |
</p> |
1016 | 1017 |
|
1017 | 1018 |