README 4.2 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106
  1. 'tor' is an implementation of The Onion Routing system, as
  2. described in a bit more detail at http://www.onion-router.net/. You
  3. can read list archives, and subscribe to the mailing list, at
  4. http://archives.seul.org/or/dev/.
  5. Is your question in the FAQ? Should it be?
  6. Quickstart version:
  7. 0) Download the absolute newest version. No, really.
  8. http://freehaven.net/or/.
  9. 1) ./configure (or do the two-line version below, if you're on bsd)
  10. 2) make
  11. 3) cd src/config
  12. 4) ../or/or -f oprc -l debug&
  13. 5) download privoxy (www.privoxy.org), and add the line
  14. "forward-socks4a / localhost:9050 ." (without the quotes) to its
  15. config file.
  16. 6) point your mozilla (or whatever) to http proxy at localhost:8118 (this
  17. points it through Privoxy, so you now get good data-scrubbing too.)
  18. 7) make sure you've set it up correctly: go to
  19. http://www.junkbusters.com/cgi-bin/privacy and see what IP it says
  20. you're coming from.
  21. More detailed version:
  22. Dependencies:
  23. You're going to need Privoxy (www.privoxy.org) installed, and configured
  24. to point at a socks4a proxy -- see below.
  25. For tor itself, you're going to need openssl (0.9.5 or later
  26. -- including the dev stuff and includes). If you're on Linux,
  27. everything will probably work fine. OS X and BSD (but see below under
  28. troubleshooting) now work too. Let us know if you get it working
  29. elsewhere.
  30. If you got the source from cvs:
  31. Run "./autogen.sh", which will run the various auto* programs and then
  32. run ./configure for you. From there, you should be able to run 'make'
  33. and you'll be on your way.
  34. If you got the source from a tarball:
  35. Run ./configure and make as usual. There isn't much point in
  36. 'make install' yet.
  37. If this doesn't work for you / troubleshooting:
  38. If you have problems finding libraries, try
  39. CPPFLAGS="-I/usr/local/include" LDFLAGS="-L/usr/local/lib" \
  40. ./configure
  41. rather than simply ./configure.
  42. Check out the list archives at http://archives.seul.org/or/dev/ and see
  43. if somebody else has reported your problem. If not, please subscribe
  44. and let us know what you did to fix it, or give us the details and
  45. we'll see what we can do.
  46. Once you've got it compiled:
  47. If you want to run a local onion proxy (that is, you're a user, not a
  48. node operator), go into src/config and look at the oprc file. You can
  49. run an onion proxy by "../or/or -f oprc". See below for how to use it.
  50. If you want to set up your own test network (that is, act like you're
  51. a full set of node operators), go into src/config/ and look at the
  52. routers.or file. Also in that directory are public and private keys for
  53. various nodes (*-public, *-private) and configuration files for the
  54. nodes (*-orrc). You can generate your own keypairs with the orkeygen
  55. program, or use the provided ones for testing.
  56. Once you've got your config files ready, you're ready to start up your
  57. network. I recommend using a screen session (man screen), or some
  58. other way to handle many windows at once. I open a window for each
  59. onion router, go into the src/config directory, and run something like
  60. "../or/or -f moria2-orrc".
  61. How to use it:
  62. Download privoxy (www.privoxy.org). Install it. Add the following
  63. line to your 'config' file:
  64. forward-socks4a / localhost:9050 .
  65. Don't forget the . at the end.
  66. From here, you can point your browser/etc at localhost:8118 and your
  67. traffic will go through Privoxy, then through the onion proxy, to the
  68. onion routing network.
  69. For more convenient command-line use, I recommend making a ~/.wgetrc
  70. with the line
  71. http_proxy=localhost:8118
  72. Then you can do things like "wget seul.org" and watch as it downloads
  73. from the onion routing network.
  74. For fun, you can wget a very large file (a megabyte or more), and
  75. then ^z the wget a little bit in. The onion routers will continue
  76. talking for a while, queueing around 500k in the kernel-level buffers.
  77. When the kernel buffers are full, and the outbuf for the AP connection
  78. also fills, the internal congestion control will kick in and the exit
  79. connection will stop reading from the webserver. The circuit will
  80. wait until you fg the wget -- and other circuits will work just fine
  81. throughout. Then try ^z'ing the onion routers, and watch how well it
  82. recovers. Then try ^z'ing several of them at once. :)