SHARE
TWEET

torrc file

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