README 3.4 KB

12345678910111213141516171819202122232425262728293031323334353637383940414243444546474849505152535455565758596061626364656667686970717273747576777879808182
  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. **************************************************************************
  7. See the INSTALL file for a quickstart. This is all you will probably need.
  8. **************************************************************************
  9. **************************************************************************
  10. You only need to look beyond this point if the quickstart in the INSTALL
  11. doesn't work for you.
  12. **************************************************************************
  13. Dependencies:
  14. For tor itself, you're going to need openssl (0.9.5 or later
  15. -- including the dev stuff and includes). If you're on Linux,
  16. everything will probably work fine. OS X and BSD (but see below under
  17. troubleshooting) may work too. Let us know if you get it working
  18. elsewhere.
  19. If you got the source from cvs:
  20. Run "./autogen.sh", which will run the various auto* programs and then
  21. run ./configure for you. From there, start at step 3 in the quickstart
  22. list above.
  23. If the quickstart doesn't work for you:
  24. If you have problems finding libraries, try
  25. CPPFLAGS="-I/usr/local/include" LDFLAGS="-L/usr/local/lib" \
  26. ./configure
  27. rather than simply ./configure.
  28. Check out the list archives at http://archives.seul.org/or/dev/ and see
  29. if somebody else has reported your problem. If not, please subscribe
  30. and let us know what you did to fix it, or give us the details and
  31. we'll see what we can do.
  32. Do you want to run a tor server?
  33. First, set up a config file for your node (start with sample-orrc and
  34. edit the top portion). Then run the node (as above, but with the new
  35. config file) to generate keys. One of the generated files is your
  36. 'fingerprint' file. Mail it to arma@mit.edu. Remember that you won't
  37. be able to authenticate to the other tor nodes until I've added you
  38. to the directory.
  39. Command-line web browsing:
  40. For more convenient command-line use, I recommend making a ~/.wgetrc
  41. with the line
  42. http_proxy=http://localhost:8118
  43. Then you can do things like "wget seul.org" and watch as it downloads
  44. from the onion routing network.
  45. For fun, you can wget a very large file (a megabyte or more), and
  46. then ^z the wget a little bit in. The onion routers will continue
  47. talking for a while, queueing around 500k in the kernel-level buffers.
  48. When the kernel buffers are full, and the outbuf for the AP connection
  49. also fills, the internal congestion control will kick in and the exit
  50. connection will stop reading from the webserver. The circuit will
  51. wait until you fg the wget -- and other circuits will work just fine
  52. throughout. Then try ^z'ing the onion routers, and watch how well it
  53. recovers. Then try ^z'ing several of them at once. :)
  54. How to use it for ssh:
  55. Download tsocks (tsocks.sourceforge.net) and configure it to talk to
  56. localhost:9050 as a socks4 server. My /etc/tsocks.conf simply has:
  57. server_port = 9050
  58. server = 127.0.0.1
  59. (I had to "cd /usr/lib; ln -s /lib/libtsocks.so" to get the tsocks
  60. library working after install, since my libpath didn't include /lib.)
  61. Then you can do "tsocks ssh arma@moria.mit.edu". But note that since
  62. ssh is suid root, you either need to do this as root, or cp a local
  63. version of ssh that isn't suid.