Update tor-manual-cvs.html
Thomas Sjögren

Thomas Sjögren commited on 2005-05-15 03:24:46
Zeige 1 geänderte Dateien mit 22 Einfügungen und 15 Löschungen.

... ...
@@ -124,7 +124,7 @@ except when the connecting process knows the contents of a file named
124 124
 "control_auth_cookie", which Tor will create in its data directory.  This
125 125
 authentication methods should only be used on systems with good filesystem
126 126
 security.
127
-<B>DirFetchPeriod </B><I>N</I> <B>seconds</B>|<B>minutes</B>|<B>hours</B>|<B>days</B>|<B>weeks</B>
127
+<DT><B>DirFetchPeriod </B><I>N</I> <B>seconds</B>|<B>minutes</B>|<B>hours</B>|<B>days</B>|<B>weeks</B><DD>
128 128
 Every time the specified period elapses, Tor downloads a directory.
129 129
 A directory contains a signed list of all known servers as well as
130 130
 their current liveness status. A value of &quot;0 seconds&quot; tells Tor to choose an
... ...
@@ -151,9 +151,10 @@ The following options are useful only for clients (that is, if <B>SOCKSPort</B>
151 151
 Where on our circuits should we allow Tor servers that the directory
152 152
 servers haven't authenticated as &quot;verified&quot;?  (Default: middle,rendezvous.)
153 153
 <DT><B>ClientOnly </B><B>0</B>|<B>1</B><DD>
154
-If set to 1, Tor will under no circumstances run as a server.  (Usually,
154
+If set to 1, Tor will under no circumstances run as a server. The default
155
+is to run as a client unless ORPort is configured.  (Usually,
155 156
 you don't need to set this; Tor is pretty smart at figuring out whether
156
-you are reliable and high-bandwidth enough to be a good server.)
157
+you are reliable and high-bandwidth enough to be a useful server.)
157 158
 <DT><B>EntryNodes </B><I>nickname</I>,<I>nickname</I>,<I>...</I><DD>
158 159
 A list of preferred nodes to use for the first hop in the circuit, if possible.
159 160
 <DT><B>ExitNodes </B><I>nickname</I>,<I>nickname</I>,<I>...</I><DD>
... ...
@@ -200,11 +201,14 @@ A list of preferred nodes to use for the rendezvous point, if possible.
200 201
 <DT><B>RendExcludeNodes </B><I>nickname</I>,<I>nickname</I>,<I>...</I><DD>
201 202
 A list of nodes to never use when choosing a rendezvous point.
202 203
 <DT><B>SOCKSPort </B><I>PORT</I><DD>
203
-Bind to this port to listen for connections from SOCKS-speaking applications.
204
-Set this to 0 if you don't want to allow application connections. (Default:
205
-9050)
206
-<DT><B>SOCKSBindAddress </B><I>IP</I><DD>
207
-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.
204
+Advertise this port to listen for connections from SOCKS-speaking
205
+applications.  Set this to 0 if you don't want to allow application
206
+connections. (Default: 9050)
207
+<DT><B>SOCKSBindAddress </B><I>IP</I>[:<I>PORT</I>]<DD>
208
+Bind to this address to listen for connections from SOCKS-speaking
209
+applications. (Default: 127.0.0.1) You can also specify a port
210
+(e.g. 192.168.0.1:9100). This directive can be specified multiple times
211
+to bind to multiple addresses/ports.
208 212
 <DT><B>SOCKSPolicy </B><I>policy</I>,<I>policy</I>,<I>...</I><DD>
209 213
 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.
210 214
 <DT><B>TrackHostExits </B><I>host</I>,<I>.domain</I>,<I>...</I><DD>
... ...
@@ -292,9 +296,11 @@ Set the server's nickname to 'name'.
292 296
 <DT><B>NumCPUs </B><I>num</I><DD>
293 297
 How many processes to use at once for decrypting onionskins. (Default: 1)
294 298
 <DT><B>ORPort </B><I>PORT</I><DD>
295
-Bind to this port to listen for connections from Tor clients and servers.
296
-<DT><B>ORBindAddress </B><I>IP</I><DD>
297
-Bind to this address to listen for connections from Tor clients and servers. (Default: 0.0.0.0)
299
+Advertise this port to listen for connections from Tor clients and servers.
300
+<DT><B>ORBindAddress </B><I>IP</I>[:<I>PORT</I>]<DD>
301
+Bind to this IP address to listen for connections from Tor clients and
302
+servers. If you specify a port, bind to this port rather than the one
303
+specified in ORPort. (Default: 0.0.0.0)
298 304
 <DT><B>RedirectExit </B><I>pattern target</I><DD>
299 305
 Whenever an outgoing connection tries to connect to one of a given set
300 306
 of addresses, connect to <I>target</I> (an <I>address:port</I> pair) instead.
... ...
@@ -357,9 +363,10 @@ Unless the clients already have you listed as a trusted directory, you
357 363
 probably do not want to set this option.  Please coordinate with the other
358 364
 admins at <A HREF="mailto:tor-ops@freehaven.net">tor-ops@freehaven.net</A> if you think you should be a directory.
359 365
 <DT><B>DirPort </B><I>PORT</I><DD>
360
-Bind the directory service to this port.
361
-<DT><B>DirBindAddress </B><I>IP</I><DD>
362
-Bind the directory service to this address. (Default: 0.0.0.0)
366
+Advertise the directory service on this port.
367
+<DT><B>DirBindAddress </B><I>IP</I>[:<I>PORT</I>]<DD>
368
+Bind the directory service to this address. If you specify a port, bind
369
+to this port rather than the one specified in DirPort. (Default: 0.0.0.0)
363 370
 <DT><B>DirPolicy </B><I>policy</I>,<I>policy</I>,<I>...</I><DD>
364 371
 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.
365 372
 <DT><B>RecommendedVersions </B><I>STRING</I><DD>
... ...
@@ -496,6 +503,6 @@ Roger Dingledine &lt;<A HREF="mailto:arma@mit.edu">arma@mit.edu</A>&gt;, Nick Ma
496 503
 This document was created by
497 504
 <A HREF="../">man2html</A>,
498 505
 using the manual pages.<BR>
499
-Time: 22:12:47 GMT, May 01, 2005
506
+Time: 01:23:43 GMT, May 15, 2005
500 507
 </BODY>
501 508
 </HTML>
502 509