diff options
| author | Nick Mathewson <nickm@torproject.org> | 2007-01-26 01:59:50 +0000 |
|---|---|---|
| committer | Nick Mathewson <nickm@torproject.org> | 2007-01-26 01:59:50 +0000 |
| commit | 489f6185bff08278e648d944ec1a9b2d03443d21 (patch) | |
| tree | ded178e269afc641461a820cb3a387feb3a4069e /doc/address-spec.txt | |
| parent | d996db90b38dac225f6cda6dffdc3807a4c3d822 (diff) | |
| download | tor-489f6185bff08278e648d944ec1a9b2d03443d21.tar tor-489f6185bff08278e648d944ec1a9b2d03443d21.tar.gz | |
Move specification documents into new doc/spec subdirectory. (Proposals, drafts, and bad ideas still remain in doc.)
svn:r9411
Diffstat (limited to 'doc/address-spec.txt')
| -rw-r--r-- | doc/address-spec.txt | 64 |
1 files changed, 0 insertions, 64 deletions
diff --git a/doc/address-spec.txt b/doc/address-spec.txt deleted file mode 100644 index 2e83a6813..000000000 --- a/doc/address-spec.txt +++ /dev/null @@ -1,64 +0,0 @@ -$Id$ - - Special Hostnames in Tor - Nick Mathewson - -1. Overview - - Most of the time, Tor treats user-specified hostnames as opaque: When the - user connects to tor.eff.org, Tor picks an exit node and uses that node to - connect to "tor.eff.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 - method (such as SOCKS4, TransPort, or NatdPort), these hostnames can be - substituted for certain IP addresses using the MapAddress configuration - option or the MAPADDRESS control command. - -2. .exit - - SYNTAX: [hostname].[name-or-digest].exit - [name-or-digest].exit - - Hostname is a valid hostname; [name-or-digest] is either the nickname of a - Tor node or the hex-encoded digest of that node's public key. - - When Tor sees an address in this format, it uses the specified hostname as - the exit node. If no "hostname" component is given, Tor defaults to the - published IPv4 address of the exit node. - - It is valid to try to resolve hostnames, and in fact upon success Tor - will cache an internal mapaddress of the form - "www.google.com.foo.exit=64.233.161.99.foo.exit" to speed subsequent - lookups. - - EXAMPLES: - www.example.com.exampletornode.exit - - Connect to www.example.com from the node called "exampletornode." - - exampletornode.exit - - Connect to the published IP address of "exampletornode" using - "exampletornode" as the exit. - -3. .onion - - SYNTAX: [digest].onion - - The digest is the first eighty bits of a SHA1 hash of the identity key for - a hidden service, encoded in base32. - - When Tor sees an address in this format, it tries to look up and connect to - the specified hidden service. See rend-spec.txt for full details. - -4. .noconnect - - SYNTAX: [string].noconnect - - When Tor sees an address in this format, it immediately closes the - connection without attaching it to any circuit. This is useful for - controllers that want to test whether a given application is indeed using - the same instance of Tor that they're controlling. - |