tor.1.txt 84 KB

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