tor-manual is now for the latest stable, tor-manual-cvs is for the cvs version. documentation.html has been updated.
Thomas Sjögren

Thomas Sjögren commited on 2005-03-18 02:26:49
Zeige 3 geänderte Dateien mit 518 Einfügungen und 62 Löschungen.

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