tor.1.txt 106 KB

12345678910111213141516171819202122232425262728293031323334353637383940414243444546474849505152535455565758596061626364656667686970717273747576777879808182838485868788899091929394959697989910010110210310410510610710810911011111211311411511611711811912012112212312412512612712812913013113213313413513613713813914014114214314414514614714814915015115215315415515615715815916016116216316416516616716816917017117217317417517617717817918018118218318418518618718818919019119219319419519619719819920020120220320420520620720820921021121221321421521621721821922022122222322422522622722822923023123223323423523623723823924024124224324424524624724824925025125225325425525625725825926026126226326426526626726826927027127227327427527627727827928028128228328428528628728828929029129229329429529629729829930030130230330430530630730830931031131231331431531631731831932032132232332432532632732832933033133233333433533633733833934034134234334434534634734834935035135235335435535635735835936036136236336436536636736836937037137237337437537637737837938038138238338438538638738838939039139239339439539639739839940040140240340440540640740840941041141241341441541641741841942042142242342442542642742842943043143243343443543643743843944044144244344444544644744844945045145245345445545645745845946046146246346446546646746846947047147247347447547647747847948048148248348448548648748848949049149249349449549649749849950050150250350450550650750850951051151251351451551651751851952052152252352452552652752852953053153253353453553653753853954054154254354454554654754854955055155255355455555655755855956056156256356456556656756856957057157257357457557657757857958058158258358458558658758858959059159259359459559659759859960060160260360460560660760860961061161261361461561661761861962062162262362462562662762862963063163263363463563663763863964064164264364464564664764864965065165265365465565665765865966066166266366466566666766866967067167267367467567667767867968068168268368468568668768868969069169269369469569669769869970070170270370470570670770870971071171271371471571671771871972072172272372472572672772872973073173273373473573673773873974074174274374474574674774874975075175275375475575675775875976076176276376476576676776876977077177277377477577677777877978078178278378478578678778878979079179279379479579679779879980080180280380480580680780880981081181281381481581681781881982082182282382482582682782882983083183283383483583683783883984084184284384484584684784884985085185285385485585685785885986086186286386486586686786886987087187287387487587687787887988088188288388488588688788888989089189289389489589689789889990090190290390490590690790890991091191291391491591691791891992092192292392492592692792892993093193293393493593693793893994094194294394494594694794894995095195295395495595695795895996096196296396496596696796896997097197297397497597697797897998098198298398498598698798898999099199299399499599699799899910001001100210031004100510061007100810091010101110121013101410151016101710181019102010211022102310241025102610271028102910301031103210331034103510361037103810391040104110421043104410451046104710481049105010511052105310541055105610571058105910601061106210631064106510661067106810691070107110721073107410751076107710781079108010811082108310841085108610871088108910901091109210931094109510961097109810991100110111021103110411051106110711081109111011111112111311141115111611171118111911201121112211231124112511261127112811291130113111321133113411351136113711381139114011411142114311441145114611471148114911501151115211531154115511561157115811591160116111621163116411651166116711681169117011711172117311741175117611771178117911801181118211831184118511861187118811891190119111921193119411951196119711981199120012011202120312041205120612071208120912101211121212131214121512161217121812191220122112221223122412251226122712281229123012311232123312341235123612371238123912401241124212431244124512461247124812491250125112521253125412551256125712581259126012611262126312641265126612671268126912701271127212731274127512761277127812791280128112821283128412851286128712881289129012911292129312941295129612971298129913001301130213031304130513061307130813091310131113121313131413151316131713181319132013211322132313241325132613271328132913301331133213331334133513361337133813391340134113421343134413451346134713481349135013511352135313541355135613571358135913601361136213631364136513661367136813691370137113721373137413751376137713781379138013811382138313841385138613871388138913901391139213931394139513961397139813991400140114021403140414051406140714081409141014111412141314141415141614171418141914201421142214231424142514261427142814291430143114321433143414351436143714381439144014411442144314441445144614471448144914501451145214531454145514561457145814591460146114621463146414651466146714681469147014711472147314741475147614771478147914801481148214831484148514861487148814891490149114921493149414951496149714981499150015011502150315041505150615071508150915101511151215131514151515161517151815191520152115221523152415251526152715281529153015311532153315341535153615371538153915401541154215431544154515461547154815491550155115521553155415551556155715581559156015611562156315641565156615671568156915701571157215731574157515761577157815791580158115821583158415851586158715881589159015911592159315941595159615971598159916001601160216031604160516061607160816091610161116121613161416151616161716181619162016211622162316241625162616271628162916301631163216331634163516361637163816391640164116421643164416451646164716481649165016511652165316541655165616571658165916601661166216631664166516661667166816691670167116721673167416751676167716781679168016811682168316841685168616871688168916901691169216931694169516961697169816991700170117021703170417051706170717081709171017111712171317141715171617171718171917201721172217231724172517261727172817291730173117321733173417351736173717381739174017411742174317441745174617471748174917501751175217531754175517561757175817591760176117621763176417651766176717681769177017711772177317741775177617771778177917801781178217831784178517861787178817891790179117921793179417951796179717981799180018011802180318041805180618071808180918101811181218131814181518161817181818191820182118221823182418251826182718281829183018311832183318341835183618371838183918401841184218431844184518461847184818491850185118521853185418551856185718581859186018611862186318641865186618671868186918701871187218731874187518761877187818791880188118821883188418851886188718881889189018911892189318941895189618971898189919001901190219031904190519061907190819091910191119121913191419151916191719181919192019211922192319241925192619271928192919301931193219331934193519361937193819391940194119421943194419451946194719481949195019511952195319541955195619571958195919601961196219631964196519661967196819691970197119721973197419751976197719781979198019811982198319841985198619871988198919901991199219931994199519961997199819992000200120022003200420052006200720082009201020112012201320142015201620172018201920202021202220232024202520262027202820292030203120322033203420352036203720382039204020412042204320442045204620472048204920502051205220532054205520562057205820592060206120622063206420652066206720682069207020712072207320742075207620772078207920802081208220832084208520862087208820892090209120922093209420952096209720982099210021012102210321042105210621072108210921102111211221132114211521162117211821192120212121222123212421252126212721282129213021312132213321342135213621372138213921402141214221432144214521462147214821492150
  1. // Copyright (c) The Tor Project, Inc.
  2. // See LICENSE for licensing information
  3. // This is an asciidoc file used to generate the manpage/html reference.
  4. // Learn asciidoc on http://www.methods.co.nz/asciidoc/userguide.html
  5. :man source: Tor
  6. :man manual: Tor Manual
  7. TOR(1)
  8. ======
  9. NAME
  10. ----
  11. tor - The second-generation onion router
  12. SYNOPSIS
  13. --------
  14. **tor** [__OPTION__ __value__]...
  15. DESCRIPTION
  16. -----------
  17. __tor__ is a connection-oriented anonymizing communication
  18. service. Users choose a source-routed path through a set of nodes, and
  19. negotiate a "virtual circuit" through the network, in which each node
  20. knows its predecessor and successor, but no others. Traffic flowing down
  21. the circuit is unwrapped by a symmetric key at each node, which reveals
  22. the downstream node. +
  23. Basically __tor__ provides a distributed network of servers ("onion routers").
  24. Users bounce their TCP streams -- web traffic, ftp, ssh, etc -- around the
  25. routers, and recipients, observers, and even the routers themselves have
  26. difficulty tracking the source of the stream.
  27. COMMAND-LINE OPTIONS
  28. --------------------
  29. **-h**, **-help**::
  30. Display a short help message and exit.
  31. **-f** __FILE__::
  32. Specify a new configuration file to contain further Tor configuration
  33. options. (Default: $HOME/.torrc, or @CONFDIR@/torrc if that file is not
  34. found)
  35. **--defaults-torrc** __FILE__::
  36. Specify a file in which to find default values for Tor options. The
  37. contents of this file are overridden by those in the regular
  38. configuration file, and by those on the command line. (Default:
  39. @CONFDIR@/torrc-defaults.)
  40. **--hash-password**::
  41. Generates a hashed password for control port access.
  42. **--list-fingerprint**::
  43. Generate your keys and output your nickname and fingerprint.
  44. **--verify-config**::
  45. Verify the configuration file is valid.
  46. **--service install** [**--options** __command-line options__]::
  47. Install an instance of Tor as a Windows service, with the provided
  48. command-line options. Current instructions can be found at
  49. https://trac.torproject.org/projects/tor/wiki/doc/TorFAQ#HowdoIrunmyTorrelayasanNTservice
  50. **--service** **remove**|**start**|**stop**::
  51. Remove, start, or stop a configured Tor Windows service.
  52. **--nt-service**::
  53. Used internally to implement a Windows service.
  54. **--list-torrc-options**::
  55. List all valid options.
  56. **--version**::
  57. Display Tor version and exit.
  58. **--quiet**|**--hush**::
  59. Override the default console log. By default, Tor starts out logging
  60. messages at level "notice" and higher to the console. It stops doing so
  61. after it parses its configuration, if the configuration tells it to log
  62. anywhere else. You can override this behavior with the **--hush** option,
  63. which tells Tor to only send warnings and errors to the console, or with
  64. the **--quiet** option, which tells Tor not to log to the console at all.
  65. Other options can be specified on the command-line in the format "--option
  66. value", in the format "option value", or in a configuration file. For
  67. instance, you can tell Tor to start listening for SOCKS connections on port
  68. 9999 by passing --SOCKSPort 9999 or SOCKSPort 9999 to it on the command line,
  69. or by putting "SOCKSPort 9999" in the configuration file. You will need to
  70. quote options with spaces in them: if you want Tor to log all debugging
  71. messages to debug.log, you will probably need to say --Log 'debug file
  72. debug.log'.
  73. Options on the command line override those in configuration files. See the
  74. next section for more information.
  75. THE CONFIGURATION FILE FORMAT
  76. -----------------------------
  77. All configuration options in a configuration are written on a single line by
  78. default. They take the form of an option name and a value, or an option name
  79. and a quoted value (option value or option "value"). Anything after a #
  80. character is treated as a comment. Options are
  81. case-insensitive. C-style escaped characters are allowed inside quoted
  82. values. To split one configuration entry into multiple lines, use a single
  83. backslash character (\) before the end of the line. Comments can be used in
  84. such multiline entries, but they must start at the beginning of a line.
  85. By default, an option on the command line overrides an option found in the
  86. configuration file, and an option in a configuration file overrides one in
  87. the defaults file.
  88. This rule is simple for options that take a single value, but it can become
  89. complicated for options that are allowed to occur more than once: if you
  90. specify four SOCKSPorts in your configuration file, and one more SOCKSPort on
  91. the command line, the option on the command line will replace __all__ of the
  92. SOCKSPorts in the configuration file. If this isn't what you want, prefix
  93. the option name with a plus sign, and it will be appended to the previous set
  94. of options instead.
  95. Alternatively, you might want to remove every instance of an option in the
  96. configuration file, and not replace it at all: you might want to say on the
  97. command line that you want no SOCKSPorts at all. To do that, prefix the
  98. option name with a forward slash.
  99. GENERAL OPTIONS
  100. ---------------
  101. **BandwidthRate** __N__ **bytes**|**KBytes**|**MBytes**|**GBytes**::
  102. A token bucket limits the average incoming bandwidth usage on this node to
  103. the specified number of bytes per second, and the average outgoing
  104. bandwidth usage to that same value. If you want to run a relay in the
  105. public network, this needs to be _at the very least_ 30 KBytes (that is,
  106. 30720 bytes). (Default: 1 GByte)
  107. **BandwidthBurst** __N__ **bytes**|**KBytes**|**MBytes**|**GBytes**::
  108. Limit the maximum token bucket size (also known as the burst) to the given
  109. number of bytes in each direction. (Default: 1 GByte)
  110. **MaxAdvertisedBandwidth** __N__ **bytes**|**KBytes**|**MBytes**|**GBytes**::
  111. If set, we will not advertise more than this amount of bandwidth for our
  112. BandwidthRate. Server operators who want to reduce the number of clients
  113. who ask to build circuits through them (since this is proportional to
  114. advertised bandwidth rate) can thus reduce the CPU demands on their server
  115. without impacting network performance.
  116. **RelayBandwidthRate** __N__ **bytes**|**KBytes**|**MBytes**|**GBytes**::
  117. If not 0, a separate token bucket limits the average incoming bandwidth
  118. usage for \_relayed traffic_ on this node to the specified number of bytes
  119. per second, and the average outgoing bandwidth usage to that same value.
  120. Relayed traffic currently is calculated to include answers to directory
  121. requests, but that may change in future versions. (Default: 0)
  122. **RelayBandwidthBurst** __N__ **bytes**|**KBytes**|**MBytes**|**GBytes**::
  123. If not 0, limit the maximum token bucket size (also known as the burst) for
  124. \_relayed traffic_ to the given number of bytes in each direction.
  125. (Default: 0)
  126. **PerConnBWRate** __N__ **bytes**|**KBytes**|**MBytes**|**GBytes**::
  127. If set, do separate rate limiting for each connection from a non-relay.
  128. You should never need to change this value, since a network-wide value is
  129. published in the consensus and your relay will use that value. (Default: 0)
  130. **PerConnBWBurst** __N__ **bytes**|**KBytes**|**MBytes**|**GBytes**::
  131. If set, do separate rate limiting for each connection from a non-relay.
  132. You should never need to change this value, since a network-wide value is
  133. published in the consensus and your relay will use that value. (Default: 0)
  134. **ClientTransportPlugin** __transport__ socks4|socks5 __IP__:__PORT__::
  135. **ClientTransportPlugin** __transport__ exec __path-to-binary__ [options]::
  136. In its first form, when set along with a corresponding Bridge line, the Tor
  137. client forwards its traffic to a SOCKS-speaking proxy on "IP:PORT". It's the
  138. duty of that proxy to properly forward the traffic to the bridge. +
  139. +
  140. In its second form, when set along with a corresponding Bridge line, the Tor
  141. client launches the pluggable transport proxy executable in
  142. __path-to-binary__ using __options__ as its command-line options, and
  143. forwards its traffic to it. It's the duty of that proxy to properly forward
  144. the traffic to the bridge.
  145. **ServerTransportPlugin** __transport__ exec __path-to-binary__ [options]::
  146. The Tor relay launches the pluggable transport proxy in __path-to-binary__
  147. using __options__ as its command-line options, and expects to receive
  148. proxied client traffic from it.
  149. **ServerTransportListenAddr** __transport__ __IP__:__PORT__::
  150. When this option is set, Tor will suggest __IP__:__PORT__ as the
  151. listening address of any pluggable transport proxy that tries to
  152. launch __transport__.
  153. **ConnLimit** __NUM__::
  154. The minimum number of file descriptors that must be available to the Tor
  155. process before it will start. Tor will ask the OS for as many file
  156. descriptors as the OS will allow (you can find this by "ulimit -H -n").
  157. If this number is less than ConnLimit, then Tor will refuse to start. +
  158. +
  159. You probably don't need to adjust this. It has no effect on Windows
  160. since that platform lacks getrlimit(). (Default: 1000)
  161. **DisableNetwork** **0**|**1**::
  162. When this option is set, we don't listen for or accept any connections
  163. other than controller connections, and we don't make any outbound
  164. connections. Controllers sometimes use this option to avoid using
  165. the network until Tor is fully configured. (Default: 0)
  166. **ConstrainedSockets** **0**|**1**::
  167. If set, Tor will tell the kernel to attempt to shrink the buffers for all
  168. sockets to the size specified in **ConstrainedSockSize**. This is useful for
  169. virtual servers and other environments where system level TCP buffers may
  170. be limited. If you're on a virtual server, and you encounter the "Error
  171. creating network socket: No buffer space available" message, you are
  172. likely experiencing this problem. +
  173. +
  174. The preferred solution is to have the admin increase the buffer pool for
  175. the host itself via /proc/sys/net/ipv4/tcp_mem or equivalent facility;
  176. this configuration option is a second-resort. +
  177. +
  178. The DirPort option should also not be used if TCP buffers are scarce. The
  179. cached directory requests consume additional sockets which exacerbates
  180. the problem. +
  181. +
  182. You should **not** enable this feature unless you encounter the "no buffer
  183. space available" issue. Reducing the TCP buffers affects window size for
  184. the TCP stream and will reduce throughput in proportion to round trip
  185. time on long paths. (Default: 0)
  186. **ConstrainedSockSize** __N__ **bytes**|**KBytes**::
  187. When **ConstrainedSockets** is enabled the receive and transmit buffers for
  188. all sockets will be set to this limit. Must be a value between 2048 and
  189. 262144, in 1024 byte increments. Default of 8192 is recommended.
  190. **ControlPort** __PORT__|**auto**::
  191. If set, Tor will accept connections on this port and allow those
  192. connections to control the Tor process using the Tor Control Protocol
  193. (described in control-spec.txt). Note: unless you also specify one or
  194. more of **HashedControlPassword** or **CookieAuthentication**,
  195. setting this option will cause Tor to allow any process on the local
  196. host to control it. (Setting both authentication methods means either
  197. method is sufficient to authenticate to Tor.) This
  198. option is required for many Tor controllers; most use the value of 9051.
  199. Set it to "auto" to have Tor pick a port for you. (Default: 0)
  200. **ControlListenAddress** __IP__[:__PORT__]::
  201. Bind the controller listener to this address. If you specify a port, bind
  202. to this port rather than the one specified in ControlPort. We strongly
  203. recommend that you leave this alone unless you know what you're doing,
  204. since giving attackers access to your control listener is really
  205. dangerous. This directive can be specified multiple
  206. times to bind to multiple addresses/ports. (Default: 127.0.0.1)
  207. **ControlSocket** __Path__::
  208. Like ControlPort, but listens on a Unix domain socket, rather than a TCP
  209. socket. (Unix and Unix-like systems only.)
  210. **ControlSocketsGroupWritable** **0**|**1**::
  211. If this option is set to 0, don't allow the filesystem group to read and
  212. write unix sockets (e.g. ControlSocket). If the option is set to 1, make
  213. the control socket readable and writable by the default GID. (Default: 0)
  214. **HashedControlPassword** __hashed_password__::
  215. Allow connections on the control port if they present
  216. the password whose one-way hash is __hashed_password__. You
  217. can compute the hash of a password by running "tor --hash-password
  218. __password__". You can provide several acceptable passwords by using more
  219. than one HashedControlPassword line.
  220. **CookieAuthentication** **0**|**1**::
  221. If this option is set to 1, allow connections on the control port
  222. when the connecting process knows the contents of a file named
  223. "control_auth_cookie", which Tor will create in its data directory. This
  224. authentication method should only be used on systems with good filesystem
  225. security. (Default: 0)
  226. **CookieAuthFile** __Path__::
  227. If set, this option overrides the default location and file name
  228. for Tor's cookie file. (See CookieAuthentication above.)
  229. **CookieAuthFileGroupReadable** **0**|**1**|__Groupname__::
  230. If this option is set to 0, don't allow the filesystem group to read the
  231. cookie file. If the option is set to 1, make the cookie file readable by
  232. the default GID. [Making the file readable by other groups is not yet
  233. implemented; let us know if you need this for some reason.] (Default: 0)
  234. **ControlPortWriteToFile** __Path__::
  235. If set, Tor writes the address and port of any control port it opens to
  236. this address. Usable by controllers to learn the actual control port
  237. when ControlPort is set to "auto".
  238. **ControlPortFileGroupReadable** **0**|**1**::
  239. If this option is set to 0, don't allow the filesystem group to read the
  240. control port file. If the option is set to 1, make the control port
  241. file readable by the default GID. (Default: 0)
  242. **DataDirectory** __DIR__::
  243. Store working data in DIR (Default: @LOCALSTATEDIR@/lib/tor)
  244. **FallbackDir** __address__:__port__ orport=__port__ id=__fingerprint__ [weight=__num__]::
  245. When we're unable to connect to any directory cache for directory info
  246. (usually because we don't know about any yet) we try a FallbackDir.
  247. By default, the directory authorities are also FallbackDirs.
  248. **DirAuthority** [__nickname__] [**flags**] __address__:__port__ __fingerprint__::
  249. Use a nonstandard authoritative directory server at the provided address
  250. and port, with the specified key fingerprint. This option can be repeated
  251. many times, for multiple authoritative directory servers. Flags are
  252. separated by spaces, and determine what kind of an authority this directory
  253. is. By default, every authority is authoritative for current ("v2")-style
  254. directories, unless the "no-v2" flag is given. If the "v1" flags is
  255. provided, Tor will use this server as an authority for old-style (v1)
  256. directories as well. (Only directory mirrors care about this.) Tor will
  257. use this server as an authority for hidden service information if the "hs"
  258. flag is set, or if the "v1" flag is set and the "no-hs" flag is **not** set.
  259. Tor will use this authority as a bridge authoritative directory if the
  260. "bridge" flag is set. If a flag "orport=**port**" is given, Tor will use the
  261. given port when opening encrypted tunnels to the dirserver. If a flag
  262. "weight=**num**" is given, then the directory server is chosen randomly
  263. with probability proportional to that weight (default 1.0). Lastly, if a
  264. flag "v3ident=**fp**" is given, the dirserver is a v3 directory authority
  265. whose v3 long-term signing key has the fingerprint **fp**. +
  266. +
  267. If no **DirAuthority** line is given, Tor will use the default directory
  268. authorities. NOTE: this option is intended for setting up a private Tor
  269. network with its own directory authorities. If you use it, you will be
  270. distinguishable from other users, because you won't believe the same
  271. authorities they do.
  272. **DirAuthorityFallbackRate** __NUM__::
  273. When configured to use both directory authorities and fallback
  274. directories, the directory authorities also work as fallbacks. They are
  275. chosen with their regular weights, multiplied by this number, which
  276. should be 1.0 or less. (Default: 1.0)
  277. **DynamicDHGroups** **0**|**1**::
  278. If this option is set to 1, when running as a server, generate our
  279. own Diffie-Hellman group instead of using the one from Apache's mod_ssl.
  280. This option may help circumvent censorship based on static
  281. Diffie-Hellman parameters. (Default: 0)
  282. **AlternateDirAuthority** [__nickname__] [**flags**] __address__:__port__ __fingerprint__ +
  283. **AlternateHSAuthority** [__nickname__] [**flags**] __address__:__port__ __fingerprint__ +
  284. **AlternateBridgeAuthority** [__nickname__] [**flags**] __address__:__port__ __ fingerprint__::
  285. These options behave as DirAuthority, but they replace fewer of the
  286. default directory authorities. Using
  287. AlternateDirAuthority replaces the default Tor directory authorities, but
  288. leaves the default hidden service authorities and bridge authorities in
  289. place. Similarly, AlternateHSAuthority replaces the default hidden
  290. service authorities, but not the directory or bridge authorities; and
  291. AlternateBridgeAuthority replaces the default bridge authority,
  292. but leaves the directory and hidden service authorities alone.
  293. **DisableAllSwap** **0**|**1**::
  294. If set to 1, Tor will attempt to lock all current and future memory pages,
  295. so that memory cannot be paged out. Windows, OS X and Solaris are currently
  296. not supported. We believe that this feature works on modern Gnu/Linux
  297. distributions, and that it should work on *BSD systems (untested). This
  298. option requires that you start your Tor as root, and you should use the
  299. **User** option to properly reduce Tor's privileges. (Default: 0)
  300. **DisableDebuggerAttachment** **0**|**1**::
  301. If set to 1, Tor will attempt to prevent basic debugging attachment attempts
  302. by other processes. It has no impact for users who wish to attach if they
  303. have CAP_SYS_PTRACE or if they are root. We believe that this feature
  304. works on modern Gnu/Linux distributions, and that it may also work on *BSD
  305. systems (untested). Some modern Gnu/Linux systems such as Ubuntu have the
  306. kernel.yama.ptrace_scope sysctl and by default enable it as an attempt to
  307. limit the PTRACE scope for all user processes by default. This feature will
  308. attempt to limit the PTRACE scope for Tor specifically - it will not attempt
  309. to alter the system wide ptrace scope as it may not even exist. If you wish
  310. to attach to Tor with a debugger such as gdb or strace you will want to set
  311. this to 0 for the duration of your debugging. Normal users should leave it
  312. on. Disabling this option while Tor is running is prohibited. (Default: 1)
  313. **FetchDirInfoEarly** **0**|**1**::
  314. If set to 1, Tor will always fetch directory information like other
  315. directory caches, even if you don't meet the normal criteria for fetching
  316. early. Normal users should leave it off. (Default: 0)
  317. **FetchDirInfoExtraEarly** **0**|**1**::
  318. If set to 1, Tor will fetch directory information before other directory
  319. caches. It will attempt to download directory information closer to the
  320. start of the consensus period. Normal users should leave it off.
  321. (Default: 0)
  322. **FetchHidServDescriptors** **0**|**1**::
  323. If set to 0, Tor will never fetch any hidden service descriptors from the
  324. rendezvous directories. This option is only useful if you're using a Tor
  325. controller that handles hidden service fetches for you. (Default: 1)
  326. **FetchServerDescriptors** **0**|**1**::
  327. If set to 0, Tor will never fetch any network status summaries or server
  328. descriptors from the directory servers. This option is only useful if
  329. you're using a Tor controller that handles directory fetches for you.
  330. (Default: 1)
  331. **FetchUselessDescriptors** **0**|**1**::
  332. If set to 1, Tor will fetch every non-obsolete descriptor from the
  333. authorities that it hears about. Otherwise, it will avoid fetching useless
  334. descriptors, for example for routers that are not running. This option is
  335. useful if you're using the contributed "exitlist" script to enumerate Tor
  336. nodes that exit to certain addresses. (Default: 0)
  337. **HTTPProxy** __host__[:__port__]::
  338. Tor will make all its directory requests through this host:port (or host:80
  339. if port is not specified), rather than connecting directly to any directory
  340. servers.
  341. **HTTPProxyAuthenticator** __username:password__::
  342. If defined, Tor will use this username:password for Basic HTTP proxy
  343. authentication, as in RFC 2617. This is currently the only form of HTTP
  344. proxy authentication that Tor supports; feel free to submit a patch if you
  345. want it to support others.
  346. **HTTPSProxy** __host__[:__port__]::
  347. Tor will make all its OR (SSL) connections through this host:port (or
  348. host:443 if port is not specified), via HTTP CONNECT rather than connecting
  349. directly to servers. You may want to set **FascistFirewall** to restrict
  350. the set of ports you might try to connect to, if your HTTPS proxy only
  351. allows connecting to certain ports.
  352. **HTTPSProxyAuthenticator** __username:password__::
  353. If defined, Tor will use this username:password for Basic HTTPS proxy
  354. authentication, as in RFC 2617. This is currently the only form of HTTPS
  355. proxy authentication that Tor supports; feel free to submit a patch if you
  356. want it to support others.
  357. **Socks4Proxy** __host__[:__port__]::
  358. Tor will make all OR connections through the SOCKS 4 proxy at host:port
  359. (or host:1080 if port is not specified).
  360. **Socks5Proxy** __host__[:__port__]::
  361. Tor will make all OR connections through the SOCKS 5 proxy at host:port
  362. (or host:1080 if port is not specified).
  363. **Socks5ProxyUsername** __username__ +
  364. **Socks5ProxyPassword** __password__::
  365. If defined, authenticate to the SOCKS 5 server using username and password
  366. in accordance to RFC 1929. Both username and password must be between 1 and
  367. 255 characters.
  368. **KeepalivePeriod** __NUM__::
  369. To keep firewalls from expiring connections, send a padding keepalive cell
  370. every NUM seconds on open connections that are in use. If the connection
  371. has no open circuits, it will instead be closed after NUM seconds of
  372. idleness. (Default: 5 minutes)
  373. **Log** __minSeverity__[-__maxSeverity__] **stderr**|**stdout**|**syslog**::
  374. Send all messages between __minSeverity__ and __maxSeverity__ to the standard
  375. output stream, the standard error stream, or to the system log. (The
  376. "syslog" value is only supported on Unix.) Recognized severity levels are
  377. debug, info, notice, warn, and err. We advise using "notice" in most cases,
  378. since anything more verbose may provide sensitive information to an
  379. attacker who obtains the logs. If only one severity level is given, all
  380. messages of that level or higher will be sent to the listed destination.
  381. **Log** __minSeverity__[-__maxSeverity__] **file** __FILENAME__::
  382. As above, but send log messages to the listed filename. The
  383. "Log" option may appear more than once in a configuration file.
  384. Messages are sent to all the logs that match their severity
  385. level.
  386. **Log** **[**__domain__,...**]**__minSeverity__[-__maxSeverity__] ... **file** __FILENAME__ +
  387. **Log** **[**__domain__,...**]**__minSeverity__[-__maxSeverity__] ... **stderr**|**stdout**|**syslog**::
  388. As above, but select messages by range of log severity __and__ by a
  389. set of "logging domains". Each logging domain corresponds to an area of
  390. functionality inside Tor. You can specify any number of severity ranges
  391. for a single log statement, each of them prefixed by a comma-separated
  392. list of logging domains. You can prefix a domain with $$~$$ to indicate
  393. negation, and use * to indicate "all domains". If you specify a severity
  394. range without a list of domains, it matches all domains. +
  395. +
  396. This is an advanced feature which is most useful for debugging one or two
  397. of Tor's subsystems at a time. +
  398. +
  399. The currently recognized domains are: general, crypto, net, config, fs,
  400. protocol, mm, http, app, control, circ, rend, bug, dir, dirserv, or, edge,
  401. acct, hist, and handshake. Domain names are case-insensitive. +
  402. +
  403. For example, "`Log [handshake]debug [~net,~mm]info notice stdout`" sends
  404. to stdout: all handshake messages of any severity, all info-and-higher
  405. messages from domains other than networking and memory management, and all
  406. messages of severity notice or higher.
  407. **LogMessageDomains** **0**|**1**::
  408. If 1, Tor includes message domains with each log message. Every log
  409. message currently has at least one domain; most currently have exactly
  410. one. This doesn't affect controller log messages. (Default: 0)
  411. **OutboundBindAddress** __IP__::
  412. Make all outbound connections originate from the IP address specified. This
  413. is only useful when you have multiple network interfaces, and you want all
  414. of Tor's outgoing connections to use a single one. This option may
  415. be used twice, once with an IPv4 address and once with an IPv6 address.
  416. This setting will be ignored for connections to the loopback addresses
  417. (127.0.0.0/8 and ::1).
  418. **PidFile** __FILE__::
  419. On startup, write our PID to FILE. On clean shutdown, remove
  420. FILE.
  421. **ProtocolWarnings** **0**|**1**::
  422. If 1, Tor will log with severity \'warn' various cases of other parties not
  423. following the Tor specification. Otherwise, they are logged with severity
  424. \'info'. (Default: 0)
  425. **RunAsDaemon** **0**|**1**::
  426. If 1, Tor forks and daemonizes to the background. This option has no effect
  427. on Windows; instead you should use the --service command-line option.
  428. (Default: 0)
  429. **LogTimeGranularity** __NUM__::
  430. Set the resolution of timestamps in Tor's logs to NUM milliseconds.
  431. NUM must be positive and either a divisor or a multiple of 1 second.
  432. Note that this option only controls the granularity written by Tor to
  433. a file or console log. Tor does not (for example) "batch up" log
  434. messages to affect times logged by a controller, times attached to
  435. syslog messages, or the mtime fields on log files. (Default: 1 second)
  436. **SafeLogging** **0**|**1**|**relay**::
  437. Tor can scrub potentially sensitive strings from log messages (e.g.
  438. addresses) by replacing them with the string [scrubbed]. This way logs can
  439. still be useful, but they don't leave behind personally identifying
  440. information about what sites a user might have visited. +
  441. +
  442. If this option is set to 0, Tor will not perform any scrubbing, if it is
  443. set to 1, all potentially sensitive strings are replaced. If it is set to
  444. relay, all log messages generated when acting as a relay are sanitized, but
  445. all messages generated when acting as a client are not. (Default: 1)
  446. **User** __UID__::
  447. On startup, setuid to this user and setgid to their primary group.
  448. **HardwareAccel** **0**|**1**::
  449. If non-zero, try to use built-in (static) crypto hardware acceleration when
  450. available. (Default: 0)
  451. **AccelName** __NAME__::
  452. When using OpenSSL hardware crypto acceleration attempt to load the dynamic
  453. engine of this name. This must be used for any dynamic hardware engine.
  454. Names can be verified with the openssl engine command.
  455. **AccelDir** __DIR__::
  456. Specify this option if using dynamic hardware acceleration and the engine
  457. implementation library resides somewhere other than the OpenSSL default.
  458. **AvoidDiskWrites** **0**|**1**::
  459. If non-zero, try to write to disk less frequently than we would otherwise.
  460. This is useful when running on flash memory or other media that support
  461. only a limited number of writes. (Default: 0)
  462. **TunnelDirConns** **0**|**1**::
  463. If non-zero, when a directory server we contact supports it, we will build
  464. a one-hop circuit and make an encrypted connection via its ORPort.
  465. (Default: 1)
  466. **PreferTunneledDirConns** **0**|**1**::
  467. If non-zero, we will avoid directory servers that don't support tunneled
  468. directory connections, when possible. (Default: 1)
  469. **CircuitPriorityHalflife** __NUM1__::
  470. If this value is set, we override the default algorithm for choosing which
  471. circuit's cell to deliver or relay next. When the value is 0, we
  472. round-robin between the active circuits on a connection, delivering one
  473. cell from each in turn. When the value is positive, we prefer delivering
  474. cells from whichever connection has the lowest weighted cell count, where
  475. cells are weighted exponentially according to the supplied
  476. CircuitPriorityHalflife value (in seconds). If this option is not set at
  477. all, we use the behavior recommended in the current consensus
  478. networkstatus. This is an advanced option; you generally shouldn't have
  479. to mess with it. (Default: not set)
  480. **DisableIOCP** **0**|**1**::
  481. If Tor was built to use the Libevent's "bufferevents" networking code
  482. and you're running on Windows, setting this option to 1 will tell Libevent
  483. not to use the Windows IOCP networking API. (Default: 1)
  484. **UserspaceIOCPBuffers** **0**|**1**::
  485. If IOCP is enabled (see DisableIOCP above), setting this option to 1
  486. will tell Tor to disable kernel-space TCP buffers, in order to avoid
  487. needless copy operations and try not to run out of non-paged RAM.
  488. This feature is experimental; don't use it yet unless you're eager to
  489. help tracking down bugs. (Default: 0)
  490. **_UseFilteringSSLBufferevents** **0**|**1**::
  491. Tells Tor to do its SSL communication using a chain of
  492. bufferevents: one for SSL and one for networking. This option has no
  493. effect if bufferevents are disabled (in which case it can't turn on), or
  494. if IOCP bufferevents are enabled (in which case it can't turn off). This
  495. option is useful for debugging only; most users shouldn't touch it.
  496. (Default: 0)
  497. **CountPrivateBandwidth** **0**|**1**::
  498. If this option is set, then Tor's rate-limiting applies not only to
  499. remote connections, but also to connections to private addresses like
  500. 127.0.0.1 or 10.0.0.1. This is mostly useful for debugging
  501. rate-limiting. (Default: 0)
  502. CLIENT OPTIONS
  503. --------------
  504. The following options are useful only for clients (that is, if
  505. **SocksPort**, **TransPort**, **DNSPort**, or **NATDPort** is non-zero):
  506. **AllowInvalidNodes** **entry**|**exit**|**middle**|**introduction**|**rendezvous**|**...**::
  507. If some Tor servers are obviously not working right, the directory
  508. authorities can manually mark them as invalid, meaning that it's not
  509. recommended you use them for entry or exit positions in your circuits. You
  510. can opt to use them in some circuit positions, though. The default is
  511. "middle,rendezvous", and other choices are not advised.
  512. **ExcludeSingleHopRelays** **0**|**1**::
  513. This option controls whether circuits built by Tor will include relays with
  514. the AllowSingleHopExits flag set to true. If ExcludeSingleHopRelays is set
  515. to 0, these relays will be included. Note that these relays might be at
  516. higher risk of being seized or observed, so they are not normally
  517. included. Also note that relatively few clients turn off this option,
  518. so using these relays might make your client stand out.
  519. (Default: 1)
  520. **Bridge** [__transport__] __IP__:__ORPort__ [__fingerprint__]::
  521. When set along with UseBridges, instructs Tor to use the relay at
  522. "IP:ORPort" as a "bridge" relaying into the Tor network. If "fingerprint"
  523. is provided (using the same format as for DirServer), we will verify that
  524. the relay running at that location has the right fingerprint. We also use
  525. fingerprint to look up the bridge descriptor at the bridge authority, if
  526. it's provided and if UpdateBridgesFromAuthority is set too. +
  527. +
  528. If "transport" is provided, and matches to a ClientTransportPlugin
  529. line, we use that pluggable transports proxy to transfer data to
  530. the bridge.
  531. **LearnCircuitBuildTimeout** **0**|**1**::
  532. If 0, CircuitBuildTimeout adaptive learning is disabled. (Default: 1)
  533. **CircuitBuildTimeout** __NUM__::
  534. Try for at most NUM seconds when building circuits. If the circuit isn't
  535. open in that time, give up on it. If LearnCircuitBuildTimeout is 1, this
  536. value serves as the initial value to use before a timeout is learned. If
  537. LearnCircuitBuildTimeout is 0, this value is the only value used.
  538. (Default: 60 seconds)
  539. **CircuitIdleTimeout** __NUM__::
  540. If we have kept a clean (never used) circuit around for NUM seconds, then
  541. close it. This way when the Tor client is entirely idle, it can expire all
  542. of its circuits, and then expire its TLS connections. Also, if we end up
  543. making a circuit that is not useful for exiting any of the requests we're
  544. receiving, it won't forever take up a slot in the circuit list. (Default: 1
  545. hour)
  546. **CircuitStreamTimeout** __NUM__::
  547. If non-zero, this option overrides our internal timeout schedule for how
  548. many seconds until we detach a stream from a circuit and try a new circuit.
  549. If your network is particularly slow, you might want to set this to a
  550. number like 60. (Default: 0)
  551. **ClientOnly** **0**|**1**::
  552. If set to 1, Tor will under no circumstances run as a relay or serve
  553. directory requests. This config option is mostly meaningless: we
  554. added it back when we were considering having Tor clients auto-promote
  555. themselves to being relays if they were stable and fast enough. The
  556. current behavior is simply that Tor is a client unless ORPort or
  557. DirPort are configured. (Default: 0)
  558. **ExcludeNodes** __node__,__node__,__...__::
  559. A list of identity fingerprints, nicknames, country codes and address
  560. patterns of nodes to avoid when building a circuit.
  561. (Example:
  562. ExcludeNodes SlowServer, ABCD1234CDEF5678ABCD1234CDEF5678ABCD1234, \{cc}, 255.254.0.0/8) +
  563. +
  564. By default, this option is treated as a preference that Tor is allowed
  565. to override in order to keep working.
  566. For example, if you try to connect to a hidden service,
  567. but you have excluded all of the hidden service's introduction points,
  568. Tor will connect to one of them anyway. If you do not want this
  569. behavior, set the StrictNodes option (documented below). +
  570. +
  571. Note also that if you are a relay, this (and the other node selection
  572. options below) only affects your own circuits that Tor builds for you.
  573. Clients can still build circuits through you to any node. Controllers
  574. can tell Tor to build circuits through any node. +
  575. +
  576. Country codes are case-insensitive. The code "\{??}" refers to nodes whose
  577. country can't be identified. No country code, including \{??}, works if
  578. no GeoIPFile can be loaded. See also the GeoIPExcludeUnknown option below.
  579. **ExcludeExitNodes** __node__,__node__,__...__::
  580. A list of identity fingerprints, nicknames, country codes and address
  581. patterns of nodes to never use when picking an exit node---that is, a
  582. node that delivers traffic for you outside the Tor network. Note that any
  583. node listed in ExcludeNodes is automatically considered to be part of this
  584. list too. See also the caveats on the "ExitNodes" option below.
  585. **GeoIPExcludeUnknown** **0**|**1**|**auto**::
  586. If this option is set to 'auto', then whenever any country code is set in
  587. ExcludeNodes or ExcludeEntryNodes, all nodes with unknown country (\{??} and
  588. possibly \{A1}) are treated as excluded as well. If this option is set to
  589. '1', then all unknown countries are treated as excluded in ExcludeNodes
  590. and ExcludeEntryNodes. This option has no effect when a GeoIP file isn't
  591. configured or can't be found. (Default: auto)
  592. **ExitNodes** __node__,__node__,__...__::
  593. A list of identity fingerprints, nicknames, country codes and address
  594. patterns of nodes to use as exit node---that is, a
  595. node that delivers traffic for you outside the Tor network. +
  596. +
  597. Note that if you list too few nodes here, or if you exclude too many exit
  598. nodes with ExcludeExitNodes, you can degrade functionality. For example,
  599. if none of the exits you list allows traffic on port 80 or 443, you won't
  600. be able to browse the web. +
  601. +
  602. Note also that not every circuit is used to deliver traffic outside of
  603. the Tor network. It is normal to see non-exit circuits (such as those
  604. used to connect to hidden services, those that do directory fetches,
  605. those used for relay reachability self-tests, and so on) that end
  606. at a non-exit node. To
  607. keep a node from being used entirely, see ExcludeNodes and StrictNodes. +
  608. +
  609. The ExcludeNodes option overrides this option: any node listed in both
  610. ExitNodes and ExcludeNodes is treated as excluded. +
  611. +
  612. The .exit address notation, if enabled via AllowDotExit, overrides
  613. this option.
  614. **EntryNodes** __node__,__node__,__...__::
  615. A list of identity fingerprints, nicknames, and country codes of nodes
  616. to use for the first hop in your normal circuits.
  617. Normal circuits include all
  618. circuits except for direct connections to directory servers. The Bridge
  619. option overrides this option; if you have configured bridges and
  620. UseBridges is 1, the Bridges are used as your entry nodes. +
  621. +
  622. The ExcludeNodes option overrides this option: any node listed in both
  623. EntryNodes and ExcludeNodes is treated as excluded.
  624. **StrictNodes** **0**|**1**::
  625. If StrictNodes is set to 1, Tor will treat the ExcludeNodes option as a
  626. requirement to follow for all the circuits you generate, even if doing so
  627. will break functionality for you. If StrictNodes is set to 0, Tor will
  628. still try to avoid nodes in the ExcludeNodes list, but it will err on the
  629. side of avoiding unexpected errors. Specifically, StrictNodes 0 tells
  630. Tor that it is okay to use an excluded node when it is *necessary* to
  631. perform relay reachability self-tests, connect to
  632. a hidden service, provide a hidden service to a client, fulfill a .exit
  633. request, upload directory information, or download directory information.
  634. (Default: 0)
  635. **FascistFirewall** **0**|**1**::
  636. If 1, Tor will only create outgoing connections to ORs running on ports
  637. that your firewall allows (defaults to 80 and 443; see **FirewallPorts**).
  638. This will allow you to run Tor as a client behind a firewall with
  639. restrictive policies, but will not allow you to run as a server behind such
  640. a firewall. If you prefer more fine-grained control, use
  641. ReachableAddresses instead.
  642. **FirewallPorts** __PORTS__::
  643. A list of ports that your firewall allows you to connect to. Only used when
  644. **FascistFirewall** is set. This option is deprecated; use ReachableAddresses
  645. instead. (Default: 80, 443)
  646. **ReachableAddresses** __ADDR__[/__MASK__][:__PORT__]...::
  647. A comma-separated list of IP addresses and ports that your firewall allows
  648. you to connect to. The format is as for the addresses in ExitPolicy, except
  649. that "accept" is understood unless "reject" is explicitly provided. For
  650. example, \'ReachableAddresses 99.0.0.0/8, reject 18.0.0.0/8:80, accept
  651. \*:80' means that your firewall allows connections to everything inside net
  652. 99, rejects port 80 connections to net 18, and accepts connections to port
  653. 80 otherwise. (Default: \'accept \*:*'.)
  654. **ReachableDirAddresses** __ADDR__[/__MASK__][:__PORT__]...::
  655. Like **ReachableAddresses**, a list of addresses and ports. Tor will obey
  656. these restrictions when fetching directory information, using standard HTTP
  657. GET requests. If not set explicitly then the value of
  658. **ReachableAddresses** is used. If **HTTPProxy** is set then these
  659. connections will go through that proxy.
  660. **ReachableORAddresses** __ADDR__[/__MASK__][:__PORT__]...::
  661. Like **ReachableAddresses**, a list of addresses and ports. Tor will obey
  662. these restrictions when connecting to Onion Routers, using TLS/SSL. If not
  663. set explicitly then the value of **ReachableAddresses** is used. If
  664. **HTTPSProxy** is set then these connections will go through that proxy. +
  665. +
  666. The separation between **ReachableORAddresses** and
  667. **ReachableDirAddresses** is only interesting when you are connecting
  668. through proxies (see **HTTPProxy** and **HTTPSProxy**). Most proxies limit
  669. TLS connections (which Tor uses to connect to Onion Routers) to port 443,
  670. and some limit HTTP GET requests (which Tor uses for fetching directory
  671. information) to port 80.
  672. **HidServAuth** __onion-address__ __auth-cookie__ [__service-name__]::
  673. Client authorization for a hidden service. Valid onion addresses contain 16
  674. characters in a-z2-7 plus ".onion", and valid auth cookies contain 22
  675. characters in A-Za-z0-9+/. The service name is only used for internal
  676. purposes, e.g., for Tor controllers. This option may be used multiple times
  677. for different hidden services. If a hidden service uses authorization and
  678. this option is not set, the hidden service is not accessible. Hidden
  679. services can be configured to require authorization using the
  680. **HiddenServiceAuthorizeClient** option.
  681. **CloseHSClientCircuitsImmediatelyOnTimeout** **0**|**1**::
  682. If 1, Tor will close unfinished hidden service client circuits
  683. which have not moved closer to connecting to their destination
  684. hidden service when their internal state has not changed for the
  685. duration of the current circuit-build timeout. Otherwise, such
  686. circuits will be left open, in the hope that they will finish
  687. connecting to their destination hidden services. In either case,
  688. another set of introduction and rendezvous circuits for the same
  689. destination hidden service will be launched. (Default: 0)
  690. **CloseHSServiceRendCircuitsImmediatelyOnTimeout** **0**|**1**::
  691. If 1, Tor will close unfinished hidden-service-side rendezvous
  692. circuits after the current circuit-build timeout. Otherwise, such
  693. circuits will be left open, in the hope that they will finish
  694. connecting to their destinations. In either case, another
  695. rendezvous circuit for the same destination client will be
  696. launched. (Default: 0)
  697. **LongLivedPorts** __PORTS__::
  698. A list of ports for services that tend to have long-running connections
  699. (e.g. chat and interactive shells). Circuits for streams that use these
  700. ports will contain only high-uptime nodes, to reduce the chance that a node
  701. will go down before the stream is finished. Note that the list is also
  702. honored for circuits (both client and service side) involving hidden
  703. services whose virtual port is in this list. (Default: 21, 22, 706,
  704. 1863, 5050, 5190, 5222, 5223, 6523, 6667, 6697, 8300)
  705. **MapAddress** __address__ __newaddress__::
  706. When a request for address arrives to Tor, it will transform to newaddress
  707. before processing it. For example, if you always want connections to
  708. www.example.com to exit via __torserver__ (where __torserver__ is the
  709. nickname of the server), use "MapAddress www.example.com
  710. www.example.com.torserver.exit". If the value is prefixed with a
  711. "\*.", matches an entire domain. For example, if you
  712. always want connections to example.com and any if its subdomains
  713. to exit via
  714. __torserver__ (where __torserver__ is the nickname of the server), use
  715. "MapAddress \*.example.com \*.example.com.torserver.exit". (Note the
  716. leading "*." in each part of the directive.) You can also redirect all
  717. subdomains of a domain to a single address. For example, "MapAddress
  718. *.example.com www.example.com". +
  719. +
  720. NOTES:
  721. 1. When evaluating MapAddress expressions Tor stops when it hits the most
  722. recently added expression that matches the requested address. So if you
  723. have the following in your torrc, www.torproject.org will map to 1.1.1.1:
  724. MapAddress www.torproject.org 2.2.2.2
  725. MapAddress www.torproject.org 1.1.1.1
  726. 2. Tor evaluates the MapAddress configuration until it finds no matches. So
  727. if you have the following in your torrc, www.torproject.org will map to
  728. 2.2.2.2:
  729. MapAddress 1.1.1.1 2.2.2.2
  730. MapAddress www.torproject.org 1.1.1.1
  731. 3. The following MapAddress expression is invalid (and will be
  732. ignored) because you cannot map from a specific address to a wildcard
  733. address:
  734. MapAddress www.torproject.org *.torproject.org.torserver.exit
  735. 4. Using a wildcard to match only part of a string (as in *ample.com) is
  736. also invalid.
  737. **NewCircuitPeriod** __NUM__::
  738. Every NUM seconds consider whether to build a new circuit. (Default: 30
  739. seconds)
  740. **MaxCircuitDirtiness** __NUM__::
  741. Feel free to reuse a circuit that was first used at most NUM seconds ago,
  742. but never attach a new stream to a circuit that is too old. For hidden
  743. services, this applies to the __last__ time a circuit was used, not the
  744. first. (Default: 10 minutes)
  745. **MaxClientCircuitsPending** __NUM__::
  746. Do not allow more than NUM circuits to be pending at a time for handling
  747. client streams. A circuit is pending if we have begun constructing it,
  748. but it has not yet been completely constructed. (Default: 32)
  749. **NodeFamily** __node__,__node__,__...__::
  750. The Tor servers, defined by their identity fingerprints or nicknames,
  751. constitute a "family" of similar or co-administered servers, so never use
  752. any two of them in the same circuit. Defining a NodeFamily is only needed
  753. when a server doesn't list the family itself (with MyFamily). This option
  754. can be used multiple times. In addition to nodes, you can also list
  755. IP address and ranges and country codes in {curly braces}.
  756. **EnforceDistinctSubnets** **0**|**1**::
  757. If 1, Tor will not put two servers whose IP addresses are "too close" on
  758. the same circuit. Currently, two addresses are "too close" if they lie in
  759. the same /16 range. (Default: 1)
  760. **SOCKSPort** \['address':]__port__|**auto** [_flags_] [_isolation flags_]::
  761. Open this port to listen for connections from SOCKS-speaking
  762. applications. Set this to 0 if you don't want to allow application
  763. connections via SOCKS. Set it to "auto" to have Tor pick a port for
  764. you. This directive can be specified multiple times to bind
  765. to multiple addresses/ports. (Default: 9050) +
  766. +
  767. The _isolation flags_ arguments give Tor rules for which streams
  768. received on this SOCKSPort are allowed to share circuits with one
  769. another. Recognized isolation flags are:
  770. **IsolateClientAddr**;;
  771. Don't share circuits with streams from a different
  772. client address. (On by default and strongly recommended;
  773. you can disable it with **NoIsolateClientAddr**.)
  774. **IsolateSOCKSAuth**;;
  775. Don't share circuits with streams for which different
  776. SOCKS authentication was provided. (On by default;
  777. you can disable it with **NoIsolateSOCKSAuth**.)
  778. **IsolateClientProtocol**;;
  779. Don't share circuits with streams using a different protocol.
  780. (SOCKS 4, SOCKS 5, TransPort connections, NATDPort connections,
  781. and DNSPort requests are all considered to be different protocols.)
  782. **IsolateDestPort**;;
  783. Don't share circuits with streams targetting a different
  784. destination port.
  785. **IsolateDestAddr**;;
  786. Don't share circuits with streams targetting a different
  787. destination address.
  788. **SessionGroup=**__INT__;;
  789. If no other isolation rules would prevent it, allow streams
  790. on this port to share circuits with streams from every other
  791. port with the same session group. (By default, streams received
  792. on different SOCKSPorts, TransPorts, etc are always isolated from one
  793. another. This option overrides that behavior.) +
  794. +
  795. Other recognized _flags_ for a SOCKSPort are:
  796. **NoIPv4Traffic**;;
  797. Tell exits to not connect to IPv4 addresses in response to SOCKS
  798. requests on this connection.
  799. **IPv6Traffic**;;
  800. Tell exits to allow IPv6 addresses in response to SOCKS requests on
  801. this connection, so long as SOCKS5 is in use. (SOCKS4 can't handle
  802. IPv6.)
  803. **PreferIPv6**;;
  804. Tells exits that, if a host has both an IPv4 and an IPv6 address,
  805. we would prefer to connect to it via IPv6. (IPv4 is the default.) +
  806. +
  807. NOTE: Although this option allows you to specify an IP address
  808. other than localhost, you should do so only with extreme caution.
  809. The SOCKS protocol is unencrypted and (as we use it)
  810. unauthenticated, so exposing it in this way could leak your
  811. information to anybody watching your network, and allow anybody
  812. to use your computer as an open proxy.
  813. **CacheIPv4DNS**;;
  814. Tells the client to remember IPv4 DNS answers we receive from exit
  815. nodes via this connection. (On by default.)
  816. **CacheIPv6DNS**;;
  817. Tells the client to remember IPv6 DNS answers we receive from exit
  818. nodes via this connection.
  819. **CacheDNS**;;
  820. Tells the client to remember all DNS answers we receive from exit
  821. nodes via this connection.
  822. **UseIPv4Cache**;;
  823. Tells the client to use any cached IPv4 DNS answers we have when making
  824. requests via this connection. (NOTE: This option, along UseIPv6Cache
  825. and UseDNSCache, can harm your anonymity, and probably
  826. won't help performance as much as you might expect. Use with care!)
  827. **UseIPv6Cache**;;
  828. Tells the client to use any cached IPv6 DNS answers we have when making
  829. requests via this connection.
  830. **UseDNSCache**;;
  831. Tells the client to use any cached DNS answers we have when making
  832. requests via this connection.
  833. **PreferIPv6Automap**;;
  834. When serving a hostname lookup request on this port that
  835. should get automapped (according to AutomapHostsOnResove),
  836. if we could return either an IPv4 or an IPv6 answer, prefer
  837. an IPv6 answer. (On by default.)
  838. **SOCKSListenAddress** __IP__[:__PORT__]::
  839. Bind to this address to listen for connections from Socks-speaking
  840. applications. (Default: 127.0.0.1) You can also specify a port (e.g.
  841. 192.168.0.1:9100). This directive can be specified multiple times to bind
  842. to multiple addresses/ports. (DEPRECATED: As of 0.2.3.x-alpha, you can
  843. now use multiple SOCKSPort entries, and provide addresses for SOCKSPort
  844. entries, so SOCKSListenAddress no longer has a purpose. For backward
  845. compatibility, SOCKSListenAddress is only allowed when SOCKSPort is just
  846. a port number.)
  847. **SocksPolicy** __policy__,__policy__,__...__::
  848. Set an entrance policy for this server, to limit who can connect to the
  849. SocksPort and DNSPort ports. The policies have the same form as exit
  850. policies below.
  851. **SocksTimeout** __NUM__::
  852. Let a socks connection wait NUM seconds handshaking, and NUM seconds
  853. unattached waiting for an appropriate circuit, before we fail it. (Default:
  854. 2 minutes)
  855. **TokenBucketRefillInterval** __NUM__ [**msec**|**second**]::
  856. Set the refill interval of Tor's token bucket to NUM milliseconds.
  857. NUM must be between 1 and 1000, inclusive. Note that the configured
  858. bandwidth limits are still expressed in bytes per second: this
  859. option only affects the frequency with which Tor checks to see whether
  860. previously exhausted connections may read again. (Default: 100 msec)
  861. **TrackHostExits** __host__,__.domain__,__...__::
  862. For each value in the comma separated list, Tor will track recent
  863. connections to hosts that match this value and attempt to reuse the same
  864. exit node for each. If the value is prepended with a \'.\', it is treated as
  865. matching an entire domain. If one of the values is just a \'.', it means
  866. match everything. This option is useful if you frequently connect to sites
  867. that will expire all your authentication cookies (i.e. log you out) if
  868. your IP address changes. Note that this option does have the disadvantage
  869. of making it more clear that a given history is associated with a single
  870. user. However, most people who would wish to observe this will observe it
  871. through cookies or other protocol-specific means anyhow.
  872. **TrackHostExitsExpire** __NUM__::
  873. Since exit servers go up and down, it is desirable to expire the
  874. association between host and exit server after NUM seconds. The default is
  875. 1800 seconds (30 minutes).
  876. **UpdateBridgesFromAuthority** **0**|**1**::
  877. When set (along with UseBridges), Tor will try to fetch bridge descriptors
  878. from the configured bridge authorities when feasible. It will fall back to
  879. a direct request if the authority responds with a 404. (Default: 0)
  880. **UseBridges** **0**|**1**::
  881. When set, Tor will fetch descriptors for each bridge listed in the "Bridge"
  882. config lines, and use these relays as both entry guards and directory
  883. guards. (Default: 0)
  884. **UseEntryGuards** **0**|**1**::
  885. If this option is set to 1, we pick a few long-term entry servers, and try
  886. to stick with them. This is desirable because constantly changing servers
  887. increases the odds that an adversary who owns some servers will observe a
  888. fraction of your paths. (Default: 1)
  889. **UseEntryGuardsAsDirectoryGuards** **0**|**1**::
  890. If this option is set to 1, we try to use our entry guards as directory
  891. guards, and failing that, pick more nodes to act as our directory guards.
  892. This helps prevent an adversary from enumerating clients. It's only
  893. available for clients (non-relay, non-bridge) that aren't configured to
  894. download any non-default directory material. It doesn't currently
  895. do anything when we lack a live consensus. (Default: 1)
  896. **NumEntryGuards** __NUM__::
  897. If UseEntryGuards is set to 1, we will try to pick a total of NUM routers
  898. as long-term entries for our circuits. (Default: 3)
  899. **NumDirectoryGuards** __NUM__::
  900. If UseEntryGuardsAsDirectoryGuards is enabled, we try to make sure we
  901. have at least NUM routers to use as directory guards. (Default: 3)
  902. **SafeSocks** **0**|**1**::
  903. When this option is enabled, Tor will reject application connections that
  904. use unsafe variants of the socks protocol -- ones that only provide an IP
  905. address, meaning the application is doing a DNS resolve first.
  906. Specifically, these are socks4 and socks5 when not doing remote DNS.
  907. (Default: 0)
  908. **TestSocks** **0**|**1**::
  909. When this option is enabled, Tor will make a notice-level log entry for
  910. each connection to the Socks port indicating whether the request used a
  911. safe socks protocol or an unsafe one (see above entry on SafeSocks). This
  912. helps to determine whether an application using Tor is possibly leaking
  913. DNS requests. (Default: 0)
  914. **WarnUnsafeSocks** **0**|**1**::
  915. When this option is enabled, Tor will warn whenever a request is
  916. received that only contains an IP address instead of a hostname. Allowing
  917. applications to do DNS resolves themselves is usually a bad idea and
  918. can leak your location to attackers. (Default: 1)
  919. **VirtualAddrNetworkIPv4** __Address__/__bits__ +
  920. **VirtualAddrNetworkIPv6** [__Address__]/__bits__::
  921. When Tor needs to assign a virtual (unused) address because of a MAPADDRESS
  922. command from the controller or the AutomapHostsOnResolve feature, Tor
  923. picks an unassigned address from this range. (Defaults:
  924. 127.192.0.0/10 and [FE80::]/10 respectively.) +
  925. +
  926. When providing proxy server service to a network of computers using a tool
  927. like dns-proxy-tor, change the IPv4 network to "10.192.0.0/10" or
  928. "172.16.0.0/12" and change the IPv6 network to "[FC00]/7".
  929. The default **VirtualAddrNetwork** address ranges on a
  930. properly configured machine will route to the loopback or link-local
  931. interface. For
  932. local use, no change to the default VirtualAddrNetwork setting is needed.
  933. **AllowNonRFC953Hostnames** **0**|**1**::
  934. When this option is disabled, Tor blocks hostnames containing illegal
  935. characters (like @ and :) rather than sending them to an exit node to be
  936. resolved. This helps trap accidental attempts to resolve URLs and so on.
  937. (Default: 0)
  938. **AllowDotExit** **0**|**1**::
  939. If enabled, we convert "www.google.com.foo.exit" addresses on the
  940. SocksPort/TransPort/NATDPort into "www.google.com" addresses that exit from
  941. the node "foo". Disabled by default since attacking websites and exit
  942. relays can use it to manipulate your path selection. (Default: 0)
  943. **FastFirstHopPK** **0**|**1**::
  944. When this option is disabled, Tor uses the public key step for the first
  945. hop of creating circuits. Skipping it is generally safe since we have
  946. already used TLS to authenticate the relay and to establish forward-secure
  947. keys. Turning this option off makes circuit building slower. +
  948. +
  949. Note that Tor will always use the public key step for the first hop if it's
  950. operating as a relay, and it will never use the public key step if it
  951. doesn't yet know the onion key of the first hop. (Default: 1)
  952. **TransPort** \['address':]__port__|**auto** [_isolation flags_]::
  953. Open this port to listen for transparent proxy connections. Set this to
  954. 0 if you don't want to allow transparent proxy connections. Set the port
  955. to "auto" to have Tor pick a port for you. This directive can be
  956. specified multiple times to bind to multiple addresses/ports. See
  957. SOCKSPort for an explanation of isolation flags. +
  958. +
  959. TransPort requires OS support for transparent proxies, such as BSDs' pf or
  960. Linux's IPTables. If you're planning to use Tor as a transparent proxy for
  961. a network, you'll want to examine and change VirtualAddrNetwork from the
  962. default setting. You'll also want to set the TransListenAddress option for
  963. the network you'd like to proxy. (Default: 0)
  964. **TransListenAddress** __IP__[:__PORT__]::
  965. Bind to this address to listen for transparent proxy connections. (Default:
  966. 127.0.0.1). This is useful for exporting a transparent proxy server to an
  967. entire network. (DEPRECATED: As of 0.2.3.x-alpha, you can
  968. now use multiple TransPort entries, and provide addresses for TransPort
  969. entries, so TransListenAddress no longer has a purpose. For backward
  970. compatibility, TransListenAddress is only allowed when TransPort is just
  971. a port number.)
  972. **NATDPort** \['address':]__port__|**auto** [_isolation flags_]::
  973. Open this port to listen for connections from old versions of ipfw (as
  974. included in old versions of FreeBSD, etc) using the NATD protocol.
  975. Use 0 if you don't want to allow NATD connections. Set the port
  976. to "auto" to have Tor pick a port for you. This directive can be
  977. specified multiple times to bind to multiple addresses/ports. See
  978. SOCKSPort for an explanation of isolation flags. +
  979. +
  980. This option is only for people who cannot use TransPort. (Default: 0)
  981. **NATDListenAddress** __IP__[:__PORT__]::
  982. Bind to this address to listen for NATD connections. (DEPRECATED: As of
  983. 0.2.3.x-alpha, you can now use multiple NATDPort entries, and provide
  984. addresses for NATDPort entries, so NATDListenAddress no longer has a
  985. purpose. For backward compatibility, NATDListenAddress is only allowed
  986. when NATDPort is just a port number.)
  987. **AutomapHostsOnResolve** **0**|**1**::
  988. When this option is enabled, and we get a request to resolve an address
  989. that ends with one of the suffixes in **AutomapHostsSuffixes**, we map an
  990. unused virtual address to that address, and return the new virtual address.
  991. This is handy for making ".onion" addresses work with applications that
  992. resolve an address and then connect to it. (Default: 0)
  993. **AutomapHostsSuffixes** __SUFFIX__,__SUFFIX__,__...__::
  994. A comma-separated list of suffixes to use with **AutomapHostsOnResolve**.
  995. The "." suffix is equivalent to "all addresses." (Default: .exit,.onion).
  996. **DNSPort** \['address':]__port__|**auto** [_isolation flags_]::
  997. If non-zero, open this port to listen for UDP DNS requests, and resolve
  998. them anonymously. This port only handles A, AAAA, and PTR requests---it
  999. doesn't handle arbitrary DNS request types. Set the port to "auto" to
  1000. have Tor pick a port for
  1001. you. This directive can be specified multiple times to bind to multiple
  1002. addresses/ports. See SOCKSPort for an explanation of isolation
  1003. flags. (Default: 0)
  1004. **DNSListenAddress** __IP__[:__PORT__]::
  1005. Bind to this address to listen for DNS connections. (DEPRECATED: As of
  1006. 0.2.3.x-alpha, you can now use multiple DNSPort entries, and provide
  1007. addresses for DNSPort entries, so DNSListenAddress no longer has a
  1008. purpose. For backward compatibility, DNSListenAddress is only allowed
  1009. when DNSPort is just a port number.)
  1010. **ClientDNSRejectInternalAddresses** **0**|**1**::
  1011. If true, Tor does not believe any anonymously retrieved DNS answer that
  1012. tells it that an address resolves to an internal address (like 127.0.0.1 or
  1013. 192.168.0.1). This option prevents certain browser-based attacks; don't
  1014. turn it off unless you know what you're doing. (Default: 1)
  1015. **ClientRejectInternalAddresses** **0**|**1**::
  1016. If true, Tor does not try to fulfill requests to connect to an internal
  1017. address (like 127.0.0.1 or 192.168.0.1) __unless a exit node is
  1018. specifically requested__ (for example, via a .exit hostname, or a
  1019. controller request). (Default: 1)
  1020. **DownloadExtraInfo** **0**|**1**::
  1021. If true, Tor downloads and caches "extra-info" documents. These documents
  1022. contain information about servers other than the information in their
  1023. regular router descriptors. Tor does not use this information for anything
  1024. itself; to save bandwidth, leave this option turned off. (Default: 0)
  1025. **WarnPlaintextPorts** __port__,__port__,__...__::
  1026. Tells Tor to issue a warnings whenever the user tries to make an anonymous
  1027. connection to one of these ports. This option is designed to alert users
  1028. to services that risk sending passwords in the clear. (Default:
  1029. 23,109,110,143)
  1030. **RejectPlaintextPorts** __port__,__port__,__...__::
  1031. Like WarnPlaintextPorts, but instead of warning about risky port uses, Tor
  1032. will instead refuse to make the connection. (Default: None)
  1033. **AllowSingleHopCircuits** **0**|**1**::
  1034. When this option is set, the attached Tor controller can use relays
  1035. that have the **AllowSingleHopExits** option turned on to build
  1036. one-hop Tor connections. (Default: 0)
  1037. **OptimisticData** **0**|**1**|**auto**::
  1038. When this option is set, and Tor is using an exit node that supports
  1039. the feature, it will try optimistically to send data to the exit node
  1040. without waiting for the exit node to report whether the connection
  1041. succeeded. This can save a round-trip time for protocols like HTTP
  1042. where the client talks first. If OptimisticData is set to **auto**,
  1043. Tor will look at the UseOptimisticData parameter in the networkstatus.
  1044. (Default: auto)
  1045. **Tor2webMode** **0**|**1**::
  1046. When this option is set, Tor connects to hidden services
  1047. **non-anonymously**. This option also disables client connections to
  1048. non-hidden-service hostnames through Tor. It **must only** be used when
  1049. running a tor2web Hidden Service web proxy.
  1050. To enable this option the compile time flag --enable-tor2webmode must be
  1051. specified. (Default: 0)
  1052. **UseMicrodescriptors** **0**|**1**|**auto**::
  1053. Microdescriptors are a smaller version of the information that Tor needs
  1054. in order to build its circuits. Using microdescriptors makes Tor clients
  1055. download less directory information, thus saving bandwidth. Directory
  1056. caches need to fetch regular descriptors and microdescriptors, so this
  1057. option doesn't save any bandwidth for them. If this option is set to
  1058. "auto" (recommended) then it is on for all clients that do not set
  1059. FetchUselessDescriptors. (Default: auto)
  1060. **UseNTorHandshake** **0**|**1**|**auto**::
  1061. The "ntor" circuit-creation handshake is faster and (we think) more
  1062. secure than the original ("TAP") circuit handshake, but starting to use
  1063. it too early might make your client stand out. If this option is 0, your
  1064. Tor client won't use the ntor handshake. If it's 1, your Tor client
  1065. will use the ntor handshake to extend circuits through servers that
  1066. support it. If this option is "auto" (recommended), then your client
  1067. will use the ntor handshake once enough directory authorities recommend
  1068. it. (Default: auto)
  1069. **PathBiasCircThreshold** __NUM__ +
  1070. **PathBiasNoticeRate** __NUM__ +
  1071. **PathBiasWarnRate** __NUM__ +
  1072. **PathBiasExtremeRate** __NUM__ +
  1073. **PathBiasDropGuards** __NUM__ +
  1074. **PathBiasScaleThreshold** __NUM__::
  1075. These options override the default behavior of Tor's (**currently
  1076. experimental**) path bias detection algorithm. To try to find broken or
  1077. misbehaving guard nodes, Tor looks for nodes where more than a certain
  1078. fraction of circuits through that guard fail to get built.
  1079. +
  1080. The PathBiasCircThreshold option controls how many circuits we need to build
  1081. through a guard before we make these checks. The PathBiasNoticeRate,
  1082. PathBiasWarnRate and PathBiasExtremeRate options control what fraction of
  1083. circuits must succeed through a guard so we won't write log messages.
  1084. If less than PathBiasExtremeRate circuits succeed *and* PathBiasDropGuards
  1085. is set to 1, we disable use of that guard. +
  1086. +
  1087. When we have seen more than PathBiasScaleThreshold
  1088. circuits through a guard, we scale our observations by 0.5 (governed by
  1089. the consensus) so that new observations don't get swamped by old ones. +
  1090. +
  1091. By default, or if a negative value is provided for one of these options,
  1092. Tor uses reasonable defaults from the networkstatus consensus document.
  1093. If no defaults are available there, these options default to 150, .70,
  1094. .50, .30, 0, and 300 respectively.
  1095. **PathBiasUseThreshold** __NUM__ +
  1096. **PathBiasNoticeUseRate** __NUM__ +
  1097. **PathBiasExtremeUseRate** __NUM__ +
  1098. **PathBiasScaleUseThreshold** __NUM__::
  1099. Similar to the above options, these options override the default behavior
  1100. of Tor's (**currently experimental**) path use bias detection algorithm.
  1101. +
  1102. Where as the path bias parameters govern thresholds for successfully
  1103. building circuits, these four path use bias parameters govern thresholds
  1104. only for circuit usage. Circuits which receive no stream usage
  1105. are not counted by this detection algorithm. A used circuit is considered
  1106. successful if it is capable of carrying streams or otherwise receiving
  1107. well-formed responses to RELAY cells.
  1108. +
  1109. By default, or if a negative value is provided for one of these options,
  1110. Tor uses reasonable defaults from the networkstatus consensus document.
  1111. If no defaults are available there, these options default to 20, .80,
  1112. .60, and 100, respectively.
  1113. **ClientUseIPv6** **0**|**1**::
  1114. If this option is set to 1, Tor might connect to entry nodes over
  1115. IPv6. Note that clients configured with an IPv6 address in a
  1116. **Bridge** line will try connecting over IPv6 even if
  1117. **ClientUseIPv6** is set to 0. (Default: 0)
  1118. **ClientPreferIPv6ORPort** **0**|**1**::
  1119. If this option is set to 1, Tor prefers an OR port with an IPv6
  1120. address over one with IPv4 if a given entry node has both. Other
  1121. things may influence the choice. This option breaks a tie to the
  1122. favor of IPv6. (Default: 0)
  1123. **PathsNeededToBuildCircuits** __NUM__::
  1124. Tor clients don't build circuits for user traffic until they know
  1125. about enough of the network so that they could potentially construct
  1126. enough of the possible paths through the network. If this option
  1127. is set to a fraction between 0.25 and 0.95, Tor won't build circuits
  1128. until it has enough descriptors or microdescriptors to construct
  1129. that fraction of possible paths. Note that setting this option too low
  1130. can make your Tor client less anonymous, and setting it too high can
  1131. prevent your Tor client from bootstrapping. If this option is negative,
  1132. Tor will use a default value chosen by the directory
  1133. authorities. (Default: -1.)
  1134. SERVER OPTIONS
  1135. --------------
  1136. The following options are useful only for servers (that is, if ORPort
  1137. is non-zero):
  1138. **Address** __address__::
  1139. The IP address or fully qualified domain name of this server (e.g.
  1140. moria.mit.edu). You can leave this unset, and Tor will guess your IP
  1141. address. This IP address is the one used to tell clients and other
  1142. servers where to find your Tor server; it doesn't affect the IP that your
  1143. Tor client binds to. To bind to a different address, use the
  1144. *ListenAddress and OutboundBindAddress options.
  1145. **AllowSingleHopExits** **0**|**1**::
  1146. This option controls whether clients can use this server as a single hop
  1147. proxy. If set to 1, clients can use this server as an exit even if it is
  1148. the only hop in the circuit. Note that most clients will refuse to use
  1149. servers that set this option, since most clients have
  1150. ExcludeSingleHopRelays set. (Default: 0)
  1151. **AssumeReachable** **0**|**1**::
  1152. This option is used when bootstrapping a new Tor network. If set to 1,
  1153. don't do self-reachability testing; just upload your server descriptor
  1154. immediately. If **AuthoritativeDirectory** is also set, this option
  1155. instructs the dirserver to bypass remote reachability testing too and list
  1156. all connected servers as running.
  1157. **BridgeRelay** **0**|**1**::
  1158. Sets the relay to act as a "bridge" with respect to relaying connections
  1159. from bridge users to the Tor network. It mainly causes Tor to publish a
  1160. server descriptor to the bridge database, rather than publishing a relay
  1161. descriptor to the public directory authorities.
  1162. **ContactInfo** __email_address__::
  1163. Administrative contact information for server. This line might get picked
  1164. up by spam harvesters, so you may want to obscure the fact that it's an
  1165. email address.
  1166. **ExitPolicy** __policy__,__policy__,__...__::
  1167. Set an exit policy for this server. Each policy is of the form
  1168. "**accept**|**reject** __ADDR__[/__MASK__][:__PORT__]". If /__MASK__ is
  1169. omitted then this policy just applies to the host given. Instead of giving
  1170. a host or network you can also use "\*" to denote the universe (0.0.0.0/0).
  1171. __PORT__ can be a single port number, an interval of ports
  1172. "__FROM_PORT__-__TO_PORT__", or "\*". If __PORT__ is omitted, that means
  1173. "\*". +
  1174. +
  1175. For example, "accept 18.7.22.69:\*,reject 18.0.0.0/8:\*,accept \*:\*" would
  1176. reject any traffic destined for MIT except for web.mit.edu, and accept
  1177. anything else. +
  1178. +
  1179. To specify all internal and link-local networks (including 0.0.0.0/8,
  1180. 169.254.0.0/16, 127.0.0.0/8, 192.168.0.0/16, 10.0.0.0/8, and
  1181. 172.16.0.0/12), you can use the "private" alias instead of an address.
  1182. These addresses are rejected by default (at the beginning of your exit
  1183. policy), along with your public IP address, unless you set the
  1184. ExitPolicyRejectPrivate config option to 0. For example, once you've done
  1185. that, you could allow HTTP to 127.0.0.1 and block all other connections to
  1186. internal networks with "accept 127.0.0.1:80,reject private:\*", though that
  1187. may also allow connections to your own computer that are addressed to its
  1188. public (external) IP address. See RFC 1918 and RFC 3330 for more details
  1189. about internal and reserved IP address space. +
  1190. +
  1191. This directive can be specified multiple times so you don't have to put it
  1192. all on one line. +
  1193. +
  1194. Policies are considered first to last, and the first match wins. If you
  1195. want to \_replace_ the default exit policy, end your exit policy with
  1196. either a reject \*:* or an accept \*:*. Otherwise, you're \_augmenting_
  1197. (prepending to) the default exit policy. The default exit policy is: +
  1198. reject *:25
  1199. reject *:119
  1200. reject *:135-139
  1201. reject *:445
  1202. reject *:563
  1203. reject *:1214
  1204. reject *:4661-4666
  1205. reject *:6346-6429
  1206. reject *:6699
  1207. reject *:6881-6999
  1208. accept *:*
  1209. **ExitPolicyRejectPrivate** **0**|**1**::
  1210. Reject all private (local) networks, along with your own public IP address,
  1211. at the beginning of your exit policy. See above entry on ExitPolicy.
  1212. (Default: 1)
  1213. **IPv6Exit** **0**|**1**::
  1214. If set, and we are an exit node, allow clients to use us for IPv6
  1215. traffic. (Default: 0)
  1216. **MaxOnionQueueDelay** __NUM__ [**msec**|**second**]::
  1217. If we have more onionskins queued for processing than we can process in
  1218. this amount of time, reject new ones. (Default: 1750 msec)
  1219. **MyFamily** __node__,__node__,__...__::
  1220. Declare that this Tor server is controlled or administered by a group or
  1221. organization identical or similar to that of the other servers, defined by
  1222. their identity fingerprints or nicknames. When two servers both declare
  1223. that they are in the same \'family', Tor clients will not use them in the
  1224. same circuit. (Each server only needs to list the other servers in its
  1225. family; it doesn't need to list itself, but it won't hurt.) Do not list
  1226. any bridge relay as it would compromise its concealment.
  1227. **Nickname** __name__::
  1228. Set the server's nickname to \'name'. Nicknames must be between 1 and 19
  1229. characters inclusive, and must contain only the characters [a-zA-Z0-9].
  1230. **NumCPUs** __num__::
  1231. How many processes to use at once for decrypting onionskins and other
  1232. parallelizable operations. If this is set to 0, Tor will try to detect
  1233. how many CPUs you have, defaulting to 1 if it can't tell. (Default: 0)
  1234. **ORPort** \['address':]__PORT__|**auto** [_flags_]::
  1235. Advertise this port to listen for connections from Tor clients and
  1236. servers. This option is required to be a Tor server.
  1237. Set it to "auto" to have Tor pick a port for you. Set it to 0 to not
  1238. run an ORPort at all. This option can occur more than once. (Default: 0)
  1239. +
  1240. Tor recognizes these flags on each ORPort:
  1241. **NoAdvertise**::
  1242. By default, we bind to a port and tell our users about it. If
  1243. NoAdvertise is specified, we don't advertise, but listen anyway. This
  1244. can be useful if the port everybody will be connecting to (for
  1245. example, one that's opened on our firewall) is somewhere else.
  1246. **NoListen**::
  1247. By default, we bind to a port and tell our users about it. If
  1248. NoListen is specified, we don't bind, but advertise anyway. This
  1249. can be useful if something else (for example, a firewall's port
  1250. forwarding configuration) is causing connections to reach us.
  1251. **IPv4Only**::
  1252. If the address is absent, or resolves to both an IPv4 and an IPv6
  1253. address, only listen to the IPv4 address.
  1254. **IPv6Only**::
  1255. If the address is absent, or resolves to both an IPv4 and an IPv6
  1256. address, only listen to the IPv6 address.
  1257. +
  1258. For obvious reasons, NoAdvertise and NoListen are mutually exclusive, and
  1259. IPv4Only and IPv6Only are mutually exclusive.
  1260. **ORListenAddress** __IP__[:__PORT__]::
  1261. Bind to this IP address to listen for connections from Tor clients and
  1262. servers. If you specify a port, bind to this port rather than the one
  1263. specified in ORPort. (Default: 0.0.0.0) This directive can be specified
  1264. multiple times to bind to multiple addresses/ports.
  1265. +
  1266. This option is deprecated; you can get the same behavior with ORPort now
  1267. that it supports NoAdvertise and explicit addresses.
  1268. **PortForwarding** **0**|**1**::
  1269. Attempt to automatically forward the DirPort and ORPort on a NAT router
  1270. connecting this Tor server to the Internet. If set, Tor will try both
  1271. NAT-PMP (common on Apple routers) and UPnP (common on routers from other
  1272. manufacturers). (Default: 0)
  1273. **PortForwardingHelper** __filename__|__pathname__::
  1274. If PortForwarding is set, use this executable to configure the forwarding.
  1275. If set to a filename, the system path will be searched for the executable.
  1276. If set to a path, only the specified path will be executed.
  1277. (Default: tor-fw-helper)
  1278. **PublishServerDescriptor** **0**|**1**|**v1**|**v2**|**v3**|**bridge**,**...**::
  1279. This option specifies which descriptors Tor will publish when acting as
  1280. a relay. You can
  1281. choose multiple arguments, separated by commas.
  1282. +
  1283. If this option is set to 0, Tor will not publish its
  1284. descriptors to any directories. (This is useful if you're testing
  1285. out your server, or if you're using a Tor controller that handles directory
  1286. publishing for you.) Otherwise, Tor will publish its descriptors of all
  1287. type(s) specified. The default is "1",
  1288. which means "if running as a server, publish the
  1289. appropriate descriptors to the authorities".
  1290. **ShutdownWaitLength** __NUM__::
  1291. When we get a SIGINT and we're a server, we begin shutting down:
  1292. we close listeners and start refusing new circuits. After **NUM**
  1293. seconds, we exit. If we get a second SIGINT, we exit immedi-
  1294. ately. (Default: 30 seconds)
  1295. **HeartbeatPeriod** __N__ **minutes**|**hours**|**days**|**weeks**::
  1296. Log a heartbeat message every **HeartbeatPeriod** seconds. This is
  1297. a log level __info__ message, designed to let you know your Tor
  1298. server is still alive and doing useful things. Settings this
  1299. to 0 will disable the heartbeat. (Default: 6 hours)
  1300. **AccountingMax** __N__ **bytes**|**KBytes**|**MBytes**|**GBytes**|**TBytes**::
  1301. Never send more than the specified number of bytes in a given accounting
  1302. period, or receive more than that number in the period. For example, with
  1303. AccountingMax set to 1 GByte, a server could send 900 MBytes and
  1304. receive 800 MBytes and continue running. It will only hibernate once
  1305. one of the two reaches 1 GByte. When the number of bytes gets low,
  1306. Tor will stop accepting new connections and circuits. When the
  1307. number of bytes is exhausted, Tor will hibernate until some
  1308. time in the next accounting period. To prevent all servers from waking at
  1309. the same time, Tor will also wait until a random point in each period
  1310. before waking up. If you have bandwidth cost issues, enabling hibernation
  1311. is preferable to setting a low bandwidth, since it provides users with a
  1312. collection of fast servers that are up some of the time, which is more
  1313. useful than a set of slow servers that are always "available".
  1314. **AccountingStart** **day**|**week**|**month** [__day__] __HH:MM__::
  1315. Specify how long accounting periods last. If **month** is given, each
  1316. accounting period runs from the time __HH:MM__ on the __dayth__ day of one
  1317. month to the same day and time of the next. (The day must be between 1 and
  1318. 28.) If **week** is given, each accounting period runs from the time __HH:MM__
  1319. of the __dayth__ day of one week to the same day and time of the next week,
  1320. with Monday as day 1 and Sunday as day 7. If **day** is given, each
  1321. accounting period runs from the time __HH:MM__ each day to the same time on
  1322. the next day. All times are local, and given in 24-hour time. (Default:
  1323. "month 1 0:00")
  1324. **RefuseUnknownExits** **0**|**1**|**auto**::
  1325. Prevent nodes that don't appear in the consensus from exiting using this
  1326. relay. If the option is 1, we always block exit attempts from such
  1327. nodes; if it's 0, we never do, and if the option is "auto", then we do
  1328. whatever the authorities suggest in the consensus (and block if the consensus
  1329. is quiet on the issue). (Default: auto)
  1330. **ServerDNSResolvConfFile** __filename__::
  1331. Overrides the default DNS configuration with the configuration in
  1332. __filename__. The file format is the same as the standard Unix
  1333. "**resolv.conf**" file (7). This option, like all other ServerDNS options,
  1334. only affects name lookups that your server does on behalf of clients.
  1335. (Defaults to use the system DNS configuration.)
  1336. **ServerDNSAllowBrokenConfig** **0**|**1**::
  1337. If this option is false, Tor exits immediately if there are problems
  1338. parsing the system DNS configuration or connecting to nameservers.
  1339. Otherwise, Tor continues to periodically retry the system nameservers until
  1340. it eventually succeeds. (Default: 1)
  1341. **ServerDNSSearchDomains** **0**|**1**::
  1342. If set to 1, then we will search for addresses in the local search domain.
  1343. For example, if this system is configured to believe it is in
  1344. "example.com", and a client tries to connect to "www", the client will be
  1345. connected to "www.example.com". This option only affects name lookups that
  1346. your server does on behalf of clients. (Default: 0)
  1347. **ServerDNSDetectHijacking** **0**|**1**::
  1348. When this option is set to 1, we will test periodically to determine
  1349. whether our local nameservers have been configured to hijack failing DNS
  1350. requests (usually to an advertising site). If they are, we will attempt to
  1351. correct this. This option only affects name lookups that your server does
  1352. on behalf of clients. (Default: 1)
  1353. **ServerDNSTestAddresses** __address__,__address__,__...__::
  1354. When we're detecting DNS hijacking, make sure that these __valid__ addresses
  1355. aren't getting redirected. If they are, then our DNS is completely useless,
  1356. and we'll reset our exit policy to "reject *:*". This option only affects
  1357. name lookups that your server does on behalf of clients. (Default:
  1358. "www.google.com, www.mit.edu, www.yahoo.com, www.slashdot.org")
  1359. **ServerDNSAllowNonRFC953Hostnames** **0**|**1**::
  1360. When this option is disabled, Tor does not try to resolve hostnames
  1361. containing illegal characters (like @ and :) rather than sending them to an
  1362. exit node to be resolved. This helps trap accidental attempts to resolve
  1363. URLs and so on. This option only affects name lookups that your server does
  1364. on behalf of clients. (Default: 0)
  1365. **BridgeRecordUsageByCountry** **0**|**1**::
  1366. When this option is enabled and BridgeRelay is also enabled, and we have
  1367. GeoIP data, Tor keeps a keep a per-country count of how many client
  1368. addresses have contacted it so that it can help the bridge authority guess
  1369. which countries have blocked access to it. (Default: 1)
  1370. **ServerDNSRandomizeCase** **0**|**1**::
  1371. When this option is set, Tor sets the case of each character randomly in
  1372. outgoing DNS requests, and makes sure that the case matches in DNS replies.
  1373. This so-called "0x20 hack" helps resist some types of DNS poisoning attack.
  1374. For more information, see "Increased DNS Forgery Resistance through
  1375. 0x20-Bit Encoding". This option only affects name lookups that your server
  1376. does on behalf of clients. (Default: 1)
  1377. **GeoIPFile** __filename__::
  1378. A filename containing IPv4 GeoIP data, for use with by-country statistics.
  1379. **GeoIPv6File** __filename__::
  1380. A filename containing IPv6 GeoIP data, for use with by-country statistics.
  1381. **TLSECGroup** **P224**|**P256**::
  1382. What EC group should we try to use for incoming TLS connections?
  1383. P224 is faster, but makes us stand out more. Has no effect if
  1384. we're a client, or if our OpenSSL version lacks support for ECDHE.
  1385. (Default: P224 for public servers; P256 for bridges.)
  1386. **CellStatistics** **0**|**1**::
  1387. When this option is enabled, Tor writes statistics on the mean time that
  1388. cells spend in circuit queues to disk every 24 hours. (Default: 0)
  1389. **DirReqStatistics** **0**|**1**::
  1390. When this option is enabled, a Tor directory writes statistics on the
  1391. number and response time of network status requests to disk every 24
  1392. hours. (Default: 1)
  1393. **EntryStatistics** **0**|**1**::
  1394. When this option is enabled, Tor writes statistics on the number of
  1395. directly connecting clients to disk every 24 hours. (Default: 0)
  1396. **ExitPortStatistics** **0**|**1**::
  1397. When this option is enabled, Tor writes statistics on the number of relayed
  1398. bytes and opened stream per exit port to disk every 24 hours. (Default: 0)
  1399. **ConnDirectionStatistics** **0**|**1**::
  1400. When this option is enabled, Tor writes statistics on the bidirectional use
  1401. of connections to disk every 24 hours. (Default: 0)
  1402. **ExtraInfoStatistics** **0**|**1**::
  1403. When this option is enabled, Tor includes previously gathered statistics in
  1404. its extra-info documents that it uploads to the directory authorities.
  1405. (Default: 1)
  1406. **ExtendAllowPrivateAddresses** **0**|**1**::
  1407. When this option is enabled, Tor routers allow EXTEND request to
  1408. localhost, RFC1918 addresses, and so on. This can create security issues;
  1409. you should probably leave it off. (Default: 0)
  1410. DIRECTORY SERVER OPTIONS
  1411. ------------------------
  1412. The following options are useful only for directory servers (that is,
  1413. if DirPort is non-zero):
  1414. **AuthoritativeDirectory** **0**|**1**::
  1415. When this option is set to 1, Tor operates as an authoritative directory
  1416. server. Instead of caching the directory, it generates its own list of
  1417. good servers, signs it, and sends that to the clients. Unless the clients
  1418. already have you listed as a trusted directory, you probably do not want
  1419. to set this option. Please coordinate with the other admins at
  1420. tor-ops@torproject.org if you think you should be a directory.
  1421. **DirPortFrontPage** __FILENAME__::
  1422. When this option is set, it takes an HTML file and publishes it as "/" on
  1423. the DirPort. Now relay operators can provide a disclaimer without needing
  1424. to set up a separate webserver. There's a sample disclaimer in
  1425. contrib/tor-exit-notice.html.
  1426. **V1AuthoritativeDirectory** **0**|**1**::
  1427. When this option is set in addition to **AuthoritativeDirectory**, Tor
  1428. generates version 1 directory and running-routers documents (for legacy
  1429. Tor clients up to 0.1.0.x).
  1430. **V2AuthoritativeDirectory** **0**|**1**::
  1431. When this option is set in addition to **AuthoritativeDirectory**, Tor
  1432. generates version 2 network statuses and serves descriptors, etc as
  1433. described in doc/spec/dir-spec-v2.txt (for Tor clients and servers running
  1434. 0.1.1.x and 0.1.2.x).
  1435. **V3AuthoritativeDirectory** **0**|**1**::
  1436. When this option is set in addition to **AuthoritativeDirectory**, Tor
  1437. generates version 3 network statuses and serves descriptors, etc as
  1438. described in doc/spec/dir-spec.txt (for Tor clients and servers running at
  1439. least 0.2.0.x).
  1440. **VersioningAuthoritativeDirectory** **0**|**1**::
  1441. When this option is set to 1, Tor adds information on which versions of
  1442. Tor are still believed safe for use to the published directory. Each
  1443. version 1 authority is automatically a versioning authority; version 2
  1444. authorities provide this service optionally. See **RecommendedVersions**,
  1445. **RecommendedClientVersions**, and **RecommendedServerVersions**.
  1446. **NamingAuthoritativeDirectory** **0**|**1**::
  1447. When this option is set to 1, then the server advertises that it has
  1448. opinions about nickname-to-fingerprint bindings. It will include these
  1449. opinions in its published network-status pages, by listing servers with
  1450. the flag "Named" if a correct binding between that nickname and fingerprint
  1451. has been registered with the dirserver. Naming dirservers will refuse to
  1452. accept or publish descriptors that contradict a registered binding. See
  1453. **approved-routers** in the **FILES** section below.
  1454. **HSAuthoritativeDir** **0**|**1**::
  1455. When this option is set in addition to **AuthoritativeDirectory**, Tor also
  1456. accepts and serves v0 hidden service descriptors,
  1457. which are produced and used by Tor 0.2.1.x and older. (Default: 0)
  1458. **HidServDirectoryV2** **0**|**1**::
  1459. When this option is set, Tor accepts and serves v2 hidden service
  1460. descriptors. Setting DirPort is not required for this, because clients
  1461. connect via the ORPort by default. (Default: 1)
  1462. **BridgeAuthoritativeDir** **0**|**1**::
  1463. When this option is set in addition to **AuthoritativeDirectory**, Tor
  1464. accepts and serves router descriptors, but it caches and serves the main
  1465. networkstatus documents rather than generating its own. (Default: 0)
  1466. **MinUptimeHidServDirectoryV2** __N__ **seconds**|**minutes**|**hours**|**days**|**weeks**::
  1467. Minimum uptime of a v2 hidden service directory to be accepted as such by
  1468. authoritative directories. (Default: 25 hours)
  1469. **DirPort** \['address':]__PORT__|**auto** [_flags_]::
  1470. If this option is nonzero, advertise the directory service on this port.
  1471. Set it to "auto" to have Tor pick a port for you. This option can occur
  1472. more than once. (Default: 0)
  1473. +
  1474. The same flags are supported here as are supported by ORPort.
  1475. **DirListenAddress** __IP__[:__PORT__]::
  1476. Bind the directory service to this address. If you specify a port, bind to
  1477. this port rather than the one specified in DirPort. (Default: 0.0.0.0)
  1478. This directive can be specified multiple times to bind to multiple
  1479. addresses/ports.
  1480. +
  1481. This option is deprecated; you can get the same behavior with DirPort now
  1482. that it supports NoAdvertise and explicit addresses.
  1483. **DirPolicy** __policy__,__policy__,__...__::
  1484. Set an entrance policy for this server, to limit who can connect to the
  1485. directory ports. The policies have the same form as exit policies above.
  1486. **FetchV2Networkstatus** **0**|**1**::
  1487. If set, we try to fetch the (obsolete, unused) version 2 network status
  1488. consensus documents from the directory authorities. No currently
  1489. supported Tor version uses them. (Default: 0)
  1490. DIRECTORY AUTHORITY SERVER OPTIONS
  1491. ----------------------------------
  1492. **RecommendedVersions** __STRING__::
  1493. STRING is a comma-separated list of Tor versions currently believed to be
  1494. safe. The list is included in each directory, and nodes which pull down the
  1495. directory learn whether they need to upgrade. This option can appear
  1496. multiple times: the values from multiple lines are spliced together. When
  1497. this is set then **VersioningAuthoritativeDirectory** should be set too.
  1498. **RecommendedClientVersions** __STRING__::
  1499. STRING is a comma-separated list of Tor versions currently believed to be
  1500. safe for clients to use. This information is included in version 2
  1501. directories. If this is not set then the value of **RecommendedVersions**
  1502. is used. When this is set then **VersioningAuthoritativeDirectory** should
  1503. be set too.
  1504. **RecommendedServerVersions** __STRING__::
  1505. STRING is a comma-separated list of Tor versions currently believed to be
  1506. safe for servers to use. This information is included in version 2
  1507. directories. If this is not set then the value of **RecommendedVersions**
  1508. is used. When this is set then **VersioningAuthoritativeDirectory** should
  1509. be set too.
  1510. **ConsensusParams** __STRING__::
  1511. STRING is a space-separated list of key=value pairs that Tor will include
  1512. in the "params" line of its networkstatus vote.
  1513. **DirAllowPrivateAddresses** **0**|**1**::
  1514. If set to 1, Tor will accept router descriptors with arbitrary "Address"
  1515. elements. Otherwise, if the address is not an IP address or is a private IP
  1516. address, it will reject the router descriptor. (Default: 0)
  1517. **AuthDirBadDir** __AddressPattern...__::
  1518. Authoritative directories only. A set of address patterns for servers that
  1519. will be listed as bad directories in any network status document this
  1520. authority publishes, if **AuthDirListBadDirs** is set.
  1521. **AuthDirBadExit** __AddressPattern...__::
  1522. Authoritative directories only. A set of address patterns for servers that
  1523. will be listed as bad exits in any network status document this authority
  1524. publishes, if **AuthDirListBadExits** is set.
  1525. **AuthDirInvalid** __AddressPattern...__::
  1526. Authoritative directories only. A set of address patterns for servers that
  1527. will never be listed as "valid" in any network status document that this
  1528. authority publishes.
  1529. **AuthDirReject** __AddressPattern__...::
  1530. Authoritative directories only. A set of address patterns for servers that
  1531. will never be listed at all in any network status document that this
  1532. authority publishes, or accepted as an OR address in any descriptor
  1533. submitted for publication by this authority.
  1534. **AuthDirBadDirCCs** __CC__,... +
  1535. **AuthDirBadExitCCs** __CC__,... +
  1536. **AuthDirInvalidCCs** __CC__,... +
  1537. **AuthDirRejectCCs** __CC__,...::
  1538. Authoritative directories only. These options contain a comma-separated
  1539. list of country codes such that any server in one of those country codes
  1540. will be marked as a bad directory/bad exit/invalid for use, or rejected
  1541. entirely.
  1542. **AuthDirListBadDirs** **0**|**1**::
  1543. Authoritative directories only. If set to 1, this directory has some
  1544. opinion about which nodes are unsuitable as directory caches. (Do not set
  1545. this to 1 unless you plan to list non-functioning directories as bad;
  1546. otherwise, you are effectively voting in favor of every declared
  1547. directory.)
  1548. **AuthDirListBadExits** **0**|**1**::
  1549. Authoritative directories only. If set to 1, this directory has some
  1550. opinion about which nodes are unsuitable as exit nodes. (Do not set this to
  1551. 1 unless you plan to list non-functioning exits as bad; otherwise, you are
  1552. effectively voting in favor of every declared exit as an exit.)
  1553. **AuthDirRejectUnlisted** **0**|**1**::
  1554. Authoritative directories only. If set to 1, the directory server rejects
  1555. all uploaded server descriptors that aren't explicitly listed in the
  1556. fingerprints file. This acts as a "panic button" if we get hit with a Sybil
  1557. attack. (Default: 0)
  1558. **AuthDirMaxServersPerAddr** __NUM__::
  1559. Authoritative directories only. The maximum number of servers that we will
  1560. list as acceptable on a single IP address. Set this to "0" for "no limit".
  1561. (Default: 2)
  1562. **AuthDirMaxServersPerAuthAddr** __NUM__::
  1563. Authoritative directories only. Like AuthDirMaxServersPerAddr, but applies
  1564. to addresses shared with directory authorities. (Default: 5)
  1565. **AuthDirFastGuarantee** __N__ **bytes**|**KBytes**|**MBytes**|**GBytes**::
  1566. Authoritative directories only. If non-zero, always vote the
  1567. Fast flag for any relay advertising this amount of capacity or
  1568. more. (Default: 100 KBytes)
  1569. **AuthDirGuardBWGuarantee** __N__ **bytes**|**KBytes**|**MBytes**|**GBytes**::
  1570. Authoritative directories only. If non-zero, this advertised capacity
  1571. or more is always sufficient to satisfy the bandwidth requirement
  1572. for the Guard flag. (Default: 250 KBytes)
  1573. **BridgePassword** __Password__::
  1574. If set, contains an HTTP authenticator that tells a bridge authority to
  1575. serve all requested bridge information. Used by the (only partially
  1576. implemented) "bridge community" design, where a community of bridge
  1577. relay operators all use an alternate bridge directory authority,
  1578. and their target user audience can periodically fetch the list of
  1579. available community bridges to stay up-to-date. (Default: not set)
  1580. **V3AuthVotingInterval** __N__ **minutes**|**hours**::
  1581. V3 authoritative directories only. Configures the server's preferred voting
  1582. interval. Note that voting will __actually__ happen at an interval chosen
  1583. by consensus from all the authorities' preferred intervals. This time
  1584. SHOULD divide evenly into a day. (Default: 1 hour)
  1585. **V3AuthVoteDelay** __N__ **minutes**|**hours**::
  1586. V3 authoritative directories only. Configures the server's preferred delay
  1587. between publishing its vote and assuming it has all the votes from all the
  1588. other authorities. Note that the actual time used is not the server's
  1589. preferred time, but the consensus of all preferences. (Default: 5 minutes)
  1590. **V3AuthDistDelay** __N__ **minutes**|**hours**::
  1591. V3 authoritative directories only. Configures the server's preferred delay
  1592. between publishing its consensus and signature and assuming it has all the
  1593. signatures from all the other authorities. Note that the actual time used
  1594. is not the server's preferred time, but the consensus of all preferences.
  1595. (Default: 5 minutes)
  1596. **V3AuthNIntervalsValid** __NUM__::
  1597. V3 authoritative directories only. Configures the number of VotingIntervals
  1598. for which each consensus should be valid for. Choosing high numbers
  1599. increases network partitioning risks; choosing low numbers increases
  1600. directory traffic. Note that the actual number of intervals used is not the
  1601. server's preferred number, but the consensus of all preferences. Must be at
  1602. least 2. (Default: 3)
  1603. **V3BandwidthsFile** __FILENAME__::
  1604. V3 authoritative directories only. Configures the location of the
  1605. bandwidth-authority generated file storing information on relays' measured
  1606. bandwidth capacities. (Default: unset)
  1607. **V3AuthUseLegacyKey** **0**|**1**::
  1608. If set, the directory authority will sign consensuses not only with its
  1609. own signing key, but also with a "legacy" key and certificate with a
  1610. different identity. This feature is used to migrate directory authority
  1611. keys in the event of a compromise. (Default: 0)
  1612. **RephistTrackTime** __N__ **seconds**|**minutes**|**hours**|**days**|**weeks**::
  1613. Tells an authority, or other node tracking node reliability and history,
  1614. that fine-grained information about nodes can be discarded when it hasn't
  1615. changed for a given amount of time. (Default: 24 hours)
  1616. **VoteOnHidServDirectoriesV2** **0**|**1**::
  1617. When this option is set in addition to **AuthoritativeDirectory**, Tor
  1618. votes on whether to accept relays as hidden service directories.
  1619. (Default: 1)
  1620. **AuthDirHasIPv6Connectivity** **0**|**1**::
  1621. Authoritative directories only. When set to 0, OR ports with an
  1622. IPv6 address are being accepted without reachability testing.
  1623. When set to 1, IPv6 OR ports are being tested just like IPv4 OR
  1624. ports. (Default: 0)
  1625. HIDDEN SERVICE OPTIONS
  1626. ----------------------
  1627. The following options are used to configure a hidden service.
  1628. **HiddenServiceDir** __DIRECTORY__::
  1629. Store data files for a hidden service in DIRECTORY. Every hidden service
  1630. must have a separate directory. You may use this option multiple times to
  1631. specify multiple services. DIRECTORY must be an existing directory.
  1632. **HiddenServicePort** __VIRTPORT__ [__TARGET__]::
  1633. Configure a virtual port VIRTPORT for a hidden service. You may use this
  1634. option multiple times; each time applies to the service using the most
  1635. recent hiddenservicedir. By default, this option maps the virtual port to
  1636. the same port on 127.0.0.1 over TCP. You may override the target port,
  1637. address, or both by specifying a target of addr, port, or addr:port.
  1638. You may also have multiple lines with the same VIRTPORT: when a user
  1639. connects to that VIRTPORT, one of the TARGETs from those lines will be
  1640. chosen at random.
  1641. **PublishHidServDescriptors** **0**|**1**::
  1642. If set to 0, Tor will run any hidden services you configure, but it won't
  1643. advertise them to the rendezvous directory. This option is only useful if
  1644. you're using a Tor controller that handles hidserv publishing for you.
  1645. (Default: 1)
  1646. **HiddenServiceVersion** __version__,__version__,__...__::
  1647. A list of rendezvous service descriptor versions to publish for the hidden
  1648. service. Currently, only version 2 is supported. (Default: 2)
  1649. **HiddenServiceAuthorizeClient** __auth-type__ __client-name__,__client-name__,__...__::
  1650. If configured, the hidden service is accessible for authorized clients
  1651. only. The auth-type can either be \'basic' for a general-purpose
  1652. authorization protocol or \'stealth' for a less scalable protocol that also
  1653. hides service activity from unauthorized clients. Only clients that are
  1654. listed here are authorized to access the hidden service. Valid client names
  1655. are 1 to 19 characters long and only use characters in A-Za-z0-9+-_ (no
  1656. spaces). If this option is set, the hidden service is not accessible for
  1657. clients without authorization any more. Generated authorization data can be
  1658. found in the hostname file. Clients need to put this authorization data in
  1659. their configuration file using **HidServAuth**.
  1660. **RendPostPeriod** __N__ **seconds**|**minutes**|**hours**|**days**|**weeks**::
  1661. Every time the specified period elapses, Tor uploads any rendezvous
  1662. service descriptors to the directory servers. This information is also
  1663. uploaded whenever it changes. (Default: 1 hour)
  1664. TESTING NETWORK OPTIONS
  1665. -----------------------
  1666. The following options are used for running a testing Tor network.
  1667. **TestingTorNetwork** **0**|**1**::
  1668. If set to 1, Tor adjusts default values of the configuration options below,
  1669. so that it is easier to set up a testing Tor network. May only be set if
  1670. non-default set of DirServers is set. Cannot be unset while Tor is running.
  1671. (Default: 0) +
  1672. ServerDNSAllowBrokenConfig 1
  1673. DirAllowPrivateAddresses 1
  1674. EnforceDistinctSubnets 0
  1675. AssumeReachable 1
  1676. AuthDirMaxServersPerAddr 0
  1677. AuthDirMaxServersPerAuthAddr 0
  1678. ClientDNSRejectInternalAddresses 0
  1679. ClientRejectInternalAddresses 0
  1680. CountPrivateBandwidth 1
  1681. ExitPolicyRejectPrivate 0
  1682. ExtendAllowPrivateAddresses 1
  1683. V3AuthVotingInterval 5 minutes
  1684. V3AuthVoteDelay 20 seconds
  1685. V3AuthDistDelay 20 seconds
  1686. MinUptimeHidServDirectoryV2 0 seconds
  1687. TestingV3AuthInitialVotingInterval 5 minutes
  1688. TestingV3AuthInitialVoteDelay 20 seconds
  1689. TestingV3AuthInitialDistDelay 20 seconds
  1690. TestingAuthDirTimeToLearnReachability 0 minutes
  1691. TestingEstimatedDescriptorPropagationTime 0 minutes
  1692. **TestingV3AuthInitialVotingInterval** __N__ **minutes**|**hours**::
  1693. Like V3AuthVotingInterval, but for initial voting interval before the first
  1694. consensus has been created. Changing this requires that
  1695. **TestingTorNetwork** is set. (Default: 30 minutes)
  1696. **TestingV3AuthInitialVoteDelay** __N__ **minutes**|**hours**::
  1697. Like TestingV3AuthInitialVoteDelay, but for initial voting interval before
  1698. the first consensus has been created. Changing this requires that
  1699. **TestingTorNetwork** is set. (Default: 5 minutes)
  1700. **TestingV3AuthInitialDistDelay** __N__ **minutes**|**hours**::
  1701. Like TestingV3AuthInitialDistDelay, but for initial voting interval before
  1702. the first consensus has been created. Changing this requires that
  1703. **TestingTorNetwork** is set. (Default: 5 minutes)
  1704. **TestingAuthDirTimeToLearnReachability** __N__ **minutes**|**hours**::
  1705. After starting as an authority, do not make claims about whether routers
  1706. are Running until this much time has passed. Changing this requires
  1707. that **TestingTorNetwork** is set. (Default: 30 minutes)
  1708. **TestingEstimatedDescriptorPropagationTime** __N__ **minutes**|**hours**::
  1709. Clients try downloading router descriptors from directory caches after this
  1710. time. Changing this requires that **TestingTorNetwork** is set. (Default:
  1711. 10 minutes)
  1712. SIGNALS
  1713. -------
  1714. Tor catches the following signals:
  1715. **SIGTERM**::
  1716. Tor will catch this, clean up and sync to disk if necessary, and exit.
  1717. **SIGINT**::
  1718. Tor clients behave as with SIGTERM; but Tor servers will do a controlled
  1719. slow shutdown, closing listeners and waiting 30 seconds before exiting.
  1720. (The delay can be configured with the ShutdownWaitLength config option.)
  1721. **SIGHUP**::
  1722. The signal instructs Tor to reload its configuration (including closing and
  1723. reopening logs), and kill and restart its helper processes if applicable.
  1724. **SIGUSR1**::
  1725. Log statistics about current connections, past connections, and throughput.
  1726. **SIGUSR2**::
  1727. Switch all logs to loglevel debug. You can go back to the old loglevels by
  1728. sending a SIGHUP.
  1729. **SIGCHLD**::
  1730. Tor receives this signal when one of its helper processes has exited, so it
  1731. can clean up.
  1732. **SIGPIPE**::
  1733. Tor catches this signal and ignores it.
  1734. **SIGXFSZ**::
  1735. If this signal exists on your platform, Tor catches and ignores it.
  1736. FILES
  1737. -----
  1738. **@CONFDIR@/torrc**::
  1739. The configuration file, which contains "option value" pairs.
  1740. **@LOCALSTATEDIR@/lib/tor/**::
  1741. The tor process stores keys and other data here.
  1742. __DataDirectory__**/cached-status/**::
  1743. The most recently downloaded network status document for each authority.
  1744. Each file holds one such document; the filenames are the hexadecimal
  1745. identity key fingerprints of the directory authorities. Mostly obsolete.
  1746. __DataDirectory__**/cached-consensus** and/or **cached-microdesc-consensus**::
  1747. The most recent consensus network status document we've downloaded.
  1748. __DataDirectory__**/cached-descriptors** and **cached-descriptors.new**::
  1749. These files hold downloaded router statuses. Some routers may appear more
  1750. than once; if so, the most recently published descriptor is used. Lines
  1751. beginning with @-signs are annotations that contain more information about
  1752. a given router. The ".new" file is an append-only journal; when it gets
  1753. too large, all entries are merged into a new cached-descriptors file.
  1754. __DataDirectory__**/cached-microdescs** and **cached-microdescs.new**::
  1755. These files hold downloaded microdescriptors. Lines beginning with
  1756. @-signs are annotations that contain more information about a given
  1757. router. The ".new" file is an append-only journal; when it gets too
  1758. large, all entries are merged into a new cached-microdescs file.
  1759. __DataDirectory__**/cached-routers** and **cached-routers.new**::
  1760. Obsolete versions of cached-descriptors and cached-descriptors.new. When
  1761. Tor can't find the newer files, it looks here instead.
  1762. __DataDirectory__**/state**::
  1763. A set of persistent key-value mappings. These are documented in
  1764. the file. These include:
  1765. - The current entry guards and their status.
  1766. - The current bandwidth accounting values (unused so far; see
  1767. below).
  1768. - When the file was last written
  1769. - What version of Tor generated the state file
  1770. - A short history of bandwidth usage, as produced in the router
  1771. descriptors.
  1772. __DataDirectory__**/bw_accounting**::
  1773. Used to track bandwidth accounting values (when the current period starts
  1774. and ends; how much has been read and written so far this period). This file
  1775. is obsolete, and the data is now stored in the \'state' file as well. Only
  1776. used when bandwidth accounting is enabled.
  1777. __DataDirectory__**/control_auth_cookie**::
  1778. Used for cookie authentication with the controller. Location can be
  1779. overridden by the CookieAuthFile config option. Regenerated on startup. See
  1780. control-spec.txt for details. Only used when cookie authentication is
  1781. enabled.
  1782. __DataDirectory__**/keys/***::
  1783. Only used by servers. Holds identity keys and onion keys.
  1784. __DataDirectory__**/fingerprint**::
  1785. Only used by servers. Holds the fingerprint of the server's identity key.
  1786. __DataDirectory__**/approved-routers**::
  1787. Only for naming authoritative directory servers (see
  1788. **NamingAuthoritativeDirectory**). This file lists nickname to identity
  1789. bindings. Each line lists a nickname and a fingerprint separated by
  1790. whitespace. See your **fingerprint** file in the __DataDirectory__ for an
  1791. example line. If the nickname is **!reject** then descriptors from the
  1792. given identity (fingerprint) are rejected by this server. If it is
  1793. **!invalid** then descriptors are accepted but marked in the directory as
  1794. not valid, that is, not recommended.
  1795. __DataDirectory__**/router-stability**::
  1796. Only used by authoritative directory servers. Tracks measurements for
  1797. router mean-time-between-failures so that authorities have a good idea of
  1798. how to set their Stable flags.
  1799. __HiddenServiceDirectory__**/hostname**::
  1800. The <base32-encoded-fingerprint>.onion domain name for this hidden service.
  1801. If the hidden service is restricted to authorized clients only, this file
  1802. also contains authorization data for all clients.
  1803. __HiddenServiceDirectory__**/private_key**::
  1804. The private key for this hidden service.
  1805. __HiddenServiceDirectory__**/client_keys**::
  1806. Authorization data for a hidden service that is only accessible by
  1807. authorized clients.
  1808. SEE ALSO
  1809. --------
  1810. **privoxy**(1), **tsocks**(1), **torify**(1) +
  1811. **https://www.torproject.org/**
  1812. BUGS
  1813. ----
  1814. Plenty, probably. Tor is still in development. Please report them.
  1815. AUTHORS
  1816. -------
  1817. Roger Dingledine [arma at mit.edu], Nick Mathewson [nickm at alum.mit.edu].