tor.1.txt 183 KB

12345678910111213141516171819202122232425262728293031323334353637383940414243444546474849505152535455565758596061626364656667686970717273747576777879808182838485868788899091929394959697989910010110210310410510610710810911011111211311411511611711811912012112212312412512612712812913013113213313413513613713813914014114214314414514614714814915015115215315415515615715815916016116216316416516616716816917017117217317417517617717817918018118218318418518618718818919019119219319419519619719819920020120220320420520620720820921021121221321421521621721821922022122222322422522622722822923023123223323423523623723823924024124224324424524624724824925025125225325425525625725825926026126226326426526626726826927027127227327427527627727827928028128228328428528628728828929029129229329429529629729829930030130230330430530630730830931031131231331431531631731831932032132232332432532632732832933033133233333433533633733833934034134234334434534634734834935035135235335435535635735835936036136236336436536636736836937037137237337437537637737837938038138238338438538638738838939039139239339439539639739839940040140240340440540640740840941041141241341441541641741841942042142242342442542642742842943043143243343443543643743843944044144244344444544644744844945045145245345445545645745845946046146246346446546646746846947047147247347447547647747847948048148248348448548648748848949049149249349449549649749849950050150250350450550650750850951051151251351451551651751851952052152252352452552652752852953053153253353453553653753853954054154254354454554654754854955055155255355455555655755855956056156256356456556656756856957057157257357457557657757857958058158258358458558658758858959059159259359459559659759859960060160260360460560660760860961061161261361461561661761861962062162262362462562662762862963063163263363463563663763863964064164264364464564664764864965065165265365465565665765865966066166266366466566666766866967067167267367467567667767867968068168268368468568668768868969069169269369469569669769869970070170270370470570670770870971071171271371471571671771871972072172272372472572672772872973073173273373473573673773873974074174274374474574674774874975075175275375475575675775875976076176276376476576676776876977077177277377477577677777877978078178278378478578678778878979079179279379479579679779879980080180280380480580680780880981081181281381481581681781881982082182282382482582682782882983083183283383483583683783883984084184284384484584684784884985085185285385485585685785885986086186286386486586686786886987087187287387487587687787887988088188288388488588688788888989089189289389489589689789889990090190290390490590690790890991091191291391491591691791891992092192292392492592692792892993093193293393493593693793893994094194294394494594694794894995095195295395495595695795895996096196296396496596696796896997097197297397497597697797897998098198298398498598698798898999099199299399499599699799899910001001100210031004100510061007100810091010101110121013101410151016101710181019102010211022102310241025102610271028102910301031103210331034103510361037103810391040104110421043104410451046104710481049105010511052105310541055105610571058105910601061106210631064106510661067106810691070107110721073107410751076107710781079108010811082108310841085108610871088108910901091109210931094109510961097109810991100110111021103110411051106110711081109111011111112111311141115111611171118111911201121112211231124112511261127112811291130113111321133113411351136113711381139114011411142114311441145114611471148114911501151115211531154115511561157115811591160116111621163116411651166116711681169117011711172117311741175117611771178117911801181118211831184118511861187118811891190119111921193119411951196119711981199120012011202120312041205120612071208120912101211121212131214121512161217121812191220122112221223122412251226122712281229123012311232123312341235123612371238123912401241124212431244124512461247124812491250125112521253125412551256125712581259126012611262126312641265126612671268126912701271127212731274127512761277127812791280128112821283128412851286128712881289129012911292129312941295129612971298129913001301130213031304130513061307130813091310131113121313131413151316131713181319132013211322132313241325132613271328132913301331133213331334133513361337133813391340134113421343134413451346134713481349135013511352135313541355135613571358135913601361136213631364136513661367136813691370137113721373137413751376137713781379138013811382138313841385138613871388138913901391139213931394139513961397139813991400140114021403140414051406140714081409141014111412141314141415141614171418141914201421142214231424142514261427142814291430143114321433143414351436143714381439144014411442144314441445144614471448144914501451145214531454145514561457145814591460146114621463146414651466146714681469147014711472147314741475147614771478147914801481148214831484148514861487148814891490149114921493149414951496149714981499150015011502150315041505150615071508150915101511151215131514151515161517151815191520152115221523152415251526152715281529153015311532153315341535153615371538153915401541154215431544154515461547154815491550155115521553155415551556155715581559156015611562156315641565156615671568156915701571157215731574157515761577157815791580158115821583158415851586158715881589159015911592159315941595159615971598159916001601160216031604160516061607160816091610161116121613161416151616161716181619162016211622162316241625162616271628162916301631163216331634163516361637163816391640164116421643164416451646164716481649165016511652165316541655165616571658165916601661166216631664166516661667166816691670167116721673167416751676167716781679168016811682168316841685168616871688168916901691169216931694169516961697169816991700170117021703170417051706170717081709171017111712171317141715171617171718171917201721172217231724172517261727172817291730173117321733173417351736173717381739174017411742174317441745174617471748174917501751175217531754175517561757175817591760176117621763176417651766176717681769177017711772177317741775177617771778177917801781178217831784178517861787178817891790179117921793179417951796179717981799180018011802180318041805180618071808180918101811181218131814181518161817181818191820182118221823182418251826182718281829183018311832183318341835183618371838183918401841184218431844184518461847184818491850185118521853185418551856185718581859186018611862186318641865186618671868186918701871187218731874187518761877187818791880188118821883188418851886188718881889189018911892189318941895189618971898189919001901190219031904190519061907190819091910191119121913191419151916191719181919192019211922192319241925192619271928192919301931193219331934193519361937193819391940194119421943194419451946194719481949195019511952195319541955195619571958195919601961196219631964196519661967196819691970197119721973197419751976197719781979198019811982198319841985198619871988198919901991199219931994199519961997199819992000200120022003200420052006200720082009201020112012201320142015201620172018201920202021202220232024202520262027202820292030203120322033203420352036203720382039204020412042204320442045204620472048204920502051205220532054205520562057205820592060206120622063206420652066206720682069207020712072207320742075207620772078207920802081208220832084208520862087208820892090209120922093209420952096209720982099210021012102210321042105210621072108210921102111211221132114211521162117211821192120212121222123212421252126212721282129213021312132213321342135213621372138213921402141214221432144214521462147214821492150215121522153215421552156215721582159216021612162216321642165216621672168216921702171217221732174217521762177217821792180218121822183218421852186218721882189219021912192219321942195219621972198219922002201220222032204220522062207220822092210221122122213221422152216221722182219222022212222222322242225222622272228222922302231223222332234223522362237223822392240224122422243224422452246224722482249225022512252225322542255225622572258225922602261226222632264226522662267226822692270227122722273227422752276227722782279228022812282228322842285228622872288228922902291229222932294229522962297229822992300230123022303230423052306230723082309231023112312231323142315231623172318231923202321232223232324232523262327232823292330233123322333233423352336233723382339234023412342234323442345234623472348234923502351235223532354235523562357235823592360236123622363236423652366236723682369237023712372237323742375237623772378237923802381238223832384238523862387238823892390239123922393239423952396239723982399240024012402240324042405240624072408240924102411241224132414241524162417241824192420242124222423242424252426242724282429243024312432243324342435243624372438243924402441244224432444244524462447244824492450245124522453245424552456245724582459246024612462246324642465246624672468246924702471247224732474247524762477247824792480248124822483248424852486248724882489249024912492249324942495249624972498249925002501250225032504250525062507250825092510251125122513251425152516251725182519252025212522252325242525252625272528252925302531253225332534253525362537253825392540254125422543254425452546254725482549255025512552255325542555255625572558255925602561256225632564256525662567256825692570257125722573257425752576257725782579258025812582258325842585258625872588258925902591259225932594259525962597259825992600260126022603260426052606260726082609261026112612261326142615261626172618261926202621262226232624262526262627262826292630263126322633263426352636263726382639264026412642264326442645264626472648264926502651265226532654265526562657265826592660266126622663266426652666266726682669267026712672267326742675267626772678267926802681268226832684268526862687268826892690269126922693269426952696269726982699270027012702270327042705270627072708270927102711271227132714271527162717271827192720272127222723272427252726272727282729273027312732273327342735273627372738273927402741274227432744274527462747274827492750275127522753275427552756275727582759276027612762276327642765276627672768276927702771277227732774277527762777277827792780278127822783278427852786278727882789279027912792279327942795279627972798279928002801280228032804280528062807280828092810281128122813281428152816281728182819282028212822282328242825282628272828282928302831283228332834283528362837283828392840284128422843284428452846284728482849285028512852285328542855285628572858285928602861286228632864286528662867286828692870287128722873287428752876287728782879288028812882288328842885288628872888288928902891289228932894289528962897289828992900290129022903290429052906290729082909291029112912291329142915291629172918291929202921292229232924292529262927292829292930293129322933293429352936293729382939294029412942294329442945294629472948294929502951295229532954295529562957295829592960296129622963296429652966296729682969297029712972297329742975297629772978297929802981298229832984298529862987298829892990299129922993299429952996299729982999300030013002300330043005300630073008300930103011301230133014301530163017301830193020302130223023302430253026302730283029303030313032303330343035303630373038303930403041304230433044304530463047304830493050305130523053305430553056305730583059306030613062306330643065306630673068306930703071307230733074307530763077307830793080308130823083308430853086308730883089309030913092309330943095309630973098309931003101310231033104310531063107310831093110311131123113311431153116311731183119312031213122312331243125312631273128312931303131313231333134313531363137313831393140314131423143314431453146314731483149315031513152315331543155315631573158315931603161316231633164316531663167316831693170317131723173317431753176317731783179318031813182318331843185318631873188318931903191319231933194319531963197319831993200320132023203320432053206320732083209321032113212321332143215321632173218321932203221322232233224322532263227322832293230323132323233323432353236323732383239324032413242324332443245324632473248324932503251325232533254325532563257325832593260326132623263326432653266326732683269327032713272327332743275327632773278327932803281328232833284328532863287328832893290329132923293329432953296329732983299330033013302330333043305330633073308330933103311331233133314331533163317331833193320332133223323332433253326332733283329333033313332333333343335333633373338333933403341334233433344334533463347334833493350335133523353335433553356335733583359336033613362336333643365336633673368336933703371337233733374337533763377337833793380338133823383338433853386338733883389339033913392339333943395339633973398339934003401340234033404340534063407340834093410341134123413341434153416341734183419342034213422342334243425342634273428342934303431343234333434343534363437343834393440344134423443344434453446344734483449345034513452345334543455345634573458345934603461346234633464346534663467346834693470347134723473347434753476347734783479348034813482348334843485348634873488348934903491349234933494349534963497349834993500350135023503350435053506350735083509351035113512351335143515351635173518351935203521352235233524352535263527352835293530353135323533353435353536353735383539354035413542354335443545354635473548354935503551355235533554355535563557355835593560356135623563356435653566
  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 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-list-deprecated-options]] **--list-deprecated-options**::
  69. List all valid options that are scheduled to become obsolete in a
  70. future version. (This is a warning, not a promise.)
  71. [[opt-version]] **--version**::
  72. Display Tor version and exit. The output is a single line of the format
  73. "Tor version [version number]." (The version number format
  74. is as specified in version-spec.txt.)
  75. [[opt-quiet]] **--quiet**|**--hush**::
  76. Override the default console log. By default, Tor starts out logging
  77. messages at level "notice" and higher to the console. It stops doing so
  78. after it parses its configuration, if the configuration tells it to log
  79. anywhere else. You can override this behavior with the **--hush** option,
  80. which tells Tor to only send warnings and errors to the console, or with
  81. the **--quiet** option, which tells Tor not to log to the console at all.
  82. [[opt-keygen]] **--keygen** [**--newpass**]::
  83. Running "tor --keygen" creates a new ed25519 master identity key for a
  84. relay, or only a fresh temporary signing key and certificate, if you
  85. already have a master key. Optionally you can encrypt the master identity
  86. key with a passphrase: Tor will ask you for one. If you don't want to
  87. encrypt the master key, just don't enter any passphrase when asked. +
  88. +
  89. The **--newpass** option should be used with --keygen only when you need
  90. to add, change, or remove a passphrase on an existing ed25519 master
  91. identity key. You will be prompted for the old passphase (if any),
  92. and the new passphrase (if any). +
  93. +
  94. When generating a master key, you will probably want to use
  95. **--DataDirectory** to control where the keys
  96. and certificates will be stored, and **--SigningKeyLifetime** to
  97. control their lifetimes. Their behavior is as documented in the
  98. server options section below. (You must have write access to the specified
  99. DataDirectory.) +
  100. +
  101. To use the generated files, you must copy them to the DataDirectory/keys
  102. directory of your Tor daemon, and make sure that they are owned by the
  103. user actually running the Tor daemon on your system.
  104. **--passphrase-fd** __FILEDES__::
  105. Filedescriptor to read the passphrase from. Note that unlike with the
  106. tor-gencert program, the entire file contents are read and used as
  107. the passphrase, including any trailing newlines.
  108. Default: read from the terminal.
  109. [[opt-key-expiration]] **--key-expiration** [**purpose**]::
  110. The **purpose** specifies which type of key certificate to determine
  111. the expiration of. The only currently recognised **purpose** is
  112. "sign". +
  113. +
  114. Running "tor --key-expiration sign" will attempt to find your signing
  115. key certificate and will output, both in the logs as well as to stdout,
  116. the signing key certificate's expiration time in ISO-8601 format.
  117. For example, the output sent to stdout will be of the form:
  118. "signing-cert-expiry: 2017-07-25 08:30:15 UTC"
  119. Other options can be specified on the command-line in the format "--option
  120. value", in the format "option value", or in a configuration file. For
  121. instance, you can tell Tor to start listening for SOCKS connections on port
  122. 9999 by passing --SocksPort 9999 or SocksPort 9999 to it on the command line,
  123. or by putting "SocksPort 9999" in the configuration file. You will need to
  124. quote options with spaces in them: if you want Tor to log all debugging
  125. messages to debug.log, you will probably need to say **--Log** `"debug file
  126. debug.log"`.
  127. Options on the command line override those in configuration files. See the
  128. next section for more information.
  129. THE CONFIGURATION FILE FORMAT
  130. -----------------------------
  131. All configuration options in a configuration are written on a single line by
  132. default. They take the form of an option name and a value, or an option name
  133. and a quoted value (option value or option "value"). Anything after a #
  134. character is treated as a comment. Options are
  135. case-insensitive. C-style escaped characters are allowed inside quoted
  136. values. To split one configuration entry into multiple lines, use a single
  137. backslash character (\) before the end of the line. Comments can be used in
  138. such multiline entries, but they must start at the beginning of a line.
  139. Configuration options can be imported from files or folders using the %include
  140. option with the value being a path. If the path is a file, the options from the
  141. file will be parsed as if they were written where the %include option is. If
  142. the path is a folder, all files on that folder will be parsed following lexical
  143. order. Files starting with a dot are ignored. Files on subfolders are ignored.
  144. The %include option can be used recursively.
  145. By default, an option on the command line overrides an option found in the
  146. configuration file, and an option in a configuration file overrides one in
  147. the defaults file.
  148. This rule is simple for options that take a single value, but it can become
  149. complicated for options that are allowed to occur more than once: if you
  150. specify four SocksPorts in your configuration file, and one more SocksPort on
  151. the command line, the option on the command line will replace __all__ of the
  152. SocksPorts in the configuration file. If this isn't what you want, prefix
  153. the option name with a plus sign (+), and it will be appended to the previous
  154. set of options instead. For example, setting SocksPort 9100 will use only
  155. port 9100, but setting +SocksPort 9100 will use ports 9100 and 9050 (because
  156. this is the default).
  157. Alternatively, you might want to remove every instance of an option in the
  158. configuration file, and not replace it at all: you might want to say on the
  159. command line that you want no SocksPorts at all. To do that, prefix the
  160. option name with a forward slash (/). You can use the plus sign (+) and the
  161. forward slash (/) in the configuration file and on the command line.
  162. GENERAL OPTIONS
  163. ---------------
  164. [[BandwidthRate]] **BandwidthRate** __N__ **bytes**|**KBytes**|**MBytes**|**GBytes**|**TBytes**|**KBits**|**MBits**|**GBits**|**TBits**::
  165. A token bucket limits the average incoming bandwidth usage on this node
  166. to the specified number of bytes per second, and the average outgoing
  167. bandwidth usage to that same value. If you want to run a relay in the
  168. public network, this needs to be _at the very least_ 75 KBytes for a
  169. relay (that is, 600 kbits) or 50 KBytes for a bridge (400 kbits) -- but of
  170. course, more is better; we recommend at least 250 KBytes (2 mbits) if
  171. possible. (Default: 1 GByte) +
  172. +
  173. Note that this option, and other bandwidth-limiting options, apply to TCP
  174. data only: They do not count TCP headers or DNS traffic. +
  175. +
  176. With this option, and in other options that take arguments in bytes,
  177. KBytes, and so on, other formats are also supported. Notably, "KBytes" can
  178. also be written as "kilobytes" or "kb"; "MBytes" can be written as
  179. "megabytes" or "MB"; "kbits" can be written as "kilobits"; and so forth.
  180. Tor also accepts "byte" and "bit" in the singular.
  181. The prefixes "tera" and "T" are also recognized.
  182. If no units are given, we default to bytes.
  183. To avoid confusion, we recommend writing "bytes" or "bits" explicitly,
  184. since it's easy to forget that "B" means bytes, not bits.
  185. [[BandwidthBurst]] **BandwidthBurst** __N__ **bytes**|**KBytes**|**MBytes**|**GBytes**|**TBytes**|**KBits**|**MBits**|**GBits**|**TBits**::
  186. Limit the maximum token bucket size (also known as the burst) to the given
  187. number of bytes in each direction. (Default: 1 GByte)
  188. [[MaxAdvertisedBandwidth]] **MaxAdvertisedBandwidth** __N__ **bytes**|**KBytes**|**MBytes**|**GBytes**|**TBytes**|**KBits**|**MBits**|**GBits**|**TBits**::
  189. If set, we will not advertise more than this amount of bandwidth for our
  190. BandwidthRate. Server operators who want to reduce the number of clients
  191. who ask to build circuits through them (since this is proportional to
  192. advertised bandwidth rate) can thus reduce the CPU demands on their server
  193. without impacting network performance.
  194. [[RelayBandwidthRate]] **RelayBandwidthRate** __N__ **bytes**|**KBytes**|**MBytes**|**GBytes**|**TBytes**|**KBits**|**MBits**|**GBits**|**TBits**::
  195. If not 0, a separate token bucket limits the average incoming bandwidth
  196. usage for \_relayed traffic_ on this node to the specified number of bytes
  197. per second, and the average outgoing bandwidth usage to that same value.
  198. Relayed traffic currently is calculated to include answers to directory
  199. requests, but that may change in future versions. They do not include directory
  200. fetches by the relay (from authority or other relays), because that is considered
  201. "client" activity. (Default: 0)
  202. [[RelayBandwidthBurst]] **RelayBandwidthBurst** __N__ **bytes**|**KBytes**|**MBytes**|**GBytes**|**TBytes**|**KBits**|**MBits**|**GBits**|**TBits**::
  203. If not 0, limit the maximum token bucket size (also known as the burst) for
  204. \_relayed traffic_ to the given number of bytes in each direction.
  205. They do not include directory fetches by the relay (from authority
  206. or other relays), because that is considered "client" activity. (Default: 0)
  207. [[PerConnBWRate]] **PerConnBWRate** __N__ **bytes**|**KBytes**|**MBytes**|**GBytes**|**TBytes**|**KBits**|**MBits**|**GBits**|**TBits**::
  208. If this option is set manually, or via the "perconnbwrate" consensus
  209. field, Tor will use it for separate rate limiting for each connection
  210. from a non-relay. (Default: 0)
  211. [[PerConnBWBurst]] **PerConnBWBurst** __N__ **bytes**|**KBytes**|**MBytes**|**GBytes**|**TBytes**|**KBits**|**MBits**|**GBits**|**TBits**::
  212. If this option is set manually, or via the "perconnbwburst" consensus
  213. field, Tor will use it for separate rate limiting for each connection
  214. from a non-relay. (Default: 0)
  215. [[ClientTransportPlugin]] **ClientTransportPlugin** __transport__ socks4|socks5 __IP__:__PORT__::
  216. **ClientTransportPlugin** __transport__ exec __path-to-binary__ [options]::
  217. In its first form, when set along with a corresponding Bridge line, the Tor
  218. client forwards its traffic to a SOCKS-speaking proxy on "IP:PORT".
  219. (IPv4 addresses should written as-is; IPv6 addresses should be wrapped in
  220. square brackets.) It's the
  221. duty of that proxy to properly forward the traffic to the bridge. +
  222. +
  223. In its second form, when set along with a corresponding Bridge line, the Tor
  224. client launches the pluggable transport proxy executable in
  225. __path-to-binary__ using __options__ as its command-line options, and
  226. forwards its traffic to it. It's the duty of that proxy to properly forward
  227. the traffic to the bridge.
  228. [[ServerTransportPlugin]] **ServerTransportPlugin** __transport__ exec __path-to-binary__ [options]::
  229. The Tor relay launches the pluggable transport proxy in __path-to-binary__
  230. using __options__ as its command-line options, and expects to receive
  231. proxied client traffic from it.
  232. [[ServerTransportListenAddr]] **ServerTransportListenAddr** __transport__ __IP__:__PORT__::
  233. When this option is set, Tor will suggest __IP__:__PORT__ as the
  234. listening address of any pluggable transport proxy that tries to
  235. launch __transport__. (IPv4 addresses should written as-is; IPv6
  236. addresses should be wrapped in square brackets.)
  237. [[ServerTransportOptions]] **ServerTransportOptions** __transport__ __k=v__ __k=v__ ...::
  238. When this option is set, Tor will pass the __k=v__ parameters to
  239. any pluggable transport proxy that tries to launch __transport__. +
  240. (Example: ServerTransportOptions obfs45 shared-secret=bridgepasswd cache=/var/lib/tor/cache)
  241. [[ExtORPort]] **ExtORPort** \['address':]__port__|**auto**::
  242. Open this port to listen for Extended ORPort connections from your
  243. pluggable transports.
  244. [[ExtORPortCookieAuthFile]] **ExtORPortCookieAuthFile** __Path__::
  245. If set, this option overrides the default location and file name
  246. for the Extended ORPort's cookie file -- the cookie file is needed
  247. for pluggable transports to communicate through the Extended ORPort.
  248. [[ExtORPortCookieAuthFileGroupReadable]] **ExtORPortCookieAuthFileGroupReadable** **0**|**1**::
  249. If this option is set to 0, don't allow the filesystem group to read the
  250. Extended OR Port cookie file. If the option is set to 1, make the cookie
  251. file readable by the default GID. [Making the file readable by other
  252. groups is not yet implemented; let us know if you need this for some
  253. reason.] (Default: 0)
  254. [[ConnLimit]] **ConnLimit** __NUM__::
  255. The minimum number of file descriptors that must be available to the Tor
  256. process before it will start. Tor will ask the OS for as many file
  257. descriptors as the OS will allow (you can find this by "ulimit -H -n").
  258. If this number is less than ConnLimit, then Tor will refuse to start. +
  259. +
  260. Tor relays need thousands of sockets, to connect to every other relay.
  261. If you are running a private bridge, you can reduce the number of sockets
  262. that Tor uses. For example, to limit Tor to 500 sockets, run
  263. "ulimit -n 500" in a shell. Then start tor in the same shell, with
  264. **ConnLimit 500**. You may also need to set **DisableOOSCheck 0**. +
  265. +
  266. Unless you have severely limited sockets, you probably don't need to
  267. adjust **ConnLimit** itself. It has no effect on Windows, since that
  268. platform lacks getrlimit(). (Default: 1000)
  269. [[DisableNetwork]] **DisableNetwork** **0**|**1**::
  270. When this option is set, we don't listen for or accept any connections
  271. other than controller connections, and we close (and don't reattempt)
  272. any outbound
  273. connections. Controllers sometimes use this option to avoid using
  274. the network until Tor is fully configured. Tor will make still certain
  275. network-related calls (like DNS lookups) as a part of its configuration
  276. process, even if DisableNetwork is set. (Default: 0)
  277. [[ConstrainedSockets]] **ConstrainedSockets** **0**|**1**::
  278. If set, Tor will tell the kernel to attempt to shrink the buffers for all
  279. sockets to the size specified in **ConstrainedSockSize**. This is useful for
  280. virtual servers and other environments where system level TCP buffers may
  281. be limited. If you're on a virtual server, and you encounter the "Error
  282. creating network socket: No buffer space available" message, you are
  283. likely experiencing this problem. +
  284. +
  285. The preferred solution is to have the admin increase the buffer pool for
  286. the host itself via /proc/sys/net/ipv4/tcp_mem or equivalent facility;
  287. this configuration option is a second-resort. +
  288. +
  289. The DirPort option should also not be used if TCP buffers are scarce. The
  290. cached directory requests consume additional sockets which exacerbates
  291. the problem. +
  292. +
  293. You should **not** enable this feature unless you encounter the "no buffer
  294. space available" issue. Reducing the TCP buffers affects window size for
  295. the TCP stream and will reduce throughput in proportion to round trip
  296. time on long paths. (Default: 0)
  297. [[ConstrainedSockSize]] **ConstrainedSockSize** __N__ **bytes**|**KBytes**::
  298. When **ConstrainedSockets** is enabled the receive and transmit buffers for
  299. all sockets will be set to this limit. Must be a value between 2048 and
  300. 262144, in 1024 byte increments. Default of 8192 is recommended.
  301. [[ControlPort]] **ControlPort** \['address':]__port__|**unix:**__path__|**auto** [__flags__]::
  302. If set, Tor will accept connections on this port and allow those
  303. connections to control the Tor process using the Tor Control Protocol
  304. (described in control-spec.txt in
  305. https://spec.torproject.org[torspec]). Note: unless you also
  306. specify one or more of **HashedControlPassword** or
  307. **CookieAuthentication**, setting this option will cause Tor to allow
  308. any process on the local host to control it. (Setting both authentication
  309. methods means either method is sufficient to authenticate to Tor.) This
  310. option is required for many Tor controllers; most use the value of 9051.
  311. If a unix domain socket is used, you may quote the path using standard
  312. C escape sequences. You can specify this directive multiple times, to
  313. bind to multiple address/port pairs.
  314. Set it to "auto" to have Tor pick a port for you. (Default: 0) +
  315. +
  316. Recognized flags are...
  317. **GroupWritable**;;
  318. Unix domain sockets only: makes the socket get created as
  319. group-writable.
  320. **WorldWritable**;;
  321. Unix domain sockets only: makes the socket get created as
  322. world-writable.
  323. **RelaxDirModeCheck**;;
  324. Unix domain sockets only: Do not insist that the directory
  325. that holds the socket be read-restricted.
  326. [[ControlSocket]] **ControlSocket** __Path__::
  327. Like ControlPort, but listens on a Unix domain socket, rather than a TCP
  328. socket. '0' disables ControlSocket. (Unix and Unix-like systems only.)
  329. (Default: 0)
  330. [[ControlSocketsGroupWritable]] **ControlSocketsGroupWritable** **0**|**1**::
  331. If this option is set to 0, don't allow the filesystem group to read and
  332. write unix sockets (e.g. ControlSocket). If the option is set to 1, make
  333. the control socket readable and writable by the default GID. (Default: 0)
  334. [[HashedControlPassword]] **HashedControlPassword** __hashed_password__::
  335. Allow connections on the control port if they present
  336. the password whose one-way hash is __hashed_password__. You
  337. can compute the hash of a password by running "tor --hash-password
  338. __password__". You can provide several acceptable passwords by using more
  339. than one HashedControlPassword line.
  340. [[CookieAuthentication]] **CookieAuthentication** **0**|**1**::
  341. If this option is set to 1, allow connections on the control port
  342. when the connecting process knows the contents of a file named
  343. "control_auth_cookie", which Tor will create in its data directory. This
  344. authentication method should only be used on systems with good filesystem
  345. security. (Default: 0)
  346. [[CookieAuthFile]] **CookieAuthFile** __Path__::
  347. If set, this option overrides the default location and file name
  348. for Tor's cookie file. (See CookieAuthentication above.)
  349. [[CookieAuthFileGroupReadable]] **CookieAuthFileGroupReadable** **0**|**1**::
  350. If this option is set to 0, don't allow the filesystem group to read the
  351. cookie file. If the option is set to 1, make the cookie file readable by
  352. the default GID. [Making the file readable by other groups is not yet
  353. implemented; let us know if you need this for some reason.] (Default: 0)
  354. [[ControlPortWriteToFile]] **ControlPortWriteToFile** __Path__::
  355. If set, Tor writes the address and port of any control port it opens to
  356. this address. Usable by controllers to learn the actual control port
  357. when ControlPort is set to "auto".
  358. [[ControlPortFileGroupReadable]] **ControlPortFileGroupReadable** **0**|**1**::
  359. If this option is set to 0, don't allow the filesystem group to read the
  360. control port file. If the option is set to 1, make the control port
  361. file readable by the default GID. (Default: 0)
  362. [[DataDirectory]] **DataDirectory** __DIR__::
  363. Store working data in DIR. Can not be changed while tor is running.
  364. (Default: ~/.tor if your home directory is not /; otherwise,
  365. @LOCALSTATEDIR@/lib/tor. On Windows, the default is
  366. your ApplicationData folder.)
  367. [[DataDirectoryGroupReadable]] **DataDirectoryGroupReadable** **0**|**1**::
  368. If this option is set to 0, don't allow the filesystem group to read the
  369. DataDirectory. If the option is set to 1, make the DataDirectory readable
  370. by the default GID. (Default: 0)
  371. [[CacheDirectory]] **CacheDirectory** __DIR__::
  372. Store cached directory data in DIR. Can not be changed while tor is
  373. running.
  374. (Default: uses the value of DataDirectory.)
  375. [[CacheDirectoryGroupReadable]] **CacheDirectoryGroupReadable** **0**|**1**|**auto**::
  376. If this option is set to 0, don't allow the filesystem group to read the
  377. CacheDirectory. If the option is set to 1, make the CacheDirectory readable
  378. by the default GID. If the option is "auto", then we use the
  379. setting for DataDirectoryGroupReadable when the CacheDirectory is the
  380. same as the DataDirectory, and 0 otherwise. (Default: auto)
  381. [[FallbackDir]] **FallbackDir** __ipv4address__:__port__ orport=__port__ id=__fingerprint__ [weight=__num__] [ipv6=**[**__ipv6address__**]**:__orport__]::
  382. When we're unable to connect to any directory cache for directory info
  383. (usually because we don't know about any yet) we try a directory authority.
  384. Clients also simultaneously try a FallbackDir, to avoid hangs on client
  385. startup if a directory authority is down. Clients retry FallbackDirs more
  386. often than directory authorities, to reduce the load on the directory
  387. authorities.
  388. By default, the directory authorities are also FallbackDirs. Specifying a
  389. FallbackDir replaces Tor's default hard-coded FallbackDirs (if any).
  390. (See the **DirAuthority** entry for an explanation of each flag.)
  391. [[UseDefaultFallbackDirs]] **UseDefaultFallbackDirs** **0**|**1**::
  392. Use Tor's default hard-coded FallbackDirs (if any). (When a
  393. FallbackDir line is present, it replaces the hard-coded FallbackDirs,
  394. regardless of the value of UseDefaultFallbackDirs.) (Default: 1)
  395. [[DirAuthority]] **DirAuthority** [__nickname__] [**flags**] __ipv4address__:__port__ __fingerprint__::
  396. Use a nonstandard authoritative directory server at the provided address
  397. and port, with the specified key fingerprint. This option can be repeated
  398. many times, for multiple authoritative directory servers. Flags are
  399. separated by spaces, and determine what kind of an authority this directory
  400. is. By default, an authority is not authoritative for any directory style
  401. or version unless an appropriate flag is given.
  402. Tor will use this authority as a bridge authoritative directory if the
  403. "bridge" flag is set. If a flag "orport=**port**" is given, Tor will use the
  404. given port when opening encrypted tunnels to the dirserver. If a flag
  405. "weight=**num**" is given, then the directory server is chosen randomly
  406. with probability proportional to that weight (default 1.0). If a
  407. flag "v3ident=**fp**" is given, the dirserver is a v3 directory authority
  408. whose v3 long-term signing key has the fingerprint **fp**. Lastly,
  409. if an "ipv6=**[**__ipv6address__**]**:__orport__" flag is present, then
  410. the directory
  411. authority is listening for IPv6 connections on the indicated IPv6 address
  412. and OR Port. +
  413. +
  414. Tor will contact the authority at __ipv4address__ to
  415. download directory documents. The provided __port__ value is a dirport;
  416. clients ignore this in favor of the specified "orport=" value. If an
  417. IPv6 ORPort is supplied, Tor will
  418. also download directory documents at the IPv6 ORPort. +
  419. +
  420. If no **DirAuthority** line is given, Tor will use the default directory
  421. authorities. NOTE: this option is intended for setting up a private Tor
  422. network with its own directory authorities. If you use it, you will be
  423. distinguishable from other users, because you won't believe the same
  424. authorities they do.
  425. [[DirAuthorityFallbackRate]] **DirAuthorityFallbackRate** __NUM__::
  426. When configured to use both directory authorities and fallback
  427. directories, the directory authorities also work as fallbacks. They are
  428. chosen with their regular weights, multiplied by this number, which
  429. should be 1.0 or less. The default is less than 1, to reduce load on
  430. authorities. (Default: 0.1)
  431. [[AlternateDirAuthority]] **AlternateDirAuthority** [__nickname__] [**flags**] __ipv4address__:__port__ __fingerprint__ +
  432. [[AlternateBridgeAuthority]] **AlternateBridgeAuthority** [__nickname__] [**flags**] __ipv4address__:__port__ __ fingerprint__::
  433. These options behave as DirAuthority, but they replace fewer of the
  434. default directory authorities. Using
  435. AlternateDirAuthority replaces the default Tor directory authorities, but
  436. leaves the default bridge authorities in
  437. place. Similarly,
  438. AlternateBridgeAuthority replaces the default bridge authority,
  439. but leaves the directory authorities alone.
  440. [[DisableAllSwap]] **DisableAllSwap** **0**|**1**::
  441. If set to 1, Tor will attempt to lock all current and future memory pages,
  442. so that memory cannot be paged out. Windows, OS X and Solaris are currently
  443. not supported. We believe that this feature works on modern Gnu/Linux
  444. distributions, and that it should work on *BSD systems (untested). This
  445. option requires that you start your Tor as root, and you should use the
  446. **User** option to properly reduce Tor's privileges.
  447. Can not be changed while tor is running. (Default: 0)
  448. [[DisableDebuggerAttachment]] **DisableDebuggerAttachment** **0**|**1**::
  449. If set to 1, Tor will attempt to prevent basic debugging attachment attempts
  450. by other processes. This may also keep Tor from generating core files if
  451. it crashes. It has no impact for users who wish to attach if they
  452. have CAP_SYS_PTRACE or if they are root. We believe that this feature
  453. works on modern Gnu/Linux distributions, and that it may also work on *BSD
  454. systems (untested). Some modern Gnu/Linux systems such as Ubuntu have the
  455. kernel.yama.ptrace_scope sysctl and by default enable it as an attempt to
  456. limit the PTRACE scope for all user processes by default. This feature will
  457. attempt to limit the PTRACE scope for Tor specifically - it will not attempt
  458. to alter the system wide ptrace scope as it may not even exist. If you wish
  459. to attach to Tor with a debugger such as gdb or strace you will want to set
  460. this to 0 for the duration of your debugging. Normal users should leave it
  461. on. Disabling this option while Tor is running is prohibited. (Default: 1)
  462. [[FetchDirInfoEarly]] **FetchDirInfoEarly** **0**|**1**::
  463. If set to 1, Tor will always fetch directory information like other
  464. directory caches, even if you don't meet the normal criteria for fetching
  465. early. Normal users should leave it off. (Default: 0)
  466. [[FetchDirInfoExtraEarly]] **FetchDirInfoExtraEarly** **0**|**1**::
  467. If set to 1, Tor will fetch directory information before other directory
  468. caches. It will attempt to download directory information closer to the
  469. start of the consensus period. Normal users should leave it off.
  470. (Default: 0)
  471. [[FetchHidServDescriptors]] **FetchHidServDescriptors** **0**|**1**::
  472. If set to 0, Tor will never fetch any hidden service descriptors from the
  473. rendezvous directories. This option is only useful if you're using a Tor
  474. controller that handles hidden service fetches for you. (Default: 1)
  475. [[FetchServerDescriptors]] **FetchServerDescriptors** **0**|**1**::
  476. If set to 0, Tor will never fetch any network status summaries or server
  477. descriptors from the directory servers. This option is only useful if
  478. you're using a Tor controller that handles directory fetches for you.
  479. (Default: 1)
  480. [[FetchUselessDescriptors]] **FetchUselessDescriptors** **0**|**1**::
  481. If set to 1, Tor will fetch every consensus flavor, and all server
  482. descriptors and authority certificates referenced by those consensuses,
  483. except for extra info descriptors. When this option is 1, Tor will also
  484. keep fetching descriptors, even when idle.
  485. If set to 0, Tor will avoid fetching useless descriptors: flavors that it
  486. is not using to build circuits, and authority certificates it does not
  487. trust. When Tor hasn't built any application circuits, it will go idle,
  488. and stop fetching descriptors. This option is useful if you're using a
  489. tor client with an external parser that uses a full consensus.
  490. This option fetches all documents except extrainfo descriptors,
  491. **DirCache** fetches and serves all documents except extrainfo
  492. descriptors, **DownloadExtraInfo*** fetches extrainfo documents, and serves
  493. them if **DirCache** is on, and **UseMicrodescriptors** changes the
  494. flavour of consensues and descriptors that is fetched and used for
  495. building circuits. (Default: 0)
  496. [[HTTPProxy]] **HTTPProxy** __host__[:__port__]::
  497. Tor will make all its directory requests through this host:port (or host:80
  498. if port is not specified), rather than connecting directly to any directory
  499. servers. (DEPRECATED: As of 0.3.1.0-alpha you should use HTTPSProxy.)
  500. [[HTTPProxyAuthenticator]] **HTTPProxyAuthenticator** __username:password__::
  501. If defined, Tor will use this username:password for Basic HTTP proxy
  502. authentication, as in RFC 2617. This is currently the only form of HTTP
  503. proxy authentication that Tor supports; feel free to submit a patch if you
  504. want it to support others. (DEPRECATED: As of 0.3.1.0-alpha you should use
  505. HTTPSProxyAuthenticator.)
  506. [[HTTPSProxy]] **HTTPSProxy** __host__[:__port__]::
  507. Tor will make all its OR (SSL) connections through this host:port (or
  508. host:443 if port is not specified), via HTTP CONNECT rather than connecting
  509. directly to servers. You may want to set **FascistFirewall** to restrict
  510. the set of ports you might try to connect to, if your HTTPS proxy only
  511. allows connecting to certain ports.
  512. [[HTTPSProxyAuthenticator]] **HTTPSProxyAuthenticator** __username:password__::
  513. If defined, Tor will use this username:password for Basic HTTPS proxy
  514. authentication, as in RFC 2617. This is currently the only form of HTTPS
  515. proxy authentication that Tor supports; feel free to submit a patch if you
  516. want it to support others.
  517. [[Sandbox]] **Sandbox** **0**|**1**::
  518. If set to 1, Tor will run securely through the use of a syscall sandbox.
  519. Otherwise the sandbox will be disabled. The option is currently an
  520. experimental feature. It only works on Linux-based operating systems,
  521. and only when Tor has been built with the libseccomp library. This option
  522. can not be changed while tor is running. +
  523. +
  524. When the **Sandbox** is 1, the following options can not be changed when tor
  525. is running:
  526. **Address**,
  527. **ConnLimit**,
  528. **CookieAuthFile**,
  529. **DirPortFrontPage**,
  530. **ExtORPortCookieAuthFile**,
  531. **Logs**,
  532. **ServerDNSResolvConfFile**,
  533. **ClientOnionAuthDir** (and any files in it won't reload on HUP signal).
  534. +
  535. Launching new Onion Services through the control port is not supported
  536. with current syscall sandboxing implementation.
  537. +
  538. Tor must remain in client or server mode (some changes to **ClientOnly**
  539. and **ORPort** are not allowed). Currently, if **Sandbox** is 1,
  540. **ControlPort** command "GETINFO address" will not work.
  541. +
  542. (Default: 0)
  543. [[Socks4Proxy]] **Socks4Proxy** __host__[:__port__]::
  544. Tor will make all OR connections through the SOCKS 4 proxy at host:port
  545. (or host:1080 if port is not specified).
  546. [[Socks5Proxy]] **Socks5Proxy** __host__[:__port__]::
  547. Tor will make all OR connections through the SOCKS 5 proxy at host:port
  548. (or host:1080 if port is not specified).
  549. [[Socks5ProxyUsername]] **Socks5ProxyUsername** __username__ +
  550. [[Socks5ProxyPassword]] **Socks5ProxyPassword** __password__::
  551. If defined, authenticate to the SOCKS 5 server using username and password
  552. in accordance to RFC 1929. Both username and password must be between 1 and
  553. 255 characters.
  554. [[UnixSocksGroupWritable]] **UnixSocksGroupWritable** **0**|**1**::
  555. If this option is set to 0, don't allow the filesystem group to read and
  556. write unix sockets (e.g. SocksPort unix:). If the option is set to 1, make
  557. the Unix socket readable and writable by the default GID. (Default: 0)
  558. [[KeepalivePeriod]] **KeepalivePeriod** __NUM__::
  559. To keep firewalls from expiring connections, send a padding keepalive cell
  560. every NUM seconds on open connections that are in use. (Default: 5 minutes)
  561. [[Log]] **Log** __minSeverity__[-__maxSeverity__] **stderr**|**stdout**|**syslog**::
  562. Send all messages between __minSeverity__ and __maxSeverity__ to the standard
  563. output stream, the standard error stream, or to the system log. (The
  564. "syslog" value is only supported on Unix.) Recognized severity levels are
  565. debug, info, notice, warn, and err. We advise using "notice" in most cases,
  566. since anything more verbose may provide sensitive information to an
  567. attacker who obtains the logs. If only one severity level is given, all
  568. messages of that level or higher will be sent to the listed destination.
  569. [[Log2]] **Log** __minSeverity__[-__maxSeverity__] **file** __FILENAME__::
  570. As above, but send log messages to the listed filename. The
  571. "Log" option may appear more than once in a configuration file.
  572. Messages are sent to all the logs that match their severity
  573. level.
  574. [[Log3]] **Log** **[**__domain__,...**]**__minSeverity__[-__maxSeverity__] ... **file** __FILENAME__ +
  575. [[Log4]] **Log** **[**__domain__,...**]**__minSeverity__[-__maxSeverity__] ... **stderr**|**stdout**|**syslog**::
  576. As above, but select messages by range of log severity __and__ by a
  577. set of "logging domains". Each logging domain corresponds to an area of
  578. functionality inside Tor. You can specify any number of severity ranges
  579. for a single log statement, each of them prefixed by a comma-separated
  580. list of logging domains. You can prefix a domain with $$~$$ to indicate
  581. negation, and use * to indicate "all domains". If you specify a severity
  582. range without a list of domains, it matches all domains. +
  583. +
  584. This is an advanced feature which is most useful for debugging one or two
  585. of Tor's subsystems at a time. +
  586. +
  587. The currently recognized domains are: general, crypto, net, config, fs,
  588. protocol, mm, http, app, control, circ, rend, bug, dir, dirserv, or, edge,
  589. acct, hist, handshake, heartbeat, channel, sched, guard, consdiff, dos,
  590. process, pt, btrack, and mesg.
  591. Domain names are case-insensitive. +
  592. +
  593. For example, "`Log [handshake]debug [~net,~mm]info notice stdout`" sends
  594. to stdout: all handshake messages of any severity, all info-and-higher
  595. messages from domains other than networking and memory management, and all
  596. messages of severity notice or higher.
  597. [[LogMessageDomains]] **LogMessageDomains** **0**|**1**::
  598. If 1, Tor includes message domains with each log message. Every log
  599. message currently has at least one domain; most currently have exactly
  600. one. This doesn't affect controller log messages. (Default: 0)
  601. [[MaxUnparseableDescSizeToLog]] **MaxUnparseableDescSizeToLog** __N__ **bytes**|**KBytes**|**MBytes**|**GBytes**|**TBytes**::
  602. Unparseable descriptors (e.g. for votes, consensuses, routers) are logged
  603. in separate files by hash, up to the specified size in total. Note that
  604. only files logged during the lifetime of this Tor process count toward the
  605. total; this is intended to be used to debug problems without opening live
  606. servers to resource exhaustion attacks. (Default: 10 MB)
  607. [[OutboundBindAddress]] **OutboundBindAddress** __IP__::
  608. Make all outbound connections originate from the IP address specified. This
  609. is only useful when you have multiple network interfaces, and you want all
  610. of Tor's outgoing connections to use a single one. This option may
  611. be used twice, once with an IPv4 address and once with an IPv6 address.
  612. IPv6 addresses should be wrapped in square brackets.
  613. This setting will be ignored for connections to the loopback addresses
  614. (127.0.0.0/8 and ::1), and is not used for DNS requests as well.
  615. [[OutboundBindAddressOR]] **OutboundBindAddressOR** __IP__::
  616. Make all outbound non-exit (relay and other) connections
  617. originate from the IP address specified. This option overrides
  618. **OutboundBindAddress** for the same IP version. This option may
  619. be used twice, once with an IPv4 address and once with an IPv6
  620. address. IPv6 addresses should be wrapped in square brackets.
  621. This setting will be ignored for connections to the loopback
  622. addresses (127.0.0.0/8 and ::1).
  623. [[OutboundBindAddressExit]] **OutboundBindAddressExit** __IP__::
  624. Make all outbound exit connections originate from the IP address
  625. specified. This option overrides **OutboundBindAddress** for the
  626. same IP version. This option may be used twice, once with an IPv4
  627. address and once with an IPv6 address.
  628. IPv6 addresses should be wrapped in square brackets.
  629. This setting will be ignored
  630. for connections to the loopback addresses (127.0.0.0/8 and ::1).
  631. [[PidFile]] **PidFile** __FILE__::
  632. On startup, write our PID to FILE. On clean shutdown, remove
  633. FILE. Can not be changed while tor is running.
  634. [[ProtocolWarnings]] **ProtocolWarnings** **0**|**1**::
  635. If 1, Tor will log with severity \'warn' various cases of other parties not
  636. following the Tor specification. Otherwise, they are logged with severity
  637. \'info'. (Default: 0)
  638. [[RunAsDaemon]] **RunAsDaemon** **0**|**1**::
  639. If 1, Tor forks and daemonizes to the background. This option has no effect
  640. on Windows; instead you should use the --service command-line option.
  641. Can not be changed while tor is running.
  642. (Default: 0)
  643. [[LogTimeGranularity]] **LogTimeGranularity** __NUM__::
  644. Set the resolution of timestamps in Tor's logs to NUM milliseconds.
  645. NUM must be positive and either a divisor or a multiple of 1 second.
  646. Note that this option only controls the granularity written by Tor to
  647. a file or console log. Tor does not (for example) "batch up" log
  648. messages to affect times logged by a controller, times attached to
  649. syslog messages, or the mtime fields on log files. (Default: 1 second)
  650. [[TruncateLogFile]] **TruncateLogFile** **0**|**1**::
  651. If 1, Tor will overwrite logs at startup and in response to a HUP signal,
  652. instead of appending to them. (Default: 0)
  653. [[SyslogIdentityTag]] **SyslogIdentityTag** __tag__::
  654. When logging to syslog, adds a tag to the syslog identity such that
  655. log entries are marked with "Tor-__tag__". Can not be changed while tor is
  656. running. (Default: none)
  657. [[AndroidIdentityTag]] **AndroidIdentityTag** __tag__::
  658. When logging to Android's logging subsystem, adds a tag to the log identity
  659. such that log entries are marked with "Tor-__tag__". Can not be changed while
  660. tor is running. (Default: none)
  661. [[SafeLogging]] **SafeLogging** **0**|**1**|**relay**::
  662. Tor can scrub potentially sensitive strings from log messages (e.g.
  663. addresses) by replacing them with the string [scrubbed]. This way logs can
  664. still be useful, but they don't leave behind personally identifying
  665. information about what sites a user might have visited. +
  666. +
  667. If this option is set to 0, Tor will not perform any scrubbing, if it is
  668. set to 1, all potentially sensitive strings are replaced. If it is set to
  669. relay, all log messages generated when acting as a relay are sanitized, but
  670. all messages generated when acting as a client are not.
  671. Note: Tor may not heed this option when logging at log levels below Notice.
  672. (Default: 1)
  673. [[User]] **User** __Username__::
  674. On startup, setuid to this user and setgid to their primary group.
  675. Can not be changed while tor is running.
  676. [[KeepBindCapabilities]] **KeepBindCapabilities** **0**|**1**|**auto**::
  677. On Linux, when we are started as root and we switch our identity using
  678. the **User** option, the **KeepBindCapabilities** option tells us whether to
  679. try to retain our ability to bind to low ports. If this value is 1, we
  680. try to keep the capability; if it is 0 we do not; and if it is **auto**,
  681. we keep the capability only if we are configured to listen on a low port.
  682. Can not be changed while tor is running.
  683. (Default: auto.)
  684. [[HardwareAccel]] **HardwareAccel** **0**|**1**::
  685. If non-zero, try to use built-in (static) crypto hardware acceleration when
  686. available. Can not be changed while tor is running. (Default: 0)
  687. [[AccelName]] **AccelName** __NAME__::
  688. When using OpenSSL hardware crypto acceleration attempt to load the dynamic
  689. engine of this name. This must be used for any dynamic hardware engine.
  690. Names can be verified with the openssl engine command. Can not be changed
  691. while tor is running.
  692. [[AccelDir]] **AccelDir** __DIR__::
  693. Specify this option if using dynamic hardware acceleration and the engine
  694. implementation library resides somewhere other than the OpenSSL default.
  695. Can not be changed while tor is running.
  696. [[AvoidDiskWrites]] **AvoidDiskWrites** **0**|**1**::
  697. If non-zero, try to write to disk less frequently than we would otherwise.
  698. This is useful when running on flash memory or other media that support
  699. only a limited number of writes. (Default: 0)
  700. [[CircuitPriorityHalflife]] **CircuitPriorityHalflife** __NUM__::
  701. If this value is set, we override the default algorithm for choosing which
  702. circuit's cell to deliver or relay next. It is delivered first to the
  703. circuit that has the lowest weighted cell count, where cells are weighted
  704. exponentially according to this value (in seconds). If the value is -1, it
  705. is taken from the consensus if possible else it will fallback to the
  706. default value of 30. Minimum: 1, Maximum: 2147483647. This can be defined
  707. as a float value. This is an advanced option; you generally shouldn't have
  708. to mess with it. (Default: -1)
  709. [[CountPrivateBandwidth]] **CountPrivateBandwidth** **0**|**1**::
  710. If this option is set, then Tor's rate-limiting applies not only to
  711. remote connections, but also to connections to private addresses like
  712. 127.0.0.1 or 10.0.0.1. This is mostly useful for debugging
  713. rate-limiting. (Default: 0)
  714. [[ExtendByEd25519ID]] **ExtendByEd25519ID** **0**|**1**|**auto**::
  715. If this option is set to 1, we always try to include a relay's Ed25519 ID
  716. when telling the proceeding relay in a circuit to extend to it.
  717. If this option is set to 0, we never include Ed25519 IDs when extending
  718. circuits. If the option is set to "default", we obey a
  719. parameter in the consensus document. (Default: auto)
  720. [[NoExec]] **NoExec** **0**|**1**::
  721. If this option is set to 1, then Tor will never launch another
  722. executable, regardless of the settings of ClientTransportPlugin
  723. or ServerTransportPlugin. Once this option has been set to 1,
  724. it cannot be set back to 0 without restarting Tor. (Default: 0)
  725. [[Schedulers]] **Schedulers** **KIST**|**KISTLite**|**Vanilla**::
  726. Specify the scheduler type that tor should use. The scheduler is
  727. responsible for moving data around within a Tor process. This is an ordered
  728. list by priority which means that the first value will be tried first and if
  729. unavailable, the second one is tried and so on. It is possible to change
  730. these values at runtime. This option mostly effects relays, and most
  731. operators should leave it set to its default value.
  732. (Default: KIST,KISTLite,Vanilla)
  733. +
  734. The possible scheduler types are:
  735. +
  736. **KIST**: Kernel-Informed Socket Transport. Tor will use TCP information
  737. from the kernel to make informed decisions regarding how much data to send
  738. and when to send it. KIST also handles traffic in batches (see
  739. KISTSchedRunInterval) in order to improve traffic prioritization decisions.
  740. As implemented, KIST will only work on Linux kernel version 2.6.39 or
  741. higher.
  742. +
  743. **KISTLite**: Same as KIST but without kernel support. Tor will use all
  744. the same mechanics as with KIST, including the batching, but its decisions
  745. regarding how much data to send will not be as good. KISTLite will work on
  746. all kernels and operating systems, and the majority of the benefits of KIST
  747. are still realized with KISTLite.
  748. +
  749. **Vanilla**: The scheduler that Tor used before KIST was implemented. It
  750. sends as much data as possible, as soon as possible. Vanilla will work on
  751. all kernels and operating systems.
  752. [[KISTSchedRunInterval]] **KISTSchedRunInterval** __NUM__ **msec**::
  753. If KIST or KISTLite is used in the Schedulers option, this controls at which
  754. interval the scheduler tick is. If the value is 0 msec, the value is taken
  755. from the consensus if possible else it will fallback to the default 10
  756. msec. Maximum possible value is 100 msec. (Default: 0 msec)
  757. [[KISTSockBufSizeFactor]] **KISTSockBufSizeFactor** __NUM__::
  758. If KIST is used in Schedulers, this is a multiplier of the per-socket
  759. limit calculation of the KIST algorithm. (Default: 1.0)
  760. CLIENT OPTIONS
  761. --------------
  762. The following options are useful only for clients (that is, if
  763. **SocksPort**, **HTTPTunnelPort**, **TransPort**, **DNSPort**, or
  764. **NATDPort** is non-zero):
  765. [[Bridge]] **Bridge** [__transport__] __IP__:__ORPort__ [__fingerprint__]::
  766. When set along with UseBridges, instructs Tor to use the relay at
  767. "IP:ORPort" as a "bridge" relaying into the Tor network. If "fingerprint"
  768. is provided (using the same format as for DirAuthority), we will verify that
  769. the relay running at that location has the right fingerprint. We also use
  770. fingerprint to look up the bridge descriptor at the bridge authority, if
  771. it's provided and if UpdateBridgesFromAuthority is set too. +
  772. +
  773. If "transport" is provided, it must match a ClientTransportPlugin line. We
  774. then use that pluggable transport's proxy to transfer data to the bridge,
  775. rather than connecting to the bridge directly. Some transports use a
  776. transport-specific method to work out the remote address to connect to.
  777. These transports typically ignore the "IP:ORPort" specified in the bridge
  778. line. +
  779. +
  780. Tor passes any "key=val" settings to the pluggable transport proxy as
  781. per-connection arguments when connecting to the bridge. Consult
  782. the documentation of the pluggable transport for details of what
  783. arguments it supports.
  784. [[LearnCircuitBuildTimeout]] **LearnCircuitBuildTimeout** **0**|**1**::
  785. If 0, CircuitBuildTimeout adaptive learning is disabled. (Default: 1)
  786. [[CircuitBuildTimeout]] **CircuitBuildTimeout** __NUM__::
  787. Try for at most NUM seconds when building circuits. If the circuit isn't
  788. open in that time, give up on it. If LearnCircuitBuildTimeout is 1, this
  789. value serves as the initial value to use before a timeout is learned. If
  790. LearnCircuitBuildTimeout is 0, this value is the only value used.
  791. (Default: 60 seconds)
  792. [[CircuitsAvailableTimeout]] **CircuitsAvailableTimeout** __NUM__::
  793. Tor will attempt to keep at least one open, unused circuit available for
  794. this amount of time. This option governs how long idle circuits are kept
  795. open, as well as the amount of time Tor will keep a circuit open to each
  796. of the recently used ports. This way when the Tor client is entirely
  797. idle, it can expire all of its circuits, and then expire its TLS
  798. connections. Note that the actual timeout value is uniformly randomized
  799. from the specified value to twice that amount. (Default: 30 minutes;
  800. Max: 24 hours)
  801. [[CircuitStreamTimeout]] **CircuitStreamTimeout** __NUM__::
  802. If non-zero, this option overrides our internal timeout schedule for how
  803. many seconds until we detach a stream from a circuit and try a new circuit.
  804. If your network is particularly slow, you might want to set this to a
  805. number like 60. (Default: 0)
  806. [[ClientOnly]] **ClientOnly** **0**|**1**::
  807. If set to 1, Tor will not run as a relay or serve
  808. directory requests, even if the ORPort, ExtORPort, or DirPort options are
  809. set. (This config option is
  810. mostly unnecessary: we added it back when we were considering having
  811. Tor clients auto-promote themselves to being relays if they were stable
  812. and fast enough. The current behavior is simply that Tor is a client
  813. unless ORPort, ExtORPort, or DirPort are configured.) (Default: 0)
  814. [[ConnectionPadding]] **ConnectionPadding** **0**|**1**|**auto**::
  815. This option governs Tor's use of padding to defend against some forms of
  816. traffic analysis. If it is set to 'auto', Tor will send padding only
  817. if both the client and the relay support it. If it is set to 0, Tor will
  818. not send any padding cells. If it is set to 1, Tor will still send padding
  819. for client connections regardless of relay support. Only clients may set
  820. this option. This option should be offered via the UI to mobile users
  821. for use where bandwidth may be expensive.
  822. (Default: auto)
  823. [[ReducedConnectionPadding]] **ReducedConnectionPadding** **0**|**1**::
  824. If set to 1, Tor will not not hold OR connections open for very long,
  825. and will send less padding on these connections. Only clients may set
  826. this option. This option should be offered via the UI to mobile users
  827. for use where bandwidth may be expensive. (Default: 0)
  828. [[ExcludeNodes]] **ExcludeNodes** __node__,__node__,__...__::
  829. A list of identity fingerprints, country codes, and address
  830. patterns of nodes to avoid when building a circuit. Country codes are
  831. 2-letter ISO3166 codes, and must
  832. be wrapped in braces; fingerprints may be preceded by a dollar sign.
  833. (Example:
  834. ExcludeNodes ABCD1234CDEF5678ABCD1234CDEF5678ABCD1234, \{cc}, 255.254.0.0/8) +
  835. +
  836. By default, this option is treated as a preference that Tor is allowed
  837. to override in order to keep working.
  838. For example, if you try to connect to a hidden service,
  839. but you have excluded all of the hidden service's introduction points,
  840. Tor will connect to one of them anyway. If you do not want this
  841. behavior, set the StrictNodes option (documented below). +
  842. +
  843. Note also that if you are a relay, this (and the other node selection
  844. options below) only affects your own circuits that Tor builds for you.
  845. Clients can still build circuits through you to any node. Controllers
  846. can tell Tor to build circuits through any node. +
  847. +
  848. Country codes are case-insensitive. The code "\{??}" refers to nodes whose
  849. country can't be identified. No country code, including \{??}, works if
  850. no GeoIPFile can be loaded. See also the GeoIPExcludeUnknown option below.
  851. [[ExcludeExitNodes]] **ExcludeExitNodes** __node__,__node__,__...__::
  852. A list of identity fingerprints, country codes, and address
  853. patterns of nodes to never use when picking an exit node---that is, a
  854. node that delivers traffic for you *outside* the Tor network. Note that any
  855. node listed in ExcludeNodes is automatically considered to be part of this
  856. list too. See
  857. the **ExcludeNodes** option for more information on how to specify
  858. nodes. See also the caveats on the "ExitNodes" option below.
  859. [[GeoIPExcludeUnknown]] **GeoIPExcludeUnknown** **0**|**1**|**auto**::
  860. If this option is set to 'auto', then whenever any country code is set in
  861. ExcludeNodes or ExcludeExitNodes, all nodes with unknown country (\{??} and
  862. possibly \{A1}) are treated as excluded as well. If this option is set to
  863. '1', then all unknown countries are treated as excluded in ExcludeNodes
  864. and ExcludeExitNodes. This option has no effect when a GeoIP file isn't
  865. configured or can't be found. (Default: auto)
  866. [[ExitNodes]] **ExitNodes** __node__,__node__,__...__::
  867. A list of identity fingerprints, country codes, and address
  868. patterns of nodes to use as exit node---that is, a
  869. node that delivers traffic for you *outside* the Tor network. See
  870. the **ExcludeNodes** option for more information on how to specify nodes. +
  871. +
  872. Note that if you list too few nodes here, or if you exclude too many exit
  873. nodes with ExcludeExitNodes, you can degrade functionality. For example,
  874. if none of the exits you list allows traffic on port 80 or 443, you won't
  875. be able to browse the web. +
  876. +
  877. Note also that not every circuit is used to deliver traffic *outside* of
  878. the Tor network. It is normal to see non-exit circuits (such as those
  879. used to connect to hidden services, those that do directory fetches,
  880. those used for relay reachability self-tests, and so on) that end
  881. at a non-exit node. To
  882. keep a node from being used entirely, see ExcludeNodes and StrictNodes. +
  883. +
  884. The ExcludeNodes option overrides this option: any node listed in both
  885. ExitNodes and ExcludeNodes is treated as excluded. +
  886. +
  887. The .exit address notation, if enabled via MapAddress, overrides
  888. this option.
  889. [[MiddleNodes]] **MiddleNodes** __node__,__node__,__...__::
  890. A list of identity fingerprints and country codes of nodes
  891. to use for "middle" hops in your normal circuits.
  892. Normal circuits include all circuits except for direct connections
  893. to directory servers. Middle hops are all hops other than exit and entry. +
  894. +
  895. This is an **experimental** feature that is meant to be used by researchers
  896. and developers to test new features in the Tor network safely. Using it
  897. without care will strongly influence your anonymity. This feature might get
  898. removed in the future.
  899. +
  900. The HSLayer2Node and HSLayer3Node options override this option for onion
  901. service circuits, if they are set. The vanguards addon will read this
  902. option, and if set, it will set HSLayer2Nodes and HSLayer3Nodes to nodes
  903. from this set.
  904. +
  905. The ExcludeNodes option overrides this option: any node listed in both
  906. MiddleNodes and ExcludeNodes is treated as excluded. See
  907. the **ExcludeNodes** option for more information on how to specify nodes.
  908. [[EntryNodes]] **EntryNodes** __node__,__node__,__...__::
  909. A list of identity fingerprints and country codes of nodes
  910. to use for the first hop in your normal circuits.
  911. Normal circuits include all
  912. circuits except for direct connections to directory servers. The Bridge
  913. option overrides this option; if you have configured bridges and
  914. UseBridges is 1, the Bridges are used as your entry nodes. +
  915. +
  916. The ExcludeNodes option overrides this option: any node listed in both
  917. EntryNodes and ExcludeNodes is treated as excluded. See
  918. the **ExcludeNodes** option for more information on how to specify nodes.
  919. [[StrictNodes]] **StrictNodes** **0**|**1**::
  920. If StrictNodes is set to 1, Tor will treat solely the ExcludeNodes option
  921. as a requirement to follow for all the circuits you generate, even if
  922. doing so will break functionality for you (StrictNodes applies to neither
  923. ExcludeExitNodes nor to ExitNodes, nor to MiddleNodes). If StrictNodes
  924. is set to 0, Tor will still try to avoid nodes in the ExcludeNodes list,
  925. but it will err on the side of avoiding unexpected errors.
  926. Specifically, StrictNodes 0 tells Tor that it is okay to use an excluded
  927. node when it is *necessary* to perform relay reachability self-tests,
  928. connect to a hidden service, provide a hidden service to a client,
  929. fulfill a .exit request, upload directory information, or download
  930. directory information. (Default: 0)
  931. [[FascistFirewall]] **FascistFirewall** **0**|**1**::
  932. If 1, Tor will only create outgoing connections to ORs running on ports
  933. that your firewall allows (defaults to 80 and 443; see **FirewallPorts**).
  934. This will allow you to run Tor as a client behind a firewall with
  935. restrictive policies, but will not allow you to run as a server behind such
  936. a firewall. If you prefer more fine-grained control, use
  937. ReachableAddresses instead.
  938. [[FirewallPorts]] **FirewallPorts** __PORTS__::
  939. A list of ports that your firewall allows you to connect to. Only used when
  940. **FascistFirewall** is set. This option is deprecated; use ReachableAddresses
  941. instead. (Default: 80, 443)
  942. [[ReachableAddresses]] **ReachableAddresses** __IP__[/__MASK__][:__PORT__]...::
  943. A comma-separated list of IP addresses and ports that your firewall allows
  944. you to connect to. The format is as for the addresses in ExitPolicy, except
  945. that "accept" is understood unless "reject" is explicitly provided. For
  946. example, \'ReachableAddresses 99.0.0.0/8, reject 18.0.0.0/8:80, accept
  947. \*:80' means that your firewall allows connections to everything inside net
  948. 99, rejects port 80 connections to net 18, and accepts connections to port
  949. 80 otherwise. (Default: \'accept \*:*'.)
  950. [[ReachableDirAddresses]] **ReachableDirAddresses** __IP__[/__MASK__][:__PORT__]...::
  951. Like **ReachableAddresses**, a list of addresses and ports. Tor will obey
  952. these restrictions when fetching directory information, using standard HTTP
  953. GET requests. If not set explicitly then the value of
  954. **ReachableAddresses** is used. If **HTTPProxy** is set then these
  955. connections will go through that proxy. (DEPRECATED: This option has
  956. had no effect for some time.)
  957. [[ReachableORAddresses]] **ReachableORAddresses** __IP__[/__MASK__][:__PORT__]...::
  958. Like **ReachableAddresses**, a list of addresses and ports. Tor will obey
  959. these restrictions when connecting to Onion Routers, using TLS/SSL. If not
  960. set explicitly then the value of **ReachableAddresses** is used. If
  961. **HTTPSProxy** is set then these connections will go through that proxy. +
  962. +
  963. The separation between **ReachableORAddresses** and
  964. **ReachableDirAddresses** is only interesting when you are connecting
  965. through proxies (see **HTTPProxy** and **HTTPSProxy**). Most proxies limit
  966. TLS connections (which Tor uses to connect to Onion Routers) to port 443,
  967. and some limit HTTP GET requests (which Tor uses for fetching directory
  968. information) to port 80.
  969. [[HidServAuth]] **HidServAuth** __onion-address__ __auth-cookie__ [__service-name__]::
  970. Client authorization for a hidden service. Valid onion addresses contain 16
  971. characters in a-z2-7 plus ".onion", and valid auth cookies contain 22
  972. characters in A-Za-z0-9+/. The service name is only used for internal
  973. purposes, e.g., for Tor controllers. This option may be used multiple times
  974. for different hidden services. If a hidden service uses authorization and
  975. this option is not set, the hidden service is not accessible. Hidden
  976. services can be configured to require authorization using the
  977. **HiddenServiceAuthorizeClient** option.
  978. [[ClientOnionAuthDir]] **ClientOnionAuthDir** __path__::
  979. Path to the directory containing v3 hidden service authorization files.
  980. Each file is for a single onion address, and the files MUST have the suffix
  981. ".auth_private" (i.e. "bob_onion.auth_private"). The content format MUST be:
  982. +
  983. <onion-address>:descriptor:x25519:<base32-encoded-privkey>
  984. +
  985. The <onion-address> MUST NOT have the ".onion" suffix. The
  986. <base32-encoded-privkey> is the base32 representation of the raw key bytes
  987. only (32 bytes for x25519). See Appendix G in the rend-spec-v3.txt file of
  988. https://spec.torproject.org/[torspec] for more information.
  989. [[LongLivedPorts]] **LongLivedPorts** __PORTS__::
  990. A list of ports for services that tend to have long-running connections
  991. (e.g. chat and interactive shells). Circuits for streams that use these
  992. ports will contain only high-uptime nodes, to reduce the chance that a node
  993. will go down before the stream is finished. Note that the list is also
  994. honored for circuits (both client and service side) involving hidden
  995. services whose virtual port is in this list. (Default: 21, 22, 706,
  996. 1863, 5050, 5190, 5222, 5223, 6523, 6667, 6697, 8300)
  997. [[MapAddress]] **MapAddress** __address__ __newaddress__::
  998. When a request for address arrives to Tor, it will transform to newaddress
  999. before processing it. For example, if you always want connections to
  1000. www.example.com to exit via __torserver__ (where __torserver__ is the
  1001. fingerprint of the server), use "MapAddress www.example.com
  1002. www.example.com.torserver.exit". If the value is prefixed with a
  1003. "\*.", matches an entire domain. For example, if you
  1004. always want connections to example.com and any if its subdomains
  1005. to exit via
  1006. __torserver__ (where __torserver__ is the fingerprint of the server), use
  1007. "MapAddress \*.example.com \*.example.com.torserver.exit". (Note the
  1008. leading "*." in each part of the directive.) You can also redirect all
  1009. subdomains of a domain to a single address. For example, "MapAddress
  1010. *.example.com www.example.com". +
  1011. +
  1012. NOTES:
  1013. 1. When evaluating MapAddress expressions Tor stops when it hits the most
  1014. recently added expression that matches the requested address. So if you
  1015. have the following in your torrc, www.torproject.org will map to
  1016. 198.51.100.1:
  1017. MapAddress www.torproject.org 192.0.2.1
  1018. MapAddress www.torproject.org 198.51.100.1
  1019. 2. Tor evaluates the MapAddress configuration until it finds no matches. So
  1020. if you have the following in your torrc, www.torproject.org will map to
  1021. 203.0.113.1:
  1022. MapAddress 198.51.100.1 203.0.113.1
  1023. MapAddress www.torproject.org 198.51.100.1
  1024. 3. The following MapAddress expression is invalid (and will be
  1025. ignored) because you cannot map from a specific address to a wildcard
  1026. address:
  1027. MapAddress www.torproject.org *.torproject.org.torserver.exit
  1028. 4. Using a wildcard to match only part of a string (as in *ample.com) is
  1029. also invalid.
  1030. [[NewCircuitPeriod]] **NewCircuitPeriod** __NUM__::
  1031. Every NUM seconds consider whether to build a new circuit. (Default: 30
  1032. seconds)
  1033. [[MaxCircuitDirtiness]] **MaxCircuitDirtiness** __NUM__::
  1034. Feel free to reuse a circuit that was first used at most NUM seconds ago,
  1035. but never attach a new stream to a circuit that is too old. For hidden
  1036. services, this applies to the __last__ time a circuit was used, not the
  1037. first. Circuits with streams constructed with SOCKS authentication via
  1038. SocksPorts that have **KeepAliveIsolateSOCKSAuth** also remain alive
  1039. for MaxCircuitDirtiness seconds after carrying the last such stream.
  1040. (Default: 10 minutes)
  1041. [[MaxClientCircuitsPending]] **MaxClientCircuitsPending** __NUM__::
  1042. Do not allow more than NUM circuits to be pending at a time for handling
  1043. client streams. A circuit is pending if we have begun constructing it,
  1044. but it has not yet been completely constructed. (Default: 32)
  1045. [[NodeFamily]] **NodeFamily** __node__,__node__,__...__::
  1046. The Tor servers, defined by their identity fingerprints,
  1047. constitute a "family" of similar or co-administered servers, so never use
  1048. any two of them in the same circuit. Defining a NodeFamily is only needed
  1049. when a server doesn't list the family itself (with MyFamily). This option
  1050. can be used multiple times; each instance defines a separate family. In
  1051. addition to nodes, you can also list IP address and ranges and country
  1052. codes in {curly braces}. See the **ExcludeNodes** option for more
  1053. information on how to specify nodes.
  1054. [[EnforceDistinctSubnets]] **EnforceDistinctSubnets** **0**|**1**::
  1055. If 1, Tor will not put two servers whose IP addresses are "too close" on
  1056. the same circuit. Currently, two addresses are "too close" if they lie in
  1057. the same /16 range. (Default: 1)
  1058. [[SocksPort]] **SocksPort** \['address':]__port__|**unix:**__path__|**auto** [_flags_] [_isolation flags_]::
  1059. Open this port to listen for connections from SOCKS-speaking
  1060. applications. Set this to 0 if you don't want to allow application
  1061. connections via SOCKS. Set it to "auto" to have Tor pick a port for
  1062. you. This directive can be specified multiple times to bind
  1063. to multiple addresses/ports. If a unix domain socket is used, you may
  1064. quote the path using standard C escape sequences.
  1065. (Default: 9050) +
  1066. +
  1067. NOTE: Although this option allows you to specify an IP address
  1068. other than localhost, you should do so only with extreme caution.
  1069. The SOCKS protocol is unencrypted and (as we use it)
  1070. unauthenticated, so exposing it in this way could leak your
  1071. information to anybody watching your network, and allow anybody
  1072. to use your computer as an open proxy. +
  1073. +
  1074. If multiple entries of this option are present in your configuration
  1075. file, Tor will perform stream isolation between listeners by default.
  1076. The _isolation flags_ arguments give Tor rules for which streams
  1077. received on this SocksPort are allowed to share circuits with one
  1078. another. Recognized isolation flags are:
  1079. **IsolateClientAddr**;;
  1080. Don't share circuits with streams from a different
  1081. client address. (On by default and strongly recommended when
  1082. supported; you can disable it with **NoIsolateClientAddr**.
  1083. Unsupported and force-disabled when using Unix domain sockets.)
  1084. **IsolateSOCKSAuth**;;
  1085. Don't share circuits with streams for which different
  1086. SOCKS authentication was provided. (For HTTPTunnelPort
  1087. connections, this option looks at the Proxy-Authorization and
  1088. X-Tor-Stream-Isolation headers. On by default;
  1089. you can disable it with **NoIsolateSOCKSAuth**.)
  1090. **IsolateClientProtocol**;;
  1091. Don't share circuits with streams using a different protocol.
  1092. (SOCKS 4, SOCKS 5, TransPort connections, NATDPort connections,
  1093. and DNSPort requests are all considered to be different protocols.)
  1094. **IsolateDestPort**;;
  1095. Don't share circuits with streams targeting a different
  1096. destination port.
  1097. **IsolateDestAddr**;;
  1098. Don't share circuits with streams targeting a different
  1099. destination address.
  1100. **KeepAliveIsolateSOCKSAuth**;;
  1101. If **IsolateSOCKSAuth** is enabled, keep alive circuits while they have
  1102. at least one stream with SOCKS authentication active. After such a circuit
  1103. is idle for more than MaxCircuitDirtiness seconds, it can be closed.
  1104. **SessionGroup=**__INT__;;
  1105. If no other isolation rules would prevent it, allow streams
  1106. on this port to share circuits with streams from every other
  1107. port with the same session group. (By default, streams received
  1108. on different SocksPorts, TransPorts, etc are always isolated from one
  1109. another. This option overrides that behavior.)
  1110. // Anchor only for formatting, not visible in the man page.
  1111. [[OtherSocksPortFlags]]::
  1112. Other recognized __flags__ for a SocksPort are:
  1113. **NoIPv4Traffic**;;
  1114. Tell exits to not connect to IPv4 addresses in response to SOCKS
  1115. requests on this connection.
  1116. **IPv6Traffic**;;
  1117. Tell exits to allow IPv6 addresses in response to SOCKS requests on
  1118. this connection, so long as SOCKS5 is in use. (SOCKS4 can't handle
  1119. IPv6.)
  1120. **PreferIPv6**;;
  1121. Tells exits that, if a host has both an IPv4 and an IPv6 address,
  1122. we would prefer to connect to it via IPv6. (IPv4 is the default.)
  1123. **NoDNSRequest**;;
  1124. Do not ask exits to resolve DNS addresses in SOCKS5 requests. Tor will
  1125. connect to IPv4 addresses, IPv6 addresses (if IPv6Traffic is set) and
  1126. .onion addresses.
  1127. **NoOnionTraffic**;;
  1128. Do not connect to .onion addresses in SOCKS5 requests.
  1129. **OnionTrafficOnly**;;
  1130. Tell the tor client to only connect to .onion addresses in response to
  1131. SOCKS5 requests on this connection. This is equivalent to NoDNSRequest,
  1132. NoIPv4Traffic, NoIPv6Traffic. The corresponding NoOnionTrafficOnly
  1133. flag is not supported.
  1134. **CacheIPv4DNS**;;
  1135. Tells the client to remember IPv4 DNS answers we receive from exit
  1136. nodes via this connection.
  1137. **CacheIPv6DNS**;;
  1138. Tells the client to remember IPv6 DNS answers we receive from exit
  1139. nodes via this connection.
  1140. **GroupWritable**;;
  1141. Unix domain sockets only: makes the socket get created as
  1142. group-writable.
  1143. **WorldWritable**;;
  1144. Unix domain sockets only: makes the socket get created as
  1145. world-writable.
  1146. **CacheDNS**;;
  1147. Tells the client to remember all DNS answers we receive from exit
  1148. nodes via this connection.
  1149. **UseIPv4Cache**;;
  1150. Tells the client to use any cached IPv4 DNS answers we have when making
  1151. requests via this connection. (NOTE: This option, or UseIPv6Cache
  1152. or UseDNSCache, can harm your anonymity, and probably
  1153. won't help performance as much as you might expect. Use with care!)
  1154. **UseIPv6Cache**;;
  1155. Tells the client to use any cached IPv6 DNS answers we have when making
  1156. requests via this connection.
  1157. **UseDNSCache**;;
  1158. Tells the client to use any cached DNS answers we have when making
  1159. requests via this connection.
  1160. **PreferIPv6Automap**;;
  1161. When serving a hostname lookup request on this port that
  1162. should get automapped (according to AutomapHostsOnResolve),
  1163. if we could return either an IPv4 or an IPv6 answer, prefer
  1164. an IPv6 answer. (On by default.)
  1165. **PreferSOCKSNoAuth**;;
  1166. Ordinarily, when an application offers both "username/password
  1167. authentication" and "no authentication" to Tor via SOCKS5, Tor
  1168. selects username/password authentication so that IsolateSOCKSAuth can
  1169. work. This can confuse some applications, if they offer a
  1170. username/password combination then get confused when asked for
  1171. one. You can disable this behavior, so that Tor will select "No
  1172. authentication" when IsolateSOCKSAuth is disabled, or when this
  1173. option is set.
  1174. // Anchor only for formatting, not visible in the man page.
  1175. [[SocksPortFlagsMisc]]::
  1176. Flags are processed left to right. If flags conflict, the last flag on the
  1177. line is used, and all earlier flags are ignored. No error is issued for
  1178. conflicting flags.
  1179. [[SocksPolicy]] **SocksPolicy** __policy__,__policy__,__...__::
  1180. Set an entrance policy for this server, to limit who can connect to the
  1181. SocksPort and DNSPort ports. The policies have the same form as exit
  1182. policies below, except that port specifiers are ignored. Any address
  1183. not matched by some entry in the policy is accepted.
  1184. [[SocksTimeout]] **SocksTimeout** __NUM__::
  1185. Let a socks connection wait NUM seconds handshaking, and NUM seconds
  1186. unattached waiting for an appropriate circuit, before we fail it. (Default:
  1187. 2 minutes)
  1188. [[TokenBucketRefillInterval]] **TokenBucketRefillInterval** __NUM__ [**msec**|**second**]::
  1189. Set the refill delay interval of Tor's token bucket to NUM milliseconds.
  1190. NUM must be between 1 and 1000, inclusive. When Tor is out of bandwidth,
  1191. on a connection or globally, it will wait up to this long before it tries
  1192. to use that connection again.
  1193. Note that bandwidth limits are still expressed in bytes per second: this
  1194. option only affects the frequency with which Tor checks to see whether
  1195. previously exhausted connections may read again.
  1196. Can not be changed while tor is running. (Default: 100 msec)
  1197. [[TrackHostExits]] **TrackHostExits** __host__,__.domain__,__...__::
  1198. For each value in the comma separated list, Tor will track recent
  1199. connections to hosts that match this value and attempt to reuse the same
  1200. exit node for each. If the value is prepended with a \'.\', it is treated as
  1201. matching an entire domain. If one of the values is just a \'.', it means
  1202. match everything. This option is useful if you frequently connect to sites
  1203. that will expire all your authentication cookies (i.e. log you out) if
  1204. your IP address changes. Note that this option does have the disadvantage
  1205. of making it more clear that a given history is associated with a single
  1206. user. However, most people who would wish to observe this will observe it
  1207. through cookies or other protocol-specific means anyhow.
  1208. [[TrackHostExitsExpire]] **TrackHostExitsExpire** __NUM__::
  1209. Since exit servers go up and down, it is desirable to expire the
  1210. association between host and exit server after NUM seconds. The default is
  1211. 1800 seconds (30 minutes).
  1212. [[UpdateBridgesFromAuthority]] **UpdateBridgesFromAuthority** **0**|**1**::
  1213. When set (along with UseBridges), Tor will try to fetch bridge descriptors
  1214. from the configured bridge authorities when feasible. It will fall back to
  1215. a direct request if the authority responds with a 404. (Default: 0)
  1216. [[UseBridges]] **UseBridges** **0**|**1**::
  1217. When set, Tor will fetch descriptors for each bridge listed in the "Bridge"
  1218. config lines, and use these relays as both entry guards and directory
  1219. guards. (Default: 0)
  1220. [[UseEntryGuards]] **UseEntryGuards** **0**|**1**::
  1221. If this option is set to 1, we pick a few long-term entry servers, and try
  1222. to stick with them. This is desirable because constantly changing servers
  1223. increases the odds that an adversary who owns some servers will observe a
  1224. fraction of your paths. Entry Guards can not be used by Directory
  1225. Authorities or Single Onion Services. In these cases,
  1226. this option is ignored. (Default: 1)
  1227. [[GuardfractionFile]] **GuardfractionFile** __FILENAME__::
  1228. V3 authoritative directories only. Configures the location of the
  1229. guardfraction file which contains information about how long relays
  1230. have been guards. (Default: unset)
  1231. [[UseGuardFraction]] **UseGuardFraction** **0**|**1**|**auto**::
  1232. This option specifies whether clients should use the
  1233. guardfraction information found in the consensus during path
  1234. selection. If it's set to 'auto', clients will do what the
  1235. UseGuardFraction consensus parameter tells them to do. (Default: auto)
  1236. [[NumEntryGuards]] **NumEntryGuards** __NUM__::
  1237. If UseEntryGuards is set to 1, we will try to pick a total of NUM routers
  1238. as long-term entries for our circuits. If NUM is 0, we try to learn the
  1239. number from the guard-n-primary-guards-to-use consensus parameter, and
  1240. default to 1 if the consensus parameter isn't set. (Default: 0)
  1241. [[NumPrimaryGuards]] **NumPrimaryGuards** __NUM__::
  1242. If UseEntryGuards is set to 1, we will try to pick NUM routers for our
  1243. primary guard list, which is the set of routers we strongly prefer when
  1244. connecting to the Tor network. If NUM is 0, we try to learn the number from
  1245. the guard-n-primary-guards consensus parameter, and default to 3 if the
  1246. consensus parameter isn't set. (Default: 0)
  1247. [[NumDirectoryGuards]] **NumDirectoryGuards** __NUM__::
  1248. If UseEntryGuards is set to 1, we try to make sure we have at least NUM
  1249. routers to use as directory guards. If this option is set to 0, use the
  1250. value from the guard-n-primary-dir-guards-to-use consensus parameter, and
  1251. default to 3 if the consensus parameter isn't set. (Default: 0)
  1252. [[GuardLifetime]] **GuardLifetime** __N__ **days**|**weeks**|**months**::
  1253. If nonzero, and UseEntryGuards is set, minimum time to keep a guard before
  1254. picking a new one. If zero, we use the GuardLifetime parameter from the
  1255. consensus directory. No value here may be less than 1 month or greater
  1256. than 5 years; out-of-range values are clamped. (Default: 0)
  1257. [[SafeSocks]] **SafeSocks** **0**|**1**::
  1258. When this option is enabled, Tor will reject application connections that
  1259. use unsafe variants of the socks protocol -- ones that only provide an IP
  1260. address, meaning the application is doing a DNS resolve first.
  1261. Specifically, these are socks4 and socks5 when not doing remote DNS.
  1262. (Default: 0)
  1263. [[TestSocks]] **TestSocks** **0**|**1**::
  1264. When this option is enabled, Tor will make a notice-level log entry for
  1265. each connection to the Socks port indicating whether the request used a
  1266. safe socks protocol or an unsafe one (see above entry on SafeSocks). This
  1267. helps to determine whether an application using Tor is possibly leaking
  1268. DNS requests. (Default: 0)
  1269. [[VirtualAddrNetworkIPv4]] **VirtualAddrNetworkIPv4** __IPv4Address__/__bits__ +
  1270. [[VirtualAddrNetworkIPv6]] **VirtualAddrNetworkIPv6** [__IPv6Address__]/__bits__::
  1271. When Tor needs to assign a virtual (unused) address because of a MAPADDRESS
  1272. command from the controller or the AutomapHostsOnResolve feature, Tor
  1273. picks an unassigned address from this range. (Defaults:
  1274. 127.192.0.0/10 and [FE80::]/10 respectively.) +
  1275. +
  1276. When providing proxy server service to a network of computers using a tool
  1277. like dns-proxy-tor, change the IPv4 network to "10.192.0.0/10" or
  1278. "172.16.0.0/12" and change the IPv6 network to "[FC00::]/7".
  1279. The default **VirtualAddrNetwork** address ranges on a
  1280. properly configured machine will route to the loopback or link-local
  1281. interface. The maximum number of bits for the network prefix is set to 104
  1282. for IPv6 and 16 for IPv4. However, a wider network - smaller prefix length
  1283. - is preferable since it reduces the chances for an attacker to guess the
  1284. used IP. For local use, no change to the default VirtualAddrNetwork setting
  1285. is needed.
  1286. [[AllowNonRFC953Hostnames]] **AllowNonRFC953Hostnames** **0**|**1**::
  1287. When this option is disabled, Tor blocks hostnames containing illegal
  1288. characters (like @ and :) rather than sending them to an exit node to be
  1289. resolved. This helps trap accidental attempts to resolve URLs and so on.
  1290. (Default: 0)
  1291. [[HTTPTunnelPort]] **HTTPTunnelPort** \['address':]__port__|**auto** [_isolation flags_]::
  1292. Open this port to listen for proxy connections using the "HTTP CONNECT"
  1293. protocol instead of SOCKS. Set this to
  1294. 0 if you don't want to allow "HTTP CONNECT" connections. Set the port
  1295. to "auto" to have Tor pick a port for you. This directive can be
  1296. specified multiple times to bind to multiple addresses/ports. If multiple
  1297. entries of this option are present in your configuration file, Tor will
  1298. perform stream isolation between listeners by default. See
  1299. SOCKSPort for an explanation of isolation flags. (Default: 0)
  1300. [[TransPort]] **TransPort** \['address':]__port__|**auto** [_isolation flags_]::
  1301. Open this port to listen for transparent proxy connections. Set this to
  1302. 0 if you don't want to allow transparent proxy connections. Set the port
  1303. to "auto" to have Tor pick a port for you. This directive can be
  1304. specified multiple times to bind to multiple addresses/ports. If multiple
  1305. entries of this option are present in your configuration file, Tor will
  1306. perform stream isolation between listeners by default. See
  1307. SOCKSPort for an explanation of isolation flags. +
  1308. +
  1309. TransPort requires OS support for transparent proxies, such as BSDs' pf or
  1310. Linux's IPTables. If you're planning to use Tor as a transparent proxy for
  1311. a network, you'll want to examine and change VirtualAddrNetwork from the
  1312. default setting. (Default: 0)
  1313. [[TransProxyType]] **TransProxyType** **default**|**TPROXY**|**ipfw**|**pf-divert**::
  1314. TransProxyType may only be enabled when there is transparent proxy listener
  1315. enabled. +
  1316. +
  1317. Set this to "TPROXY" if you wish to be able to use the TPROXY Linux module
  1318. to transparently proxy connections that are configured using the TransPort
  1319. option. Detailed information on how to configure the TPROXY
  1320. feature can be found in the Linux kernel source tree in the file
  1321. Documentation/networking/tproxy.txt. +
  1322. +
  1323. Set this option to "ipfw" to use the FreeBSD ipfw interface. +
  1324. +
  1325. On *BSD operating systems when using pf, set this to "pf-divert" to take
  1326. advantage of +divert-to+ rules, which do not modify the packets like
  1327. +rdr-to+ rules do. Detailed information on how to configure pf to use
  1328. +divert-to+ rules can be found in the pf.conf(5) manual page. On OpenBSD,
  1329. +divert-to+ is available to use on versions greater than or equal to
  1330. OpenBSD 4.4. +
  1331. +
  1332. Set this to "default", or leave it unconfigured, to use regular IPTables
  1333. on Linux, or to use pf +rdr-to+ rules on *BSD systems. +
  1334. +
  1335. (Default: "default")
  1336. [[NATDPort]] **NATDPort** \['address':]__port__|**auto** [_isolation flags_]::
  1337. Open this port to listen for connections from old versions of ipfw (as
  1338. included in old versions of FreeBSD, etc) using the NATD protocol.
  1339. Use 0 if you don't want to allow NATD connections. Set the port
  1340. to "auto" to have Tor pick a port for you. This directive can be
  1341. specified multiple times to bind to multiple addresses/ports. If multiple
  1342. entries of this option are present in your configuration file, Tor will
  1343. perform stream isolation between listeners by default. See
  1344. SocksPort for an explanation of isolation flags. +
  1345. +
  1346. This option is only for people who cannot use TransPort. (Default: 0)
  1347. [[AutomapHostsOnResolve]] **AutomapHostsOnResolve** **0**|**1**::
  1348. When this option is enabled, and we get a request to resolve an address
  1349. that ends with one of the suffixes in **AutomapHostsSuffixes**, we map an
  1350. unused virtual address to that address, and return the new virtual address.
  1351. This is handy for making ".onion" addresses work with applications that
  1352. resolve an address and then connect to it. (Default: 0)
  1353. [[AutomapHostsSuffixes]] **AutomapHostsSuffixes** __SUFFIX__,__SUFFIX__,__...__::
  1354. A comma-separated list of suffixes to use with **AutomapHostsOnResolve**.
  1355. The "." suffix is equivalent to "all addresses." (Default: .exit,.onion).
  1356. [[DNSPort]] **DNSPort** \['address':]__port__|**auto** [_isolation flags_]::
  1357. If non-zero, open this port to listen for UDP DNS requests, and resolve
  1358. them anonymously. This port only handles A, AAAA, and PTR requests---it
  1359. doesn't handle arbitrary DNS request types. Set the port to "auto" to
  1360. have Tor pick a port for
  1361. you. This directive can be specified multiple times to bind to multiple
  1362. addresses/ports. See SocksPort for an explanation of isolation
  1363. flags. (Default: 0)
  1364. [[ClientDNSRejectInternalAddresses]] **ClientDNSRejectInternalAddresses** **0**|**1**::
  1365. If true, Tor does not believe any anonymously retrieved DNS answer that
  1366. tells it that an address resolves to an internal address (like 127.0.0.1 or
  1367. 192.168.0.1). This option prevents certain browser-based attacks; it
  1368. is not allowed to be set on the default network. (Default: 1)
  1369. [[ClientRejectInternalAddresses]] **ClientRejectInternalAddresses** **0**|**1**::
  1370. If true, Tor does not try to fulfill requests to connect to an internal
  1371. address (like 127.0.0.1 or 192.168.0.1) __unless an exit node is
  1372. specifically requested__ (for example, via a .exit hostname, or a
  1373. controller request). If true, multicast DNS hostnames for machines on the
  1374. local network (of the form *.local) are also rejected. (Default: 1)
  1375. [[DownloadExtraInfo]] **DownloadExtraInfo** **0**|**1**::
  1376. If true, Tor downloads and caches "extra-info" documents. These documents
  1377. contain information about servers other than the information in their
  1378. regular server descriptors. Tor does not use this information for anything
  1379. itself; to save bandwidth, leave this option turned off. (Default: 0)
  1380. [[WarnPlaintextPorts]] **WarnPlaintextPorts** __port__,__port__,__...__::
  1381. Tells Tor to issue a warnings whenever the user tries to make an anonymous
  1382. connection to one of these ports. This option is designed to alert users
  1383. to services that risk sending passwords in the clear. (Default:
  1384. 23,109,110,143)
  1385. [[RejectPlaintextPorts]] **RejectPlaintextPorts** __port__,__port__,__...__::
  1386. Like WarnPlaintextPorts, but instead of warning about risky port uses, Tor
  1387. will instead refuse to make the connection. (Default: None)
  1388. [[OptimisticData]] **OptimisticData** **0**|**1**|**auto**::
  1389. When this option is set, and Tor is using an exit node that supports
  1390. the feature, it will try optimistically to send data to the exit node
  1391. without waiting for the exit node to report whether the connection
  1392. succeeded. This can save a round-trip time for protocols like HTTP
  1393. where the client talks first. If OptimisticData is set to **auto**,
  1394. Tor will look at the UseOptimisticData parameter in the networkstatus.
  1395. (Default: auto)
  1396. [[HSLayer2Nodes]] **HSLayer2Nodes** __node__,__node__,__...__::
  1397. A list of identity fingerprints, nicknames, country codes, and
  1398. address patterns of nodes that are allowed to be used as the
  1399. second hop in all client or service-side Onion Service circuits.
  1400. This option mitigates attacks where the adversary runs middle nodes
  1401. and induces your client or service to create many circuits, in order
  1402. to discover your primary guard node.
  1403. (Default: Any node in the network may be used in the second hop.)
  1404. +
  1405. (Example:
  1406. HSLayer2Nodes ABCD1234CDEF5678ABCD1234CDEF5678ABCD1234, \{cc}, 255.254.0.0/8) +
  1407. +
  1408. When this is set, the resulting hidden service paths will
  1409. look like:
  1410. +
  1411. C - G - L2 - M - Rend +
  1412. C - G - L2 - M - HSDir +
  1413. C - G - L2 - M - Intro +
  1414. S - G - L2 - M - Rend +
  1415. S - G - L2 - M - HSDir +
  1416. S - G - L2 - M - Intro +
  1417. +
  1418. where C is this client, S is the service, G is the Guard node,
  1419. L2 is a node from this option, and M is a random middle node.
  1420. Rend, HSDir, and Intro point selection is not affected by this
  1421. option.
  1422. +
  1423. This option may be combined with HSLayer3Nodes to create
  1424. paths of the form:
  1425. +
  1426. C - G - L2 - L3 - Rend +
  1427. C - G - L2 - L3 - M - HSDir +
  1428. C - G - L2 - L3 - M - Intro +
  1429. S - G - L2 - L3 - M - Rend +
  1430. S - G - L2 - L3 - HSDir +
  1431. S - G - L2 - L3 - Intro +
  1432. +
  1433. ExcludeNodes have higher priority than HSLayer2Nodes,
  1434. which means that nodes specified in ExcludeNodes will not be
  1435. picked.
  1436. +
  1437. When either this option or HSLayer3Nodes are set, the /16 subnet
  1438. and node family restrictions are removed for hidden service
  1439. circuits. Additionally, we allow the guard node to be present
  1440. as the Rend, HSDir, and IP node, and as the hop before it. This
  1441. is done to prevent the adversary from inferring information
  1442. about our guard, layer2, and layer3 node choices at later points
  1443. in the path.
  1444. +
  1445. This option is meant to be managed by a Tor controller such as
  1446. https://github.com/mikeperry-tor/vanguards that selects and
  1447. updates this set of nodes for you. Hence it does not do load
  1448. balancing if fewer than 20 nodes are selected, and if no nodes in
  1449. HSLayer2Nodes are currently available for use, Tor will not work.
  1450. Please use extreme care if you are setting this option manually.
  1451. [[HSLayer3Nodes]] **HSLayer3Nodes** __node__,__node__,__...__::
  1452. A list of identity fingerprints, nicknames, country codes, and
  1453. address patterns of nodes that are allowed to be used as the
  1454. third hop in all client and service-side Onion Service circuits.
  1455. This option mitigates attacks where the adversary runs middle nodes
  1456. and induces your client or service to create many circuits, in order
  1457. to discover your primary or Layer2 guard nodes.
  1458. (Default: Any node in the network may be used in the third hop.)
  1459. +
  1460. (Example:
  1461. HSLayer3Nodes ABCD1234CDEF5678ABCD1234CDEF5678ABCD1234, \{cc}, 255.254.0.0/8) +
  1462. +
  1463. When this is set by itself, the resulting hidden service paths
  1464. will look like: +
  1465. C - G - M - L3 - Rend +
  1466. C - G - M - L3 - M - HSDir +
  1467. C - G - M - L3 - M - Intro +
  1468. S - G - M - L3 - M - Rend +
  1469. S - G - M - L3 - HSDir +
  1470. S - G - M - L3 - Intro +
  1471. where C is this client, S is the service, G is the Guard node,
  1472. L2 is a node from this option, and M is a random middle node.
  1473. Rend, HSDir, and Intro point selection is not affected by this
  1474. option.
  1475. +
  1476. While it is possible to use this option by itself, it should be
  1477. combined with HSLayer2Nodes to create paths of the form:
  1478. +
  1479. C - G - L2 - L3 - Rend +
  1480. C - G - L2 - L3 - M - HSDir +
  1481. C - G - L2 - L3 - M - Intro +
  1482. S - G - L2 - L3 - M - Rend +
  1483. S - G - L2 - L3 - HSDir +
  1484. S - G - L2 - L3 - Intro +
  1485. +
  1486. ExcludeNodes have higher priority than HSLayer3Nodes,
  1487. which means that nodes specified in ExcludeNodes will not be
  1488. picked.
  1489. +
  1490. When either this option or HSLayer2Nodes are set, the /16 subnet
  1491. and node family restrictions are removed for hidden service
  1492. circuits. Additionally, we allow the guard node to be present
  1493. as the Rend, HSDir, and IP node, and as the hop before it. This
  1494. is done to prevent the adversary from inferring information
  1495. about our guard, layer2, and layer3 node choices at later points
  1496. in the path.
  1497. +
  1498. This option is meant to be managed by a Tor controller such as
  1499. https://github.com/mikeperry-tor/vanguards that selects and
  1500. updates this set of nodes for you. Hence it does not do load
  1501. balancing if fewer than 20 nodes are selected, and if no nodes in
  1502. HSLayer3Nodes are currently available for use, Tor will not work.
  1503. Please use extreme care if you are setting this option manually.
  1504. [[UseMicrodescriptors]] **UseMicrodescriptors** **0**|**1**|**auto**::
  1505. Microdescriptors are a smaller version of the information that Tor needs
  1506. in order to build its circuits. Using microdescriptors makes Tor clients
  1507. download less directory information, thus saving bandwidth. Directory
  1508. caches need to fetch regular descriptors and microdescriptors, so this
  1509. option doesn't save any bandwidth for them. For legacy reasons, auto is
  1510. accepted, but it has the same effect as 1. (Default: auto)
  1511. [[PathBiasCircThreshold]] **PathBiasCircThreshold** __NUM__ +
  1512. [[PathBiasNoticeRate]] **PathBiasNoticeRate** __NUM__ +
  1513. [[PathBiasWarnRate]] **PathBiasWarnRate** __NUM__ +
  1514. [[PathBiasExtremeRate]] **PathBiasExtremeRate** __NUM__ +
  1515. [[PathBiasDropGuards]] **PathBiasDropGuards** __NUM__ +
  1516. [[PathBiasScaleThreshold]] **PathBiasScaleThreshold** __NUM__::
  1517. These options override the default behavior of Tor's (**currently
  1518. experimental**) path bias detection algorithm. To try to find broken or
  1519. misbehaving guard nodes, Tor looks for nodes where more than a certain
  1520. fraction of circuits through that guard fail to get built. +
  1521. +
  1522. The PathBiasCircThreshold option controls how many circuits we need to build
  1523. through a guard before we make these checks. The PathBiasNoticeRate,
  1524. PathBiasWarnRate and PathBiasExtremeRate options control what fraction of
  1525. circuits must succeed through a guard so we won't write log messages.
  1526. If less than PathBiasExtremeRate circuits succeed *and* PathBiasDropGuards
  1527. is set to 1, we disable use of that guard. +
  1528. +
  1529. When we have seen more than PathBiasScaleThreshold
  1530. circuits through a guard, we scale our observations by 0.5 (governed by
  1531. the consensus) so that new observations don't get swamped by old ones. +
  1532. +
  1533. By default, or if a negative value is provided for one of these options,
  1534. Tor uses reasonable defaults from the networkstatus consensus document.
  1535. If no defaults are available there, these options default to 150, .70,
  1536. .50, .30, 0, and 300 respectively.
  1537. [[PathBiasUseThreshold]] **PathBiasUseThreshold** __NUM__ +
  1538. [[PathBiasNoticeUseRate]] **PathBiasNoticeUseRate** __NUM__ +
  1539. [[PathBiasExtremeUseRate]] **PathBiasExtremeUseRate** __NUM__ +
  1540. [[PathBiasScaleUseThreshold]] **PathBiasScaleUseThreshold** __NUM__::
  1541. Similar to the above options, these options override the default behavior
  1542. of Tor's (**currently experimental**) path use bias detection algorithm. +
  1543. +
  1544. Where as the path bias parameters govern thresholds for successfully
  1545. building circuits, these four path use bias parameters govern thresholds
  1546. only for circuit usage. Circuits which receive no stream usage
  1547. are not counted by this detection algorithm. A used circuit is considered
  1548. successful if it is capable of carrying streams or otherwise receiving
  1549. well-formed responses to RELAY cells. +
  1550. +
  1551. By default, or if a negative value is provided for one of these options,
  1552. Tor uses reasonable defaults from the networkstatus consensus document.
  1553. If no defaults are available there, these options default to 20, .80,
  1554. .60, and 100, respectively.
  1555. [[ClientUseIPv4]] **ClientUseIPv4** **0**|**1**::
  1556. If this option is set to 0, Tor will avoid connecting to directory servers
  1557. and entry nodes over IPv4. Note that clients with an IPv4
  1558. address in a **Bridge**, proxy, or pluggable transport line will try
  1559. connecting over IPv4 even if **ClientUseIPv4** is set to 0. (Default: 1)
  1560. [[ClientUseIPv6]] **ClientUseIPv6** **0**|**1**::
  1561. If this option is set to 1, Tor might connect to directory servers or
  1562. entry nodes over IPv6. For IPv6 only hosts, you need to also set
  1563. **ClientUseIPv4** to 0 to disable IPv4. Note that clients configured with
  1564. an IPv6 address in a **Bridge**, proxy, or pluggable transportline will
  1565. try connecting over IPv6 even if **ClientUseIPv6** is set to 0. (Default: 0)
  1566. [[ClientPreferIPv6DirPort]] **ClientPreferIPv6DirPort** **0**|**1**|**auto**::
  1567. If this option is set to 1, Tor prefers a directory port with an IPv6
  1568. address over one with IPv4, for direct connections, if a given directory
  1569. server has both. (Tor also prefers an IPv6 DirPort if IPv4Client is set to
  1570. 0.) If this option is set to auto, clients prefer IPv4. Other things may
  1571. influence the choice. This option breaks a tie to the favor of IPv6.
  1572. (Default: auto) (DEPRECATED: This option has had no effect for some
  1573. time.)
  1574. [[ClientPreferIPv6ORPort]] **ClientPreferIPv6ORPort** **0**|**1**|**auto**::
  1575. If this option is set to 1, Tor prefers an OR port with an IPv6
  1576. address over one with IPv4 if a given entry node has both. (Tor also
  1577. prefers an IPv6 ORPort if IPv4Client is set to 0.) If this option is set
  1578. to auto, Tor bridge clients prefer the configured bridge address, and
  1579. other clients prefer IPv4. Other things may influence the choice. This
  1580. option breaks a tie to the favor of IPv6. (Default: auto)
  1581. [[ClientAutoIPv6ORPort]] **ClientAutoIPv6ORPort** **0**|**1**::
  1582. If this option is set to 1, Tor clients randomly prefer a node's IPv4 or
  1583. IPv6 ORPort. The random preference is set every time a node is loaded
  1584. from a new consensus or bridge config. When this option is set to 1,
  1585. **ClientPreferIPv6ORPort** is ignored. (Default: 0)
  1586. [[PathsNeededToBuildCircuits]] **PathsNeededToBuildCircuits** __NUM__::
  1587. Tor clients don't build circuits for user traffic until they know
  1588. about enough of the network so that they could potentially construct
  1589. enough of the possible paths through the network. If this option
  1590. is set to a fraction between 0.25 and 0.95, Tor won't build circuits
  1591. until it has enough descriptors or microdescriptors to construct
  1592. that fraction of possible paths. Note that setting this option too low
  1593. can make your Tor client less anonymous, and setting it too high can
  1594. prevent your Tor client from bootstrapping. If this option is negative,
  1595. Tor will use a default value chosen by the directory authorities. If the
  1596. directory authorities do not choose a value, Tor will default to 0.6.
  1597. (Default: -1)
  1598. [[ClientBootstrapConsensusAuthorityDownloadInitialDelay]] **ClientBootstrapConsensusAuthorityDownloadInitialDelay** __N__::
  1599. Initial delay in seconds for when clients should download consensuses from authorities
  1600. if they are bootstrapping (that is, they don't have a usable, reasonably
  1601. live consensus). Only used by clients fetching from a list of fallback
  1602. directory mirrors. This schedule is advanced by (potentially concurrent)
  1603. connection attempts, unlike other schedules, which are advanced by
  1604. connection failures. (Default: 6)
  1605. [[ClientBootstrapConsensusFallbackDownloadInitialDelay]] **ClientBootstrapConsensusFallbackDownloadInitialDelay** __N__::
  1606. Initial delay in seconds for when clients should download consensuses from fallback
  1607. directory mirrors if they are bootstrapping (that is, they don't have a
  1608. usable, reasonably live consensus). Only used by clients fetching from a
  1609. list of fallback directory mirrors. This schedule is advanced by
  1610. (potentially concurrent) connection attempts, unlike other schedules,
  1611. which are advanced by connection failures. (Default: 0)
  1612. [[ClientBootstrapConsensusAuthorityOnlyDownloadInitialDelay]] **ClientBootstrapConsensusAuthorityOnlyDownloadInitialDelay** __N__::
  1613. Initial delay in seconds for when clients should download consensuses from authorities
  1614. if they are bootstrapping (that is, they don't have a usable, reasonably
  1615. live consensus). Only used by clients which don't have or won't fetch
  1616. from a list of fallback directory mirrors. This schedule is advanced by
  1617. (potentially concurrent) connection attempts, unlike other schedules,
  1618. which are advanced by connection failures. (Default: 0)
  1619. [[ClientBootstrapConsensusMaxInProgressTries]] **ClientBootstrapConsensusMaxInProgressTries** __NUM__::
  1620. Try this many simultaneous connections to download a consensus before
  1621. waiting for one to complete, timeout, or error out. (Default: 3)
  1622. [[DormantClientTimeout]] **DormantClientTimeout** __N__ **minutes**|**hours**|**days**|**weeks**::
  1623. If Tor spends this much time without any client activity,
  1624. enter a dormant state where automatic circuits are not built, and
  1625. directory information is not fetched.
  1626. Does not affect servers or onion services. Must be at least 10 minutes.
  1627. (Default: 24 hours)
  1628. [[DormantTimeoutDisabledByIdleStreams]] **DormantTimeoutDisabledByIdleStreams** **0**|**1**::
  1629. If true, then any open client stream (even one not reading or writing)
  1630. counts as client activity for the purpose of DormantClientTimeout.
  1631. If false, then only network activity counts. (Default: 1)
  1632. [[DormantOnFirstStartup]] **DormantOnFirstStartup** **0**|**1**::
  1633. If true, then the first time Tor starts up with a fresh DataDirectory,
  1634. it starts in dormant mode, and takes no actions until the user has made
  1635. a request. (This mode is recommended if installing a Tor client for a
  1636. user who might not actually use it.) If false, Tor bootstraps the first
  1637. time it is started, whether it sees a user request or not.
  1638. +
  1639. After the first time Tor starts, it begins in dormant mode if it was
  1640. dormant before, and not otherwise. (Default: 0)
  1641. [[DormantCanceledByStartup]] **DormantCanceledByStartup** **0**|**1**::
  1642. By default, Tor starts in active mode if it was active the last time
  1643. it was shut down, and in dormant mode if it was dormant. But if
  1644. this option is true, Tor treats every startup event as user
  1645. activity, and Tor will never start in Dormant mode, even if it has
  1646. been unused for a long time on previous runs. (Default: 0)
  1647. +
  1648. Note: Packagers and application developers should change the value of
  1649. this option only with great caution: it has the potential to
  1650. create spurious traffic on the network. This option should only
  1651. be used if Tor is started by an affirmative user activity (like
  1652. clicking on an applcation or running a command), and not if Tor
  1653. is launched for some other reason (for example, by a startup
  1654. process, or by an application that launches itself on every login.)
  1655. SERVER OPTIONS
  1656. --------------
  1657. The following options are useful only for servers (that is, if ORPort
  1658. is non-zero):
  1659. [[Address]] **Address** __address__::
  1660. The IPv4 address of this server, or a fully qualified domain name of
  1661. this server that resolves to an IPv4 address. You can leave this
  1662. unset, and Tor will try to guess your IPv4 address. This IPv4
  1663. address is the one used to tell clients and other servers where to
  1664. find your Tor server; it doesn't affect the address that your server
  1665. binds to. To bind to a different address, use the ORPort and
  1666. OutboundBindAddress options.
  1667. [[AssumeReachable]] **AssumeReachable** **0**|**1**::
  1668. This option is used when bootstrapping a new Tor network. If set to 1,
  1669. don't do self-reachability testing; just upload your server descriptor
  1670. immediately. If **AuthoritativeDirectory** is also set, this option
  1671. instructs the dirserver to bypass remote reachability testing too and list
  1672. all connected servers as running.
  1673. [[BridgeRelay]] **BridgeRelay** **0**|**1**::
  1674. Sets the relay to act as a "bridge" with respect to relaying connections
  1675. from bridge users to the Tor network. It mainly causes Tor to publish a
  1676. server descriptor to the bridge database, rather than
  1677. to the public directory authorities. +
  1678. +
  1679. Note: make sure that no MyFamily lines are present in your torrc when
  1680. relay is configured in bridge mode.
  1681. [[BridgeDistribution]] **BridgeDistribution** __string__::
  1682. If set along with BridgeRelay, Tor will include a new line in its
  1683. bridge descriptor which indicates to the BridgeDB service how it
  1684. would like its bridge address to be given out. Set it to "none" if
  1685. you want BridgeDB to avoid distributing your bridge address, or "any" to
  1686. let BridgeDB decide. (Default: any)
  1687. +
  1688. Note: as of Oct 2017, the BridgeDB part of this option is not yet
  1689. implemented. Until BridgeDB is updated to obey this option, your
  1690. bridge will make this request, but it will not (yet) be obeyed.
  1691. [[ContactInfo]] **ContactInfo** __email_address__::
  1692. Administrative contact information for this relay or bridge. This line
  1693. can be used to contact you if your relay or bridge is misconfigured or
  1694. something else goes wrong. Note that we archive and publish all
  1695. descriptors containing these lines and that Google indexes them, so
  1696. spammers might also collect them. You may want to obscure the fact
  1697. that it's an email address and/or generate a new address for this
  1698. purpose. +
  1699. +
  1700. ContactInfo **must** be set to a working address if you run more than one
  1701. relay or bridge. (Really, everybody running a relay or bridge should set
  1702. it.)
  1703. [[ExitRelay]] **ExitRelay** **0**|**1**|**auto**::
  1704. Tells Tor whether to run as an exit relay. If Tor is running as a
  1705. non-bridge server, and ExitRelay is set to 1, then Tor allows traffic to
  1706. exit according to the ExitPolicy option, the ReducedExitPolicy option,
  1707. or the default ExitPolicy (if no other exit policy option is specified). +
  1708. +
  1709. If ExitRelay is set to 0, no traffic is allowed to exit, and the
  1710. ExitPolicy, ReducedExitPolicy, and IPv6Exit options are ignored. +
  1711. +
  1712. If ExitRelay is set to "auto", then Tor checks the ExitPolicy,
  1713. ReducedExitPolicy, and IPv6Exit options. If at least one of these options
  1714. is set, Tor behaves as if ExitRelay were set to 1. If none of these exit
  1715. policy options are set, Tor behaves as if ExitRelay were set to 0.
  1716. (Default: auto)
  1717. [[ExitPolicy]] **ExitPolicy** __policy__,__policy__,__...__::
  1718. Set an exit policy for this server. Each policy is of the form
  1719. "**accept[6]**|**reject[6]** __ADDR__[/__MASK__][:__PORT__]". If /__MASK__ is
  1720. omitted then this policy just applies to the host given. Instead of giving
  1721. a host or network you can also use "\*" to denote the universe (0.0.0.0/0
  1722. and ::/0), or \*4 to denote all IPv4 addresses, and \*6 to denote all IPv6
  1723. addresses.
  1724. __PORT__ can be a single port number, an interval of ports
  1725. "__FROM_PORT__-__TO_PORT__", or "\*". If __PORT__ is omitted, that means
  1726. "\*". +
  1727. +
  1728. For example, "accept 18.7.22.69:\*,reject 18.0.0.0/8:\*,accept \*:\*" would
  1729. reject any IPv4 traffic destined for MIT except for web.mit.edu, and accept
  1730. any other IPv4 or IPv6 traffic. +
  1731. +
  1732. Tor also allows IPv6 exit policy entries. For instance, "reject6 [FC00::]/7:\*"
  1733. rejects all destinations that share 7 most significant bit prefix with
  1734. address FC00::. Respectively, "accept6 [C000::]/3:\*" accepts all destinations
  1735. that share 3 most significant bit prefix with address C000::. +
  1736. +
  1737. accept6 and reject6 only produce IPv6 exit policy entries. Using an IPv4
  1738. address with accept6 or reject6 is ignored and generates a warning.
  1739. accept/reject allows either IPv4 or IPv6 addresses. Use \*4 as an IPv4
  1740. wildcard address, and \*6 as an IPv6 wildcard address. accept/reject *
  1741. expands to matching IPv4 and IPv6 wildcard address rules. +
  1742. +
  1743. To specify all IPv4 and IPv6 internal and link-local networks (including
  1744. 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,
  1745. 172.16.0.0/12, [::]/8, [FC00::]/7, [FE80::]/10, [FEC0::]/10, [FF00::]/8,
  1746. and [::]/127), you can use the "private" alias instead of an address.
  1747. ("private" always produces rules for IPv4 and IPv6 addresses, even when
  1748. used with accept6/reject6.) +
  1749. +
  1750. Private addresses are rejected by default (at the beginning of your exit
  1751. policy), along with any configured primary public IPv4 and IPv6 addresses.
  1752. These private addresses are rejected unless you set the
  1753. ExitPolicyRejectPrivate config option to 0. For example, once you've done
  1754. that, you could allow HTTP to 127.0.0.1 and block all other connections to
  1755. internal networks with "accept 127.0.0.1:80,reject private:\*", though that
  1756. may also allow connections to your own computer that are addressed to its
  1757. public (external) IP address. See RFC 1918 and RFC 3330 for more details
  1758. about internal and reserved IP address space. See
  1759. ExitPolicyRejectLocalInterfaces if you want to block every address on the
  1760. relay, even those that aren't advertised in the descriptor. +
  1761. +
  1762. This directive can be specified multiple times so you don't have to put it
  1763. all on one line. +
  1764. +
  1765. Policies are considered first to last, and the first match wins. If you
  1766. want to allow the same ports on IPv4 and IPv6, write your rules using
  1767. accept/reject \*. If you want to allow different ports on IPv4 and IPv6,
  1768. write your IPv6 rules using accept6/reject6 \*6, and your IPv4 rules using
  1769. accept/reject \*4. If you want to \_replace_ the default exit policy, end
  1770. your exit policy with either a reject \*:* or an accept \*:*. Otherwise,
  1771. you're \_augmenting_ (prepending to) the default exit policy. +
  1772. +
  1773. If you want to use a reduced exit policy rather than the default exit
  1774. policy, set "ReducedExitPolicy 1". If you want to _replace_ the default
  1775. exit policy with your custom exit policy, end your exit policy with either
  1776. a reject *:* or an accept *:*. Otherwise, you're _augmenting_ (prepending
  1777. to) the default or reduced exit policy. +
  1778. +
  1779. The default exit policy is:
  1780. reject *:25
  1781. reject *:119
  1782. reject *:135-139
  1783. reject *:445
  1784. reject *:563
  1785. reject *:1214
  1786. reject *:4661-4666
  1787. reject *:6346-6429
  1788. reject *:6699
  1789. reject *:6881-6999
  1790. accept *:*
  1791. // Anchor only for formatting, not visible in the man page.
  1792. [[ExitPolicyDefault]]::
  1793. Since the default exit policy uses accept/reject *, it applies to both
  1794. IPv4 and IPv6 addresses.
  1795. [[ExitPolicyRejectPrivate]] **ExitPolicyRejectPrivate** **0**|**1**::
  1796. Reject all private (local) networks, along with the relay's advertised
  1797. public IPv4 and IPv6 addresses, at the beginning of your exit policy.
  1798. See above entry on ExitPolicy.
  1799. (Default: 1)
  1800. [[ExitPolicyRejectLocalInterfaces]] **ExitPolicyRejectLocalInterfaces** **0**|**1**::
  1801. Reject all IPv4 and IPv6 addresses that the relay knows about, at the
  1802. beginning of your exit policy. This includes any OutboundBindAddress, the
  1803. bind addresses of any port options, such as ControlPort or DNSPort, and any
  1804. public IPv4 and IPv6 addresses on any interface on the relay. (If IPv6Exit
  1805. is not set, all IPv6 addresses will be rejected anyway.)
  1806. See above entry on ExitPolicy.
  1807. This option is off by default, because it lists all public relay IP
  1808. addresses in the ExitPolicy, even those relay operators might prefer not
  1809. to disclose.
  1810. (Default: 0)
  1811. [[ReducedExitPolicy]] **ReducedExitPolicy** **0**|**1**::
  1812. If set, use a reduced exit policy rather than the default one. +
  1813. +
  1814. The reduced exit policy is an alternative to the default exit policy. It
  1815. allows as many Internet services as possible while still blocking the
  1816. majority of TCP ports. Currently, the policy allows approximately 65 ports.
  1817. This reduces the odds that your node will be used for peer-to-peer
  1818. applications. +
  1819. +
  1820. The reduced exit policy is:
  1821. accept *:20-21
  1822. accept *:22
  1823. accept *:23
  1824. accept *:43
  1825. accept *:53
  1826. accept *:79
  1827. accept *:80-81
  1828. accept *:88
  1829. accept *:110
  1830. accept *:143
  1831. accept *:194
  1832. accept *:220
  1833. accept *:389
  1834. accept *:443
  1835. accept *:464
  1836. accept *:465
  1837. accept *:531
  1838. accept *:543-544
  1839. accept *:554
  1840. accept *:563
  1841. accept *:587
  1842. accept *:636
  1843. accept *:706
  1844. accept *:749
  1845. accept *:873
  1846. accept *:902-904
  1847. accept *:981
  1848. accept *:989-990
  1849. accept *:991
  1850. accept *:992
  1851. accept *:993
  1852. accept *:994
  1853. accept *:995
  1854. accept *:1194
  1855. accept *:1220
  1856. accept *:1293
  1857. accept *:1500
  1858. accept *:1533
  1859. accept *:1677
  1860. accept *:1723
  1861. accept *:1755
  1862. accept *:1863
  1863. accept *:2082
  1864. accept *:2083
  1865. accept *:2086-2087
  1866. accept *:2095-2096
  1867. accept *:2102-2104
  1868. accept *:3128
  1869. accept *:3389
  1870. accept *:3690
  1871. accept *:4321
  1872. accept *:4643
  1873. accept *:5050
  1874. accept *:5190
  1875. accept *:5222-5223
  1876. accept *:5228
  1877. accept *:5900
  1878. accept *:6660-6669
  1879. accept *:6679
  1880. accept *:6697
  1881. accept *:8000
  1882. accept *:8008
  1883. accept *:8074
  1884. accept *:8080
  1885. accept *:8082
  1886. accept *:8087-8088
  1887. accept *:8232-8233
  1888. accept *:8332-8333
  1889. accept *:8443
  1890. accept *:8888
  1891. accept *:9418
  1892. accept *:9999
  1893. accept *:10000
  1894. accept *:11371
  1895. accept *:19294
  1896. accept *:19638
  1897. accept *:50002
  1898. accept *:64738
  1899. reject *:*
  1900. (Default: 0)
  1901. [[IPv6Exit]] **IPv6Exit** **0**|**1**::
  1902. If set, and we are an exit node, allow clients to use us for IPv6 traffic.
  1903. When this option is set and ExitRelay is auto, we act as if ExitRelay
  1904. is 1. (Default: 0)
  1905. [[MaxOnionQueueDelay]] **MaxOnionQueueDelay** __NUM__ [**msec**|**second**]::
  1906. If we have more onionskins queued for processing than we can process in
  1907. this amount of time, reject new ones. (Default: 1750 msec)
  1908. [[MyFamily]] **MyFamily** __fingerprint__,__fingerprint__,...::
  1909. Declare that this Tor relay is controlled or administered by a group or
  1910. organization identical or similar to that of the other relays, defined by
  1911. their (possibly $-prefixed) identity fingerprints.
  1912. This option can be repeated many times, for
  1913. convenience in defining large families: all fingerprints in all MyFamily
  1914. lines are merged into one list.
  1915. When two relays both declare that they are in the
  1916. same \'family', Tor clients will not use them in the same circuit. (Each
  1917. relay only needs to list the other servers in its family; it doesn't need to
  1918. list itself, but it won't hurt if it does.) Do not list any bridge relay as it would
  1919. compromise its concealment. +
  1920. +
  1921. When listing a node, it's better to list it by fingerprint than by
  1922. nickname: fingerprints are more reliable. +
  1923. +
  1924. If you run more than one relay, the MyFamily option on each relay
  1925. **must** list all other relays, as described above. +
  1926. +
  1927. Note: do not use MyFamily when configuring your Tor instance as a
  1928. brigde.
  1929. [[Nickname]] **Nickname** __name__::
  1930. Set the server's nickname to \'name'. Nicknames must be between 1 and 19
  1931. characters inclusive, and must contain only the characters [a-zA-Z0-9].
  1932. If not set, **Unnamed** will be used. Relays can always be uniquely identified
  1933. by their identity fingerprints.
  1934. [[NumCPUs]] **NumCPUs** __num__::
  1935. How many processes to use at once for decrypting onionskins and other
  1936. parallelizable operations. If this is set to 0, Tor will try to detect
  1937. how many CPUs you have, defaulting to 1 if it can't tell. (Default: 0)
  1938. [[ORPort]] **ORPort** \['address':]__PORT__|**auto** [_flags_]::
  1939. Advertise this port to listen for connections from Tor clients and
  1940. servers. This option is required to be a Tor server.
  1941. Set it to "auto" to have Tor pick a port for you. Set it to 0 to not
  1942. run an ORPort at all. This option can occur more than once. (Default: 0) +
  1943. +
  1944. Tor recognizes these flags on each ORPort:
  1945. **NoAdvertise**;;
  1946. By default, we bind to a port and tell our users about it. If
  1947. NoAdvertise is specified, we don't advertise, but listen anyway. This
  1948. can be useful if the port everybody will be connecting to (for
  1949. example, one that's opened on our firewall) is somewhere else.
  1950. **NoListen**;;
  1951. By default, we bind to a port and tell our users about it. If
  1952. NoListen is specified, we don't bind, but advertise anyway. This
  1953. can be useful if something else (for example, a firewall's port
  1954. forwarding configuration) is causing connections to reach us.
  1955. **IPv4Only**;;
  1956. If the address is absent, or resolves to both an IPv4 and an IPv6
  1957. address, only listen to the IPv4 address.
  1958. **IPv6Only**;;
  1959. If the address is absent, or resolves to both an IPv4 and an IPv6
  1960. address, only listen to the IPv6 address.
  1961. // Anchor only for formatting, not visible in the man page.
  1962. [[ORPortFlagsExclusive]]::
  1963. For obvious reasons, NoAdvertise and NoListen are mutually exclusive, and
  1964. IPv4Only and IPv6Only are mutually exclusive.
  1965. [[PublishServerDescriptor]] **PublishServerDescriptor** **0**|**1**|**v3**|**bridge**,**...**::
  1966. This option specifies which descriptors Tor will publish when acting as
  1967. a relay. You can
  1968. choose multiple arguments, separated by commas. +
  1969. +
  1970. If this option is set to 0, Tor will not publish its
  1971. descriptors to any directories. (This is useful if you're testing
  1972. out your server, or if you're using a Tor controller that handles
  1973. directory publishing for you.) Otherwise, Tor will publish its
  1974. descriptors of all type(s) specified. The default is "1", which
  1975. means "if running as a relay or bridge, publish descriptors to the
  1976. appropriate authorities". Other possibilities are "v3", meaning
  1977. "publish as if you're a relay", and "bridge", meaning "publish as
  1978. if you're a bridge".
  1979. [[ShutdownWaitLength]] **ShutdownWaitLength** __NUM__::
  1980. When we get a SIGINT and we're a server, we begin shutting down:
  1981. we close listeners and start refusing new circuits. After **NUM**
  1982. seconds, we exit. If we get a second SIGINT, we exit immediately.
  1983. (Default: 30 seconds)
  1984. [[SSLKeyLifetime]] **SSLKeyLifetime** __N__ **minutes**|**hours**|**days**|**weeks**::
  1985. When creating a link certificate for our outermost SSL handshake,
  1986. set its lifetime to this amount of time. If set to 0, Tor will choose
  1987. some reasonable random defaults. (Default: 0)
  1988. [[HeartbeatPeriod]] **HeartbeatPeriod** __N__ **minutes**|**hours**|**days**|**weeks**::
  1989. Log a heartbeat message every **HeartbeatPeriod** seconds. This is
  1990. a log level __notice__ message, designed to let you know your Tor
  1991. server is still alive and doing useful things. Settings this
  1992. to 0 will disable the heartbeat. Otherwise, it must be at least 30
  1993. minutes. (Default: 6 hours)
  1994. [[MainloopStats]] **MainloopStats** **0**|**1**::
  1995. Log main loop statistics every **HeartbeatPeriod** seconds. This is a log
  1996. level __notice__ message designed to help developers instrumenting Tor's
  1997. main event loop. (Default: 0)
  1998. [[AccountingMax]] **AccountingMax** __N__ **bytes**|**KBytes**|**MBytes**|**GBytes**|**TBytes**|**KBits**|**MBits**|**GBits**|**TBits**::
  1999. Limits the max number of bytes sent and received within a set time period
  2000. using a given calculation rule (see: AccountingStart, AccountingRule).
  2001. Useful if you need to stay under a specific bandwidth. By default, the
  2002. number used for calculation is the max of either the bytes sent or
  2003. received. For example, with AccountingMax set to 1 GByte, a server
  2004. could send 900 MBytes and receive 800 MBytes and continue running.
  2005. It will only hibernate once one of the two reaches 1 GByte. This can
  2006. be changed to use the sum of the both bytes received and sent by setting
  2007. the AccountingRule option to "sum" (total bandwidth in/out). When the
  2008. number of bytes remaining gets low, Tor will stop accepting new connections
  2009. and circuits. When the number of bytes is exhausted, Tor will hibernate
  2010. until some time in the next accounting period. To prevent all servers
  2011. from waking at the same time, Tor will also wait until a random point
  2012. in each period before waking up. If you have bandwidth cost issues,
  2013. enabling hibernation is preferable to setting a low bandwidth, since
  2014. it provides users with a collection of fast servers that are up some
  2015. of the time, which is more useful than a set of slow servers that are
  2016. always "available".
  2017. [[AccountingRule]] **AccountingRule** **sum**|**max**|**in**|**out**::
  2018. How we determine when our AccountingMax has been reached (when we
  2019. should hibernate) during a time interval. Set to "max" to calculate
  2020. using the higher of either the sent or received bytes (this is the
  2021. default functionality). Set to "sum" to calculate using the sent
  2022. plus received bytes. Set to "in" to calculate using only the
  2023. received bytes. Set to "out" to calculate using only the sent bytes.
  2024. (Default: max)
  2025. [[AccountingStart]] **AccountingStart** **day**|**week**|**month** [__day__] __HH:MM__::
  2026. Specify how long accounting periods last. If **month** is given,
  2027. each accounting period runs from the time __HH:MM__ on the __dayth__ day of one
  2028. month to the same day and time of the next. The relay will go at full speed,
  2029. use all the quota you specify, then hibernate for the rest of the period. (The
  2030. day must be between 1 and 28.) If **week** is given, each accounting period
  2031. runs from the time __HH:MM__ of the __dayth__ day of one week to the same day
  2032. and time of the next week, with Monday as day 1 and Sunday as day 7. If **day**
  2033. is given, each accounting period runs from the time __HH:MM__ each day to the
  2034. same time on the next day. All times are local, and given in 24-hour time.
  2035. (Default: "month 1 0:00")
  2036. [[RefuseUnknownExits]] **RefuseUnknownExits** **0**|**1**|**auto**::
  2037. Prevent nodes that don't appear in the consensus from exiting using this
  2038. relay. If the option is 1, we always block exit attempts from such
  2039. nodes; if it's 0, we never do, and if the option is "auto", then we do
  2040. whatever the authorities suggest in the consensus (and block if the consensus
  2041. is quiet on the issue). (Default: auto)
  2042. [[ServerDNSResolvConfFile]] **ServerDNSResolvConfFile** __filename__::
  2043. Overrides the default DNS configuration with the configuration in
  2044. __filename__. The file format is the same as the standard Unix
  2045. "**resolv.conf**" file (7). This option, like all other ServerDNS options,
  2046. only affects name lookups that your server does on behalf of clients.
  2047. (Defaults to use the system DNS configuration or a localhost DNS service
  2048. in case no nameservers are found in a given configuration.)
  2049. [[ServerDNSAllowBrokenConfig]] **ServerDNSAllowBrokenConfig** **0**|**1**::
  2050. If this option is false, Tor exits immediately if there are problems
  2051. parsing the system DNS configuration or connecting to nameservers.
  2052. Otherwise, Tor continues to periodically retry the system nameservers until
  2053. it eventually succeeds. (Default: 1)
  2054. [[ServerDNSSearchDomains]] **ServerDNSSearchDomains** **0**|**1**::
  2055. If set to 1, then we will search for addresses in the local search domain.
  2056. For example, if this system is configured to believe it is in
  2057. "example.com", and a client tries to connect to "www", the client will be
  2058. connected to "www.example.com". This option only affects name lookups that
  2059. your server does on behalf of clients. (Default: 0)
  2060. [[ServerDNSDetectHijacking]] **ServerDNSDetectHijacking** **0**|**1**::
  2061. When this option is set to 1, we will test periodically to determine
  2062. whether our local nameservers have been configured to hijack failing DNS
  2063. requests (usually to an advertising site). If they are, we will attempt to
  2064. correct this. This option only affects name lookups that your server does
  2065. on behalf of clients. (Default: 1)
  2066. [[ServerDNSTestAddresses]] **ServerDNSTestAddresses** __hostname__,__hostname__,__...__::
  2067. When we're detecting DNS hijacking, make sure that these __valid__ addresses
  2068. aren't getting redirected. If they are, then our DNS is completely useless,
  2069. and we'll reset our exit policy to "reject \*:*". This option only affects
  2070. name lookups that your server does on behalf of clients. (Default:
  2071. "www.google.com, www.mit.edu, www.yahoo.com, www.slashdot.org")
  2072. [[ServerDNSAllowNonRFC953Hostnames]] **ServerDNSAllowNonRFC953Hostnames** **0**|**1**::
  2073. When this option is disabled, Tor does not try to resolve hostnames
  2074. containing illegal characters (like @ and :) rather than sending them to an
  2075. exit node to be resolved. This helps trap accidental attempts to resolve
  2076. URLs and so on. This option only affects name lookups that your server does
  2077. on behalf of clients. (Default: 0)
  2078. [[BridgeRecordUsageByCountry]] **BridgeRecordUsageByCountry** **0**|**1**::
  2079. When this option is enabled and BridgeRelay is also enabled, and we have
  2080. GeoIP data, Tor keeps a per-country count of how many client
  2081. addresses have contacted it so that it can help the bridge authority guess
  2082. which countries have blocked access to it. If ExtraInfoStatistics is
  2083. enabled, it will be published as part of extra-info document. (Default: 1)
  2084. [[ServerDNSRandomizeCase]] **ServerDNSRandomizeCase** **0**|**1**::
  2085. When this option is set, Tor sets the case of each character randomly in
  2086. outgoing DNS requests, and makes sure that the case matches in DNS replies.
  2087. This so-called "0x20 hack" helps resist some types of DNS poisoning attack.
  2088. For more information, see "Increased DNS Forgery Resistance through
  2089. 0x20-Bit Encoding". This option only affects name lookups that your server
  2090. does on behalf of clients. (Default: 1)
  2091. [[GeoIPFile]] **GeoIPFile** __filename__::
  2092. A filename containing IPv4 GeoIP data, for use with by-country statistics.
  2093. [[GeoIPv6File]] **GeoIPv6File** __filename__::
  2094. A filename containing IPv6 GeoIP data, for use with by-country statistics.
  2095. [[CellStatistics]] **CellStatistics** **0**|**1**::
  2096. Relays only.
  2097. When this option is enabled, Tor collects statistics about cell
  2098. processing (i.e. mean time a cell is spending in a queue, mean
  2099. number of cells in a queue and mean number of processed cells per
  2100. circuit) and writes them into disk every 24 hours. Onion router
  2101. operators may use the statistics for performance monitoring.
  2102. If ExtraInfoStatistics is enabled, it will published as part of
  2103. extra-info document. (Default: 0)
  2104. [[PaddingStatistics]] **PaddingStatistics** **0**|**1**::
  2105. Relays and bridges only.
  2106. When this option is enabled, Tor collects statistics for padding cells
  2107. sent and received by this relay, in addition to total cell counts.
  2108. These statistics are rounded, and omitted if traffic is low. This
  2109. information is important for load balancing decisions related to padding.
  2110. If ExtraInfoStatistics is enabled, it will be published
  2111. as a part of extra-info document. (Default: 1)
  2112. [[DirReqStatistics]] **DirReqStatistics** **0**|**1**::
  2113. Relays and bridges only.
  2114. When this option is enabled, a Tor directory writes statistics on the
  2115. number and response time of network status requests to disk every 24
  2116. hours. Enables relay and bridge operators to monitor how much their
  2117. server is being used by clients to learn about Tor network.
  2118. If ExtraInfoStatistics is enabled, it will published as part of
  2119. extra-info document. (Default: 1)
  2120. [[EntryStatistics]] **EntryStatistics** **0**|**1**::
  2121. Relays only.
  2122. When this option is enabled, Tor writes statistics on the number of
  2123. directly connecting clients to disk every 24 hours. Enables relay
  2124. operators to monitor how much inbound traffic that originates from
  2125. Tor clients passes through their server to go further down the
  2126. Tor network. If ExtraInfoStatistics is enabled, it will be published
  2127. as part of extra-info document. (Default: 0)
  2128. [[ExitPortStatistics]] **ExitPortStatistics** **0**|**1**::
  2129. Exit relays only.
  2130. When this option is enabled, Tor writes statistics on the number of
  2131. relayed bytes and opened stream per exit port to disk every 24 hours.
  2132. Enables exit relay operators to measure and monitor amounts of traffic
  2133. that leaves Tor network through their exit node. If ExtraInfoStatistics
  2134. is enabled, it will be published as part of extra-info document.
  2135. (Default: 0)
  2136. [[ConnDirectionStatistics]] **ConnDirectionStatistics** **0**|**1**::
  2137. Relays only.
  2138. When this option is enabled, Tor writes statistics on the amounts of
  2139. traffic it passes between itself and other relays to disk every 24
  2140. hours. Enables relay operators to monitor how much their relay is
  2141. being used as middle node in the circuit. If ExtraInfoStatistics is
  2142. enabled, it will be published as part of extra-info document.
  2143. (Default: 0)
  2144. [[HiddenServiceStatistics]] **HiddenServiceStatistics** **0**|**1**::
  2145. Relays only.
  2146. When this option is enabled, a Tor relay writes obfuscated
  2147. statistics on its role as hidden-service directory, introduction
  2148. point, or rendezvous point to disk every 24 hours. If
  2149. ExtraInfoStatistics is also enabled, these statistics are further
  2150. published to the directory authorities. (Default: 1)
  2151. [[ExtraInfoStatistics]] **ExtraInfoStatistics** **0**|**1**::
  2152. When this option is enabled, Tor includes previously gathered statistics in
  2153. its extra-info documents that it uploads to the directory authorities.
  2154. Disabling this option also disables bandwidth usage statistics, GeoIPFile
  2155. hashes, and ServerTransportPlugin lists in the extra-info file.
  2156. (Default: 1)
  2157. [[ExtendAllowPrivateAddresses]] **ExtendAllowPrivateAddresses** **0**|**1**::
  2158. When this option is enabled, Tor will connect to relays on localhost,
  2159. RFC1918 addresses, and so on. In particular, Tor will make direct OR
  2160. connections, and Tor routers allow EXTEND requests, to these private
  2161. addresses. (Tor will always allow connections to bridges, proxies, and
  2162. pluggable transports configured on private addresses.) Enabling this
  2163. option can create security issues; you should probably leave it off.
  2164. (Default: 0)
  2165. [[MaxMemInQueues]] **MaxMemInQueues** __N__ **bytes**|**KB**|**MB**|**GB**::
  2166. This option configures a threshold above which Tor will assume that it
  2167. needs to stop queueing or buffering data because it's about to run out of
  2168. memory. If it hits this threshold, it will begin killing circuits until
  2169. it has recovered at least 10% of this memory. Do not set this option too
  2170. low, or your relay may be unreliable under load. This option only
  2171. affects some queues, so the actual process size will be larger than
  2172. this. If this option is set to 0, Tor will try to pick a reasonable
  2173. default based on your system's physical memory. (Default: 0)
  2174. [[DisableOOSCheck]] **DisableOOSCheck** **0**|**1**::
  2175. This option disables the code that closes connections when Tor notices
  2176. that it is running low on sockets. Right now, it is on by default,
  2177. since the existing out-of-sockets mechanism tends to kill OR connections
  2178. more than it should. (Default: 1)
  2179. [[SigningKeyLifetime]] **SigningKeyLifetime** __N__ **days**|**weeks**|**months**::
  2180. For how long should each Ed25519 signing key be valid? Tor uses a
  2181. permanent master identity key that can be kept offline, and periodically
  2182. generates new "signing" keys that it uses online. This option
  2183. configures their lifetime.
  2184. (Default: 30 days)
  2185. [[OfflineMasterKey]] **OfflineMasterKey** **0**|**1**::
  2186. If non-zero, the Tor relay will never generate or load its master secret
  2187. key. Instead, you'll have to use "tor --keygen" to manage the permanent
  2188. ed25519 master identity key, as well as the corresponding temporary
  2189. signing keys and certificates. (Default: 0)
  2190. [[KeyDirectory]] **KeyDirectory** __DIR__::
  2191. Store secret keys in DIR. Can not be changed while tor is
  2192. running.
  2193. (Default: the "keys" subdirectory of DataDirectory.)
  2194. [[KeyDirectoryGroupReadable]] **KeyDirectoryGroupReadable** **0**|**1**::
  2195. If this option is set to 0, don't allow the filesystem group to read the
  2196. KeywDirectory. If the option is set to 1, make the KeyDirectory readable
  2197. by the default GID. (Default: 0)
  2198. [[RephistTrackTime]] **RephistTrackTime** __N__ **seconds**|**minutes**|**hours**|**days**|**weeks**::
  2199. Tells an authority, or other node tracking node reliability and history,
  2200. that fine-grained information about nodes can be discarded when it hasn't
  2201. changed for a given amount of time. (Default: 24 hours)
  2202. DIRECTORY SERVER OPTIONS
  2203. ------------------------
  2204. The following options are useful only for directory servers. (Relays with
  2205. enough bandwidth automatically become directory servers; see DirCache for
  2206. details.)
  2207. [[DirPortFrontPage]] **DirPortFrontPage** __FILENAME__::
  2208. When this option is set, it takes an HTML file and publishes it as "/" on
  2209. the DirPort. Now relay operators can provide a disclaimer without needing
  2210. to set up a separate webserver. There's a sample disclaimer in
  2211. contrib/operator-tools/tor-exit-notice.html.
  2212. [[DirPort]] **DirPort** \['address':]__PORT__|**auto** [_flags_]::
  2213. If this option is nonzero, advertise the directory service on this port.
  2214. Set it to "auto" to have Tor pick a port for you. This option can occur
  2215. more than once, but only one advertised DirPort is supported: all
  2216. but one DirPort must have the **NoAdvertise** flag set. (Default: 0) +
  2217. +
  2218. The same flags are supported here as are supported by ORPort.
  2219. [[DirPolicy]] **DirPolicy** __policy__,__policy__,__...__::
  2220. Set an entrance policy for this server, to limit who can connect to the
  2221. directory ports. The policies have the same form as exit policies above,
  2222. except that port specifiers are ignored. Any address not matched by
  2223. some entry in the policy is accepted.
  2224. [[DirCache]] **DirCache** **0**|**1**::
  2225. When this option is set, Tor caches all current directory documents except
  2226. extra info documents, and accepts client requests for them. If
  2227. **DownloadExtraInfo** is set, cached extra info documents are also cached.
  2228. Setting **DirPort** is not required for **DirCache**, because clients
  2229. connect via the ORPort by default. Setting either DirPort or BridgeRelay
  2230. and setting DirCache to 0 is not supported. (Default: 1)
  2231. [[MaxConsensusAgeForDiffs]] **MaxConsensusAgeForDiffs** __N__ **minutes**|**hours**|**days**|**weeks**::
  2232. When this option is nonzero, Tor caches will not try to generate
  2233. consensus diffs for any consensus older than this amount of time.
  2234. If this option is set to zero, Tor will pick a reasonable default from
  2235. the current networkstatus document. You should not set this
  2236. option unless your cache is severely low on disk space or CPU.
  2237. If you need to set it, keeping it above 3 or 4 hours will help clients
  2238. much more than setting it to zero.
  2239. (Default: 0)
  2240. DENIAL OF SERVICE MITIGATION OPTIONS
  2241. ------------------------------------
  2242. Tor has three built-in mitigation options that can be individually
  2243. enabled/disabled and fine-tuned, but by default Tor directory authorities will
  2244. define reasonable values for relays and no explicit configuration is required
  2245. to make use of these protections. The mitigations take place at relays,
  2246. and are as follows:
  2247. 1. If a single client address makes too many concurrent connections (this is
  2248. configurable via DoSConnectionMaxConcurrentCount), hang up on further
  2249. connections.
  2250. +
  2251. 2. If a single client IP address (v4 or v6) makes circuits too quickly
  2252. (default values are more than 3 per second, with an allowed burst of 90,
  2253. see DoSCircuitCreationRate and DoSCircuitCreationBurst) while also having
  2254. too many connections open (default is 3, see
  2255. DoSCircuitCreationMinConnections), tor will refuse any new circuit (CREATE
  2256. cells) for the next while (random value between 1 and 2 hours).
  2257. +
  2258. 3. If a client asks to establish a rendezvous point to you directly (ex:
  2259. Tor2Web client), ignore the request.
  2260. These defenses can be manually controlled by torrc options, but relays will
  2261. also take guidance from consensus parameters using these same names, so there's
  2262. no need to configure anything manually. In doubt, do not change those values.
  2263. The values set by the consensus, if any, can be found here:
  2264. https://consensus-health.torproject.org/#consensusparams
  2265. If any of the DoS mitigations are enabled, a heartbeat message will appear in
  2266. your log at NOTICE level which looks like:
  2267. DoS mitigation since startup: 429042 circuits rejected, 17 marked addresses.
  2268. 2238 connections closed. 8052 single hop clients refused.
  2269. The following options are useful only for a public relay. They control the
  2270. Denial of Service mitigation subsystem described above.
  2271. [[DoSCircuitCreationEnabled]] **DoSCircuitCreationEnabled** **0**|**1**|**auto**::
  2272. Enable circuit creation DoS mitigation. If set to 1 (enabled), tor will
  2273. cache client IPs along with statistics in order to detect circuit DoS
  2274. attacks. If an address is positively identified, tor will activate
  2275. defenses against the address. See the DoSCircuitCreationDefenseType option
  2276. for more details. This is a client to relay detection only. "auto" means
  2277. use the consensus parameter. If not defined in the consensus, the value is 0.
  2278. (Default: auto)
  2279. [[DoSCircuitCreationMinConnections]] **DoSCircuitCreationMinConnections** __NUM__::
  2280. Minimum threshold of concurrent connections before a client address can be
  2281. flagged as executing a circuit creation DoS. In other words, once a client
  2282. address reaches the circuit rate and has a minimum of NUM concurrent
  2283. connections, a detection is positive. "0" means use the consensus
  2284. parameter. If not defined in the consensus, the value is 3.
  2285. (Default: 0)
  2286. [[DoSCircuitCreationRate]] **DoSCircuitCreationRate** __NUM__::
  2287. The allowed circuit creation rate per second applied per client IP
  2288. address. If this option is 0, it obeys a consensus parameter. If not
  2289. defined in the consensus, the value is 3.
  2290. (Default: 0)
  2291. [[DoSCircuitCreationBurst]] **DoSCircuitCreationBurst** __NUM__::
  2292. The allowed circuit creation burst per client IP address. If the circuit
  2293. rate and the burst are reached, a client is marked as executing a circuit
  2294. creation DoS. "0" means use the consensus parameter. If not defined in the
  2295. consensus, the value is 90.
  2296. (Default: 0)
  2297. [[DoSCircuitCreationDefenseType]] **DoSCircuitCreationDefenseType** __NUM__::
  2298. This is the type of defense applied to a detected client address. The
  2299. possible values are:
  2300. +
  2301. 1: No defense.
  2302. +
  2303. 2: Refuse circuit creation for the DoSCircuitCreationDefenseTimePeriod period of time.
  2304. +
  2305. "0" means use the consensus parameter. If not defined in the consensus, the value is 2.
  2306. (Default: 0)
  2307. [[DoSCircuitCreationDefenseTimePeriod]] **DoSCircuitCreationDefenseTimePeriod** __N__ **seconds**|**minutes**|**hours**::
  2308. The base time period in seconds that the DoS defense is activated for. The
  2309. actual value is selected randomly for each activation from N+1 to 3/2 * N.
  2310. "0" means use the consensus parameter. If not defined in the consensus,
  2311. the value is 3600 seconds (1 hour).
  2312. (Default: 0)
  2313. [[DoSConnectionEnabled]] **DoSConnectionEnabled** **0**|**1**|**auto**::
  2314. Enable the connection DoS mitigation. If set to 1 (enabled), for client
  2315. address only, this allows tor to mitigate against large number of
  2316. concurrent connections made by a single IP address. "auto" means use the
  2317. consensus parameter. If not defined in the consensus, the value is 0.
  2318. (Default: auto)
  2319. [[DoSConnectionMaxConcurrentCount]] **DoSConnectionMaxConcurrentCount** __NUM__::
  2320. The maximum threshold of concurrent connection from a client IP address.
  2321. Above this limit, a defense selected by DoSConnectionDefenseType is
  2322. applied. "0" means use the consensus parameter. If not defined in the
  2323. consensus, the value is 100.
  2324. (Default: 0)
  2325. [[DoSConnectionDefenseType]] **DoSConnectionDefenseType** __NUM__::
  2326. This is the type of defense applied to a detected client address for the
  2327. connection mitigation. The possible values are:
  2328. +
  2329. 1: No defense.
  2330. +
  2331. 2: Immediately close new connections.
  2332. +
  2333. "0" means use the consensus parameter. If not defined in the consensus, the value is 2.
  2334. (Default: 0)
  2335. [[DoSRefuseSingleHopClientRendezvous]] **DoSRefuseSingleHopClientRendezvous** **0**|**1**|**auto**::
  2336. Refuse establishment of rendezvous points for single hop clients. In other
  2337. words, if a client directly connects to the relay and sends an
  2338. ESTABLISH_RENDEZVOUS cell, it is silently dropped. "auto" means use the
  2339. consensus parameter. If not defined in the consensus, the value is 0.
  2340. (Default: auto)
  2341. DIRECTORY AUTHORITY SERVER OPTIONS
  2342. ----------------------------------
  2343. The following options enable operation as a directory authority, and
  2344. control how Tor behaves as a directory authority. You should not need
  2345. to adjust any of them if you're running a regular relay or exit server
  2346. on the public Tor network.
  2347. [[AuthoritativeDirectory]] **AuthoritativeDirectory** **0**|**1**::
  2348. When this option is set to 1, Tor operates as an authoritative directory
  2349. server. Instead of caching the directory, it generates its own list of
  2350. good servers, signs it, and sends that to the clients. Unless the clients
  2351. already have you listed as a trusted directory, you probably do not want
  2352. to set this option.
  2353. [[V3AuthoritativeDirectory]] **V3AuthoritativeDirectory** **0**|**1**::
  2354. When this option is set in addition to **AuthoritativeDirectory**, Tor
  2355. generates version 3 network statuses and serves descriptors, etc as
  2356. described in dir-spec.txt file of https://spec.torproject.org/[torspec]
  2357. (for Tor clients and servers running at least 0.2.0.x).
  2358. [[VersioningAuthoritativeDirectory]] **VersioningAuthoritativeDirectory** **0**|**1**::
  2359. When this option is set to 1, Tor adds information on which versions of
  2360. Tor are still believed safe for use to the published directory. Each
  2361. version 1 authority is automatically a versioning authority; version 2
  2362. authorities provide this service optionally. See **RecommendedVersions**,
  2363. **RecommendedClientVersions**, and **RecommendedServerVersions**.
  2364. [[RecommendedVersions]] **RecommendedVersions** __STRING__::
  2365. STRING is a comma-separated list of Tor versions currently believed to be
  2366. safe. The list is included in each directory, and nodes which pull down the
  2367. directory learn whether they need to upgrade. This option can appear
  2368. multiple times: the values from multiple lines are spliced together. When
  2369. this is set then **VersioningAuthoritativeDirectory** should be set too.
  2370. [[RecommendedPackages]] **RecommendedPackages** __PACKAGENAME__ __VERSION__ __URL__ __DIGESTTYPE__**=**__DIGEST__ ::
  2371. Adds "package" line to the directory authority's vote. This information
  2372. is used to vote on the correct URL and digest for the released versions
  2373. of different Tor-related packages, so that the consensus can certify
  2374. them. This line may appear any number of times.
  2375. [[RecommendedClientVersions]] **RecommendedClientVersions** __STRING__::
  2376. STRING is a comma-separated list of Tor versions currently believed to be
  2377. safe for clients to use. This information is included in version 2
  2378. directories. If this is not set then the value of **RecommendedVersions**
  2379. is used. When this is set then **VersioningAuthoritativeDirectory** should
  2380. be set too.
  2381. [[BridgeAuthoritativeDir]] **BridgeAuthoritativeDir** **0**|**1**::
  2382. When this option is set in addition to **AuthoritativeDirectory**, Tor
  2383. accepts and serves server descriptors, but it caches and serves the main
  2384. networkstatus documents rather than generating its own. (Default: 0)
  2385. [[MinUptimeHidServDirectoryV2]] **MinUptimeHidServDirectoryV2** __N__ **seconds**|**minutes**|**hours**|**days**|**weeks**::
  2386. Minimum uptime of a v2 hidden service directory to be accepted as such by
  2387. authoritative directories. (Default: 25 hours)
  2388. [[RecommendedServerVersions]] **RecommendedServerVersions** __STRING__::
  2389. STRING is a comma-separated list of Tor versions currently believed to be
  2390. safe for servers to use. This information is included in version 2
  2391. directories. If this is not set then the value of **RecommendedVersions**
  2392. is used. When this is set then **VersioningAuthoritativeDirectory** should
  2393. be set too.
  2394. [[ConsensusParams]] **ConsensusParams** __STRING__::
  2395. STRING is a space-separated list of key=value pairs that Tor will include
  2396. in the "params" line of its networkstatus vote.
  2397. [[DirAllowPrivateAddresses]] **DirAllowPrivateAddresses** **0**|**1**::
  2398. If set to 1, Tor will accept server descriptors with arbitrary "Address"
  2399. elements. Otherwise, if the address is not an IP address or is a private IP
  2400. address, it will reject the server descriptor. Additionally, Tor
  2401. will allow exit policies for private networks to fulfill Exit flag
  2402. requirements. (Default: 0)
  2403. [[AuthDirBadExit]] **AuthDirBadExit** __AddressPattern...__::
  2404. Authoritative directories only. A set of address patterns for servers that
  2405. will be listed as bad exits in any network status document this authority
  2406. publishes, if **AuthDirListBadExits** is set. +
  2407. +
  2408. (The address pattern syntax here and in the options below
  2409. is the same as for exit policies, except that you don't need to say
  2410. "accept" or "reject", and ports are not needed.)
  2411. [[AuthDirInvalid]] **AuthDirInvalid** __AddressPattern...__::
  2412. Authoritative directories only. A set of address patterns for servers that
  2413. will never be listed as "valid" in any network status document that this
  2414. authority publishes.
  2415. [[AuthDirReject]] **AuthDirReject** __AddressPattern__...::
  2416. Authoritative directories only. A set of address patterns for servers that
  2417. will never be listed at all in any network status document that this
  2418. authority publishes, or accepted as an OR address in any descriptor
  2419. submitted for publication by this authority.
  2420. [[AuthDirBadExitCCs]] **AuthDirBadExitCCs** __CC__,... +
  2421. [[AuthDirInvalidCCs]] **AuthDirInvalidCCs** __CC__,... +
  2422. [[AuthDirRejectCCs]] **AuthDirRejectCCs** __CC__,...::
  2423. Authoritative directories only. These options contain a comma-separated
  2424. list of country codes such that any server in one of those country codes
  2425. will be marked as a bad exit/invalid for use, or rejected
  2426. entirely.
  2427. [[AuthDirListBadExits]] **AuthDirListBadExits** **0**|**1**::
  2428. Authoritative directories only. If set to 1, this directory has some
  2429. opinion about which nodes are unsuitable as exit nodes. (Do not set this to
  2430. 1 unless you plan to list non-functioning exits as bad; otherwise, you are
  2431. effectively voting in favor of every declared exit as an exit.)
  2432. [[AuthDirMaxServersPerAddr]] **AuthDirMaxServersPerAddr** __NUM__::
  2433. Authoritative directories only. The maximum number of servers that we will
  2434. list as acceptable on a single IP address. Set this to "0" for "no limit".
  2435. (Default: 2)
  2436. [[AuthDirFastGuarantee]] **AuthDirFastGuarantee** __N__ **bytes**|**KBytes**|**MBytes**|**GBytes**|**TBytes**|**KBits**|**MBits**|**GBits**|**TBits**::
  2437. Authoritative directories only. If non-zero, always vote the
  2438. Fast flag for any relay advertising this amount of capacity or
  2439. more. (Default: 100 KBytes)
  2440. [[AuthDirGuardBWGuarantee]] **AuthDirGuardBWGuarantee** __N__ **bytes**|**KBytes**|**MBytes**|**GBytes**|**TBytes**|**KBits**|**MBits**|**GBits**|**TBits**::
  2441. Authoritative directories only. If non-zero, this advertised capacity
  2442. or more is always sufficient to satisfy the bandwidth requirement
  2443. for the Guard flag. (Default: 2 MBytes)
  2444. [[AuthDirPinKeys]] **AuthDirPinKeys** **0**|**1**::
  2445. Authoritative directories only. If non-zero, do not allow any relay to
  2446. publish a descriptor if any other relay has reserved its <Ed25519,RSA>
  2447. identity keypair. In all cases, Tor records every keypair it accepts
  2448. in a journal if it is new, or if it differs from the most recently
  2449. accepted pinning for one of the keys it contains. (Default: 1)
  2450. [[AuthDirSharedRandomness]] **AuthDirSharedRandomness** **0**|**1**::
  2451. Authoritative directories only. Switch for the shared random protocol.
  2452. If zero, the authority won't participate in the protocol. If non-zero
  2453. (default), the flag "shared-rand-participate" is added to the authority
  2454. vote indicating participation in the protocol. (Default: 1)
  2455. [[AuthDirTestEd25519LinkKeys]] **AuthDirTestEd25519LinkKeys** **0**|**1**::
  2456. Authoritative directories only. If this option is set to 0, then we treat
  2457. relays as "Running" if their RSA key is correct when we probe them,
  2458. regardless of their Ed25519 key. We should only ever set this option to 0
  2459. if there is some major bug in Ed25519 link authentication that causes us
  2460. to label all the relays as not Running. (Default: 1)
  2461. [[BridgePassword]] **BridgePassword** __Password__::
  2462. If set, contains an HTTP authenticator that tells a bridge authority to
  2463. serve all requested bridge information. Used by the (only partially
  2464. implemented) "bridge community" design, where a community of bridge
  2465. relay operators all use an alternate bridge directory authority,
  2466. and their target user audience can periodically fetch the list of
  2467. available community bridges to stay up-to-date. (Default: not set)
  2468. [[V3AuthVotingInterval]] **V3AuthVotingInterval** __N__ **minutes**|**hours**::
  2469. V3 authoritative directories only. Configures the server's preferred voting
  2470. interval. Note that voting will __actually__ happen at an interval chosen
  2471. by consensus from all the authorities' preferred intervals. This time
  2472. SHOULD divide evenly into a day. (Default: 1 hour)
  2473. [[V3AuthVoteDelay]] **V3AuthVoteDelay** __N__ **minutes**|**hours**::
  2474. V3 authoritative directories only. Configures the server's preferred delay
  2475. between publishing its vote and assuming it has all the votes from all the
  2476. other authorities. Note that the actual time used is not the server's
  2477. preferred time, but the consensus of all preferences. (Default: 5 minutes)
  2478. [[V3AuthDistDelay]] **V3AuthDistDelay** __N__ **minutes**|**hours**::
  2479. V3 authoritative directories only. Configures the server's preferred delay
  2480. between publishing its consensus and signature and assuming it has all the
  2481. signatures from all the other authorities. Note that the actual time used
  2482. is not the server's preferred time, but the consensus of all preferences.
  2483. (Default: 5 minutes)
  2484. [[V3AuthNIntervalsValid]] **V3AuthNIntervalsValid** __NUM__::
  2485. V3 authoritative directories only. Configures the number of VotingIntervals
  2486. for which each consensus should be valid for. Choosing high numbers
  2487. increases network partitioning risks; choosing low numbers increases
  2488. directory traffic. Note that the actual number of intervals used is not the
  2489. server's preferred number, but the consensus of all preferences. Must be at
  2490. least 2. (Default: 3)
  2491. [[V3BandwidthsFile]] **V3BandwidthsFile** __FILENAME__::
  2492. V3 authoritative directories only. Configures the location of the
  2493. bandwidth-authority generated file storing information on relays' measured
  2494. bandwidth capacities. To avoid inconsistent reads, bandwidth data should
  2495. be written to temporary file, then renamed to the configured filename.
  2496. (Default: unset)
  2497. [[V3AuthUseLegacyKey]] **V3AuthUseLegacyKey** **0**|**1**::
  2498. If set, the directory authority will sign consensuses not only with its
  2499. own signing key, but also with a "legacy" key and certificate with a
  2500. different identity. This feature is used to migrate directory authority
  2501. keys in the event of a compromise. (Default: 0)
  2502. [[AuthDirHasIPv6Connectivity]] **AuthDirHasIPv6Connectivity** **0**|**1**::
  2503. Authoritative directories only. When set to 0, OR ports with an
  2504. IPv6 address are not included in the authority's votes. When set to 1,
  2505. IPv6 OR ports are tested for reachability like IPv4 OR ports. If the
  2506. reachability test succeeds, the authority votes for the IPv6 ORPort, and
  2507. votes Running for the relay. If the reachability test fails, the authority
  2508. does not vote for the IPv6 ORPort, and does not vote Running (Default: 0) +
  2509. +
  2510. The content of the consensus depends on the number of voting authorities
  2511. that set AuthDirHasIPv6Connectivity:
  2512. If no authorities set AuthDirHasIPv6Connectivity 1, there will be no
  2513. IPv6 ORPorts in the consensus.
  2514. If a minority of authorities set AuthDirHasIPv6Connectivity 1,
  2515. unreachable IPv6 ORPorts will be removed from the consensus. But the
  2516. majority of IPv4-only authorities will still vote the relay as Running.
  2517. Reachable IPv6 ORPort lines will be included in the consensus
  2518. If a majority of voting authorities set AuthDirHasIPv6Connectivity 1,
  2519. relays with unreachable IPv6 ORPorts will not be listed as Running.
  2520. Reachable IPv6 ORPort lines will be included in the consensus
  2521. (To ensure that any valid majority will vote relays with unreachable
  2522. IPv6 ORPorts not Running, 75% of authorities must set
  2523. AuthDirHasIPv6Connectivity 1.)
  2524. [[MinMeasuredBWsForAuthToIgnoreAdvertised]] **MinMeasuredBWsForAuthToIgnoreAdvertised** __N__::
  2525. A total value, in abstract bandwidth units, describing how much
  2526. measured total bandwidth an authority should have observed on the network
  2527. before it will treat advertised bandwidths as wholly
  2528. unreliable. (Default: 500)
  2529. HIDDEN SERVICE OPTIONS
  2530. ----------------------
  2531. The following options are used to configure a hidden service.
  2532. [[HiddenServiceDir]] **HiddenServiceDir** __DIRECTORY__::
  2533. Store data files for a hidden service in DIRECTORY. Every hidden service
  2534. must have a separate directory. You may use this option multiple times to
  2535. specify multiple services. If DIRECTORY does not exist, Tor will create it.
  2536. Please note that you cannot add new Onion Service to already running Tor
  2537. instance if **Sandbox** is enabled.
  2538. (Note: in current versions of Tor, if DIRECTORY is a relative path,
  2539. it will be relative to the current
  2540. working directory of Tor instance, not to its DataDirectory. Do not
  2541. rely on this behavior; it is not guaranteed to remain the same in future
  2542. versions.)
  2543. [[HiddenServicePort]] **HiddenServicePort** __VIRTPORT__ [__TARGET__]::
  2544. Configure a virtual port VIRTPORT for a hidden service. You may use this
  2545. option multiple times; each time applies to the service using the most
  2546. recent HiddenServiceDir. By default, this option maps the virtual port to
  2547. the same port on 127.0.0.1 over TCP. You may override the target port,
  2548. address, or both by specifying a target of addr, port, addr:port, or
  2549. **unix:**__path__. (You can specify an IPv6 target as [addr]:port. Unix
  2550. paths may be quoted, and may use standard C escapes.)
  2551. You may also have multiple lines with the same VIRTPORT: when a user
  2552. connects to that VIRTPORT, one of the TARGETs from those lines will be
  2553. chosen at random. Note that address-port pairs have to be comma-separated.
  2554. [[PublishHidServDescriptors]] **PublishHidServDescriptors** **0**|**1**::
  2555. If set to 0, Tor will run any hidden services you configure, but it won't
  2556. advertise them to the rendezvous directory. This option is only useful if
  2557. you're using a Tor controller that handles hidserv publishing for you.
  2558. (Default: 1)
  2559. [[HiddenServiceVersion]] **HiddenServiceVersion** **2**|**3**::
  2560. A list of rendezvous service descriptor versions to publish for the hidden
  2561. service. Currently, versions 2 and 3 are supported. (Default: 3)
  2562. [[HiddenServiceAuthorizeClient]] **HiddenServiceAuthorizeClient** __auth-type__ __client-name__,__client-name__,__...__::
  2563. If configured, the hidden service is accessible for authorized clients
  2564. only. The auth-type can either be \'basic' for a general-purpose
  2565. authorization protocol or \'stealth' for a less scalable protocol that also
  2566. hides service activity from unauthorized clients. Only clients that are
  2567. listed here are authorized to access the hidden service. Valid client names
  2568. are 1 to 16 characters long and only use characters in A-Za-z0-9+-_ (no
  2569. spaces). If this option is set, the hidden service is not accessible for
  2570. clients without authorization any more. Generated authorization data can be
  2571. found in the hostname file. Clients need to put this authorization data in
  2572. their configuration file using **HidServAuth**. This option is only for v2
  2573. services; v3 services configure client authentication in a subdirectory of
  2574. HiddenServiceDir instead (see the **Client Authorization** section).
  2575. [[HiddenServiceAllowUnknownPorts]] **HiddenServiceAllowUnknownPorts** **0**|**1**::
  2576. If set to 1, then connections to unrecognized ports do not cause the
  2577. current hidden service to close rendezvous circuits. (Setting this to 0 is
  2578. not an authorization mechanism; it is instead meant to be a mild
  2579. inconvenience to port-scanners.) (Default: 0)
  2580. [[HiddenServiceExportCircuitID]] **HiddenServiceExportCircuitID** __protocol__::
  2581. The onion service will use the given protocol to expose the global circuit
  2582. identifier of each inbound client circuit via the selected protocol. The only
  2583. protocol supported right now \'haproxy'. This option is only for v3
  2584. services. (Default: none) +
  2585. +
  2586. The haproxy option works in the following way: when the feature is
  2587. enabled, the Tor process will write a header line when a client is connecting
  2588. to the onion service. The header will look like this: +
  2589. +
  2590. "PROXY TCP6 fc00:dead:beef:4dad::ffff:ffff ::1 65535 42\r\n" +
  2591. +
  2592. We encode the "global circuit identifier" as the last 32-bits of the first
  2593. IPv6 address. All other values in the header can safely be ignored. You can
  2594. compute the global circuit identifier using the following formula given the
  2595. IPv6 address "fc00:dead:beef:4dad::AABB:CCDD": +
  2596. +
  2597. global_circuit_id = (0xAA << 24) + (0xBB << 16) + (0xCC << 8) + 0xDD; +
  2598. +
  2599. In the case above, where the last 32-bit is 0xffffffff, the global circuit
  2600. identifier would be 4294967295. You can use this value together with Tor's
  2601. control port where it is possible to terminate a circuit given the global
  2602. circuit identifier. For more information about this see controls-spec.txt. +
  2603. +
  2604. The HAProxy version 1 proxy protocol is described in detail at
  2605. https://www.haproxy.org/download/1.8/doc/proxy-protocol.txt
  2606. [[HiddenServiceMaxStreams]] **HiddenServiceMaxStreams** __N__::
  2607. The maximum number of simultaneous streams (connections) per rendezvous
  2608. circuit. The maximum value allowed is 65535. (Setting this to 0 will allow
  2609. an unlimited number of simultaneous streams.) (Default: 0)
  2610. [[HiddenServiceMaxStreamsCloseCircuit]] **HiddenServiceMaxStreamsCloseCircuit** **0**|**1**::
  2611. If set to 1, then exceeding **HiddenServiceMaxStreams** will cause the
  2612. offending rendezvous circuit to be torn down, as opposed to stream creation
  2613. requests that exceed the limit being silently ignored. (Default: 0)
  2614. [[RendPostPeriod]] **RendPostPeriod** __N__ **seconds**|**minutes**|**hours**|**days**|**weeks**::
  2615. Every time the specified period elapses, Tor uploads any rendezvous
  2616. service descriptors to the directory servers. This information is also
  2617. uploaded whenever it changes. Minimum value allowed is 10 minutes and
  2618. maximum is 3.5 days. This option is only for v2 services.
  2619. (Default: 1 hour)
  2620. [[HiddenServiceDirGroupReadable]] **HiddenServiceDirGroupReadable** **0**|**1**::
  2621. If this option is set to 1, allow the filesystem group to read the
  2622. hidden service directory and hostname file. If the option is set to 0,
  2623. only owner is able to read the hidden service directory. (Default: 0)
  2624. Has no effect on Windows.
  2625. [[HiddenServiceNumIntroductionPoints]] **HiddenServiceNumIntroductionPoints** __NUM__::
  2626. Number of introduction points the hidden service will have. You can't
  2627. have more than 10 for v2 service and 20 for v3. (Default: 3)
  2628. [[HiddenServiceSingleHopMode]] **HiddenServiceSingleHopMode** **0**|**1**::
  2629. **Experimental - Non Anonymous** Hidden Services on a tor instance in
  2630. HiddenServiceSingleHopMode make one-hop (direct) circuits between the onion
  2631. service server, and the introduction and rendezvous points. (Onion service
  2632. descriptors are still posted using 3-hop paths, to avoid onion service
  2633. directories blocking the service.)
  2634. This option makes every hidden service instance hosted by a tor instance a
  2635. Single Onion Service. One-hop circuits make Single Onion servers easily
  2636. locatable, but clients remain location-anonymous. However, the fact that a
  2637. client is accessing a Single Onion rather than a Hidden Service may be
  2638. statistically distinguishable. +
  2639. +
  2640. **WARNING:** Once a hidden service directory has been used by a tor
  2641. instance in HiddenServiceSingleHopMode, it can **NEVER** be used again for
  2642. a hidden service. It is best practice to create a new hidden service
  2643. directory, key, and address for each new Single Onion Service and Hidden
  2644. Service. It is not possible to run Single Onion Services and Hidden
  2645. Services from the same tor instance: they should be run on different
  2646. servers with different IP addresses. +
  2647. +
  2648. HiddenServiceSingleHopMode requires HiddenServiceNonAnonymousMode to be set
  2649. to 1. Since a Single Onion service is non-anonymous, you can not configure
  2650. a SOCKSPort on a tor instance that is running in
  2651. **HiddenServiceSingleHopMode**. Can not be changed while tor is running.
  2652. (Default: 0)
  2653. [[HiddenServiceNonAnonymousMode]] **HiddenServiceNonAnonymousMode** **0**|**1**::
  2654. Makes hidden services non-anonymous on this tor instance. Allows the
  2655. non-anonymous HiddenServiceSingleHopMode. Enables direct connections in the
  2656. server-side hidden service protocol. If you are using this option,
  2657. you need to disable all client-side services on your Tor instance,
  2658. including setting SOCKSPort to "0". Can not be changed while tor is
  2659. running. (Default: 0)
  2660. Client Authorization
  2661. --------------------
  2662. (Version 3 only)
  2663. To configure client authorization on the service side, the
  2664. "<HiddenServiceDir>/authorized_clients/" directory needs to exist. Each file
  2665. in that directory should be suffixed with ".auth" (i.e. "alice.auth"; the
  2666. file name is irrelevant) and its content format MUST be:
  2667. <auth-type>:<key-type>:<base32-encoded-public-key>
  2668. The supported <auth-type> are: "descriptor". The supported <key-type> are:
  2669. "x25519". The <base32-encoded-public-key> is the base32 representation of
  2670. the raw key bytes only (32 bytes for x25519).
  2671. Each file MUST contain one line only. Any malformed file will be
  2672. ignored. Client authorization will only be enabled for the service if tor
  2673. successfully loads at least one authorization file.
  2674. Note that once you've configured client authorization, anyone else with the
  2675. address won't be able to access it from this point on. If no authorization is
  2676. configured, the service will be accessible to anyone with the onion address.
  2677. Revoking a client can be done by removing their ".auth" file, however the
  2678. revocation will be in effect only after the tor process gets restarted even if
  2679. a SIGHUP takes place.
  2680. See the Appendix G in the rend-spec-v3.txt file of
  2681. https://spec.torproject.org/[torspec] for more information.
  2682. TESTING NETWORK OPTIONS
  2683. -----------------------
  2684. The following options are used for running a testing Tor network.
  2685. [[TestingTorNetwork]] **TestingTorNetwork** **0**|**1**::
  2686. If set to 1, Tor adjusts default values of the configuration options below,
  2687. so that it is easier to set up a testing Tor network. May only be set if
  2688. non-default set of DirAuthorities is set. Cannot be unset while Tor is
  2689. running.
  2690. (Default: 0) +
  2691. ServerDNSAllowBrokenConfig 1
  2692. DirAllowPrivateAddresses 1
  2693. EnforceDistinctSubnets 0
  2694. AssumeReachable 1
  2695. AuthDirMaxServersPerAddr 0
  2696. AuthDirMaxServersPerAuthAddr 0
  2697. ClientBootstrapConsensusAuthorityDownloadInitialDelay 0
  2698. ClientBootstrapConsensusFallbackDownloadInitialDelay 0
  2699. ClientBootstrapConsensusAuthorityOnlyDownloadInitialDelay 0
  2700. ClientDNSRejectInternalAddresses 0
  2701. ClientRejectInternalAddresses 0
  2702. CountPrivateBandwidth 1
  2703. ExitPolicyRejectPrivate 0
  2704. ExtendAllowPrivateAddresses 1
  2705. V3AuthVotingInterval 5 minutes
  2706. V3AuthVoteDelay 20 seconds
  2707. V3AuthDistDelay 20 seconds
  2708. MinUptimeHidServDirectoryV2 0 seconds
  2709. TestingV3AuthInitialVotingInterval 5 minutes
  2710. TestingV3AuthInitialVoteDelay 20 seconds
  2711. TestingV3AuthInitialDistDelay 20 seconds
  2712. TestingAuthDirTimeToLearnReachability 0 minutes
  2713. TestingEstimatedDescriptorPropagationTime 0 minutes
  2714. TestingServerDownloadInitialDelay 0
  2715. TestingClientDownloadInitialDelay 0
  2716. TestingServerConsensusDownloadInitialDelay 0
  2717. TestingClientConsensusDownloadInitialDelay 0
  2718. TestingBridgeDownloadInitialDelay 10
  2719. TestingBridgeBootstrapDownloadInitialDelay 0
  2720. TestingClientMaxIntervalWithoutRequest 5 seconds
  2721. TestingDirConnectionMaxStall 30 seconds
  2722. TestingEnableConnBwEvent 1
  2723. TestingEnableCellStatsEvent 1
  2724. [[TestingV3AuthInitialVotingInterval]] **TestingV3AuthInitialVotingInterval** __N__ **minutes**|**hours**::
  2725. Like V3AuthVotingInterval, but for initial voting interval before the first
  2726. consensus has been created. Changing this requires that
  2727. **TestingTorNetwork** is set. (Default: 30 minutes)
  2728. [[TestingV3AuthInitialVoteDelay]] **TestingV3AuthInitialVoteDelay** __N__ **minutes**|**hours**::
  2729. Like V3AuthVoteDelay, but for initial voting interval before
  2730. the first consensus has been created. Changing this requires that
  2731. **TestingTorNetwork** is set. (Default: 5 minutes)
  2732. [[TestingV3AuthInitialDistDelay]] **TestingV3AuthInitialDistDelay** __N__ **minutes**|**hours**::
  2733. Like V3AuthDistDelay, but for initial voting interval before
  2734. the first consensus has been created. Changing this requires that
  2735. **TestingTorNetwork** is set. (Default: 5 minutes)
  2736. [[TestingV3AuthVotingStartOffset]] **TestingV3AuthVotingStartOffset** __N__ **seconds**|**minutes**|**hours**::
  2737. Directory authorities offset voting start time by this much.
  2738. Changing this requires that **TestingTorNetwork** is set. (Default: 0)
  2739. [[TestingAuthDirTimeToLearnReachability]] **TestingAuthDirTimeToLearnReachability** __N__ **minutes**|**hours**::
  2740. After starting as an authority, do not make claims about whether routers
  2741. are Running until this much time has passed. Changing this requires
  2742. that **TestingTorNetwork** is set. (Default: 30 minutes)
  2743. [[TestingEstimatedDescriptorPropagationTime]] **TestingEstimatedDescriptorPropagationTime** __N__ **minutes**|**hours**::
  2744. Clients try downloading server descriptors from directory caches after this
  2745. time. Changing this requires that **TestingTorNetwork** is set. (Default:
  2746. 10 minutes)
  2747. [[TestingMinFastFlagThreshold]] **TestingMinFastFlagThreshold** __N__ **bytes**|**KBytes**|**MBytes**|**GBytes**|**TBytes**|**KBits**|**MBits**|**GBits**|**TBits**::
  2748. Minimum value for the Fast flag. Overrides the ordinary minimum taken
  2749. from the consensus when TestingTorNetwork is set. (Default: 0.)
  2750. [[TestingServerDownloadInitialDelay]] **TestingServerDownloadInitialDelay** __N__::
  2751. Initial delay in seconds for when servers should download things in general. Changing this
  2752. requires that **TestingTorNetwork** is set. (Default: 0)
  2753. [[TestingClientDownloadInitialDelay]] **TestingClientDownloadInitialDelay** __N__::
  2754. Initial delay in seconds for when clients should download things in general. Changing this
  2755. requires that **TestingTorNetwork** is set. (Default: 0)
  2756. [[TestingServerConsensusDownloadInitialDelay]] **TestingServerConsensusDownloadInitialDelay** __N__::
  2757. Initial delay in seconds for when servers should download consensuses. Changing this
  2758. requires that **TestingTorNetwork** is set. (Default: 0)
  2759. [[TestingClientConsensusDownloadInitialDelay]] **TestingClientConsensusDownloadInitialDelay** __N__::
  2760. Initial delay in seconds for when clients should download consensuses. Changing this
  2761. requires that **TestingTorNetwork** is set. (Default: 0)
  2762. [[TestingBridgeDownloadInitialDelay]] **TestingBridgeDownloadInitialDelay** __N__::
  2763. Initial delay in seconds for when clients should download each bridge descriptor when they
  2764. know that one or more of their configured bridges are running. Changing
  2765. this requires that **TestingTorNetwork** is set. (Default: 10800)
  2766. [[TestingBridgeBootstrapDownloadInitialDelay]] **TestingBridgeBootstrapDownloadInitialDelay** __N__::
  2767. Initial delay in seconds for when clients should download each bridge descriptor when they
  2768. have just started, or when they can not contact any of their bridges.
  2769. Changing this requires that **TestingTorNetwork** is set. (Default: 0)
  2770. [[TestingClientMaxIntervalWithoutRequest]] **TestingClientMaxIntervalWithoutRequest** __N__ **seconds**|**minutes**::
  2771. When directory clients have only a few descriptors to request, they batch
  2772. them until they have more, or until this amount of time has passed.
  2773. Changing this requires that **TestingTorNetwork** is set. (Default: 10
  2774. minutes)
  2775. [[TestingDirConnectionMaxStall]] **TestingDirConnectionMaxStall** __N__ **seconds**|**minutes**::
  2776. Let a directory connection stall this long before expiring it.
  2777. Changing this requires that **TestingTorNetwork** is set. (Default:
  2778. 5 minutes)
  2779. [[TestingDirAuthVoteExit]] **TestingDirAuthVoteExit** __node__,__node__,__...__::
  2780. A list of identity fingerprints, country codes, and
  2781. address patterns of nodes to vote Exit for regardless of their
  2782. uptime, bandwidth, or exit policy. See the **ExcludeNodes**
  2783. option for more information on how to specify nodes. +
  2784. +
  2785. In order for this option to have any effect, **TestingTorNetwork**
  2786. has to be set. See the **ExcludeNodes** option for more
  2787. information on how to specify nodes.
  2788. [[TestingDirAuthVoteExitIsStrict]] **TestingDirAuthVoteExitIsStrict** **0**|**1** ::
  2789. If True (1), a node will never receive the Exit flag unless it is specified
  2790. in the **TestingDirAuthVoteExit** list, regardless of its uptime, bandwidth,
  2791. or exit policy. +
  2792. +
  2793. In order for this option to have any effect, **TestingTorNetwork**
  2794. has to be set.
  2795. [[TestingDirAuthVoteGuard]] **TestingDirAuthVoteGuard** __node__,__node__,__...__::
  2796. A list of identity fingerprints and country codes and
  2797. address patterns of nodes to vote Guard for regardless of their
  2798. uptime and bandwidth. See the **ExcludeNodes** option for more
  2799. information on how to specify nodes. +
  2800. +
  2801. In order for this option to have any effect, **TestingTorNetwork**
  2802. has to be set.
  2803. [[TestingDirAuthVoteGuardIsStrict]] **TestingDirAuthVoteGuardIsStrict** **0**|**1** ::
  2804. If True (1), a node will never receive the Guard flag unless it is specified
  2805. in the **TestingDirAuthVoteGuard** list, regardless of its uptime and bandwidth. +
  2806. +
  2807. In order for this option to have any effect, **TestingTorNetwork**
  2808. has to be set.
  2809. [[TestingDirAuthVoteHSDir]] **TestingDirAuthVoteHSDir** __node__,__node__,__...__::
  2810. A list of identity fingerprints and country codes and
  2811. address patterns of nodes to vote HSDir for regardless of their
  2812. uptime and DirPort. See the **ExcludeNodes** option for more
  2813. information on how to specify nodes. +
  2814. +
  2815. In order for this option to have any effect, **TestingTorNetwork**
  2816. must be set.
  2817. [[TestingDirAuthVoteHSDirIsStrict]] **TestingDirAuthVoteHSDirIsStrict** **0**|**1** ::
  2818. If True (1), a node will never receive the HSDir flag unless it is specified
  2819. in the **TestingDirAuthVoteHSDir** list, regardless of its uptime and DirPort. +
  2820. +
  2821. In order for this option to have any effect, **TestingTorNetwork**
  2822. has to be set.
  2823. [[TestingEnableConnBwEvent]] **TestingEnableConnBwEvent** **0**|**1**::
  2824. If this option is set, then Tor controllers may register for CONN_BW
  2825. events. Changing this requires that **TestingTorNetwork** is set.
  2826. (Default: 0)
  2827. [[TestingEnableCellStatsEvent]] **TestingEnableCellStatsEvent** **0**|**1**::
  2828. If this option is set, then Tor controllers may register for CELL_STATS
  2829. events. Changing this requires that **TestingTorNetwork** is set.
  2830. (Default: 0)
  2831. [[TestingMinExitFlagThreshold]] **TestingMinExitFlagThreshold** __N__ **KBytes**|**MBytes**|**GBytes**|**TBytes**|**KBits**|**MBits**|**GBits**|**TBits**::
  2832. Sets a lower-bound for assigning an exit flag when running as an
  2833. authority on a testing network. Overrides the usual default lower bound
  2834. of 4 KB. (Default: 0)
  2835. [[TestingLinkCertLifetime]] **TestingLinkCertLifetime** __N__ **seconds**|**minutes**|**hours**|**days**|**weeks**|**months**::
  2836. Overrides the default lifetime for the certificates used to authenticate
  2837. our X509 link cert with our ed25519 signing key.
  2838. (Default: 2 days)
  2839. [[TestingAuthKeyLifetime]] **TestingAuthKeyLifetime** __N__ **seconds**|**minutes**|**hours**|**days**|**weeks**|**months**::
  2840. Overrides the default lifetime for a signing Ed25519 TLS Link authentication
  2841. key.
  2842. (Default: 2 days)
  2843. [[TestingLinkKeySlop]] **TestingLinkKeySlop** __N__ **seconds**|**minutes**|**hours** +
  2844. [[TestingAuthKeySlop]] **TestingAuthKeySlop** __N__ **seconds**|**minutes**|**hours** +
  2845. [[TestingSigningKeySlop]] **TestingSigningKeySlop** __N__ **seconds**|**minutes**|**hours**::
  2846. How early before the official expiration of a an Ed25519 signing key do
  2847. we replace it and issue a new key?
  2848. (Default: 3 hours for link and auth; 1 day for signing.)
  2849. NON-PERSISTENT OPTIONS
  2850. ----------------------
  2851. These options are not saved to the torrc file by the "SAVECONF" controller
  2852. command. Other options of this type are documented in control-spec.txt,
  2853. section 5.4. End-users should mostly ignore them.
  2854. [[UnderscorePorts]] **\_\_ControlPort**, **\_\_DirPort**, **\_\_DNSPort**, **\_\_ExtORPort**, **\_\_NATDPort**, **\_\_ORPort**, **\_\_SocksPort**, **\_\_TransPort**::
  2855. These underscore-prefixed options are variants of the regular Port
  2856. options. They behave the same, except they are not saved to the
  2857. torrc file by the controller's SAVECONF command.
  2858. SIGNALS
  2859. -------
  2860. Tor catches the following signals:
  2861. [[SIGTERM]] **SIGTERM**::
  2862. Tor will catch this, clean up and sync to disk if necessary, and exit.
  2863. [[SIGINT]] **SIGINT**::
  2864. Tor clients behave as with SIGTERM; but Tor servers will do a controlled
  2865. slow shutdown, closing listeners and waiting 30 seconds before exiting.
  2866. (The delay can be configured with the ShutdownWaitLength config option.)
  2867. [[SIGHUP]] **SIGHUP**::
  2868. The signal instructs Tor to reload its configuration (including closing and
  2869. reopening logs), and kill and restart its helper processes if applicable.
  2870. [[SIGUSR1]] **SIGUSR1**::
  2871. Log statistics about current connections, past connections, and throughput.
  2872. [[SIGUSR2]] **SIGUSR2**::
  2873. Switch all logs to loglevel debug. You can go back to the old loglevels by
  2874. sending a SIGHUP.
  2875. [[SIGCHLD]] **SIGCHLD**::
  2876. Tor receives this signal when one of its helper processes has exited, so it
  2877. can clean up.
  2878. [[SIGPIPE]] **SIGPIPE**::
  2879. Tor catches this signal and ignores it.
  2880. [[SIGXFSZ]] **SIGXFSZ**::
  2881. If this signal exists on your platform, Tor catches and ignores it.
  2882. FILES
  2883. -----
  2884. **@CONFDIR@/torrc**::
  2885. The configuration file, which contains "option value" pairs.
  2886. **$HOME/.torrc**::
  2887. Fallback location for torrc, if @CONFDIR@/torrc is not found.
  2888. **@LOCALSTATEDIR@/lib/tor/**::
  2889. The tor process stores keys and other data here.
  2890. __CacheDirectory__**/cached-certs**::
  2891. This file holds downloaded directory key certificates that are used to
  2892. verify authenticity of documents generated by Tor directory authorities.
  2893. __CacheDirectory__**/cached-consensus** and/or **cached-microdesc-consensus**::
  2894. The most recent consensus network status document we've downloaded.
  2895. __CacheDirectory__**/cached-descriptors** and **cached-descriptors.new**::
  2896. These files hold downloaded router statuses. Some routers may appear more
  2897. than once; if so, the most recently published descriptor is used. Lines
  2898. beginning with @-signs are annotations that contain more information about
  2899. a given router. The ".new" file is an append-only journal; when it gets
  2900. too large, all entries are merged into a new cached-descriptors file.
  2901. __CacheDirectory__**/cached-extrainfo** and **cached-extrainfo.new**::
  2902. As "cached-descriptors", but holds optionally-downloaded "extra-info"
  2903. documents. Relays use these documents to send inessential information
  2904. about statistics, bandwidth history, and network health to the
  2905. authorities. They aren't fetched by default; see the DownloadExtraInfo
  2906. option for more info.
  2907. __CacheDirectory__**/cached-microdescs** and **cached-microdescs.new**::
  2908. These files hold downloaded microdescriptors. Lines beginning with
  2909. @-signs are annotations that contain more information about a given
  2910. router. The ".new" file is an append-only journal; when it gets too
  2911. large, all entries are merged into a new cached-microdescs file.
  2912. __DataDirectory__**/state**::
  2913. A set of persistent key-value mappings. These are documented in
  2914. the file. These include:
  2915. - The current entry guards and their status.
  2916. - The current bandwidth accounting values.
  2917. - When the file was last written
  2918. - What version of Tor generated the state file
  2919. - A short history of bandwidth usage, as produced in the server
  2920. descriptors.
  2921. __DataDirectory__**/sr-state**::
  2922. Authority only. State file used to record information about the current
  2923. status of the shared-random-value voting state.
  2924. __CacheDirectory__**/diff-cache**::
  2925. Directory cache only. Holds older consensuses, and diffs from older
  2926. consensuses to the most recent consensus of each type, compressed
  2927. in various ways. Each file contains a set of key-value arguments
  2928. describing its contents, followed by a single NUL byte, followed by the
  2929. main file contents.
  2930. __DataDirectory__**/bw_accounting**::
  2931. Used to track bandwidth accounting values (when the current period starts
  2932. and ends; how much has been read and written so far this period). This file
  2933. is obsolete, and the data is now stored in the \'state' file instead.
  2934. __DataDirectory__**/control_auth_cookie**::
  2935. Used for cookie authentication with the controller. Location can be
  2936. overridden by the CookieAuthFile config option. Regenerated on startup. See
  2937. control-spec.txt in https://spec.torproject.org/[torspec] for details.
  2938. Only used when cookie authentication is enabled.
  2939. __DataDirectory__**/lock**::
  2940. This file is used to prevent two Tor instances from using same data
  2941. directory. If access to this file is locked, data directory is already
  2942. in use by Tor.
  2943. __DataDirectory__**/key-pinning-journal**::
  2944. Used by authorities. A line-based file that records mappings between
  2945. RSA1024 identity keys and Ed25519 identity keys. Authorities enforce
  2946. these mappings, so that once a relay has picked an Ed25519 key, stealing
  2947. or factoring the RSA1024 key will no longer let an attacker impersonate
  2948. the relay.
  2949. __KeyDirectory__**/authority_identity_key**::
  2950. A v3 directory authority's master identity key, used to authenticate its
  2951. signing key. Tor doesn't use this while it's running. The tor-gencert
  2952. program uses this. If you're running an authority, you should keep this
  2953. key offline, and not actually put it here.
  2954. __KeyDirectory__**/authority_certificate**::
  2955. A v3 directory authority's certificate, which authenticates the authority's
  2956. current vote- and consensus-signing key using its master identity key.
  2957. Only directory authorities use this file.
  2958. __KeyDirectory__**/authority_signing_key**::
  2959. A v3 directory authority's signing key, used to sign votes and consensuses.
  2960. Only directory authorities use this file. Corresponds to the
  2961. **authority_certificate** cert.
  2962. __KeyDirectory__**/legacy_certificate**::
  2963. As authority_certificate: used only when V3AuthUseLegacyKey is set.
  2964. See documentation for V3AuthUseLegacyKey.
  2965. __KeyDirectory__**/legacy_signing_key**::
  2966. As authority_signing_key: used only when V3AuthUseLegacyKey is set.
  2967. See documentation for V3AuthUseLegacyKey.
  2968. __KeyDirectory__**/secret_id_key**::
  2969. A relay's RSA1024 permanent identity key, including private and public
  2970. components. Used to sign router descriptors, and to sign other keys.
  2971. __KeyDirectory__**/ed25519_master_id_public_key**::
  2972. The public part of a relay's Ed25519 permanent identity key.
  2973. __KeyDirectory__**/ed25519_master_id_secret_key**::
  2974. The private part of a relay's Ed25519 permanent identity key. This key
  2975. is used to sign the medium-term ed25519 signing key. This file can be
  2976. kept offline, or kept encrypted. If so, Tor will not be able to generate
  2977. new signing keys itself; you'll need to use tor --keygen yourself to do
  2978. so.
  2979. __KeyDirectory__**/ed25519_signing_secret_key**::
  2980. The private and public components of a relay's medium-term Ed25519 signing
  2981. key. This key is authenticated by the Ed25519 master key, in turn
  2982. authenticates other keys (and router descriptors).
  2983. __KeyDirectory__**/ed25519_signing_cert**::
  2984. The certificate which authenticates "ed25519_signing_secret_key" as
  2985. having been signed by the Ed25519 master key.
  2986. __KeyDirectory__**/secret_onion_key** and **secret_onion_key.old**::
  2987. A relay's RSA1024 short-term onion key. Used to decrypt old-style ("TAP")
  2988. circuit extension requests. The ".old" file holds the previously
  2989. generated key, which the relay uses to handle any requests that were
  2990. made by clients that didn't have the new one.
  2991. __KeyDirectory__**/secret_onion_key_ntor** and **secret_onion_key_ntor.old**::
  2992. A relay's Curve25519 short-term onion key. Used to handle modern ("ntor")
  2993. circuit extension requests. The ".old" file holds the previously
  2994. generated key, which the relay uses to handle any requests that were
  2995. made by clients that didn't have the new one.
  2996. __DataDirectory__**/fingerprint**::
  2997. Only used by servers. Holds the fingerprint of the server's identity key.
  2998. __DataDirectory__**/hashed-fingerprint**::
  2999. Only used by bridges. Holds the hashed fingerprint of the bridge's
  3000. identity key. (That is, the hash of the hash of the identity key.)
  3001. __DataDirectory__**/approved-routers**::
  3002. Only used by authoritative directory servers. This file lists
  3003. the status of routers by their identity fingerprint.
  3004. Each line lists a status and a fingerprint separated by
  3005. whitespace. See your **fingerprint** file in the __DataDirectory__ for an
  3006. example line. If the status is **!reject** then descriptors from the
  3007. given identity (fingerprint) are rejected by this server. If it is
  3008. **!invalid** then descriptors are accepted but marked in the directory as
  3009. not valid, that is, not recommended.
  3010. __DataDirectory__**/v3-status-votes**::
  3011. Only for v3 authoritative directory servers. This file contains
  3012. status votes from all the authoritative directory servers.
  3013. __CacheDirectory__**/unverified-consensus**::
  3014. This file contains a network consensus document that has been downloaded,
  3015. but which we didn't have the right certificates to check yet.
  3016. __CacheDirectory__**/unverified-microdesc-consensus**::
  3017. This file contains a microdescriptor-flavored network consensus document
  3018. that has been downloaded, but which we didn't have the right certificates
  3019. to check yet.
  3020. __DataDirectory__**/unparseable-desc**::
  3021. Onion server descriptors that Tor was unable to parse are dumped to this
  3022. file. Only used for debugging.
  3023. __DataDirectory__**/router-stability**::
  3024. Only used by authoritative directory servers. Tracks measurements for
  3025. router mean-time-between-failures so that authorities have a good idea of
  3026. how to set their Stable flags.
  3027. __DataDirectory__**/stats/dirreq-stats**::
  3028. Only used by directory caches and authorities. This file is used to
  3029. collect directory request statistics.
  3030. __DataDirectory__**/stats/entry-stats**::
  3031. Only used by servers. This file is used to collect incoming connection
  3032. statistics by Tor entry nodes.
  3033. __DataDirectory__**/stats/bridge-stats**::
  3034. Only used by servers. This file is used to collect incoming connection
  3035. statistics by Tor bridges.
  3036. __DataDirectory__**/stats/exit-stats**::
  3037. Only used by servers. This file is used to collect outgoing connection
  3038. statistics by Tor exit routers.
  3039. __DataDirectory__**/stats/buffer-stats**::
  3040. Only used by servers. This file is used to collect buffer usage
  3041. history.
  3042. __DataDirectory__**/stats/conn-stats**::
  3043. Only used by servers. This file is used to collect approximate connection
  3044. history (number of active connections over time).
  3045. __DataDirectory__**/stats/hidserv-stats**::
  3046. Only used by servers. This file is used to collect approximate counts
  3047. of what fraction of the traffic is hidden service rendezvous traffic, and
  3048. approximately how many hidden services the relay has seen.
  3049. __DataDirectory__**/networkstatus-bridges**::
  3050. Only used by authoritative bridge directories. Contains information
  3051. about bridges that have self-reported themselves to the bridge
  3052. authority.
  3053. __DataDirectory__**/approved-routers**::
  3054. Authorities only. This file is used to configure which relays are
  3055. known to be valid, invalid, and so forth.
  3056. __HiddenServiceDirectory__**/hostname**::
  3057. The <base32-encoded-fingerprint>.onion domain name for this hidden service.
  3058. If the hidden service is restricted to authorized clients only, this file
  3059. also contains authorization data for all clients.
  3060. +
  3061. Note that clients will ignore any extra subdomains prepended to a hidden
  3062. service hostname. So if you have "xyz.onion" as your hostname, you
  3063. can tell clients to connect to "www.xyz.onion" or "irc.xyz.onion"
  3064. for virtual-hosting purposes.
  3065. __HiddenServiceDirectory__**/private_key**::
  3066. The private key for this hidden service.
  3067. __HiddenServiceDirectory__**/client_keys**::
  3068. Authorization data for a hidden service that is only accessible by
  3069. authorized clients.
  3070. __HiddenServiceDirectory__**/onion_service_non_anonymous**::
  3071. This file is present if a hidden service key was created in
  3072. **HiddenServiceNonAnonymousMode**.
  3073. SEE ALSO
  3074. --------
  3075. **torsocks**(1), **torify**(1) +
  3076. **https://www.torproject.org/**
  3077. **torspec: https://spec.torproject.org **
  3078. BUGS
  3079. ----
  3080. Plenty, probably. Tor is still in development. Please report them at https://trac.torproject.org/.
  3081. AUTHORS
  3082. -------
  3083. Roger Dingledine [arma at mit.edu], Nick Mathewson [nickm at alum.mit.edu].