tor/README

'tor' is an implementation of The Onion Routing system, as
described in a bit more detail at http://www.onion-router.net/. You
can read list archives, and subscribe to the mailing list, at
http://archives.seul.org/or/dev/.

Is your question in the FAQ? Should it be?

**************************************************************************
See the INSTALL file for a quickstart. That is all you will probably need.
**************************************************************************

**************************************************************************
You only need to look beyond this point if the quickstart in the INSTALL
doesn't work for you.
**************************************************************************

Do you want to run a tor server?

  We're looking for people with reasonably reliable Internet connections,
  that have at least 768kbit each way. Currently we don't use all of that,
  but we want it available for burst traffic.

  First, copy torrc.sample to torrc (by default it's in
  /usr/local/etc/tor/), and edit the middle part. Create the
  DataDirectory, and make sure it's owned by whoever will be running
  tor. Fix your system clock so it's not too far off. Make sure name
  resolution works.

  Then run tor to generate keys. One of the files generated
  in your DataDirectory is your 'fingerprint' file. Mail it to
  tor-ops@freehaven.net.

  NOTE: You won't be able to use tor as a client or server
  in this configuration until you've been added to the directory
  and can authenticate to the other nodes.

Do you want to run a hidden service?

  Copy torrc.sample to torrc (by default it's in /usr/local/etc/tor/), and
  edit the bottom part. Then run Tor. It will create each HiddenServiceDir
  you have configured, and it will create a 'hostname' file which
  specifies the url (xyz.onion) for that service. You can tell people
  the url, and they can connect to it via their Tor client.

Configuring tsocks:

  If you want to use Tor for protocols that can't use Privoxy, or
  with applications that are not socksified, then download tsocks
  (tsocks.sourceforge.net) and configure it to talk to localhost:9050
  as a socks4 server. My /etc/tsocks.conf simply has:
    server_port = 9050
    server = 127.0.0.1
  (I had to "cd /usr/lib; ln -s /lib/libtsocks.so" to get the tsocks
   library working after install, since my libpath didn't include /lib.)
  Then you can do "tsocks ssh arma@moria.mit.edu". But note that if
  ssh is suid root, you either need to do this as root, or cp a local
  version of ssh that isn't suid.