tor.1.txt 67 KB

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