Changes between Version 39 and Version 40 of doc/TorExitGuidelines


Ignore:
Timestamp:
Jan 12, 2018, 12:15:17 PM (3 months ago)
Author:
cypherpunks
Comment:

remove section "Technical" (content available in TorRelayGuide now)

Legend:

Unmodified
Added
Removed
Modified
  • doc/TorExitGuidelines

    v39 v40  
    8585If you have your own experience of abuse handling, just share it on our public mailing list or write us an email to tor-assistants@torproject.org.
    8686
    87 == Technical ==
    88 
    89 Please read all the technical details before getting started. If you have any questions or need help, please contact us at support@torservers.net.
    90 
    91  * Hardware
    92 
    93   The minimum desired speed for your Tor relay is 256 kbps.
    94 
    95   With one modern CPU core, you will be able to push ~100 Mbps. If you want to do more than that, you need to run more than one Tor process. There is [https://www.torservers.net/wiki/setup/server#multiple_tor_processes a modified initscript]  to help you with that.  Ideally, you have a CPU with [https://www.torservers.net/wiki/setup/server#aes-ni_crypto_acceleration AES-NI support], which allows around 300 Mbps per core.
    96 
    97  * Software
    98 
    99   Tor relays should work on Linux, FreeBSD 5.x+, OS X Tiger or later, and versions of Windows with the word Server in their name. That said, you'll likely be happiest with the packages for Debian (or with Ubuntu but only if you [https://www.torproject.org/docs/debian.html.en#ubuntu use our debs] ). Torservers.net published a helpful setup guide at https://www.torservers.net/wiki/setup/server. It helps you with some improvements such as kernel settings and settings in your torrc, so you can have a super-fast relay. This is really helpful for the Tor network.
    100 
    101  * Set up an informative website on the exit IP(s) on port 80.
    102 
    103   A disclaimer helps giving people the right idea about what is behind traffic coming from these IPs. A simple notice can be published without a separate webserver using Tor's "DirPortFrontPage " directive.
    104 
    105  * Try to use dedicated IPs, and when possible dedicated hardware.
    106 
    107  * Disk encryption might be useful to protect your node keys, but on the other hand unencrypted machines are easier to "audit" if required. We feel it's best to be able to easily show that you do Tor exiting, and nothing else (on that IP or server).
    108 
    109  * Set reverse DNS to something that signals its use, e.g. 'anonymous-relay', 'proxy', 'tor-proxy'. so when other people see the address in their web logs, they will more quickly understand what's going on. If you do, and if SMTP is allowed in your exit policy, consider configuring [https://en.wikipedia.org/wiki/Sender_Policy_Framework SPF] on your domain: this will protect you from users using your exit node to forge e-mails which look like they come from you.
    110 
    11187== Support ==
    11288 * If you are running an exit, or are thinking about it, you should subscribe to the [https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays/ Tor-Relays list].