tor.1.txt 186 KB

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