README 2.2 KB

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