torrc.minimal.in-staging (10586B)
1 ## Configuration file for a typical Tor user 2 ## Last updated 22 December 2017 for Tor 0.3.2.8-rc. 3 ## (may or may not work for much older or much newer versions of Tor.) 4 ## 5 ## Lines that begin with "## " try to explain what's going on. Lines 6 ## that begin with just "#" are disabled commands: you can enable them 7 ## by removing the "#" symbol. 8 ## 9 ## See 'man tor', or https://www.torproject.org/docs/tor-manual.html, 10 ## for more options you can use in this file. 11 ## 12 ## Tor will look for this file in various places based on your platform: 13 ## https://www.torproject.org/docs/faq#torrc 14 15 ## Tor opens a SOCKS proxy on port 9050 by default -- even if you don't 16 ## configure one below. Set "SOCKSPort 0" if you plan to run Tor only 17 ## as a relay, and not make any local application connections yourself. 18 #SOCKSPort 9050 # Default: Bind to localhost:9050 for local connections. 19 #SOCKSPort 192.168.0.1:9100 # Bind to this address:port too. 20 21 ## Entry policies to allow/deny SOCKS requests based on IP address. 22 ## First entry that matches wins. If no SOCKSPolicy is set, we accept 23 ## all (and only) requests that reach a SOCKSPort. Untrusted users who 24 ## can access your SOCKSPort may be able to learn about the connections 25 ## you make. 26 #SOCKSPolicy accept 192.168.0.0/16 27 #SOCKSPolicy accept6 FC00::/7 28 #SOCKSPolicy reject * 29 30 ## Logs go to stdout at level "notice" unless redirected by something 31 ## else, like one of the below lines. You can have as many Log lines as 32 ## you want. 33 ## 34 ## We advise using "notice" in most cases, since anything more verbose 35 ## may provide sensitive information to an attacker who obtains the logs. 36 ## 37 ## Send all messages of level 'notice' or higher to @LOCALSTATEDIR@/log/tor/notices.log 38 #Log notice file @LOCALSTATEDIR@/log/tor/notices.log 39 ## Send every possible message to @LOCALSTATEDIR@/log/tor/debug.log 40 #Log debug file @LOCALSTATEDIR@/log/tor/debug.log 41 ## Use the system log instead of Tor's logfiles 42 #Log notice syslog 43 ## To send all messages to stderr: 44 #Log debug stderr 45 46 ## Uncomment this to start the process in the background... or use 47 ## --runasdaemon 1 on the command line. This is ignored on Windows; 48 ## see the FAQ entry if you want Tor to run as an NT service. 49 #RunAsDaemon 1 50 51 ## The directory for keeping all the keys/etc. By default, we store 52 ## things in $HOME/.tor on Unix, and in Application Data\tor on Windows. 53 #DataDirectory @LOCALSTATEDIR@/lib/tor 54 55 ## The port on which Tor will listen for local connections from Tor 56 ## controller applications, as documented in control-spec.txt. 57 #ControlPort 9051 58 ## If you enable the controlport, be sure to enable one of these 59 ## authentication methods, to prevent attackers from accessing it. 60 #HashedControlPassword 16:872860B76453A77D60CA2BB8C1A7042072093276A3D701AD684053EC4C 61 #CookieAuthentication 1 62 63 ############### This section is just for location-hidden services ### 64 65 ## Once you have configured a hidden service, you can look at the 66 ## contents of the file ".../hidden_service/hostname" for the address 67 ## to tell people. 68 ## 69 ## HiddenServicePort x y:z says to redirect requests on port x to the 70 ## address y:z. 71 72 #HiddenServiceDir @LOCALSTATEDIR@/lib/tor/hidden_service/ 73 #HiddenServicePort 80 127.0.0.1:80 74 75 #HiddenServiceDir @LOCALSTATEDIR@/lib/tor/other_hidden_service/ 76 #HiddenServicePort 80 127.0.0.1:80 77 #HiddenServicePort 22 127.0.0.1:22 78 79 ################ This section is just for relays ##################### 80 # 81 ## See https://www.torproject.org/docs/tor-doc-relay for details. 82 83 ## Required: what port to advertise for incoming Tor connections. 84 #ORPort 9001 85 ## If you want to listen on a port other than the one advertised in 86 ## ORPort (e.g. to advertise 443 but bind to 9090), you can do it as 87 ## follows. You'll need to do ipchains or other port forwarding 88 ## yourself to make this work. 89 #ORPort 443 NoListen 90 #ORPort 127.0.0.1:9090 NoAdvertise 91 ## If you want to listen on IPv6 your numeric address must be explicitly 92 ## between square brackets as follows. You must also listen on IPv4. 93 #ORPort [2001:DB8::1]:9050 94 95 ## The IP address or full DNS name for incoming connections to your 96 ## relay. Leave commented out and Tor will guess. 97 #Address noname.example.com 98 99 ## If you have multiple network interfaces, you can specify one for 100 ## outgoing traffic to use. 101 # OutboundBindAddress 10.0.0.5 102 103 ## A handle for your relay, so people don't have to refer to it by key. 104 ## Nicknames must be between 1 and 19 characters inclusive, and must 105 ## contain only the alphanumeric characters (a-z, A-Z, 0-9). No unicode, 106 ## no emoji. If not set, "Unnamed" will be used. 107 #Nickname ididnteditheconfig 108 109 ## Define these to limit how much relayed traffic you will allow. Your 110 ## own traffic is still unthrottled. Note that RelayBandwidthRate must 111 ## be at least 75 kilobytes per second. 112 ## Note that units for these config options are bytes (per second), not 113 ## bits (per second), and that prefixes are binary prefixes, i.e. 2^10, 114 ## 2^20, etc. 115 #RelayBandwidthRate 100 KBytes # Throttle traffic to 100KB/s (800Kbps) 116 #RelayBandwidthBurst 200 KBytes # But allow bursts up to 200KB (1600Kb) 117 118 ## Use these to restrict the maximum traffic per day, week, or month. 119 ## Note that this threshold applies separately to sent and received bytes, 120 ## not to their sum: setting "40 GB" may allow up to 80 GB total before 121 ## hibernating. 122 ## 123 ## Set a maximum of 40 gigabytes each way per period. 124 #AccountingMax 40 GBytes 125 ## Each period starts daily at midnight (AccountingMax is per day) 126 #AccountingStart day 00:00 127 ## Each period starts on the 3rd of the month at 15:00 (AccountingMax 128 ## is per month) 129 #AccountingStart month 3 15:00 130 131 ## Administrative contact information for this relay or bridge. This line 132 ## can be used to contact you if your relay or bridge is misconfigured or 133 ## something else goes wrong. Note that we archive and publish all 134 ## descriptors containing these lines and that Google indexes them, so 135 ## spammers might also collect them. You may want to obscure the fact that 136 ## it's an email address and/or generate a new address for this purpose. 137 ## Notice that "<" and ">" are recommended. 138 ## 139 ## If you are running multiple relays, you MUST set this option. 140 ## 141 #ContactInfo Random Person <nobody AT example dot com> 142 ## You might also include your PGP or GPG fingerprint if you have one. 143 ## Use the full fingerprint, not just a (short) KeyID: KeyIDs are easy 144 ## to forge. 145 #ContactInfo FFFFFFFFFFFFFFFFFFFF FFFFFFFFFFFFFFFFFFFF Random Person <nobody AT example dot com> 146 147 ## Uncomment this to mirror directory information for others. Please do 148 ## if you have enough bandwidth. 149 #DirPort 9030 # what port to advertise for directory connections 150 ## If you want to listen on a port other than the one advertised in 151 ## DirPort (e.g. to advertise 80 but bind to 9091), you can do it as 152 ## follows. below too. You'll need to do ipchains or other port 153 ## forwarding yourself to make this work. 154 #DirPort 80 NoListen 155 #DirPort 127.0.0.1:9091 NoAdvertise 156 ## Uncomment to return an arbitrary blob of html on your DirPort. Now you 157 ## can explain what Tor is if anybody wonders why your IP address is 158 ## contacting them. See contrib/tor-exit-notice.html in Tor's source 159 ## distribution for a sample. 160 #DirPortFrontPage @CONFDIR@/tor-exit-notice.html 161 162 ## Uncomment this if you run more than one Tor relay, and add the 163 ## identity key fingerprint of each Tor relay you control, even if 164 ## they're on different networks. Include "$" with each key id. You 165 ## declare it here so Tor clients can avoid using more than one of 166 ## your relays in a single circuit. 167 ## See https://www.torproject.org/docs/faq#MultipleRelays 168 ## However, you should never include a bridge's fingerprint here, as it would 169 ## break its concealability and potentially reveal its IP/TCP address. 170 ## 171 ## If you are running multiple relays, you MUST set this option. 172 ## 173 ## Note: do not use MyFamily on bridge relays. 174 #MyFamily $keyid,$keyid,... 175 176 ## Uncomment this if you want your relay to allow IPv6 exit traffic. 177 ## (Relays only allow IPv4 exit traffic by default.) 178 #IPv6Exit 1 179 180 ## A comma-separated list of exit policies. They're considered first 181 ## to last, and the first match wins. 182 ## 183 ## If you want to allow the same ports on IPv4 and IPv6, write your rules 184 ## using accept/reject *. If you want to allow different ports on IPv4 and 185 ## IPv6, write your IPv6 rules using accept6/reject6 *6, and your IPv4 rules 186 ## using accept/reject *4. 187 ## 188 ## If you want to _replace_ the default exit policy, end this with either a 189 ## reject *:* or an accept *:*. Otherwise, you're _augmenting_ (prepending to) 190 ## the default exit policy. Leave commented to just use the default, which is 191 ## described in the man page or at 192 ## https://www.torproject.org/documentation.html 193 ## 194 ## Look at https://www.torproject.org/faq-abuse.html#TypicalAbuses 195 ## for issues you might encounter if you use the default exit policy. 196 ## 197 ## If certain IPs and ports are blocked externally, e.g. by your firewall, 198 ## you should update your exit policy to reflect this -- otherwise Tor 199 ## users will be told that those destinations are down. 200 ## 201 ## For security, by default Tor rejects connections to private (local) 202 ## networks, including to the configured primary public IPv4 and IPv6 addresses, 203 ## and any public IPv4 and IPv6 addresses on any interface on the relay. 204 ## See the man page entry for ExitPolicyRejectPrivate if you want to allow 205 ## "exit enclaving". 206 ## 207 #ExitPolicy accept *:6660-6667,reject *:* # allow irc ports on IPv4 and IPv6 but no more 208 #ExitPolicy accept *:119 # accept nntp ports on IPv4 and IPv6 as well as default exit policy 209 #ExitPolicy accept *4:119 # accept nntp ports on IPv4 only as well as default exit policy 210 #ExitPolicy accept6 *6:119 # accept nntp ports on IPv6 only as well as default exit policy 211 #ExitPolicy reject *:* # no exits allowed 212 213 ## Bridge relays (or "bridges") are Tor relays that aren't listed in the 214 ## main directory. Since there is no complete public list of them, even an 215 ## ISP that filters connections to all the known Tor relays probably 216 ## won't be able to block all the bridges. Also, websites won't treat you 217 ## differently because they won't know you're running Tor. If you can 218 ## be a real relay, please do; but if not, be a bridge! 219 ## 220 ## Warning: when running your Tor as a bridge, make sure than MyFamily is 221 ## NOT configured. 222 #BridgeRelay 1 223 ## By default, Tor will advertise your bridge to users through various 224 ## mechanisms like https://bridges.torproject.org/. If you want to run 225 ## a private bridge, for example because you'll give out your bridge 226 ## address manually to your friends, uncomment this line: 227 #BridgeDistribution none