tor-manual is now for the l...
Thomas Sjögren authored 19 years ago
|
1) Content-type: text/html
2)
3) <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
4) <HTML><HEAD><TITLE>Man page of TOR</TITLE>
5) </HEAD><BODY>
6) <H1>TOR</H1>
|
Update tor-manual-cvs.html
Thomas Sjögren authored 19 years ago
|
7) Section: User Commands (1)<BR>Updated: May 2005<BR><A HREF="#index">Index</A>
|
Updated tor-manual-cvs.html...
Thomas Sjögren authored 19 years ago
|
8) <A HREF="../">Return to Main Contents</A><HR>
|
tor-manual is now for the l...
Thomas Sjögren authored 19 years ago
|
9)
10) <A NAME="lbAB"> </A>
11) <H2>NAME</H2>
12)
13) tor - The second-generation onion router
14) <A NAME="lbAC"> </A>
15) <H2>SYNOPSIS</H2>
16)
17) <B>tor</B>
18)
19) [<I>OPTION value</I>]...
20) <A NAME="lbAD"> </A>
21) <H2>DESCRIPTION</H2>
22)
23) <I>tor</I>
24)
25) is a connection-oriented anonymizing communication
26) service. Users choose a source-routed path through a set of nodes, and
27) negotiate a "virtual circuit" through the network, in which each node
28) knows its predecessor and successor, but no others. Traffic flowing down
29) the circuit is unwrapped by a symmetric key at each node, which reveals
30) the downstream node.
31) <P>
32)
33) Basically <I>tor</I> provides a distributed network of servers ("onion
34) routers"). Users bounce their TCP streams -- web traffic, ftp, ssh, etc --
35) around the routers, and recipients, observers, and even the routers
36) themselves have difficulty tracking the source of the stream.
37) <A NAME="lbAE"> </A>
38) <H2>OPTIONS</H2>
39)
40) <B>-h, -help</B>
41) Display a short help message and exit.
42) <DL COMPACT>
43) <DT><B>-f </B><I>FILE</I><DD>
44) FILE contains further "option value" pairs. (Default: @CONFDIR@/torrc)
45) <DT>Other options can be specified either on the command-line (<I>--option<DD>
46) value</I>), or in the configuration file (<I>option value</I>).
47) Options are case-insensitive.
48) <DT><B>BandwidthRate </B><I>N</I> <B>bytes</B>|<B>KB</B>|<B>MB</B>|<B>GB</B>|<B>TB</B><DD>
49) A token bucket limits the average incoming bandwidth on this node to
|
update tor-manual-cvs.html
Thomas Sjögren authored 19 years ago
|
50) the specified number of bytes per second. (Default: 2 MB)
|
tor-manual is now for the l...
Thomas Sjögren authored 19 years ago
|
51) <DT><B>BandwidthBurst </B><I>N</I> <B>bytes</B>|<B>KB</B>|<B>MB</B>|<B>GB</B>|<B>TB</B><DD>
|
update tor-manual-cvs.html
Thomas Sjögren authored 19 years ago
|
52) Limit the maximum token bucket size (also known as the burst) to the given number of bytes. (Default: 5 MB)
|
Updated tor-manual-cvs.html...
Thomas Sjögren authored 19 years ago
|
53) <DT><B>MaxAdvertisedBandwidth </B><I>N</I> <B>bytes</B>|<B>KB</B>|<B>MB</B>|<B>GB</B>|<B>TB</B><DD>
54) If set, we will not advertise more than this amount of bandwidth for our
55) BandwidthRate. Server operators who want to reduce the number of clients
56) who ask to build circuits through them (since this is proportional to
57) advertised bandwidth rate) can thus reduce the CPU demands on their
58) server without impacting network performance.
|
Update tor-manual-cvs.html
Thomas Sjögren authored 19 years ago
|
59) <DT><B>ControlPort </B><I>Port</I><DD>
60) If set, Tor will accept connections from the same machine (localhost only) on
61) this port, and allow those connections to control the Tor process using the
62) Tor Control Protocol (described in control-spec.txt). Note: unless you also
63) specify one of <B>HashedControlPassword</B> or <B>CookieAuthentication</B>,
64) setting this option will cause Tor to allow any process on the local host to
65) control it.
66) <DT><B>HashedControlPassword </B><I>hashed_password</I><DD>
67) Don't allow any connections on the control port except when the other process
68) knows the password whose one-way hash is <I>hashed_password</I>. You can
69) compute the hash of a password by running "tor --hash-password
70) <I>password</I>".
71) <DT><B>CookieAuthentication </B><B>0</B>|<B>1</B><DD>
72) If this option is set to 1, don't allow any connections on the control port
73) except when the connecting process knows the contents of a file named
74) "control_auth_cookie", which Tor will create in its data directory. This
75) authentication methods should only be used on systems with good filesystem
76) security. (Default: 0)
|
tor-manual is now for the l...
Thomas Sjögren authored 19 years ago
|
77) <DT><B>DataDirectory </B><I>DIR</I><DD>
78) Store working data in DIR (Default: @LOCALSTATEDIR@/lib/tor)
|
Update tor-manual-cvs.html
Thomas Sjögren authored 19 years ago
|
79) <DT><B>DirFetchPeriod </B><I>N</I> <B>seconds</B>|<B>minutes</B>|<B>hours</B>|<B>days</B>|<B>weeks</B><DD>
80) Every time the specified period elapses, Tor downloads a directory.
81) A directory contains a signed list of all known servers as well as
82) their current liveness status. A value of "0 seconds" tells Tor to choose an
83) appropriate default. (Default: 1 hour for clients, 20 minutes for servers.)
|
tor-manual is now for the l...
Thomas Sjögren authored 19 years ago
|
84) <DT><B>DirServer </B><I>address:port fingerprint</I><DD>
85) Use a nonstandard authoritative directory server at the provided
86) address and port, with the specified key fingerprint. This option can
87) be repeated many times, for multiple authoritative directory
88) servers. If no <B>dirserver</B> line is given, Tor will use the default
89) directory servers: moria1, moria2, and tor26.
90) <DT><B>Group </B><I>GID</I><DD>
91) On startup, setgid to this user.
92) <DT><B>HttpProxy</B> <I>host</I>[:<I>port</I>]<DD>
93) If set, Tor will make all its directory requests through this host:port,
94) rather than connecting directly to any directory servers.
95) <DT><B>HttpsProxy</B> <I>host</I>[:<I>port</I>]<DD>
96) If set, Tor will make all its OR (SSL) connections through this host:port,
97) via HTTP CONNECT, rather than connecting directly to servers.
|
Update tor-manual-cvs.html
Thomas Sjögren authored 19 years ago
|
98) <DT><B>HttpsProxyAuthenticator</B> <I>username:password</I><DD>
99) If defined, Tor will use this username:password for Basic Https proxy
100) authentication, as in RFC 2617. This is currently the only form of
101) Https proxy authentication that Tor supports; feel free to submit a
102) patch if you want it to support others. You may want to set FascistFirewall
103) to restrict the set of ports you might try to connect to, if your Https
104) proxy only allows connecting to certain ports.
|
tor-manual is now for the l...
Thomas Sjögren authored 19 years ago
|
105) <DT><B>KeepalivePeriod </B><I>NUM</I><DD>
106) To keep firewalls from expiring connections, send a padding keepalive
107) cell on open connections every NUM seconds. (Default: 5 minutes.)
|
Update tor-manual-cvs.html
Thomas Sjögren authored 19 years ago
|
108) <DT><B>Log </B><I>minSeverity</I>[-<I>maxSeverity</I>] <B>stderr</B>|<B>stdout</B>|<B>syslog</B><DD>
109) Send all messages between <I>minSeverity</I> and <I>maxSeverity</I> to
110) the standard output stream, the standard error stream, or to the system
111) log. (The "syslog" value is only supported on Unix.) Recognized
112) severity levels are debug, info, notice, warn, and err. If only one
113) severity level is given, all messages of that level or higher will be
114) sent to the listed destination.
115) <DT><B>Log </B><I>minSeverity</I>[-<I>maxSeverity</I>] <B>file</B> <I>FILENAME</I><DD>
116) As above, but send log messages to the listed filename. The "Log"
117) option may appear more than once in a configuration file. Messages
118) are sent to all the logs that match their severity level.
|
tor-manual is now for the l...
Thomas Sjögren authored 19 years ago
|
119) <DT><B>MaxConn </B><I>NUM</I><DD>
120) Maximum number of simultaneous sockets allowed. You probably don't need
121) to adjust this. (Default: 1024)
122) <DT><B>OutboundBindAddress </B><I>IP</I><DD>
123) Make all outbound connections originate from the IP address specified. This
124) is only useful when you have multiple network interfaces, and you want all
125) of Tor's outgoing connections to use a single one.
126) <DT><B>PIDFile </B><I>FILE</I><DD>
127) On startup, write our PID to FILE. On clean shutdown, remove FILE.
128) <DT><B>RunAsDaemon </B><B>0</B>|<B>1</B><DD>
129) If 1, Tor forks and daemonizes to the background. (Default: 0)
|
Update tor-manual-cvs.html
Thomas Sjögren authored 19 years ago
|
130) <DT><B>SafeLogging </B><B>0</B>|<B>1</B><DD>
131) If 1, Tor replaces potentially sensitive strings in the logs
132) (e.g. addresses) with the string [scrubbed]. This way logs can still be
133) useful, but they don't leave behind personally identifying information
134) about what sites a user might have visited. (Default: 1)
135) <DT><B>StatusFetchPeriod </B><I>N</I> <B>seconds</B>|<B>minutes</B>|<B>hours</B>|<B>days</B>|<B>weeks</B><DD>
136) Every time the specified period elapses, Tor downloads signed status
137) information about the current state of known servers. A value of
138) "0 seconds" tells Tor to choose an appropriate default. (Default: 30
139) minutes for clients, 15 minutes for servers.)
|
tor-manual is now for the l...
Thomas Sjögren authored 19 years ago
|
140) <DT><B>User </B><I>UID</I><DD>
141) On startup, setuid to this user.
142) <P>
143) </DL>
144) <A NAME="lbAF"> </A>
145) <H2>CLIENT OPTIONS</H2>
146)
147) <P>
148)
149) The following options are useful only for clients (that is, if <B>SOCKSPort</B> is non-zero):
150) <DL COMPACT>
151) <DT><B>AllowUnverifiedNodes</B> <B>entry</B>|<B>exit</B>|<B>middle</B>|<B>introduction</B>|<B>rendezvous</B>|...<DD>
152) Where on our circuits should we allow Tor servers that the directory
153) servers haven't authenticated as "verified"? (Default: middle,rendezvous.)
154) <DT><B>ClientOnly </B><B>0</B>|<B>1</B><DD>
|
Update tor-manual-cvs.html
Thomas Sjögren authored 19 years ago
|
155) If set to 1, Tor will under no circumstances run as a server. The default
156) is to run as a client unless ORPort is configured. (Usually,
|
tor-manual is now for the l...
Thomas Sjögren authored 19 years ago
|
157) you don't need to set this; Tor is pretty smart at figuring out whether
|
Update tor-manual-cvs.html
Thomas Sjögren authored 19 years ago
|
158) you are reliable and high-bandwidth enough to be a useful server.)
|
tor-manual is now for the l...
Thomas Sjögren authored 19 years ago
|
159) <DT><B>EntryNodes </B><I>nickname</I>,<I>nickname</I>,<I>...</I><DD>
160) A list of preferred nodes to use for the first hop in the circuit, if possible.
161) <DT><B>ExitNodes </B><I>nickname</I>,<I>nickname</I>,<I>...</I><DD>
162) A list of preferred nodes to use for the last hop in the circuit, if possible.
163) <DT><B>ExcludeNodes </B><I>nickname</I>,<I>nickname</I>,<I>...</I><DD>
164) A list of nodes to never use when building a circuit.
165) <DT><B>StrictExitNodes </B><B>0</B>|<B>1</B><DD>
166) If 1, Tor will never use any nodes besides those listed in "exitnodes" for
167) the last hop of a circuit.
168) <DT><B>StrictEntryNodes </B><B>0</B>|<B>1</B><DD>
169) If 1, Tor will never use any nodes besides those listed in "entrynodes" for
170) the first hop of a circuit.
171) <DT><B>FascistFirewall </B><B>0</B>|<B>1</B><DD>
172) If 1, Tor will only create outgoing connections to ORs running on ports that
173) your firewall allows (defaults to 80 and 443; see <B>FirewallPorts</B>). This will
174) allow you to run Tor as a client behind a firewall with restrictive policies,
175) but will not allow you to run as a server behind such a firewall.
176) <DT><B>FirewallPorts </B><I>PORTS</I><DD>
177) A list of ports that your firewall allows you to connect to. Only used when
178) <B>FascistFirewall</B> is set. (Default: 80, 443.)
179) <DT><B>LongLivedPorts </B><I>PORTS</I><DD>
180) A list of ports for services that tend to have long-running connections
181) (e.g. chat and interactive shells). Circuits for streams that use these
182) ports will contain only high-uptime nodes, to reduce the chance that a
183) node will go down before the stream is finished.
184) <DT><B>MapAddress</B> <I>address</I> <I>newaddress</I><DD>
|
Update tor-manual-cvs.html...
Thomas Sjögren authored 19 years ago
|
185) When a request for address arrives to Tor, it will rewrite it to newaddress before processing it. For example, if you always want connections to <A HREF="http://www.indymedia.org">www.indymedia.org</A> to exit via <I>torserver</I> (where <I>torserver</I> is the nickname of the server), use "MapAddress <A HREF="http://www.indymedia.org">www.indymedia.org</A> <A HREF="http://www.indymedia.org.torserver.exit">www.indymedia.org.torserver.exit</A>".
|
tor-manual is now for the l...
Thomas Sjögren authored 19 years ago
|
186) <DT><B>NewCircuitPeriod </B><I>NUM</I><DD>
|
Update tor-manual-cvs.html
Thomas Sjögren authored 19 years ago
|
187) Every NUM seconds consider whether to build a new circuit. (Default: 30 seconds)
|
tor-manual is now for the l...
Thomas Sjögren authored 19 years ago
|
188) <DT><B>MaxCircuitDirtiness </B><I>NUM</I><DD>
189) Feel free to reuse a circuit that was first used at most NUM seconds
|
Update tor-manual-cvs.html
Thomas Sjögren authored 19 years ago
|
190) ago, but never attach a new stream to a circuit that is too old. (Default: 10 minutes)
|
tor-manual is now for the l...
Thomas Sjögren authored 19 years ago
|
191) <DT><B>NodeFamily </B><I>nickname</I>,<I>nickname</I>,<I>...</I><DD>
192) The named Tor servers constitute a "family" of similar or co-administered
193) servers, so never use any two of them in the same circuit. Defining a
194) NodeFamily is only needed when a server doesn't list the family itself
195) (with MyFamily). This option can be used multiple times.
196) <DT>
197) <DD>
198)
199)
200) <B>RendNodes </B><I>nickname</I>,<I>nickname</I>,<I>...</I>
201) A list of preferred nodes to use for the rendezvous point, if possible.
202) <DT><B>RendExcludeNodes </B><I>nickname</I>,<I>nickname</I>,<I>...</I><DD>
203) A list of nodes to never use when choosing a rendezvous point.
204) <DT><B>SOCKSPort </B><I>PORT</I><DD>
|
Update tor-manual-cvs.html
Thomas Sjögren authored 19 years ago
|
205) Advertise this port to listen for connections from SOCKS-speaking
206) applications. Set this to 0 if you don't want to allow application
207) connections. (Default: 9050)
208) <DT><B>SOCKSBindAddress </B><I>IP</I>[:<I>PORT</I>]<DD>
209) Bind to this address to listen for connections from SOCKS-speaking
210) applications. (Default: 127.0.0.1) You can also specify a port
211) (e.g. 192.168.0.1:9100). This directive can be specified multiple times
212) to bind to multiple addresses/ports.
|
tor-manual is now for the l...
Thomas Sjögren authored 19 years ago
|
213) <DT><B>SOCKSPolicy </B><I>policy</I>,<I>policy</I>,<I>...</I><DD>
214) Set an entrance policy for this server, to limit who can connect to the SOCKS ports. The policies have the same form as exit policies below.
|
update tor-manual-cvs.html
Thomas Sjögren authored 19 years ago
|
215) <DT><B>TrackHostExits </B><I>host</I>,<I>.domain</I>,<I>...</I><DD>
|
tor-manual is now for the l...
Thomas Sjögren authored 19 years ago
|
216) For each value in the comma separated list, Tor will track recent connections
217) to hosts that match this value and attempt to
218) reuse the same exit node for each. If the value is prepended with a '.', it is
219) treated as matching an entire domain. If one of the values is just a '.', it
220) means match everything. This option is useful if you frequently connect to
221) sites that will expire all your authentication cookies (ie log you out) if
222) your IP address changes. Note that this option does have the disadvantage of
223) making it more clear that a given history is
224) associated with a single user. However, most people who would wish to observe
225) this will observe it through cookies or other protocol-specific means anyhow.
226) <DT><B>TrackHostExitsExpire </B><I>NUM</I><DD>
227) Since exit servers go up and down, it is desirable to expire the association
228) between host and exit server after NUM seconds of inactivity. The default
229) is 1800 seconds (30 minutes).
230) <P>
231) </DL>
232) <A NAME="lbAG"> </A>
233) <H2>SERVER OPTIONS</H2>
234)
235) <P>
236)
237) The following options are useful only for servers (that is, if <B>ORPort</B> is non-zero):
238) <DL COMPACT>
239) <DT><B>Address </B><I>address</I><DD>
240) The IP or fqdn of this server (e.g. moria.mit.edu). You can leave this
241) unset, and Tor will guess your IP.
242) <DT><B>ContactInfo </B><I>email_address</I><DD>
243) Administrative contact information for server.
244) <DT><B>ExitPolicy </B><I>policy</I>,<I>policy</I>,<I>...</I><DD>
245) Set an exit policy for this server. Each policy is of the form
246) "<B>accept</B>|<B>reject</B> <I>ADDR</I>[<B>/</B><I>MASK</I>]<B>:</B><I>PORT</I>".
247) If <B>/</B><I>MASK</I> is omitted then this policy just applies to the host
248) given. Instead of giving a host or network you can also use "<B>*</B>" to
249) denote the universe (0.0.0.0/0). <I>PORT</I> can be a single port number,
250) an interval of ports "<I>FROM_PORT</I><B>-</B><I>TO_PORT</I>", or "<B>*</B>".
251) <P>
252) For example, "reject 127.0.0.1:*,reject 192.168.1.0/24:*,accept *:*" would
253) reject any traffic destined for localhost and any 192.168.1.* address, but
254) accept anything else.
255) <P>
256) This directive can be specified multiple times so you don't have to put
257) it all on one line.
258) <P>
259) See RFC 3330 for more details about internal and reserved IP address
260) space. Policies are considered first to last, and the first match wins. If
261) you want to _replace_ the default exit policy, end your exit policy with
262) either a reject *:* or an accept *:*. Otherwise, you're _augmenting_
263) (prepending to) the default exit policy. The default exit policy is:
264)
265) <DL COMPACT><DT><DD>
266) <DL COMPACT>
267) <DT>reject 0.0.0.0/8<DD>
268) <DT>reject 169.254.0.0/16<DD>
269) <DT>reject 127.0.0.0/8<DD>
270) <DT>reject 192.168.0.0/16<DD>
271) <DT>reject 10.0.0.0/8<DD>
272) <DT>reject 172.16.0.0/12<DD>
273) <DT>reject *:25<DD>
274) <DT>reject *:119<DD>
275) <DT>reject *:135-139<DD>
276) <DT>reject *:445<DD>
277) <DT>reject *:1214<DD>
278) <DT>reject *:4661-4666<DD>
279) <DT>reject *:6346-6429<DD>
280) <DT>reject *:6699<DD>
281) <DT>reject *:6881-6999<DD>
282) <DT>accept *:*<DD>
283) </DL>
284) </DL>
285)
286)
287) <DT><B>MaxOnionsPending </B><I>NUM</I><DD>
288) If you have more than this number of onionskins queued for decrypt, reject new ones. (Default: 100)
289) <DT><B>MyFamily </B><I>nickname</I>,<I>nickname</I>,<I>...</I><DD>
290) Declare that this Tor server is controlled or administered by a group
291) or organization identical or similar to that of the other named servers.
292) When two servers both declare that they are in the same 'family', Tor clients
293) will not use them in the same circuit. (Each server only needs to list the
294) other servers in its family; it doesn't need to list itself, but it won't hurt.)
295) <DT><B>Nickname </B><I>name</I><DD>
296) Set the server's nickname to 'name'.
297) <DT><B>NumCPUs </B><I>num</I><DD>
298) How many processes to use at once for decrypting onionskins. (Default: 1)
299) <DT><B>ORPort </B><I>PORT</I><DD>
|
Update tor-manual-cvs.html
Thomas Sjögren authored 19 years ago
|
300) Advertise this port to listen for connections from Tor clients and servers.
301) <DT><B>ORBindAddress </B><I>IP</I>[:<I>PORT</I>]<DD>
302) Bind to this IP address to listen for connections from Tor clients and
303) servers. If you specify a port, bind to this port rather than the one
304) specified in ORPort. (Default: 0.0.0.0)
|
tor-manual is now for the l...
Thomas Sjögren authored 19 years ago
|
305) <DT><B>RedirectExit </B><I>pattern target</I><DD>
306) Whenever an outgoing connection tries to connect to one of a given set
307) of addresses, connect to <I>target</I> (an <I>address:port</I> pair) instead.
308) The address
309) pattern is given in the same format as for an exit policy. The
310) address translation applies after exit policies are applied. Multiple
311) <B>RedirectExit</B> options can be used: once any one has matched
312) successfully, no subsequent rules are considered. You can specify that no
313) redirection is to be performed on a given set of addresses by using the
314) special target string "pass", which prevents subsequent rules from being
315) considered.
316) <DT><B>ShutdownWaitLength</B><I>NUM</I><DD>
317) When we get a SIGINT and we're a server, we begin shutting down: we close
318) listeners and start refusing new circuits. After <B>NUM</B> seconds,
319) we exit. If we get a second SIGINT, we exit immediately. (Default:
320) 30 seconds)
321) <DT><B>DirPostPeriod </B><I>N</I> <B>seconds</B>|<B>minutes</B>|<B>hours</B>|<B>days</B>|<B>weeks</B><DD>
322) Every time the specified period elapses, Tor uploads its server
323) descriptors to the directory servers. This information is also
324) uploaded whenever it changes. (Default: 20 minutes.)
325) <DT><B>AccountingMax </B><I>N</I> <B>bytes</B>|<B>KB</B>|<B>MB</B>|<B>GB</B>|<B>TB</B><DD>
326) Never send more than the specified number of bytes in a given
327) accounting period, or receive more than that number in the period.
|
Update tor-manual-cvs.html
Thomas Sjögren authored 19 years ago
|
328) For example, with AccountingMax set to 1 GB, a server could send 900 MB
329) and receive 800 MB and continue running. It will only hibernate once one
330) of the two reaches 1 GB.
|
tor-manual is now for the l...
Thomas Sjögren authored 19 years ago
|
331) When the number of bytes is exhausted, Tor will hibernate until some
332) time in the next accounting period. To prevent all servers from
333) waking at the same time, Tor will also wait until a random point in
334) each period before waking up. If you have bandwidth cost issues,
|
Updated tor-manual-cvs.html...
Thomas Sjögren authored 19 years ago
|
335) enabling hibernation is preferable to setting a low bandwidth, since it
|
tor-manual is now for the l...
Thomas Sjögren authored 19 years ago
|
336) provides users with a collection of fast servers that are up some of
337) the time, which is more useful than a set of slow servers that are
338) always "available".
339) <DT><B>AccountingStart </B><B>day</B>|<B>week</B>|<B>month</B> [<I>day</I>] <I>HH:MM</I><DD>
340) Specify how long accounting periods last. If <B>month</B> is given,
341) each accounting period runs from the time <I>HH:MM</I> on the
342) <I>day</I>th day of one month to the same day and time of the next.
343) (The day must be between 1 and 28.) If <B>week</B> is given, each
344) accounting period runs from the time <I>HH:MM</I> of the <I>day</I>th
345) day of one week to the same day and time of the next week, with Monday
346) as day 1 and Sunday as day 7. If <B>day</B> is given, each accounting
347) period runs from the time <I>HH:MM</I> each day to the same time on the
348) next day. All times are local, and given in 24-hour time. (Defaults to
349) "month 1 0:00".)
350) <P>
351) </DL>
352) <A NAME="lbAH"> </A>
353) <H2>DIRECTORY SERVER OPTIONS</H2>
354)
355) <P>
356)
357) The following options are useful only for directory servers (that is, if <B>DirPort</B> is non-zero):
358) <DL COMPACT>
359) <DT><B>AuthoritativeDirectory </B><B>0</B>|<B>1</B><DD>
360) When this option is set to 1, Tor operates as an authoritative
361) directory server. Instead of caching the directory, it generates its
362) own list of good servers, signs it, and sends that to the clients.
363) Unless the clients already have you listed as a trusted directory, you
364) probably do not want to set this option. Please coordinate with the other
365) admins at <A HREF="mailto:tor-ops@freehaven.net">tor-ops@freehaven.net</A> if you think you should be a directory.
366) <DT><B>DirPort </B><I>PORT</I><DD>
|
Update tor-manual-cvs.html
Thomas Sjögren authored 19 years ago
|
367) Advertise the directory service on this port.
368) <DT><B>DirBindAddress </B><I>IP</I>[:<I>PORT</I>]<DD>
369) Bind the directory service to this address. If you specify a port, bind
370) to this port rather than the one specified in DirPort. (Default: 0.0.0.0)
|
tor-manual is now for the l...
Thomas Sjögren authored 19 years ago
|
371) <DT><B>DirPolicy </B><I>policy</I>,<I>policy</I>,<I>...</I><DD>
372) Set an entrance policy for this server, to limit who can connect to the directory ports. The policies have the same form as exit policies above.
373) <DT><B>RecommendedVersions </B><I>STRING</I><DD>
374) STRING is a command-separated list of Tor versions currently believed
375) to be safe. The list is included in each directory, and nodes which
376) pull down the directory learn whether they need to upgrade. This
377) option can appear multiple times: the values from multiple lines are
378) spliced together.
379) <DT><B>DirAllowPrivateAddresses </B><B>0</B>|<B>1</B><DD>
380) If set to 1, Tor will accept router descriptors with arbitrary "Address"
381) elements. Otherwise, if the address is not an IP or is a private IP,
382) it will reject the router descriptor. Defaults to 0.
383) <DT><B>RunTesting </B><B>0</B>|<B>1</B><DD>
384) If set to 1, Tor tries to build circuits through all of the servers it
385) knows about, so it can tell which are up and which are down. This
386) option is only useful for authoritative directories, so you probably
387) don't want to use it.
388) <P>
389) </DL>
390) <A NAME="lbAI"> </A>
391) <H2>HIDDEN SERVICE OPTIONS</H2>
392)
393) <P>
394)
395) The following options are used to configure a hidden service.
396) <DL COMPACT>
397) <DT><B>HiddenServiceDir </B><I>DIRECTORY</I><DD>
398) Store data files for a hidden service in DIRECTORY. Every hidden
399) service must have a separate directory. You may use this option multiple
400) times to specify multiple services.
401) <DT><B>HiddenServicePort </B><I>VIRTPORT </I>[<I>TARGET</I>]<DD>
402) Configure a virtual port VIRTPORT for a hidden service. You may use this
403) option multiple times; each time applies to the service using the most recent
404) hiddenservicedir. By default, this option maps the virtual port to the
405) same port on 127.0.0.1. You may override the target port, address, or both
406) by specifying a target of addr, port, or addr:port.
407) <DT><B>HiddenServiceNodes </B><I>nickname</I>,<I>nickname</I>,<I>...</I><DD>
408) If possible, use the specified nodes as introduction points for the hidden
409) service. If this is left unset, Tor will be smart and pick some reasonable
410) ones; most people can leave this unset.
411) <DT><B>HiddenServiceExcludeNodes </B><I>nickname</I>,<I>nickname</I>,<I>...</I><DD>
412) Do not use the specified nodes as introduction points for the hidden
413) service. In normal use there is no reason to set this.
|
Update tor-manual-cvs.html
Thomas Sjögren authored 19 years ago
|
414) <DT><B>RendPostPeriod </B><I>N</I> <B>seconds</B>|<B>minutes</B>|<B>hours</B>|<B>days</B>|<B>weeks</B><DD>
415) Every time the specified period elapses, Tor uploads any rendezvous
416) service descriptors to the directory servers. This information is also
417) uploaded whenever it changes. (Default: 20 minutes.)
|
tor-manual is now for the l...
Thomas Sjögren authored 19 years ago
|
418) <P>
419)
420)
421) <P>
422) </DL>
423) <A NAME="lbAJ"> </A>
424) <H2>SIGNALS</H2>
425)
426) Tor catches the following signals:
427) <DL COMPACT>
428) <DT><B>SIGTERM</B><DD>
429) Tor will catch this, clean up and sync to disk if necessary, and exit.
430) <DT><B>SIGINT</B><DD>
431) Tor clients behave as with SIGTERM; but Tor servers will do a controlled
432) slow shutdown, closing listeners and waiting 30 seconds before exiting.
|
Update tor-manual-cvs.html
Thomas Sjögren authored 19 years ago
|
433) (The delay can be configured with the ShutdownWaitLength config option.)
|
tor-manual is now for the l...
Thomas Sjögren authored 19 years ago
|
434) <DT><B>SIGHUP</B><DD>
435) The signal instructs Tor to reload its configuration (including closing
436) and reopening logs), fetch a new directory, and kill and restart its
437) helper processes if applicable.
438) <DT><B>SIGUSR1</B><DD>
439) Log statistics about current connections, past connections, and
440) throughput.
441) <DT><B>SIGUSR2</B><DD>
442) Switch all logs to loglevel debug. You can go back to the old loglevels
443) by sending a SIGHUP.
444) <DT><B>SIGCHLD</B><DD>
445) Tor receives this signal when one of its helper processes has exited,
446) so it can clean up.
447) <DT><B>SIGPIPE</B><DD>
448) Tor catches this signal and ignores it.
449) <DT><B>SIGXFSZ</B><DD>
450) If this signal exists on your platform, Tor catches and ignores it.
451) <P>
452) </DL>
453) <A NAME="lbAK"> </A>
454) <H2>FILES</H2>
455)
456) <DL COMPACT>
457) <DT><I>@CONFDIR@/torrc</I>
458)
459) <DD>
460) The configuration file, which contains "option value" pairs.
461) <DT><I>@LOCALSTATEDIR@/lib/tor/</I>
462)
463) <DD>
464) The tor process stores keys and other data here.
465) <P>
466) </DL>
467) <A NAME="lbAL"> </A>
468) <H2>SEE ALSO</H2>
469)
|
Updated tor-manual-cvs.html...
Thomas Sjögren authored 19 years ago
|
470) <B><A HREF="../?1+privoxy">privoxy</A></B>(1),
|
tor-manual is now for the l...
Thomas Sjögren authored 19 years ago
|
471)
|
Updated tor-manual-cvs.html...
Thomas Sjögren authored 19 years ago
|
472) <B><A HREF="../?1+tsocks">tsocks</A></B>(1),
|
tor-manual is now for the l...
Thomas Sjögren authored 19 years ago
|
473)
|
Updated tor-manual-cvs.html...
Thomas Sjögren authored 19 years ago
|
474) <B><A HREF="../?1+torify">torify</A></B>(1)
|
tor-manual is now for the l...
Thomas Sjögren authored 19 years ago
|
475)
476) <P>
477) <B><A HREF="http://tor.eff.org/">http://tor.eff.org/</A></B>
478)
479) <P>
480) <A NAME="lbAM"> </A>
481) <H2>BUGS</H2>
482)
|
Update tor-manual-cvs.html
Thomas Sjögren authored 19 years ago
|
483) Plenty, probably. Tor is still in development. Please report them.
|
tor-manual is now for the l...
Thomas Sjögren authored 19 years ago
|
484) <A NAME="lbAN"> </A>
485) <H2>AUTHORS</H2>
486)
487) Roger Dingledine <<A HREF="mailto:arma@mit.edu">arma@mit.edu</A>>, Nick Mathewson <<A HREF="mailto:nickm@alum.mit.edu">nickm@alum.mit.edu</A>>.
488) <P>
489)
490) <HR>
491) <A NAME="index"> </A><H2>Index</H2>
492) <DL>
493) <DT><A HREF="#lbAB">NAME</A><DD>
494) <DT><A HREF="#lbAC">SYNOPSIS</A><DD>
495) <DT><A HREF="#lbAD">DESCRIPTION</A><DD>
496) <DT><A HREF="#lbAE">OPTIONS</A><DD>
497) <DT><A HREF="#lbAF">CLIENT OPTIONS</A><DD>
498) <DT><A HREF="#lbAG">SERVER OPTIONS</A><DD>
499) <DT><A HREF="#lbAH">DIRECTORY SERVER OPTIONS</A><DD>
500) <DT><A HREF="#lbAI">HIDDEN SERVICE OPTIONS</A><DD>
501) <DT><A HREF="#lbAJ">SIGNALS</A><DD>
502) <DT><A HREF="#lbAK">FILES</A><DD>
503) <DT><A HREF="#lbAL">SEE ALSO</A><DD>
504) <DT><A HREF="#lbAM">BUGS</A><DD>
505) <DT><A HREF="#lbAN">AUTHORS</A><DD>
506) </DL>
507) <HR>
508) This document was created by
|
Updated tor-manual-cvs.html...
Thomas Sjögren authored 19 years ago
|
509) <A HREF="../">man2html</A>,
|
tor-manual is now for the l...
Thomas Sjögren authored 19 years ago
|
510) using the manual pages.<BR>
|
Update tor-manual-cvs.html
Thomas Sjögren authored 19 years ago
|
511) Time: 10:38:23 GMT, May 15, 2005
|