[or-cvs] document ReachableDirAddresses and ReachableORAddresses

[weasel@xxxxxxxx (Peter Palfrader)]

Update of /home/or/cvsroot/tor/doc
In directory moria:/tmp/cvs-serv15615

Modified Files:
	TODO tor.1.in 
Log Message:
document ReachableDirAddresses and ReachableORAddresses

Index: TODO
===================================================================
RCS file: /home/or/cvsroot/tor/doc/TODO,v
retrieving revision 1.429
retrieving revision 1.430
diff -u -p -d -r1.429 -r1.430
--- TODO	13 Feb 2006 21:17:19 -0000	1.429
+++ TODO	13 Feb 2006 22:43:42 -0000	1.430
@@ -37,7 +37,7 @@ N - building on freebsd 6.0: (with multi
       by default, if it works?
 
   o Split into ReachableDirAddresses and ReachableORAddresses
-    - document
+    o document
 R - Jan 26 10:25:04.832 [warn] add_an_entry_guard(): Tried finding a
     new entry, but failed. Bad news. XXX.
 N - look at the proposed os x uninstaller:

Index: tor.1.in
===================================================================
RCS file: /home/or/cvsroot/tor/doc/tor.1.in,v
retrieving revision 1.131
retrieving revision 1.132
diff -u -p -d -r1.131 -r1.132
--- tor.1.in	13 Feb 2006 06:25:13 -0000	1.131
+++ tor.1.in	13 Feb 2006 22:43:42 -0000	1.132
@@ -267,8 +267,8 @@ ReachableAddresses instead. (Default: 80
 .LP
 .TP
 \fBReachableAddresses \fR\fIADDR\fP[\fB/\fP\fIMASK\fP][:\fIPORT\fP]...\fP
-A comma-separated list of IPs that your firewall allows you to connect
-to. The format is as
+A comma-separated list of IP addressess and ports that your firewall allows you
+to connect to. The format is as
 for the addresses in ExitPolicy, except that "accept" is understood
 unless "reject" is explicitly provided.  For example, 'ReachableAddresses
 99.0.0.0/8, reject 18.0.0.0/8:80, accept *:80' means that your
@@ -277,6 +277,28 @@ firewall allows connections to everythin
 (Default: 'accept *:*'.)
 .LP
 .TP
+\fBReachableDirAddresses \fR\fIADDR\fP[\fB/\fP\fIMASK\fP][:\fIPORT\fP]...\fP
+Like \fBReachableAddresses\fP, a list of addresses and ports.  Tor will obey
+these restrictions when fetching directory information, using standard HTTP
+GET requests. If not set explicitly then the value of \fBfBReachableAddresses\fP
+is used.  If \fBHttpProxy\fR is set then these connections will go through that
+proxy.
+.LP
+.TP
+\fBReachableORAddresses \fR\fIADDR\fP[\fB/\fP\fIMASK\fP][:\fIPORT\fP]...\fP
+Like \fBReachableAddresses\fP, a list of addresses and ports.  Tor will obey
+these restrictions when connecting to Onion Routers, using TLS/SSL.  If not set
+explicitly then the value of \fBfBReachableAddresses\fP is used. If
+\fBHttpsProxy\fR is set then these connections will go through that proxy.
+
+The separation between \fBReachableORAddresses\fP and
+\fBReachableDirAddresses\fP is only interesting when you are connecting through
+proxies (see \fBHttpProxy\fR and \fBHttpsProxy\fR).  Most proxies limit TLS
+connections (which Tor uses to connect to Onion Routers) to port 443, and some
+limit HTTP GET requests (which Tor uses for fetching directory information) to
+port 80.
+.LP
+.TP
 \fBLongLivedPorts \fR\fIPORTS\fP
 A list of ports for services that tend to have long-running connections
 (e.g. chat and interactive shells). Circuits for streams that use these