import the exit policy faq question to the new faq
Roger Dingledine commited on 2009-06-24 06:42:20
Zeige 1 geänderte Dateien mit 43 Einfügungen und 0 Löschungen.
- en/faq.wml 884b958e8..c56a2eaf2
| ... | ... |
@@ -49,6 +49,8 @@ have a virus or spyware?</a></li> |
| 49 | 49 |
<p>Running a Tor relay:</p> |
| 50 | 50 |
<ul> |
| 51 | 51 |
<li><a href="#RelayFlexible">How stable does my relay need to be?</a></li> |
| 52 |
+<li><a href="#RunARelayBut">I'd run a relay, but I don't want to deal |
|
| 53 |
+with abuse issues.</a></li> |
|
| 52 | 54 |
<li><a href="#WhyNotNamed">Why is my Tor relay not named?</a></li> |
| 53 | 55 |
</ul> |
| 54 | 56 |
|
| ... | ... |
@@ -731,6 +733,47 @@ low-bandwidth ones. Therefore having low-bandwidth relays is useful too. |
| 731 | 733 |
|
| 732 | 734 |
<hr /> |
| 733 | 735 |
|
| 736 |
+<a id="RunARelayBut"></a> |
|
| 737 |
+<h3><a class="anchor" href="#RunARelayBut">I'd run a relay, but I don't |
|
| 738 |
+want to deal with abuse issues.</a></h3> |
|
| 739 |
+ |
|
| 740 |
+<p> |
|
| 741 |
+Great. That's exactly why we implemented exit policies. |
|
| 742 |
+</p> |
|
| 743 |
+ |
|
| 744 |
+<p> |
|
| 745 |
+Each Tor relay has an exit policy that specifies what sort of outbound |
|
| 746 |
+connections he will allow from his relay, and what sort he will |
|
| 747 |
+refuse. The exit policies are propagated to the client in the directory, |
|
| 748 |
+so clients will avoid picking exit nodes that would refuse to exit to |
|
| 749 |
+their intended destination. |
|
| 750 |
+</p> |
|
| 751 |
+ |
|
| 752 |
+<p> |
|
| 753 |
+By default, your relay allows access to many popular |
|
| 754 |
+services, but restricts some (such as port 25, see all <a |
|
| 755 |
+href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#DefaultPorts">default |
|
| 756 |
+restricted ports</a>) due to abuse potential. You can edit your torrc |
|
| 757 |
+to make your exit policy more or less restrictive. If you want to avoid |
|
| 758 |
+most if not all abuse potential, set it to "reject *:*". This setting |
|
| 759 |
+forces a "non-exit" operation. Nobody exits through your node, only |
|
| 760 |
+direct connections to other nodes will be established. |
|
| 761 |
+</p> |
|
| 762 |
+ |
|
| 763 |
+<p> |
|
| 764 |
+One good way to minimize abuse complaints in general |
|
| 765 |
+for exit nodes is to set the reverse DNS of your Tor |
|
| 766 |
+exit IP to be something like 'tor-exit.yourhost.org' |
|
| 767 |
+or 'tor-readme.yourhost.org'. You can then place <a |
|
| 768 |
+href="https://tor-svn.freehaven.net/svn/tor/trunk/contrib/tor-exit-notice.html">this |
|
| 769 |
+exit notice</a> html page (<a href="http://tor-exit.fscked.org">live |
|
| 770 |
+version</a>) on a vhost for that hostname to try to educate people |
|
| 771 |
+before they run off and harass you or your ISP. This actually does cut |
|
| 772 |
+down on abuse complaints quite a bit, believe it or not. |
|
| 773 |
+</p> |
|
| 774 |
+ |
|
| 775 |
+<hr /> |
|
| 776 |
+ |
|
| 734 | 777 |
<a id="WhyNotNamed"></a> |
| 735 | 778 |
<h3><a class="anchor" href="#WhyNotNamed">Why is my Tor relay not named?</a></h3> |
| 736 | 779 |
|
| 737 | 780 |