aboutsummaryrefslogtreecommitdiff
path: root/address-spec.txt
diff options
context:
space:
mode:
authorRoger Dingledine <arma@torproject.org>2008-08-03 15:34:28 +0000
committerRoger Dingledine <arma@torproject.org>2008-08-03 15:34:28 +0000
commitb7f5a34928a1189f16ca24655df6fbc264b756c5 (patch)
tree76f036e2261b399fa9df78cd381e1550e4df769b /address-spec.txt
parentae5b189071bd7a9fa06b0fc754ba74153a74780d (diff)
downloadtorspec-b7f5a34928a1189f16ca24655df6fbc264b756c5.tar.gz
torspec-b7f5a34928a1189f16ca24655df6fbc264b756c5.zip
update and integrate proposals 125 (bridges) and 137 (bootstrap status)
svn:r16374
Diffstat (limited to 'address-spec.txt')
-rw-r--r--address-spec.txt9
1 files changed, 5 insertions, 4 deletions
diff --git a/address-spec.txt b/address-spec.txt
index 966f34c..2a84d85 100644
--- a/address-spec.txt
+++ b/address-spec.txt
@@ -5,10 +5,11 @@ $Id$
1. Overview
- Most of the time, Tor treats user-specified hostnames as opaque: When the
- user connects to www.torproject.org, Tor picks an exit node and uses that node to
- connect to "www.torproject.org". Some hostnames, however, can be used to override
- Tor's default behavior and circuit-building rules.
+ Most of the time, Tor treats user-specified hostnames as opaque: When
+ the user connects to www.torproject.org, Tor picks an exit node and uses
+ that node to connect to "www.torproject.org". Some hostnames, however,
+ can be used to override Tor's default behavior and circuit-building
+ rules.
These hostnames can be passed to Tor as the address part of a SOCKS4a or
SOCKS5 request. If the application is connected to Tor using an IP-only