README 1.9 KB

1234567891011121314151617181920212223242526272829303132333435363738394041424344
  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. That 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. Do you want to run a tor server?
  14. First, move sample-server-torrc onto torrc, and edit it. Create the
  15. DataDirectory, and make sure it's owned by whoever will be running
  16. tor. Fix your system clock so it's not too far off. Make sure name
  17. resolution works. Make sure other people can reliably resolve the
  18. Address you chose.
  19. Then run tor to generate keys. One of the files generated
  20. in your DataDirectory is your 'fingerprint' file. Mail it to
  21. arma@mit.edu. Remember that you won't be able to authenticate to the
  22. other tor nodes until I've added you to the directory.
  23. Configuring tsocks:
  24. If you want to use Tor for protocols that can't use Privoxy, or
  25. with applications that are not socksified, then download tsocks
  26. (tsocks.sourceforge.net) and configure it to talk to localhost:9050
  27. as a socks4 server. My /etc/tsocks.conf simply has:
  28. server_port = 9050
  29. server = 127.0.0.1
  30. (I had to "cd /usr/lib; ln -s /lib/libtsocks.so" to get the tsocks
  31. library working after install, since my libpath didn't include /lib.)
  32. Then you can do "tsocks ssh arma@moria.mit.edu". But note that if
  33. ssh is suid root, you either need to do this as root, or cp a local
  34. version of ssh that isn't suid.