tor.1.txt 138 KB

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