Home Explore Help
Sign In
piros
/
tor
3
0
Fork 0
Files Issues 0 Pull Requests 0 Wiki
Tree: 1ce86f1fca
Branches Tags
tor
/
doc
/
address-spec.txt

address-spec.txt 2.0 KB
History Raw

12345678910111213141516171819202122232425262728293031323334353637383940414243444546474849505152535455565758596061 
  1. $Id$
    2. 

  2. 

  3.                           Special Hostnames in Tor
    4. 

  4.                                Nick Mathewson
    5. 

  5. 

  6. 1. Overview
    7. 

  7. 

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

  9.   user connects to tor.eff.org, Tor picks an exit node and uses that node to
    10. 

  10.   connect to "tor.eff.org".  Some hostnames, however, can be used to override
    11. 

  11.   Tor's default behavior and circuit-building 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 
    32. 

  32. 

  33.   EXAMPLES:
    34. 

  34.      www.example.com.exampletornode.exit
    35. 

  35. 

  36.         Connect to www.example.com from the node called "exampletornode."
    37. 

  37. 

  38.      exampletornode.exit
    39. 

  39. 

  40.         Connect to the published IP address of "exampletornode" using
    41. 

  41.         "exampletornode" as the exit.
    42. 

  42. 

  43. 3. .onion
    44. 

  44. 

  45.   SYNTAX [digest].onion
    46. 

  46. 

  47.   The digest is the first eighty bits of a SHA1 hash of the identity key for
    48. 

  48.   a hidden service, encoded in base32.
    49. 

  49. 

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

  51.   the specified hidden service.  See rend-spec.txt for full details.
    52. 

  52. 

  53. 4. .noconnect
    54. 

  54. 

  55.   SYNTAX: [string].noconnect
    56. 

  56. 

  57.   When Tor sees an address in this format, it immediately closes the
    58. 

  58.   connection without attaching it to any circuit.  This is useful for
    59. 

  59.   controllers that want to test whether a given application is indeed using
    60. 

  60.   the same instance of Tor that they're controlling.
    61. 

  61.