README 1.9 KB

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