mirror repository of the tor core protocol in case of issues
Go to file
2003-11-11 03:01:48 +00:00
doc clean up some TODO items; rename ACI to circID 2003-11-11 02:36:50 +00:00
src Rename aci to circ_id throughout. 2003-11-11 03:01:48 +00:00
Win32Build Tor now builds on win32. 2003-08-14 17:51:36 +00:00
.cvsignore Update .cvsignores to exclude files generated due to recent build improvements 2003-10-21 17:49:52 +00:00
AUTHORS patch the README more for new routers 2003-10-27 10:28:26 +00:00
autogen.sh ./autogen.sh runs auto* and then ./configure 2002-06-29 03:01:49 +00:00
ChangeLog added automake/autoconf support. When in doubt, "aclocal && autoconf && autoheader && automake" from the top dir. 2002-06-28 23:26:42 +00:00
configure.in Use daemon(3) function where available. 2003-10-23 14:28:44 +00:00
depcomp added automake/autoconf support. When in doubt, "aclocal && autoconf && autoheader && automake" from the top dir. 2002-06-28 23:26:42 +00:00
INSTALL update install and readme: people should now do 'make install' 2003-10-18 00:44:10 +00:00
install-sh added automake/autoconf support. When in doubt, "aclocal && autoconf && autoheader && automake" from the top dir. 2002-06-28 23:26:42 +00:00
LICENSE fill in some blanks 2003-10-08 02:28:00 +00:00
Makefile.am figured out how to make autoconf a bit less viral 2003-10-24 03:27:53 +00:00
missing added automake/autoconf support. When in doubt, "aclocal && autoconf && autoheader && automake" from the top dir. 2002-06-28 23:26:42 +00:00
mkinstalldirs added automake/autoconf support. When in doubt, "aclocal && autoconf && autoheader && automake" from the top dir. 2002-06-28 23:26:42 +00:00
README client now survives going offline better 2003-11-10 08:06:55 +00:00
tor.sh.in patch from aaron to abstract into $TORARGS 2003-10-16 22:10:48 +00:00

'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?

  First, move sample-server-torrc onto torrc, and edit it. 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. Make sure other people can reliably resolve the
  Address you chose.

  Then run tor to generate keys. One of the files generated
  in your DataDirectory is your 'fingerprint' file. Mail it to
  arma@mit.edu. Remember that you won't be able to authenticate to the
  other tor nodes until I've added you to the directory.

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.