README 2.3 KB

12345678910111213141516171819202122232425262728293031323334353637383940414243444546474849505152535455
  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, copy torrc.sample to torrc (by default it's in
  15. /usr/local/etc/tor/), and edit the middle part. Create the
  16. DataDirectory, and make sure it's owned by whoever will be running
  17. tor. Fix your system clock so it's not too far off. Make sure name
  18. resolution works.
  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.
  22. NOTE: You won't be able to use tor as a client or server
  23. in this configuration until you've been added to the directory
  24. and can authenticate to the other nodes.
  25. Do you want to run a hidden service?
  26. Copy torrc.sample to torrc (by default it's in /usr/local/etc/tor/), and
  27. edit the bottom part. Then run Tor. It will create each HiddenServiceDir
  28. you have configured, and it will create a 'hostname' file which
  29. specifies the url (xyz.onion) for that service. You can tell people
  30. the url, and they can connect to it via their Tor proxy.
  31. Configuring tsocks:
  32. If you want to use Tor for protocols that can't use Privoxy, or
  33. with applications that are not socksified, then download tsocks
  34. (tsocks.sourceforge.net) and configure it to talk to localhost:9050
  35. as a socks4 server. My /etc/tsocks.conf simply has:
  36. server_port = 9050
  37. server = 127.0.0.1
  38. (I had to "cd /usr/lib; ln -s /lib/libtsocks.so" to get the tsocks
  39. library working after install, since my libpath didn't include /lib.)
  40. Then you can do "tsocks ssh arma@moria.mit.edu". But note that if
  41. ssh is suid root, you either need to do this as root, or cp a local
  42. version of ssh that isn't suid.