Advertisement
Guest User

Untitled

a guest
Oct 3rd, 2020
695
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
  1. ## Configuration file for a typical Tor user
  2. ## Last updated 28 February 2019 for Tor 0.3.5.1-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.  
  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 192.168.1.40:9050 # Default: Bind to localhost:9050 for local connections.
  19. #SOCKSPort 192.168.0.1:9100 # Bind to this address:port too.
  20.  
  21. HTTPTunnelPort 8118
  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 @LOCALSTATEDIR@/log/tor/notices.log
  40. #Log notice file @LOCALSTATEDIR@/log/tor/notices.log
  41. ## Send every possible message to @LOCALSTATEDIR@/log/tor/debug.log
  42. #Log debug file @LOCALSTATEDIR@/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 @LOCALSTATEDIR@/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:D1E855E05232572C604D0B2D550E297801FD6A25587A5E92C437F96EBE
  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 @LOCALSTATEDIR@/lib/tor/hidden_service/
  75. #HiddenServicePort 80 127.0.0.1:80
  76.  
  77. #HiddenServiceDir @LOCALSTATEDIR@/lib/tor/other_hidden_service/
  78. #HiddenServicePort 80 127.0.0.1:80
  79. #HiddenServicePort 22 127.0.0.1:22
  80.  
  81. ################ This section is just for relays #####################
  82. #
  83. ## See https://www.torproject.org/docs/tor-doc-relay for details.
  84.  
  85. ## Required: what port to advertise for incoming Tor connections.
  86. #ORPort 9001
  87. ## If you want to listen on a port other than the one advertised in
  88. ## ORPort (e.g. to advertise 443 but bind to 9090), you can do it as
  89. ## follows. You'll need to do ipchains or other port forwarding
  90. ## yourself to make this work.
  91. #ORPort 443 NoListen
  92. #ORPort 127.0.0.1:9090 NoAdvertise
  93. ## If you want to listen on IPv6 your numeric address must be explictly
  94. ## between square brackets as follows. You must also listen on IPv4.
  95. #ORPort [2001:DB8::1]:9050
  96.  
  97. ## The IP address or full DNS name for incoming connections to your
  98. ## relay. Leave commented out and Tor will guess.
  99. #Address noname.example.com
  100.  
  101. ## If you have multiple network interfaces, you can specify one for
  102. ## outgoing traffic to use.
  103. ## OutboundBindAddressExit will be used for all exit traffic, while
  104. ## OutboundBindAddressOR will be used for all OR and Dir connections
  105. ## (DNS connections ignore OutboundBindAddress).
  106. ## If you do not wish to differentiate, use OutboundBindAddress to
  107. ## specify the same address for both in a single line.
  108. #OutboundBindAddressExit 10.0.0.4
  109. #OutboundBindAddressOR 10.0.0.5
  110.  
  111. ## A handle for your relay, so people don't have to refer to it by key.
  112. ## Nicknames must be between 1 and 19 characters inclusive, and must
  113. ## contain only the characters [a-zA-Z0-9].
  114. ## If not set, "Unnamed" will be used.
  115. #Nickname ididnteditheconfig
  116.  
  117. ## Define these to limit how much relayed traffic you will allow. Your
  118. ## own traffic is still unthrottled. Note that RelayBandwidthRate must
  119. ## be at least 75 kilobytes per second.
  120. ## Note that units for these config options are bytes (per second), not
  121. ## bits (per second), and that prefixes are binary prefixes, i.e. 2^10,
  122. ## 2^20, etc.
  123. #RelayBandwidthRate 100 KBytes # Throttle traffic to 100KB/s (800Kbps)
  124. #RelayBandwidthBurst 200 KBytes # But allow bursts up to 200KB (1600Kb)
  125.  
  126. ## Use these to restrict the maximum traffic per day, week, or month.
  127. ## Note that this threshold applies separately to sent and received bytes,
  128. ## not to their sum: setting "40 GB" may allow up to 80 GB total before
  129. ## hibernating.
  130. ##
  131. ## Set a maximum of 40 gigabytes each way per period.
  132. #AccountingMax 40 GBytes
  133. ## Each period starts daily at midnight (AccountingMax is per day)
  134. #AccountingStart day 00:00
  135. ## Each period starts on the 3rd of the month at 15:00 (AccountingMax
  136. ## is per month)
  137. #AccountingStart month 3 15:00
  138.  
  139. ## Administrative contact information for this relay or bridge. This line
  140. ## can be used to contact you if your relay or bridge is misconfigured or
  141. ## something else goes wrong. Note that we archive and publish all
  142. ## descriptors containing these lines and that Google indexes them, so
  143. ## spammers might also collect them. You may want to obscure the fact that
  144. ## it's an email address and/or generate a new address for this purpose.
  145. ##
  146. ## If you are running multiple relays, you MUST set this option.
  147. ##
  148. #ContactInfo Random Person <nobody AT example dot com>
  149. ## You might also include your PGP or GPG fingerprint if you have one:
  150. #ContactInfo 0xFFFFFFFF Random Person <nobody AT example dot com>
  151.  
  152. ## Uncomment this to mirror directory information for others. Please do
  153. ## if you have enough bandwidth.
  154. #DirPort 9030 # what port to advertise for directory connections
  155. ## If you want to listen on a port other than the one advertised in
  156. ## DirPort (e.g. to advertise 80 but bind to 9091), you can do it as
  157. ## follows. below too. You'll need to do ipchains or other port
  158. ## forwarding yourself to make this work.
  159. #DirPort 80 NoListen
  160. #DirPort 127.0.0.1:9091 NoAdvertise
  161. ## Uncomment to return an arbitrary blob of html on your DirPort. Now you
  162. ## can explain what Tor is if anybody wonders why your IP address is
  163. ## contacting them. See contrib/tor-exit-notice.html in Tor's source
  164. ## distribution for a sample.
  165. #DirPortFrontPage @CONFDIR@/tor-exit-notice.html
  166.  
  167. ## Uncomment this if you run more than one Tor relay, and add the identity
  168. ## key fingerprint of each Tor relay you control, even if they're on
  169. ## different networks. You declare it here so Tor clients can avoid
  170. ## using more than one of your relays in a single circuit. See
  171. ## https://www.torproject.org/docs/faq#MultipleRelays
  172. ## However, you should never include a bridge's fingerprint here, as it would
  173. ## break its concealability and potentially reveal its IP/TCP address.
  174. ##
  175. ## If you are running multiple relays, you MUST set this option.
  176. ##
  177. ## Note: do not use MyFamily on bridge relays.
  178. #MyFamily $keyid,$keyid,...
  179.  
  180. ## Uncomment this if you want your relay to be an exit, with the default
  181. ## exit policy (or whatever exit policy you set below).
  182. ## (If ReducedExitPolicy, ExitPolicy, or IPv6Exit are set, relays are exits.
  183. ## If none of these options are set, relays are non-exits.)
  184. #ExitRelay 1
  185.  
  186. ## Uncomment this if you want your relay to allow IPv6 exit traffic.
  187. ## (Relays do not allow any exit traffic by default.)
  188. #IPv6Exit 1
  189.  
  190. ## Uncomment this if you want your relay to be an exit, with a reduced set
  191. ## of exit ports.
  192. #ReducedExitPolicy 1
  193.  
  194. ## Uncomment these lines if you want your relay to be an exit, with the
  195. ## specified set of exit IPs and ports.
  196. ##
  197. ## A comma-separated list of exit policies. They're considered first
  198. ## to last, and the first match wins.
  199. ##
  200. ## If you want to allow the same ports on IPv4 and IPv6, write your rules
  201. ## using accept/reject *. If you want to allow different ports on IPv4 and
  202. ## IPv6, write your IPv6 rules using accept6/reject6 *6, and your IPv4 rules
  203. ## using accept/reject *4.
  204. ##
  205. ## If you want to _replace_ the default exit policy, end this with either a
  206. ## reject *:* or an accept *:*. Otherwise, you're _augmenting_ (prepending to)
  207. ## the default exit policy. Leave commented to just use the default, which is
  208. ## described in the man page or at
  209. ## https://www.torproject.org/documentation.html
  210. ##
  211. ## Look at https://www.torproject.org/faq-abuse.html#TypicalAbuses
  212. ## for issues you might encounter if you use the default exit policy.
  213. ##
  214. ## If certain IPs and ports are blocked externally, e.g. by your firewall,
  215. ## you should update your exit policy to reflect this -- otherwise Tor
  216. ## users will be told that those destinations are down.
  217. ##
  218. ## For security, by default Tor rejects connections to private (local)
  219. ## networks, including to the configured primary public IPv4 and IPv6 addresses,
  220. ## and any public IPv4 and IPv6 addresses on any interface on the relay.
  221. ## See the man page entry for ExitPolicyRejectPrivate if you want to allow
  222. ## "exit enclaving".
  223. ##
  224. #ExitPolicy accept *:6660-6667,reject *:* # allow irc ports on IPv4 and IPv6 but no more
  225. #ExitPolicy accept *:119 # accept nntp ports on IPv4 and IPv6 as well as default exit policy
  226. #ExitPolicy accept *4:119 # accept nntp ports on IPv4 only as well as default exit policy
  227. #ExitPolicy accept6 *6:119 # accept nntp ports on IPv6 only as well as default exit policy
  228. #ExitPolicy reject *:* # no exits allowed
  229.  
  230. ## Bridge relays (or "bridges") are Tor relays that aren't listed in the
  231. ## main directory. Since there is no complete public list of them, even an
  232. ## ISP that filters connections to all the known Tor relays probably
  233. ## won't be able to block all the bridges. Also, websites won't treat you
  234. ## differently because they won't know you're running Tor. If you can
  235. ## be a real relay, please do; but if not, be a bridge!
  236. ##
  237. ## Warning: when running your Tor as a bridge, make sure than MyFamily is
  238. ## NOT configured.
  239. #BridgeRelay 1
  240. ## By default, Tor will advertise your bridge to users through various
  241. ## mechanisms like https://bridges.torproject.org/. If you want to run
  242. ## a private bridge, for example because you'll give out your bridge
  243. ## address manually to your friends, uncomment this line:
  244. #PublishServerDescriptor 0
  245.  
  246. ## Configuration options can be imported from files or folders using the %include
  247. ## option with the value being a path. If the path is a file, the options from the
  248. ## file will be parsed as if they were written where the %include option is. If
  249. ## the path is a folder, all files on that folder will be parsed following lexical
  250. ## order. Files starting with a dot are ignored. Files on subfolders are ignored.
  251. ## The %include option can be used recursively.
  252. #%include /etc/torrc.d/
  253. #%include /etc/torrc.custom
Advertisement
Advertisement
Advertisement
RAW Paste Data Copied
Advertisement