Guest User

zerak

a guest
Jan 6th, 2009
120
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 22 December 2007 for Tor 0.2.0.14-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 the man page, or https://www.torproject.org/tor-manual-dev.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. ## http://wiki.noreply.org/noreply/TheOnionRouter/TorFAQ#torrc
  14.  
  15.  
  16. ## Replace this with "SocksPort 0" if you plan to run Tor only as a
  17. ## server, and not make any local application connections yourself.
  18. SocksPort 0
  19. #SocksPort 9050 # what port to open for local application connections
  20. #SocksListenAddress 127.0.0.1 # accept connections only from localhost
  21. #SocksListenAddress 192.168.0.1:9100 # listen on this IP:port also
  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 from SocksListenAddress.
  26. #SocksPolicy accept 192.168.0.0/16
  27. #SocksPolicy reject *
  28.  
  29. ## Logs go to stdout at level "notice" unless redirected by something
  30. ## else, like one of the below lines. You can have as many Log lines as
  31. ## you want.
  32. ##
  33. ## We advise using "notice" in most cases, since anything more verbose
  34. ## may provide sensitive information to an attacker who obtains the logs.
  35. ##
  36. ## Send all messages of level 'notice' or higher to C:\Documents and Settings\Application Data\Tor\notices.log
  37. #Log notice file @CONFDIR@\notices.log
  38. ## Send every possible message to C:\Documents and Settings\Application Data\Tor\debug.log
  39. #Log debug file
  40. ## Use the system log instead of Tor's logfiles
  41. #Log notice syslog
  42. ## To send all messages to stderr:
  43. #Log debug stderr
  44.  
  45. ## Uncomment this to start the process in the background... or use
  46. ## --runasdaemon 1 on the command line. This is ignored on Windows;
  47. ## see the FAQ entry if you want Tor to run as an NT service.
  48. #RunAsDaemon 1
  49.  
  50. ## The directory for keeping all the keys/etc. By default, we store
  51. ## things in $HOME/.tor on Unix, and in Application Data\tor on Windows.
  52. #DataDirectory
  53.  
  54. ## The port on which Tor will listen for local connections from Tor
  55. ## controller applications, as documented in control-spec.txt.
  56. #ControlPort 9051
  57.  
  58. ############### This section is just for location-hidden services ###
  59.  
  60. ## Once you have configured a hidden service, you can look at the
  61. ## contents of the file ".../hidden_service/hostname" for the address
  62. ## to tell people.
  63. ##
  64. ## HiddenServicePort x y:z says to redirect requests on port x to the
  65. ## address y:z.
  66.  
  67. #HiddenServiceDir C:\Documents and Settings\Application Data\Tor\hidden_service/
  68. #HiddenServicePort 80 127.0.0.1:80
  69.  
  70. #HiddenServiceDir C:\Documents and Settings\Application Data\Tor\other_hidden_service/
  71. #HiddenServicePort 80 127.0.0.1:80
  72. #HiddenServicePort 22 127.0.0.1:22
  73.  
  74. ################ This section is just for relays #####################
  75. #
  76. ## See https://www.torproject.org/docs/tor-doc-relay for details.
  77.  
  78. ## A unique handle for your server.
  79. Nickname onesmalltorforman
  80.  
  81. ## The IP or FQDN for your server. Leave commented out and Tor will guess.
  82. #Address noname.example.com
  83.  
  84. ## Define these to limit the bandwidth usage of relayed (server)
  85. ## traffic. Your own traffic is still unthrottled.
  86. ## Note that RelayBandwidthRate must be at least 20 KB.
  87. RelayBandwidthRate 100 KBytes # Throttle traffic to 100KB/s (800Kbps)
  88. RelayBandwidthBurst 200 KBytes # But allow bursts up to 200KB/s (1600Kbps)
  89.  
  90. ## Contact info to be published in the directory, so we can contact you
  91. ## if your server is misconfigured or something else goes wrong.
  92. #ContactInfo Random Person <nobody AT example dot com>
  93. ## You might also include your PGP or GPG fingerprint if you have one:
  94. #ContactInfo 1234D/FFFFFFFF Random Person <nobody AT example dot com>
  95.  
  96. ## Required: what port to advertise for Tor connections.
  97. ORPort 8213
  98. ## If you need to listen on a port other than the one advertised
  99. ## in ORPort (e.g. to advertise 443 but bind to 9090), uncomment the
  100. ## line below too. You'll need to do ipchains or other port forwarding
  101. ## yourself to make this work.
  102. #ORListenAddress 0.0.0.0:9001
  103.  
  104. ## Uncomment this to mirror directory information for others. Please do
  105. ## if you have enough bandwidth.
  106. DirPort 8214 # what port to advertise for directory connections
  107. ## If you need to listen on a port other than the one advertised
  108. ## in DirPort (e.g. to advertise 80 but bind to 9091), uncomment the line
  109. ## below too. You'll need to do ipchains or other port forwarding yourself
  110. ## to make this work.
  111. #DirListenAddress 0.0.0.0:9030
  112.  
  113. ## Uncomment this if you run more than one Tor server, and add the
  114. ## nickname of each Tor server you control, even if they're on different
  115. ## networks. You declare it here so Tor clients can avoid using more than
  116. ## one of your servers in a single circuit. See
  117. ## http://wiki.noreply.org/noreply/TheOnionRouter/TorFAQ#MultipleServers
  118. #MyFamily nickname1,nickname2,...
  119.  
  120. ## A comma-separated list of exit policies. They're considered first
  121. ## to last, and the first match wins. If you want to _replace_
  122. ## the default exit policy, end this with either a reject *:* or an
  123. ## accept *:*. Otherwise, you're _augmenting_ (prepending to) the
  124. ## default exit policy. Leave commented to just use the default, which is
  125. ## available in the man page or at https://www.torproject.org/documentation.html
  126. ##
  127. ## Look at https://www.torproject.org/faq-abuse.html#TypicalAbuses
  128. ## for issues you might encounter if you use the default exit policy.
  129. ##
  130. ## If certain IPs and ports are blocked externally, e.g. by your firewall,
  131. ## you should update your exit policy to reflect this -- otherwise Tor
  132. ## users will be told that those destinations are down.
  133. ##
  134. #ExitPolicy accept *:6660-6667,reject *:* # allow irc ports but no more
  135. #ExitPolicy accept *:119 # accept nntp as well as default exit policy
  136. #ExitPolicy reject *:* # no exits allowed
  137. #
  138. ################ This section is just for bridge relays ##############
  139. #
  140. ## Bridge relays (or "bridges" ) are Tor relays that aren't listed in the
  141. ## main directory. Since there is no complete public list of them, even if an
  142. ## ISP is filtering connections to all the known Tor relays, they probably
  143. ## won't be able to block all the bridges. Unlike running an exit relay,
  144. ## running a bridge relay just passes data to and from the Tor network --
  145. ## so it shouldn't expose the operator to abuse complaints.
  146.  
  147. #ORPort 443
  148. #BridgeRelay 1
  149. #RelayBandwidthRate 50KBytes
  150. #ExitPolicy reject *:*
RAW Paste Data