tor.1.txt 138 KB

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