tor.1.in 37 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251252253254255256257258259260261262263264265266267268269270271272273274275276277278279280281282283284285286287288289290291292293294295296297298299300301302303304305306307308309310311312313314315316317318319320321322323324325326327328329330331332333334335336337338339340341342343344345346347348349350351352353354355356357358359360361362363364365366367368369370371372373374375376377378379380381382383384385386387388389390391392393394395396397398399400401402403404405406407408409410411412413414415416417418419420421422423424425426427428429430431432433434435436437438439440441442443444445446447448449450451452453454455456457458459460461462463464465466467468469470471472473474475476477478479480481482483484485486487488489490491492493494495496497498499500501502503504505506507508509510511512513514515516517518519520521522523524525526527528529530531532533534535536537538539540541542543544545546547548549550551552553554555556557558559560561562563564565566567568569570571572573574575576577578579580581582583584585586587588589590591592593594595596597598599600601602603604605606607608609610611612613614615616617618619620621622623624625626627628629630631632633634635636637638639640641642643644645646647648649650651652653654655656657658659660661662663664665666667668669670671672673674675676677678679680681682683684685686687688689690691692693694695696697698699700701702703704705706707708709710711712713714715716717718719720721722723724725726727728729730731732733734735736737738739740741742743744745746747748749750751752753754755756757758759760761762763764765766767768769770771772773774775776777778779780781782783784785786787788789790791792793794795796797798799800801802803804805806807808809810811812813814815816817818819820821822823824825826827828829830831832833834835836837838839840841842843844845846847848849850851852853854855856857858859860861862863864865866867868869870871872873874875876877878879880881882883884885886887888889890891892893894895896897898899900901902903904905906907908909910911912913914915916917918919920921922923924925926
  1. .TH TOR 1 "January 2006" "TOR"
  2. .SH NAME
  3. tor \- The second-generation onion router
  4. .SH SYNOPSIS
  5. .B tor
  6. [\fIOPTION value\fR]...
  7. .SH DESCRIPTION
  8. .I tor
  9. is a connection-oriented anonymizing communication
  10. service. Users choose a source-routed path through a set of nodes, and
  11. negotiate a "virtual circuit" through the network, in which each node
  12. knows its predecessor and successor, but no others. Traffic flowing down
  13. the circuit is unwrapped by a symmetric key at each node, which reveals
  14. the downstream node.
  15. .PP
  16. Basically \fItor\fR provides a distributed network of servers ("onion
  17. routers"). Users bounce their TCP streams -- web traffic, ftp, ssh, etc --
  18. around the routers, and recipients, observers, and even the routers
  19. themselves have difficulty tracking the source of the stream.
  20. .SH OPTIONS
  21. \fB-h, -help\fP
  22. Display a short help message and exit.
  23. .LP
  24. .TP
  25. \fB-f \fR\fIFILE\fP
  26. FILE contains further "option value" pairs. (Default: @CONFDIR@/torrc)
  27. .LP
  28. .TP
  29. Other options can be specified either on the command-line (\fI--option
  30. value\fR), or in the configuration file (\fIoption value\fR).
  31. Options are case-insensitive.
  32. .LP
  33. .TP
  34. \fBBandwidthRate \fR\fIN\fR \fBbytes\fR|\fBKB\fR|\fBMB\fR|\fBGB\fR|\fBTB\fP
  35. A token bucket limits the average incoming bandwidth on this node to
  36. the specified number of bytes per second. (Default: 3 MB)
  37. .LP
  38. .TP
  39. \fBBandwidthBurst \fR\fIN\fR \fBbytes\fR|\fBKB\fR|\fBMB\fR|\fBGB\fR|\fBTB\fP
  40. Limit the maximum token bucket size (also known as the burst) to the
  41. given number of bytes. (Default: 6 MB)
  42. .LP
  43. .TP
  44. \fBMaxAdvertisedBandwidth \fR\fIN\fR \fBbytes\fR|\fBKB\fR|\fBMB\fR|\fBGB\fR|\fBTB\fP
  45. If set, we will not advertise more than this amount of bandwidth for our
  46. BandwidthRate. Server operators who want to reduce the number of clients
  47. who ask to build circuits through them (since this is proportional to
  48. advertised bandwidth rate) can thus reduce the CPU demands on their
  49. server without impacting network performance.
  50. .LP
  51. .TP
  52. \fBConnLimit \fR\fINUM\fP
  53. The minimum number of file descriptors that must be available to
  54. the Tor process before it will start. Tor will ask the OS for as
  55. many file descriptors as the OS will allow (you can find this
  56. by "ulimit -H -n"). If this number is less than ConnLimit, then
  57. Tor will refuse to start.
  58. You probably don't need to adjust this. It has no effect on
  59. Windows since that platform lacks getrlimit(). (Default: 1000)
  60. .LP
  61. .TP
  62. \fBControlPort \fR\fIPort\fP
  63. If set, Tor will accept connections on
  64. this port, and allow those connections to control the Tor process using the
  65. Tor Control Protocol (described in control-spec.txt). Note: unless you also
  66. specify one of \fBHashedControlPassword\fP or \fBCookieAuthentication\fP,
  67. setting this option will cause Tor to allow any process on the local host to
  68. control it.
  69. .LP
  70. .TP
  71. \fBControlListenAddress \fR\fIIP\fR[:\fIPORT\fR]\fP
  72. Bind the controller listener to this address. If you specify a port,
  73. bind to this port rather than the one specified in ControlPort. We
  74. strongly recommend that you leave this alone unless you know what you're
  75. doing, since giving attackers access to your control listener is really
  76. dangerous. (Default: 127.0.0.1)
  77. This directive can be specified multiple times to bind to multiple
  78. addresses/ports.
  79. .LP
  80. .TP
  81. \fBHashedControlPassword \fR\fIhashed_password\fP
  82. Don't allow any connections on the control port except when the other process
  83. knows the password whose one-way hash is \fIhashed_password\fP. You can
  84. compute the hash of a password by running "tor --hash-password
  85. \fIpassword\fP".
  86. .LP
  87. .TP
  88. \fBCookieAuthentication \fR\fB0\fR|\fB1\fP
  89. If this option is set to 1, don't allow any connections on the control port
  90. except when the connecting process knows the contents of a file named
  91. "control_auth_cookie", which Tor will create in its data directory. This
  92. authentication methods should only be used on systems with good filesystem
  93. security. (Default: 0)
  94. .LP
  95. .TP
  96. \fBDataDirectory \fR\fIDIR\fP
  97. Store working data in DIR (Default: @LOCALSTATEDIR@/lib/tor)
  98. .LP
  99. .TP
  100. \fBDirServer \fR[\fInickname\fR] [\fBflags\fR] \fIaddress\fR\fB:\fIport fingerprint\fP
  101. Use a nonstandard authoritative directory server at the provided
  102. address and port, with the specified key fingerprint. This option can
  103. be repeated many times, for multiple authoritative directory
  104. servers. Flags are separated by spaces, and determine what kind of an
  105. authority this directory is. By default, every authority is authoritative
  106. for current ("v2")-style directories, unless the "no-v2" flag is given. If the "v1" flags is provided, Tor will use this server as an
  107. authority for old-style (v1) directories as well. (Only directory mirrors
  108. care about this.) Tor will use this server as an authority for hidden
  109. service information if the "hs" flag is set, or if the "v1" flag is set and
  110. the "no-hs" flag is \fBnot\fP set.
  111. If no \fBdirserver\fP line is given, Tor will use the default
  112. directory servers. NOTE: this option is intended
  113. for setting up a private Tor network with its own directory authorities. If
  114. you use it, you will be distinguishable from other users, because you won't
  115. believe the same authorities they do.
  116. .LP
  117. .TP
  118. \fBFetchHidServDescriptors \fR\fB0\fR|\fB1\fR\fP
  119. If set to 0, Tor will never fetch any hidden service descriptors from
  120. the rendezvous directories. This option is only useful if you're using
  121. a Tor controller that handles hidserv fetches for you.
  122. (Default: 1)
  123. .LP
  124. .TP
  125. \fBFetchServerDescriptors \fR\fB0\fR|\fB1\fR\fP
  126. If set to 0, Tor will never fetch any network status summaries or server
  127. descriptors from the directory servers. This option is only useful if
  128. you're using a Tor controller that handles directory fetches for you.
  129. (Default: 1)
  130. .LP
  131. .TP
  132. \fBFetchUselessDescriptors \fR\fB0\fR|\fB1\fR\fP
  133. If set to 1, Tor will fetch every non-obsolete descriptor from the
  134. authorities that it hears about. Otherwise, it will avoid fetching
  135. useless descriptors, for example for routers that are not running.
  136. This option is useful if you're using the contributed "exitlist"
  137. script to enumerate Tor nodes that exit to certain addresses.
  138. (Default: 0)
  139. .LP
  140. .TP
  141. \fBGroup \fR\fIGID\fP
  142. On startup, setgid to this user.
  143. .LP
  144. .TP
  145. \fBHttpProxy\fR \fIhost\fR[:\fIport\fR]\fP
  146. Tor will make all its directory requests through this host:port
  147. (or host:80 if port is not specified),
  148. rather than connecting directly to any directory servers.
  149. .LP
  150. .TP
  151. \fBHttpProxyAuthenticator\fR \fIusername:password\fP
  152. If defined, Tor will use this username:password for Basic Http proxy
  153. authentication, as in RFC 2617. This is currently the only form of
  154. Http proxy authentication that Tor supports; feel free to submit a
  155. patch if you want it to support others.
  156. .LP
  157. .TP
  158. \fBHttpsProxy\fR \fIhost\fR[:\fIport\fR]\fP
  159. Tor will make all its OR (SSL) connections through this host:port
  160. (or host:443 if port is not specified), via HTTP CONNECT rather than
  161. connecting directly to servers. You may want to set \fBFascistFirewall\fR
  162. to restrict the set of ports you might try to connect to, if your Https
  163. proxy only allows connecting to certain ports.
  164. .LP
  165. .TP
  166. \fBHttpsProxyAuthenticator\fR \fIusername:password\fP
  167. If defined, Tor will use this username:password for Basic Https proxy
  168. authentication, as in RFC 2617. This is currently the only form of
  169. Https proxy authentication that Tor supports; feel free to submit a
  170. patch if you want it to support others.
  171. .LP
  172. .TP
  173. \fBKeepalivePeriod \fR\fINUM\fP
  174. To keep firewalls from expiring connections, send a padding keepalive
  175. cell every NUM seconds on open connections that are in use. If the
  176. connection has no open circuits, it will instead be closed after NUM
  177. seconds of idleness. (Default: 5 minutes)
  178. .LP
  179. .TP
  180. \fBLog \fR\fIminSeverity\fR[-\fImaxSeverity\fR] \fBstderr\fR|\fBstdout\fR|\fBsyslog\fR\fP
  181. Send all messages between \fIminSeverity\fR and \fImaxSeverity\fR to
  182. the standard output stream, the standard error stream, or to the system
  183. log. (The "syslog" value is only supported on Unix.) Recognized
  184. severity levels are debug, info, notice, warn, and err. We advise using
  185. "notice" in most cases, since anything more verbose may provide sensitive
  186. information to an attacker who obtains the logs. If only one
  187. severity level is given, all messages of that level or higher will be
  188. sent to the listed destination.
  189. .LP
  190. .TP
  191. \fBLog \fR\fIminSeverity\fR[-\fImaxSeverity\fR] \fBfile\fR \fIFILENAME\fP
  192. As above, but send log messages to the listed filename. The "Log"
  193. option may appear more than once in a configuration file. Messages
  194. are sent to all the logs that match their severity level.
  195. .LP
  196. .TP
  197. \fBOutboundBindAddress \fR\fIIP\fP
  198. Make all outbound connections originate from the IP address specified. This
  199. is only useful when you have multiple network interfaces, and you want all
  200. of Tor's outgoing connections to use a single one.
  201. .LP
  202. .TP
  203. \fBPidFile \fR\fIFILE\fP
  204. On startup, write our PID to FILE. On clean shutdown, remove FILE.
  205. .LP
  206. .TP
  207. \fBProtocolWarnings \fR\fB0\fR|\fB1\fR\fP
  208. If 1, Tor will log with severity 'warn' various cases of other parties
  209. not following the Tor specification. Otherwise, they are logged with
  210. severity 'info'. (Default: 0)
  211. .LP
  212. .TP
  213. \fBRunAsDaemon \fR\fB0\fR|\fB1\fR\fP
  214. If 1, Tor forks and daemonizes to the background. This option has
  215. no effect on Windows; instead you should use the --service command-line
  216. option. (Default: 0)
  217. .LP
  218. .TP
  219. \fBSafeLogging \fR\fB0\fR|\fB1\fP
  220. If 1, Tor replaces potentially sensitive strings in the logs
  221. (e.g. addresses) with the string [scrubbed]. This way logs can still be
  222. useful, but they don't leave behind personally identifying information
  223. about what sites a user might have visited. (Default: 1)
  224. .LP
  225. .TP
  226. \fBUser \fR\fIUID\fP
  227. On startup, setuid to this user.
  228. .LP
  229. .TP
  230. \fBHardwareAccel \fR\fB0\fR|\fB1\fP
  231. If non-zero, try to use crypto hardware acceleration when
  232. available. This is untested and probably buggy. (Default: 0)
  233. .SH CLIENT OPTIONS
  234. .PP
  235. The following options are useful only for clients (that is, if \fBSocksPort\fP is non-zero):
  236. .LP
  237. .TP
  238. \fBAllowInvalidNodes\fR \fBentry\fR|\fBexit\fR|\fBmiddle\fR|\fBintroduction\fR|\fBrendezvous\fR|...\fP
  239. If some Tor servers are obviously not working right, the directory
  240. authorities can manually mark them as invalid, meaning that it's not
  241. recommended you use them for entry or exit positions in your circuits. You
  242. can opt to use them in some circuit positions, though. The default is
  243. "middle,rendezvous", and other choices are not advised.
  244. .LP
  245. .TP
  246. \fBCircuitBuildTimeout \fR\fINUM\fP
  247. Try for at most NUM seconds when building circuits. If the circuit
  248. isn't open in that time, give up on it.
  249. (Default: 1 minute.)
  250. .LP
  251. .TP
  252. \fBCircuitIdleTimeout \fR\fINUM\fP
  253. If we have keept a clean (never used) circuit around for NUM seconds,
  254. then close it. This way when the Tor client is entirely idle, it can
  255. expire all of its circuits, and then expire its TLS connections. Also,
  256. if we end up making a circuit that is not useful for exiting any of
  257. the requests we're receiving, it won't forever take up a slot in the
  258. circuit list.
  259. (Default: 1 hour.)
  260. .LP
  261. .TP
  262. \fBClientOnly \fR\fB0\fR|\fB1\fR\fP
  263. If set to 1, Tor will under no circumstances run as a server. The default
  264. is to run as a client unless ORPort is configured. (Usually,
  265. you don't need to set this; Tor is pretty smart at figuring out whether
  266. you are reliable and high-bandwidth enough to be a useful server.)
  267. (Default: 0)
  268. .LP
  269. .TP
  270. \fBExcludeNodes \fR\fInickname\fR,\fInickname\fR,\fI...\fP
  271. A list of nodes to never use when building a circuit.
  272. .LP
  273. .TP
  274. \fBEntryNodes \fR\fInickname\fR,\fInickname\fR,\fI...\fP
  275. A list of preferred nodes to use for the first hop in the circuit.
  276. These are treated only as preferences unless StrictEntryNodes (see
  277. below) is also set.
  278. .LP
  279. .TP
  280. \fBExitNodes \fR\fInickname\fR,\fInickname\fR,\fI...\fP
  281. A list of preferred nodes to use for the last hop in the circuit.
  282. These are treated only as preferences unless StrictExitNodes (see
  283. below) is also set.
  284. .LP
  285. .TP
  286. \fBStrictEntryNodes \fR\fB0\fR|\fB1\fR\fP
  287. If 1, Tor will never use any nodes besides those listed in "EntryNodes" for
  288. the first hop of a circuit.
  289. .LP
  290. .TP
  291. \fBStrictExitNodes \fR\fB0\fR|\fB1\fR\fP
  292. If 1, Tor will never use any nodes besides those listed in "ExitNodes" for
  293. the last hop of a circuit.
  294. .LP
  295. .TP
  296. \fBFascistFirewall \fR\fB0\fR|\fB1\fR\fP
  297. If 1, Tor will only create outgoing connections to ORs running on ports that
  298. your firewall allows (defaults to 80 and 443; see \fBFirewallPorts\fR). This will
  299. allow you to run Tor as a client behind a firewall with restrictive policies,
  300. but will not allow you to run as a server behind such a firewall.
  301. This option is deprecated; use
  302. ReachableAddresses instead.
  303. .LP
  304. .TP
  305. \fBFirewallPorts \fR\fIPORTS\fP
  306. A list of ports that your firewall allows you to connect to. Only
  307. used when \fBFascistFirewall\fR is set. This option is deprecated; use
  308. ReachableAddresses instead. (Default: 80, 443)
  309. .LP
  310. .TP
  311. \fBReachableAddresses \fR\fIADDR\fP[\fB/\fP\fIMASK\fP][:\fIPORT\fP]...\fP
  312. A comma-separated list of IP addresses and ports that your firewall allows you
  313. to connect to. The format is as
  314. for the addresses in ExitPolicy, except that "accept" is understood
  315. unless "reject" is explicitly provided. For example, 'ReachableAddresses
  316. 99.0.0.0/8, reject 18.0.0.0/8:80, accept *:80' means that your
  317. firewall allows connections to everything inside net 99, rejects port
  318. 80 connections to net 18, and accepts connections to port 80 otherwise.
  319. (Default: 'accept *:*'.)
  320. .LP
  321. .TP
  322. \fBReachableDirAddresses \fR\fIADDR\fP[\fB/\fP\fIMASK\fP][:\fIPORT\fP]...\fP
  323. Like \fBReachableAddresses\fP, a list of addresses and ports. Tor will obey
  324. these restrictions when fetching directory information, using standard HTTP
  325. GET requests. If not set explicitly then the value of \fBReachableAddresses\fP
  326. is used. If \fBHttpProxy\fR is set then these connections will go through that
  327. proxy.
  328. .LP
  329. .TP
  330. \fBReachableORAddresses \fR\fIADDR\fP[\fB/\fP\fIMASK\fP][:\fIPORT\fP]...\fP
  331. Like \fBReachableAddresses\fP, a list of addresses and ports. Tor will obey
  332. these restrictions when connecting to Onion Routers, using TLS/SSL. If not set
  333. explicitly then the value of \fBReachableAddresses\fP is used. If
  334. \fBHttpsProxy\fR is set then these connections will go through that proxy.
  335. The separation between \fBReachableORAddresses\fP and
  336. \fBReachableDirAddresses\fP is only interesting when you are connecting through
  337. proxies (see \fBHttpProxy\fR and \fBHttpsProxy\fR). Most proxies limit TLS
  338. connections (which Tor uses to connect to Onion Routers) to port 443, and some
  339. limit HTTP GET requests (which Tor uses for fetching directory information) to
  340. port 80.
  341. .LP
  342. .TP
  343. \fBLongLivedPorts \fR\fIPORTS\fP
  344. A list of ports for services that tend to have long-running connections
  345. (e.g. chat and interactive shells). Circuits for streams that use these
  346. ports will contain only high-uptime nodes, to reduce the chance that a
  347. node will go down before the stream is finished.
  348. (Default: 21, 22, 706, 1863, 5050, 5190, 5222, 5223, 6667, 6697, 8300)
  349. .LP
  350. .TP
  351. \fBMapAddress\fR \fIaddress\fR \fInewaddress\fR
  352. When a request for address arrives to Tor, it will rewrite it to
  353. newaddress before processing it. For example, if you always want
  354. connections to www.indymedia.org to exit via \fItorserver\fR (where
  355. \fItorserver\fR is the nickname of the server),
  356. use "MapAddress www.indymedia.org www.indymedia.org.torserver.exit".
  357. .LP
  358. .TP
  359. \fBNewCircuitPeriod \fR\fINUM\fP
  360. Every NUM seconds consider whether to build a new circuit. (Default: 30 seconds)
  361. .LP
  362. .TP
  363. \fBMaxCircuitDirtiness \fR\fINUM\fP
  364. Feel free to reuse a circuit that was first used at most NUM seconds ago,
  365. but never attach a new stream to a circuit that is too old.
  366. (Default: 10 minutes)
  367. .LP
  368. .TP
  369. \fBNodeFamily \fR\fInickname\fR,\fInickname\fR,\fI...\fP
  370. The named Tor servers constitute a "family" of similar or co-administered
  371. servers, so never use any two of them in the same circuit. Defining a
  372. NodeFamily is only needed when a server doesn't list the family itself
  373. (with MyFamily). This option can be used multiple times.
  374. .LP
  375. .TP
  376. \fBEnforceDistinctSubnets \fR\fB0\fR|\fB1\fR\fP
  377. If 1, Tor will not put two servers whose IP addresses are "too
  378. close" on the same circuit. Currently, two addresses are
  379. "too close" if they lie in the same /16 range. (Default: 1)
  380. .\" \fBPathlenCoinWeight \fR\fI0.0-1.0\fP
  381. .\" Paths are 3 hops plus a geometric distribution centered around this coinweight.
  382. .\" Must be >=0.0 and <1.0. (Default: 0.3) NOT USED CURRENTLY
  383. .\" .TP
  384. .LP
  385. .TP
  386. \fBRendNodes \fR\fInickname\fR,\fInickname\fR,\fI...\fP
  387. A list of preferred nodes to use for the rendezvous point, if possible.
  388. .LP
  389. .TP
  390. \fBRendExcludeNodes \fR\fInickname\fR,\fInickname\fR,\fI...\fP
  391. A list of nodes to never use when choosing a rendezvous point.
  392. .LP
  393. .TP
  394. \fBSocksPort \fR\fIPORT\fP
  395. Advertise this port to listen for connections from Socks-speaking
  396. applications. Set this to 0 if you don't want to allow application
  397. connections. (Default: 9050)
  398. .LP
  399. .TP
  400. \fBSocksListenAddress \fR\fIIP\fR[:\fIPORT\fR]\fP
  401. Bind to this address to listen for connections from Socks-speaking
  402. applications. (Default: 127.0.0.1) You can also specify a port
  403. (e.g. 192.168.0.1:9100).
  404. This directive can be specified multiple times to bind to multiple
  405. addresses/ports.
  406. .LP
  407. .TP
  408. \fBSocksPolicy \fR\fIpolicy\fR,\fIpolicy\fR,\fI...\fP
  409. Set an entrance policy for this server, to limit who can connect to the
  410. Socks ports.
  411. The policies have the same form as exit policies below.
  412. .LP
  413. .TP
  414. \fBSocksTimeout \fR\fINUM\fP
  415. Let a socks connection wait NUM seconds unattached before we fail it.
  416. (Default: 2 minutes.)
  417. .LP
  418. .TP
  419. \fBTestVia \fR\fInickname\fR,\fInickname\fR,\fI...\fP
  420. A list of nodes to prefer for your middle hop when building testing
  421. circuits. This option is mainly for debugging reachability problems.
  422. .LP
  423. .TP
  424. \fBTrackHostExits \fR\fIhost\fR,\fI.domain\fR,\fI...\fR\fP
  425. For each value in the comma separated list, Tor will track recent connections
  426. to hosts that match this value and attempt to
  427. reuse the same exit node for each. If the value is prepended with a '.', it is
  428. treated as matching an entire domain. If one of the values is just a '.', it
  429. means match everything. This option is useful if you frequently connect to
  430. sites that will expire all your authentication cookies (ie log you out) if
  431. your IP address changes. Note that this option does have the disadvantage of
  432. making it more clear that a given history is
  433. associated with a single user. However, most people who would wish to observe
  434. this will observe it through cookies or other protocol-specific means anyhow.
  435. .LP
  436. .TP
  437. \fBTrackHostExitsExpire \fR\fINUM\fP
  438. Since exit servers go up and down, it is desirable to expire the association
  439. between host and exit server after NUM seconds. The default
  440. is 1800 seconds (30 minutes).
  441. .LP
  442. .TP
  443. \fBUseEntryGuards \fR\fB0\fR|\fB1\fR\fP
  444. If this option is set to 1, we pick a few long-term entry servers, and
  445. try to stick with them. This is desirable because
  446. constantly changing servers increases the odds that an adversary who owns
  447. some servers will observe a fraction of your paths.
  448. (Defaults to 1.)
  449. .LP
  450. .TP
  451. \fBNumEntryGuards \fR\fINUM\fP
  452. If UseEntryGuards is set to 1, we will try to pick a total of NUM routers
  453. as long-term entries for our circuits.
  454. (Defaults to 3.)
  455. .LP
  456. .TP
  457. \fBSafeSocks \fR\fB0\fR|\fB1\fR\fP
  458. When this option is enabled, Tor will reject application connections that
  459. use unsafe variants of the socks protocol -- ones that only provide an
  460. IP address, meaning the application is doing a DNS resolve first.
  461. Specifically, these are socks4 and socks5 when not doing remote DNS.
  462. (Defaults to 0.)
  463. .LP
  464. .TP
  465. \fBTestSocks \fR\fB0\fR|\fB1\fR\fP
  466. When this option is enabled, Tor will make a notice-level log entry for
  467. each connection to the Socks port indicating whether the request used
  468. a safe socks protocol or an unsafe one (see above entry on SafeSocks).
  469. This helps to determine whether an application using Tor is possibly
  470. leaking DNS requests.
  471. (Default: 0)
  472. .LP
  473. .TP
  474. \fBVirtualAddrNetwork \fR\fIAddress\fB/\fIbits\fP
  475. When a controller asks for a virtual (unused) address with the
  476. 'MAPADDRESS' command, Tor picks an unassigned address from this range.
  477. (Default: 127.192.0.0/10)
  478. .SH SERVER OPTIONS
  479. .PP
  480. The following options are useful only for servers (that is, if \fBORPort\fP is non-zero):
  481. .LP
  482. .TP
  483. \fBAddress \fR\fIaddress\fP
  484. The IP or fqdn of this server (e.g. moria.mit.edu). You can leave this
  485. unset, and Tor will guess your IP.
  486. .LP
  487. .TP
  488. \fBAssumeReachable \fR\fB0\fR|\fB1\fR\fP
  489. This option is used when bootstrapping a new Tor network. If set to 1,
  490. don't do self-reachability testing; just upload your server descriptor
  491. immediately. If \fBAuthoritativeDirectory\fP is also set, this option
  492. instructs the dirserver to bypass remote reachability testing too and
  493. list all connected servers as running.
  494. .LP
  495. .TP
  496. \fBContactInfo \fR\fIemail_address\fP
  497. Administrative contact information for server. This line might get
  498. picked up by spam harvesters, so you may want to obscure the fact
  499. that it's an email address.
  500. .LP
  501. .TP
  502. \fBExitPolicy \fR\fIpolicy\fR,\fIpolicy\fR,\fI...\fP
  503. Set an exit policy for this server. Each policy is of the form
  504. "\fBaccept\fP|\fBreject\fP \fIADDR\fP[\fB/\fP\fIMASK\fP]\fB[:\fP\fIPORT\fP]".
  505. If \fB/\fP\fIMASK\fP is omitted then this policy just applies to the host
  506. given. Instead of giving a host or network you can also use "\fB*\fP" to
  507. denote the universe (0.0.0.0/0). \fIPORT\fP can be a single port number,
  508. an interval of ports "\fIFROM_PORT\fP\fB-\fP\fITO_PORT\fP", or "\fB*\fP".
  509. If \fIPORT\fP is omitted, that means "\fB*\fP".
  510. For example, "accept 18.7.22.69:*,reject 18.0.0.0/8:*,accept *:*" would
  511. reject any traffic destined for MIT except for web.mit.edu, and
  512. accept anything else.
  513. To specify all internal and link-local networks (including 0.0.0.0/8,
  514. 169.254.0.0/16, 127.0.0.0/8, 192.168.0.0/16, 10.0.0.0/8, and
  515. 172.16.0.0/12), you can use the "private" alias instead of an address.
  516. These addresses are rejected by default (at the beginning of your
  517. exit policy) unless you set the ExitPolicyRejectPrivate config option
  518. to 0. For example, once you've done that, you could allow HTTP to
  519. 127.0.0.1 and block all other connections to internal networks with
  520. "accept
  521. 127.0.0.1:80,reject private:*". See RFC 1918 and RFC 3330 for more
  522. details about internal and reserved IP address space.
  523. This directive can be specified multiple times so you don't have to put
  524. it all on one line.
  525. Policies are considered first to last, and the first match wins. If
  526. you want to _replace_ the default exit policy, end your exit policy with
  527. either a reject *:* or an accept *:*. Otherwise, you're _augmenting_
  528. (prepending to) the default exit policy. The default exit policy is:
  529. .PD 0
  530. .RS 12
  531. .IP "reject *:25"
  532. .IP "reject *:119"
  533. .IP "reject *:135-139"
  534. .IP "reject *:445"
  535. .IP "reject *:465"
  536. .IP "reject *:587"
  537. .IP "reject *:1214"
  538. .IP "reject *:4661-4666"
  539. .IP "reject *:6346-6429"
  540. .IP "reject *:6699"
  541. .IP "reject *:6881-6999"
  542. .IP "accept *:*"
  543. .RE
  544. .PD
  545. .LP
  546. .TP
  547. \fBExitPolicyRejectPrivate \fR\fB0\fR|\fB1\fR\fP
  548. Reject all private (local) networks at the beginning of your exit
  549. policy. See above entry on ExitPolicy. (Default: 1)
  550. .LP
  551. .TP
  552. \fBMaxOnionsPending \fR\fINUM\fP
  553. If you have more than this number of onionskins queued for decrypt, reject new ones. (Default: 100)
  554. .LP
  555. .TP
  556. \fBMyFamily \fR\fInickname\fR,\fInickname\fR,\fI...\fP
  557. Declare that this Tor server is controlled or administered by a group
  558. or organization identical or similar to that of the other named servers.
  559. When two servers both declare that they are in the same 'family', Tor clients
  560. will not use them in the same circuit. (Each server only needs to list the
  561. other servers in its family; it doesn't need to list itself, but it won't hurt.)
  562. .LP
  563. .TP
  564. \fBNickname \fR\fIname\fP
  565. Set the server's nickname to 'name'. Nicknames must be between 1
  566. and 19 characters inclusive, and must contain only the characters
  567. [a-zA-Z0-9].
  568. .LP
  569. .TP
  570. \fBNumCPUs \fR\fInum\fP
  571. How many processes to use at once for decrypting onionskins. (Default: 1)
  572. .LP
  573. .TP
  574. \fBORPort \fR\fIPORT\fP
  575. Advertise this port to listen for connections from Tor clients and servers.
  576. .LP
  577. .TP
  578. \fBORListenAddress \fR\fIIP\fR[:\fIPORT\fR]\fP
  579. Bind to this IP address to listen for connections from Tor clients and
  580. servers. If you specify a port, bind to this port rather than the one
  581. specified in ORPort. (Default: 0.0.0.0)
  582. This directive can be specified multiple times to bind to multiple
  583. addresses/ports.
  584. .LP
  585. .TP
  586. \fBPublishServerDescriptor \fR\fB0\fR|\fB1\fR\fP
  587. If set to 0, Tor will act as a server if you have an ORPort
  588. defined, but it will not publish its descriptor to the dirservers. This
  589. option is useful if you're testing out your server, or if you're using
  590. a Tor controller that handles directory publishing for you.
  591. (Default: 1)
  592. .LP
  593. .TP
  594. \fBRedirectExit \fR\fIpattern target\fP
  595. Whenever an outgoing connection tries to connect to one of a given set
  596. of addresses, connect to \fItarget\fP (an \fIaddress:port\fP pair) instead.
  597. The address
  598. pattern is given in the same format as for an exit policy. The
  599. address translation applies after exit policies are applied. Multiple
  600. \fBRedirectExit\fP options can be used: once any one has matched
  601. successfully, no subsequent rules are considered. You can specify that no
  602. redirection is to be performed on a given set of addresses by using the
  603. special target string "pass", which prevents subsequent rules from being
  604. considered.
  605. .LP
  606. .TP
  607. \fBShutdownWaitLength\fR \fINUM\fP
  608. When we get a SIGINT and we're a server, we begin shutting down: we close
  609. listeners and start refusing new circuits. After \fBNUM\fP seconds,
  610. we exit. If we get a second SIGINT, we exit immediately. (Default:
  611. 30 seconds)
  612. .LP
  613. .TP
  614. \fBAccountingMax \fR\fIN\fR \fBbytes\fR|\fBKB\fR|\fBMB\fR|\fBGB\fR|\fBTB\fP
  615. Never send more than the specified number of bytes in a given
  616. accounting period, or receive more than that number in the period.
  617. For example, with AccountingMax set to 1 GB, a server could send 900 MB
  618. and receive 800 MB and continue running. It will only hibernate once one
  619. of the two reaches 1 GB.
  620. When the number of bytes is exhausted, Tor will hibernate until some
  621. time in the next accounting period. To prevent all servers from
  622. waking at the same time, Tor will also wait until a random point in
  623. each period before waking up. If you have bandwidth cost issues,
  624. enabling hibernation is preferable to setting a low bandwidth, since it
  625. provides users with a collection of fast servers that are up some of
  626. the time, which is more useful than a set of slow servers that are
  627. always "available".
  628. .LP
  629. .TP
  630. \fBAccountingStart \fR\fBday\fR|\fBweek\fR|\fBmonth\fR [\fIday\fR] \fIHH:MM\fR\fP
  631. Specify how long accounting periods last. If \fBmonth\fP is given,
  632. each accounting period runs from the time \fIHH:MM\fR on the
  633. \fIday\fRth day of one month to the same day and time of the next.
  634. (The day must be between 1 and 28.) If \fBweek\fP is given, each
  635. accounting period runs from the time \fIHH:MM\fR of the \fIday\fRth
  636. day of one week to the same day and time of the next week, with Monday
  637. as day 1 and Sunday as day 7. If \fBday\fR is given, each accounting
  638. period runs from the time \fIHH:MM\fR each day to the same time on the
  639. next day. All times are local, and given in 24-hour time. (Defaults to
  640. "month 1 0:00".)
  641. .LP
  642. .TP
  643. \fBServerDNSResolvConfFile \fR\fIfilename\fP
  644. Overrides the default DNS configuration with the configuration in
  645. \fIfilename\fP. The file format is the same as the standard Unix
  646. "\fBresolv.conf\fP" file (7). This option only affects name lookup for
  647. addresses requested by clients; and only takes effect if Tor was built with
  648. eventdns support. (Defaults to use the system DNS configuration.)
  649. .LP
  650. .TP
  651. \fBServerDNSSearchDomains \fR\fB0\fR|\fB1\fR\fP
  652. If set to \fB1\fP, then we will search for addresses in the local search
  653. domain. For example, if this system is configured to believe it is in
  654. "example.com", and a client tries to connect to "www", the client will be
  655. connected to "www.example.com".
  656. This option only affects name lookup for addresses requested by clients.
  657. (Defaults to "0".)
  658. .LP
  659. .TP
  660. \fBServerDNSDetectHijacking \fR\fB0\fR|\fB1\fR\fP
  661. When this option is set to 1, we will test periodically to determine whether
  662. our local nameservers have been configured to hijack failing DNS requests
  663. (usually to an advertising site). If they are, we will attempt to correct
  664. this. This option only affects name lookup for addresses requested by
  665. clients; and only takes effect if Tor was built with eventdns support.
  666. (Defaults to "1".)
  667. .SH DIRECTORY SERVER OPTIONS
  668. .PP
  669. The following options are useful only for directory servers (that is, if \fBDirPort\fP is non-zero):
  670. .LP
  671. .TP
  672. \fBAuthoritativeDirectory \fR\fB0\fR|\fB1\fR\fP
  673. When this option is set to 1, Tor operates as an authoritative
  674. directory server. Instead of caching the directory, it generates its
  675. own list of good servers, signs it, and sends that to the clients.
  676. Unless the clients already have you listed as a trusted directory, you
  677. probably do not want to set this option. Please coordinate with the other
  678. admins at tor-ops@freehaven.net if you think you should be a directory.
  679. .LP
  680. .TP
  681. \fBV1AuthoritativeDirectory \fR\fB0\fR|\fB1\fR\fP
  682. When this option is set in addition to \fBAuthoritativeDirectory\fP, Tor also
  683. generates a version 1 directory (for Tor clients up to 0.1.0.x).
  684. (As of Tor 0.1.1.12 every (v2) authoritative directory still provides most of
  685. the v1 directory functionality, even without this option set to 1.
  686. This however is expected to change in the future.)
  687. .LP
  688. .TP
  689. \fBVersioningAuthoritativeDirectory \fR\fB0\fR|\fB1\fR\fP
  690. When this option is set to 1, Tor adds information on
  691. which versions of Tor are still believed safe for use to
  692. the published directory. Each version 1 authority is
  693. automatically a versioning authority; version 2 authorities
  694. provide this service optionally. See \fBRecommendedVersions\fP,
  695. \fBRecommendedClientVersions\fP, and \fBRecommendedServerVersions\fP.
  696. .LP
  697. .TP
  698. \fBNamingAuthoritativeDirectory \fR\fB0\fR|\fB1\fR\fP
  699. When this option is set to 1, then the server advertises that it has
  700. opinions about nickname-to-fingerprint bindings. It will include these
  701. opinions in its published network-status pages, by listing servers with
  702. the flag "Named" if a correct binding between that nickname and
  703. fingerprint has been registered with the dirserver. Naming dirservers
  704. will refuse to accept or publish descriptors that contradict a
  705. registered binding. See \fBapproved-routers\fP in the \fBFILES\fP
  706. section below.
  707. .LP
  708. .TP
  709. \fBHSAuthoritativeDir \fR\fB0\fR|\fB1\fR\fP
  710. When this option is set in addition to \fBAuthoritativeDirectory\fP, Tor also
  711. accepts and serves hidden service descriptors. (Default: 0)
  712. .LP
  713. .TP
  714. \fBDirPort \fR\fIPORT\fP
  715. Advertise the directory service on this port.
  716. .LP
  717. .TP
  718. \fBDirListenAddress \fR\fIIP\fR[:\fIPORT\fR]\fP
  719. Bind the directory service to this address. If you specify a port, bind
  720. to this port rather than the one specified in DirPort. (Default: 0.0.0.0)
  721. This directive can be specified multiple times to bind to multiple
  722. addresses/ports.
  723. .LP
  724. .TP
  725. \fBDirPolicy \fR\fIpolicy\fR,\fIpolicy\fR,\fI...\fP
  726. Set an entrance policy for this server, to limit who can connect to the
  727. directory ports.
  728. The policies have the same form as exit policies above.
  729. .LP
  730. .TP
  731. \fBRecommendedVersions \fR\fISTRING\fP
  732. STRING is a comma-separated list of Tor versions currently believed
  733. to be safe. The list is included in each directory, and nodes which
  734. pull down the directory learn whether they need to upgrade. This
  735. option can appear multiple times: the values from multiple lines are
  736. spliced together.
  737. When this is set then
  738. \fBVersioningAuthoritativeDirectory\fP should be set too.
  739. .LP
  740. .TP
  741. \fBRecommendedClientVersions \fR\fISTRING\fP
  742. STRING is a comma-separated list of Tor versions currently believed
  743. to be safe for clients to use. This information is included in version 2
  744. directories. If this is not set then the value of \fBRecommendedVersions\fR
  745. is used.
  746. When this is set then
  747. \fBVersioningAuthoritativeDirectory\fP should be set too.
  748. .LP
  749. .TP
  750. \fBRecommendedServerVersions \fR\fISTRING\fP
  751. STRING is a comma-separated list of Tor versions currently believed
  752. to be safe for servers to use. This information is included in version 2
  753. directories. If this is not set then the value of \fBRecommendedVersions\fR
  754. is used.
  755. When this is set then
  756. \fBVersioningAuthoritativeDirectory\fP should be set too.
  757. .LP
  758. .TP
  759. \fBDirAllowPrivateAddresses \fR\fB0\fR|\fB1\fR\fP
  760. If set to 1, Tor will accept router descriptors with arbitrary "Address"
  761. elements. Otherwise, if the address is not an IP or is a private IP,
  762. it will reject the router descriptor. Defaults to 0.
  763. .LP
  764. .TP
  765. \fBAuthDirBadExit \fR\fIAddressPattern\fR...\fP
  766. Authoritative directories only. A set of address patterns for servers that
  767. will be listed as bad exits in any network status document this authority
  768. publishes, if \fBAuthDirListBadExits\fR is set.
  769. .LP
  770. .TP
  771. \fBAuthDirInvalid \fR\fIAddressPattern\fR...\fP
  772. Authoritative directories only. A set of address patterns for servers that
  773. will never be listed as "valid" in any network status document that this
  774. authority publishes.
  775. .LP
  776. .TP
  777. \fBAuthDirReject \fR\fIAddressPattern\fR...\fP
  778. Authoritative directories only. A set of address patterns for servers that
  779. will never be listed at all in any network status document that this
  780. authority publishes, or accepted as an OR address in any descriptor submitted
  781. for publication by this authority.
  782. .LP
  783. .TP
  784. \fBAuthDirListBadExits \fR\fB0\fR|\fB1\fR\fP
  785. Authoritative directories only. If set to 1, this directory has
  786. some opinion about which nodes are unsuitable as exit nodes. (Do not
  787. set this to 1 unless you plan to list nonfunctioning exits as bad;
  788. otherwise, you are effectively voting in favor of every declared exit
  789. as an exit.)
  790. .LP
  791. .TP
  792. \fBAuthDirRejectUnlisted \fR\fB0\fR|\fB1\fR\fP
  793. Authoritative directories only. If set to 1, the directory server
  794. rejects all uploaded server descriptors that aren't explicitly listed
  795. in the fingerprints file. This acts as a "panic button" if we get
  796. Sybiled. (Default: 0)
  797. .SH HIDDEN SERVICE OPTIONS
  798. .PP
  799. The following options are used to configure a hidden service.
  800. .LP
  801. .TP
  802. \fBHiddenServiceDir \fR\fIDIRECTORY\fP
  803. Store data files for a hidden service in DIRECTORY. Every hidden
  804. service must have a separate directory. You may use this option multiple
  805. times to specify multiple services.
  806. .LP
  807. .TP
  808. \fBHiddenServicePort \fR\fIVIRTPORT \fR[\fITARGET\fR]\fP
  809. Configure a virtual port VIRTPORT for a hidden service. You may use this
  810. option multiple times; each time applies to the service using the most recent
  811. hiddenservicedir. By default, this option maps the virtual port to the
  812. same port on 127.0.0.1. You may override the target port, address, or both
  813. by specifying a target of addr, port, or addr:port.
  814. .LP
  815. .TP
  816. \fBHiddenServiceNodes \fR\fInickname\fR,\fInickname\fR,\fI...\fP
  817. If possible, use the specified nodes as introduction points for the hidden
  818. service. If this is left unset, Tor will be smart and pick some reasonable
  819. ones; most people can leave this unset.
  820. .LP
  821. .TP
  822. \fBHiddenServiceExcludeNodes \fR\fInickname\fR,\fInickname\fR,\fI...\fP
  823. Do not use the specified nodes as introduction points for the hidden
  824. service. In normal use there is no reason to set this.
  825. .LP
  826. .TP
  827. \fBPublishHidServDescriptors \fR\fB0\fR|\fB1\fR\fP
  828. If set to 0, Tor will run any hidden services you configure, but it won't
  829. advertise them to the rendezvous directory. This option is only useful
  830. if you're using a Tor controller that handles hidserv publishing for you.
  831. (Default: 1)
  832. .LP
  833. .TP
  834. \fBRendPostPeriod \fR\fIN\fR \fBseconds\fR|\fBminutes\fR|\fBhours\fR|\fBdays\fR|\fBweeks\fP
  835. Every time the specified period elapses, Tor uploads any rendezvous
  836. service descriptors to the directory servers. This information is also
  837. uploaded whenever it changes. (Default: 20 minutes)
  838. .\" UNDOCUMENTED
  839. .\" ignoreversion
  840. .SH SIGNALS
  841. Tor catches the following signals:
  842. .LP
  843. .TP
  844. \fBSIGTERM\fR
  845. Tor will catch this, clean up and sync to disk if necessary, and exit.
  846. .LP
  847. .TP
  848. \fBSIGINT\fR
  849. Tor clients behave as with SIGTERM; but Tor servers will do a controlled
  850. slow shutdown, closing listeners and waiting 30 seconds before exiting.
  851. (The delay can be configured with the ShutdownWaitLength config option.)
  852. .LP
  853. .TP
  854. \fBSIGHUP\fR
  855. The signal instructs Tor to reload its configuration (including closing
  856. and reopening logs), fetch a new directory, and kill and restart its
  857. helper processes if applicable.
  858. .LP
  859. .TP
  860. \fBSIGUSR1\fR
  861. Log statistics about current connections, past connections, and
  862. throughput.
  863. .LP
  864. .TP
  865. \fBSIGUSR2\fR
  866. Switch all logs to loglevel debug. You can go back to the old loglevels
  867. by sending a SIGHUP.
  868. .LP
  869. .TP
  870. \fBSIGCHLD\fR
  871. Tor receives this signal when one of its helper processes has exited,
  872. so it can clean up.
  873. .LP
  874. .TP
  875. \fBSIGPIPE\fR
  876. Tor catches this signal and ignores it.
  877. .LP
  878. .TP
  879. \fBSIGXFSZ\fR
  880. If this signal exists on your platform, Tor catches and ignores it.
  881. .SH FILES
  882. .LP
  883. .TP
  884. .B @CONFDIR@/torrc
  885. The configuration file, which contains "option value" pairs.
  886. .LP
  887. .TP
  888. .B @LOCALSTATEDIR@/lib/tor/
  889. The tor process stores keys and other data here.
  890. .LP
  891. .TP
  892. .B \fIDataDirectory\fP/approved-routers
  893. Only for naming authoritative directory servers
  894. (see \fBNamingAuthoritativeDirectory\fP).
  895. This file lists nickname to identity bindings. Each line lists a
  896. nickname and a fingerprint seperated by whitespace. See your
  897. \fBfingerprint\fP file in the \fIDataDirectory\fP for an example line.
  898. If the nickname is \fB!reject\fP then descriptors from the given
  899. identity (fingerprint) are rejected by the authoritative directory
  900. server. If it is \fB!invalid\fP then descriptors are accepted but marked
  901. in the directory as not valid, that is, not recommended.
  902. .SH SEE ALSO
  903. .BR privoxy (1),
  904. .BR tsocks (1),
  905. .BR torify (1)
  906. .BR http://tor.eff.org/
  907. .SH BUGS
  908. Plenty, probably. Tor is still in development. Please report them.
  909. .SH AUTHORS
  910. Roger Dingledine <arma@mit.edu>, Nick Mathewson <nickm@alum.mit.edu>.