torrc.minimal.in 8.8 KB

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