Home Explore Help
Sign In
sengler
/
tor-parallel-relay-conn
1
0
Fork 0
Files Issues 0 Pull Requests 0 Wiki
Tree: 8c2affe637
Branches Tags
tor-parallel...
/
doc
/
spec
/
address-spec.txt

address-spec.txt 2.0 KB
History Raw

12345678910111213141516171819202122232425262728293031323334353637383940414243444546474849505152535455565758 
  1. 

  2.                           Special Hostnames in Tor
    3. 

  3.                                Nick Mathewson
    4. 

  4. 

  5. 1. Overview
    6. 

  6. 

  7.   Most of the time, Tor treats user-specified hostnames as opaque:  When
    8. 

  8.   the user connects to www.torproject.org, Tor picks an exit node and uses
    9. 

  9.   that node to connect to "www.torproject.org".  Some hostnames, however,
    10. 

  10.   can be used to override Tor's default behavior and circuit-building
    11. 

  11.   rules.
    12. 

  12. 

  13.   These hostnames can be passed to Tor as the address part of a SOCKS4a or
    14. 

  14.   SOCKS5 request.  If the application is connected to Tor using an IP-only
    15. 

  15.   method (such as SOCKS4, TransPort, or NATDPort), these hostnames can be
    16. 

  16.   substituted for certain IP addresses using the MapAddress configuration
    17. 

  17.   option or the MAPADDRESS control command.
    18. 

  18. 

  19. 2. .exit
    20. 

  20. 

  21.   SYNTAX:  [hostname].[name-or-digest].exit
    22. 

  22.            [name-or-digest].exit
    23. 

  23. 

  24.   Hostname is a valid hostname; [name-or-digest] is either the nickname of a
    25. 

  25.   Tor node or the hex-encoded digest of that node's public key.
    26. 

  26. 

  27.   When Tor sees an address in this format, it uses the specified hostname as
    28. 

  28.   the exit node.  If no "hostname" component is given, Tor defaults to the
    29. 

  29.   published IPv4 address of the exit node.
    30. 

  30. 

  31.   It is valid to try to resolve hostnames, and in fact upon success Tor
    32. 

  32.   will cache an internal mapaddress of the form
    33. 

  33.   "www.google.com.foo.exit=64.233.161.99.foo.exit" to speed subsequent
    34. 

  34.   lookups.
    35. 

  35. 

  36.   The .exit notation is disabled by default as of Tor 0.2.2.1-alpha, due
    37. 

  37.   to potential application-level attacks.
    38. 

  38. 

  39.   EXAMPLES:
    40. 

  40.      www.example.com.exampletornode.exit
    41. 

  41. 

  42.         Connect to www.example.com from the node called "exampletornode".
    43. 

  43. 

  44.      exampletornode.exit
    45. 

  45. 

  46.         Connect to the published IP address of "exampletornode" using
    47. 

  47.         "exampletornode" as the exit.
    48. 

  48. 

  49. 3. .onion
    50. 

  50. 

  51.   SYNTAX:  [digest].onion
    52. 

  52. 

  53.   The digest is the first eighty bits of a SHA1 hash of the identity key for
    54. 

  54.   a hidden service, encoded in base32.
    55. 

  55. 

  56.   When Tor sees an address in this format, it tries to look up and connect to
    57. 

  57.   the specified hidden service.  See rend-spec.txt for full details.
    58. 

  58.